<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="9788793519459.xsl"?>
<book id="home" xmlns:xlink="http://www.w3.org/1999/xlink">
<bookinfo>
<title>Parkinson&#x2019;s Disease Management through ICT</title>
<subtitle>The REMPARK Approach</subtitle>
<affiliation><emphasis role="strong">Editors</emphasis></affiliation>
<authorgroup>
<author><firstname>Joan</firstname>
<surname>Cabestany</surname></author>
</authorgroup>
<affiliation>Universitat Polit&#x00E8;cnica de Catalunya UPC, Barcelona, Spain</affiliation>
<authorgroup>
<author><firstname>&#x00C0;ngels</firstname>
<surname>Bay&#x00E9;s</surname></author>
</authorgroup>
<affiliation>Centro M&#x00E9;dico Teknon, Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</affiliation>
<publisher>
<publishername>River Publishers</publishername>
</publisher>
<isbn>9788793519459</isbn>
</bookinfo>
<preface class="preface" id="preface01">
<title>RIVER PUBLISHERS SERIES IN BIOMEDICAL ENGINEERING</title>
<para><emphasis>Series Editor</emphasis></para>
<para><emphasis role="strong">Dinesh Kant Kumar</emphasis></para>
<para><emphasis>RMIT</emphasis></para>
<para><emphasis>Australia</emphasis></para>
<para>Indexing: All books published in this series are submitted to Thomson Reuters Book Citation Index (BkCI), CrossRef and to Google Scholar.</para>
<para>The &#x0201C;River Publishers Series in Biomedical Engineering&#x0201D; is a series of comprehensive academic and professional books which focus on the engineering and mathematics in medicine and biology. The series presents innovative experimental science and technological development in the biomedical field as well as clinical application of new developments.</para>
<para>Books published in the series include research monographs, edited volumes, handbooks and textbooks. The books provide professionals, researchers, educators, and advanced students in the field with an invaluable insight into the latest research and developments.</para>
<para>Topics covered in the series include, but are by no means restricted to the following:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Biomedical engineering</para></listitem>
<listitem>
<para>Biomedical physics and applied biophysics</para></listitem>
<listitem>
<para>Bio-informatics</para></listitem>
<listitem>
<para>Bio-metrics</para></listitem>
<listitem>
<para>Bio-signals</para></listitem>
<listitem>
<para>Medical Imaging</para></listitem>
</itemizedlist>
<para>For a list of other books in this series, visit <ulink url="http://www.riverpublishers.com">www.riverpublishers.com</ulink></para>
</preface>
<preface class="preface" id="preface02">
<title>Preface</title>
<para>Parkinson&#x02019;s Disease (PD) is a neurodegenerative disorder that manifests with motor and non-motor symptoms. PD treatment is symptomatic and tries to alleviate the associated symptoms through a correct adjustment of the medication. As the disease evolves with time and this evolution strongly depends on each patient, it could be very difficult to correctly manage the disease.</para>
<para>Currently available ITC technology (electronics, communication, computing...) correctly combined with wearables can be of great utility to obtain and process useful information for both clinicians and patients. In this way, patients can actively involve in their condition and clinicians can obtain complimentary information for helping purposes.</para>
<para>This book presents the work done, main results, and conclusions of the REMPARK project (2011&#x02013;2015) funded by the European Union under contract FP7-ICT-2011-7-287677. REMPARK system was proposed and developed as a real personal health device for the remote and autonomous management of Parkinson&#x02019;s Disease, composed of different levels of interaction with the patient, clinician and carers; and integrating a set of interconnected sub-systems: sensor, auditory cueing, smartphone, and server.</para>
<para>The sensor subsystem, using embedded algorithmics, is able to detect the motor symptoms associated with PD in real-time. This information is sent through the smartphone to the REMPARK server and is used for an efficient management of the disease.?</para>
<para>Implementation of REMPARK will increase the independence and Quality of Life of patients; and improve their disease management, treatment and rehabilitation.</para>
</preface>
<preface class="preface" id="preface03">
<title>List of Contributors</title>
<para><emphasis role="strong">Albert Sama</emphasis> <emphasis>Universitat Polit&#x00E8;cnica de Catalunya &#x02013; UPC, CETpD &#x02013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</emphasis></para> 
<para><emphasis role="strong">Alejandro Rodriguez-Molinero</emphasis> <emphasis>National University of Galway &#x02013; NUIG, Galway, Ireland</emphasis></para> 
<para><emphasis role="strong">Ana Correira de Barros</emphasis> <emphasis>Fraunhofer Portugal AICOS &#x02013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</emphasis></para> 
<para><emphasis role="strong">Angels Bay&#x00E9;s</emphasis><emphasis>CentroM&#x00E9;dicoTeknon &#x02013; GrupoHospitalarioQuir&#x00F3;n,Parkinson Unit, Barcelona, Spain</emphasis></para> 
<para><emphasis role="strong">Anna Prats</emphasis> <emphasis>Centro M&#x00E9;dico Teknon &#x02013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</emphasis></para> 
<para><emphasis role="strong">Berta Mestre</emphasis><emphasis>Centro M&#x00E9;dico Teknon&#x02013;GrupoHospitalarioQuir&#x00F3;n,Parkinson Unit, Barcelona, Spain</emphasis></para> 
<para><emphasis role="strong">Carlos P&#x00E9;rez</emphasis> <emphasis>Universitat Polit&#x00E8;cnica de Catalunya &#x02013; UPC, CETpD &#x02013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</emphasis></para> 
<para><emphasis role="strong">Daniel Rodriguez-Martin</emphasis> <emphasis>Universitat Polit&#x00E8;cnica de Catalunya &#x02013; UPC, CETpD &#x02013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</emphasis></para> 
<para><emphasis role="strong">Hadas Lewy</emphasis> <emphasis>Maccabi Healthcare Services, Tel-Aviv, Israel (actually with Holon Institute of Technology, Holon, Israel)</emphasis></para> 
<para><emphasis role="strong">J. Manuel Moreno</emphasis> <emphasis>Universitat Polit&#x00E8;cnica de Catalunya &#x02013; UPC, CETpD &#x02013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</emphasis></para> 
<para><emphasis role="strong">Joan Cabestany</emphasis> <emphasis>Universitat Polit&#x00E8;cnica de Catalunya &#x02013; UPC, CETpD &#x02013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</emphasis></para> 
<para><emphasis role="strong">Jo&#x00E3;o Cevada</emphasis> <emphasis>Fraunhofer Portugal AICOS &#x02013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</emphasis></para> 
<para><emphasis role="strong">Jordi Rovira</emphasis> <emphasis>Telef&#x00F3;nica I+D, Spain (actually with MySphera, Valencia, Spain)</emphasis></para> 
<para><emphasis role="strong">M. Cruz Crespo</emphasis> <emphasis>Centro M&#x00E9;dico Teknon &#x02013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</emphasis></para> 
<para><emphasis role="strong">Ricardo Gra&#x00E7;a</emphasis> <emphasis>Fraunhofer Portugal AICOS &#x02013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</emphasis></para> 
<para><emphasis role="strong">Roberta Annicchiarico</emphasis> <emphasis>IRCCS Fondazione Santa Lucia (FSL), Rome, Italy</emphasis></para> 
<para><emphasis role="strong">Rui Castro</emphasis> <emphasis>Fraunhofer Portugal AICOS &#x02013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</emphasis></para> 
<para><emphasis role="strong">Sheila Alcaine</emphasis> <emphasis>Centro M&#x00E9;dico Teknon &#x02013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</emphasis></para> 
<para><emphasis role="strong">Timothy J Counihan</emphasis> <emphasis>National University of Galway &#x02013; NUIG, Galway, Ireland</emphasis></para> 
<para><emphasis role="strong">V&#x00E2;nia Guimar&#x00E3;es</emphasis> <emphasis>Fraunhofer Portugal AICOS &#x02013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</emphasis></para> 
</preface>
<preface class="preface" id="preface04">
<title>List of Figures</title>
<table-wrap position="float">
<table cellspacing="5" cellpadding="5" frame="none" rules="none">
<tbody>
<tr><td valign="top" width="15%"><emphasis role="strong"><link linkend="F3-1">Figure <xref linkend="F3-1" remap="3.1"/></link></emphasis></td><td>Hierarchical organization of REMPARK system.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F3-2">Figure <xref linkend="F3-2" remap="3.2"/></link></emphasis></td><td>System architecture overview.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F3-3">Figure <xref linkend="F3-3" remap="3.3"/></link></emphasis></td><td>Simplified representation of the ACS functionalities.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F3-4">Figure <xref linkend="F3-4" remap="3.4"/></link></emphasis></td><td>Smartphone connectivity and information flows.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F3-5">Figure <xref linkend="F3-5" remap="3.5"/></link></emphasis></td><td>Platform functional architecture.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F3-6">Figure <xref linkend="F3-6" remap="3.6"/></link></emphasis></td><td>Server services.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-1">Figure <xref linkend="F4-1" remap="4.1"/></link></emphasis></td><td>Illustration of the number of professional who filled the questionnaire divided according to their country of origin. Years of clinical practice in PD area are also reported in the average, also in this case individually for each country. Vertical bars represent the standard deviation.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-2">Figure <xref linkend="F4-2" remap="4.2"/></link></emphasis></td><td>Indices of clinical relevance for each PD motor symptoms examined referred to the mild (blue columns), moderate (red columns) and advanced (green columns) PD stages. Vertical bars represent standard errors.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-3">Figure <xref linkend="F4-3" remap="4.3"/></link></emphasis></td><td>Subjective judgment expressed by professionals about the utility of REMPARK system for both improvement and monitoring of motor symptoms. Vertical bars represent standard errors.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-4">Figure <xref linkend="F4-4" remap="4.4"/></link></emphasis></td><td>Design of the experimental visit.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-5">Figure <xref linkend="F4-5" remap="4.5"/></link></emphasis></td><td>Waist sensor.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-6">Figure <xref linkend="F4-6" remap="4.6"/></link></emphasis></td><td>Wrist sensor.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-7">Figure <xref linkend="F4-7" remap="4.7"/></link></emphasis></td><td>Data structure collected from each patient.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-8">Figure <xref linkend="F4-8" remap="4.8"/></link></emphasis></td><td>Outline of the structure defined for the algorithms for detecting symptoms of PD.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-9">Figure <xref linkend="F4-9" remap="4.9"/></link></emphasis></td><td>Scheme of the bradykinesia detection algorithm.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F4-10">Figure <xref linkend="F4-10" remap="4.10"/></link></emphasis></td><td>(a) The inertial system prototype (9 &#x000D7; 2, Version 6) positioned in a neoprene belt on left lateral side of waist. Acceleration signals obtained from (a) Lumbosecaral point of waist and (b) left lateral side of waist.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-1">Figure <xref linkend="F5-1" remap="5.1"/></link></emphasis></td><td>Data flow for the algorithms implementation.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-2">Figure <xref linkend="F5-2" remap="5.2"/></link></emphasis></td><td>Internal organisation of the sensor unit.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-3">Figure <xref linkend="F5-3" remap="5.3"/></link></emphasis></td><td>Timing for the online algorithms implementation.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-4">Figure <xref linkend="F5-4" remap="5.4"/></link></emphasis></td><td>Power Management block diagram.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-5">Figure <xref linkend="F5-5" remap="5.5"/></link></emphasis></td><td>Sensor unit casing.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-6">Figure <xref linkend="F5-6" remap="5.6"/></link></emphasis></td><td>External components of the sensor unit.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-7">Figure <xref linkend="F5-7" remap="5.7"/></link></emphasis></td><td>Status of the sensor unit.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F5-8">Figure <xref linkend="F5-8" remap="5.8"/></link></emphasis></td><td>Special belt and REMPARK final sensor.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-1">Figure <xref linkend="F6-1" remap="6.1"/></link></emphasis></td><td>Sequence of interaction of different experiments. a) Participants had to touch the target, which appeared in different sizes, at different positions and surrounded by distractions of different sizes; b) Participants had to slide a rug which appeared in different heights with different spaces to the distractions; c) Participants had to control the water level, by filling the pipette by touching the arrow up until the water reached the green mark; d) Participants had to use the seek bar with a ball as a selector to drag the ball to the boy; scale and mark&#x02019;s position changed with test progression.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-2">Figure <xref linkend="F6-2" remap="6.2"/></link></emphasis></td><td>Some examples of UI patterns and gestures.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-3">Figure <xref linkend="F6-3" remap="6.3"/></link></emphasis></td><td>Sequence for text input.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-4">Figure <xref linkend="F6-4" remap="6.4"/></link></emphasis></td><td>Screenshots of the home screens: Applications screen (to the left) and Favourites screen (to the right).</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-5">Figure <xref linkend="F6-5" remap="6.5"/></link></emphasis></td><td>Screen flow for the &#x02018;My Data&#x02019; application.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-6">Figure <xref linkend="F6-6" remap="6.6"/></link></emphasis></td><td>Screenshot of the &#x02018;My Day&#x02019; app.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-7">Figure <xref linkend="F6-7" remap="6.7"/></link></emphasis></td><td>a) Initial screen; b) Number indicating the tap counting; c) Custom display of a tap event.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-8">Figure <xref linkend="F6-8" remap="6.8"/></link></emphasis></td><td>Arrow buttons as an alternative to the scroll gesture.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-9">Figure <xref linkend="F6-9" remap="6.9"/></link></emphasis></td><td>Calendar screens: a) Calendar; b) Week list.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-10">Figure <xref linkend="F6-10" remap="6.10"/></link></emphasis></td><td>New/Edit appointment screen.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-11">Figure <xref linkend="F6-11" remap="6.11"/></link></emphasis></td><td>Medication apps screens: a) medication list; b) medication details; c) edit intake.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F6-12">Figure <xref linkend="F6-12" remap="6.12"/></link></emphasis></td><td>Notification pop-up screen (medication reminder).</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-1">Figure <xref linkend="F7-1" remap="7.1"/></link></emphasis></td><td>Examples of visual cueing strategies.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-2">Figure <xref linkend="F7-2" remap="7.2"/></link></emphasis></td><td>REMPARK Auditory Cueing System.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-3">Figure <xref linkend="F7-3" remap="7.3"/></link></emphasis></td><td>Cueing rhythm (beats per minute BPM) and cadence (steps per minute SPM).</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-4">Figure <xref linkend="F7-4" remap="7.4"/></link></emphasis></td><td>Pop-Up window for basic control of ACS when it starts automatically.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-5">Figure <xref linkend="F7-5" remap="7.5"/></link></emphasis></td><td>Auditory Cueing System application.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-6">Figure <xref linkend="F7-6" remap="7.6"/></link></emphasis></td><td>Preliminary tests with PD patients for the ACS.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-7">Figure <xref linkend="F7-7" remap="7.7"/></link></emphasis></td><td>Infusion pump to be adapted for a possible use with REMPARK system.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-8">Figure <xref linkend="F7-8" remap="7.8"/></link></emphasis></td><td>Modified pump.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-9">Figure <xref linkend="F7-9" remap="7.9"/></link></emphasis></td><td>PCB general scheme.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-10">Figure <xref linkend="F7-10" remap="7.10"/></link></emphasis></td><td>System operation overview.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F7-11">Figure <xref linkend="F7-11" remap="7.11"/></link></emphasis></td><td>Connection diagram between the pump and the designed PCB.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-1">Figure <xref linkend="F8-1" remap="8.1"/></link></emphasis></td><td>View of data on a patient from a list. (All appearing data are not real).</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-2">Figure <xref linkend="F8-2" remap="8.2"/></link></emphasis></td><td>Protocol screen capture for apomorphine pump alert.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-3">Figure <xref linkend="F8-3" remap="8.3"/></link></emphasis></td><td>Questionnaire&#x02019;s section detail.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-4">Figure <xref linkend="F8-4" remap="8.4"/></link></emphasis></td><td>Treatment Plan. A patient&#x02019;s interface view.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-5">Figure <xref linkend="F8-5" remap="8.5"/></link></emphasis></td><td>The server acting as a communication hub interfacing the DMA System.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F8-6">Figure <xref linkend="F8-6" remap="8.6"/></link></emphasis></td><td>The Web interface architecture.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-1">Figure <xref linkend="F9-1" remap="9.1"/></link></emphasis></td><td>Communication flow of motor symptoms detection and actuation in REMPARK system.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-2">Figure <xref linkend="F9-2" remap="9.2"/></link></emphasis></td><td>Communication flow of non-motor symptoms management and actuation in REMPARK system.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-3">Figure <xref linkend="F9-3" remap="9.3"/></link></emphasis></td><td>Final REMPARK platform (ready for pilots) functional view.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-4">Figure <xref linkend="F9-4" remap="9.4"/></link></emphasis></td><td>REMPARK server in isolated network.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-5">Figure <xref linkend="F9-5" remap="9.5"/></link></emphasis></td><td>Final REMPARK system deployment and used for the pilots.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-6">Figure <xref linkend="F9-6" remap="9.6"/></link></emphasis></td><td>Timing of the methodological study design.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-7">Figure <xref linkend="F9-7" remap="9.7"/></link></emphasis></td><td>Motor states section of the diary filled by one patient during the first day of experimentation. Third row corresponds to the &#x02018;intermediate state&#x02019;.</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="F9-8">Figure <xref linkend="F9-8" remap="9.8"/></link></emphasis></td><td>System Usability Scale.</td></tr>
</tbody>
</table>
</table-wrap>
</preface>
<preface class="preface" id="preface05">
<title>List of Tables</title>
<table-wrap position="float">
<table cellspacing="5" cellpadding="5" frame="none" rules="none">
<tbody>
<tr><td valign="top"><emphasis role="strong"><link linkend="T1-1">Table <xref linkend="T1-1" remap="1.1"/></link></emphasis></td><td>Modified Hoehn and Yahr scale</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T2-1">Table <xref linkend="T2-1" remap="2.1"/></link></emphasis></td><td>Common motor and non-motor fluctuations in PD</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-1">Table <xref linkend="T3-1" remap="3.1"/></link></emphasis></td><td>Technical specifications derived from the user feedback</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-2">Table <xref linkend="T3-2" remap="3.2"/></link></emphasis></td><td>Some important technical requirements for the sensor module</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-3">Table <xref linkend="T3-3" remap="3.3"/></link></emphasis></td><td>Parameters/Measures considered by the ACS</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-4">Table <xref linkend="T3-4" remap="3.4"/></link></emphasis></td><td>General functional requirements of the ACS system</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-5">Table <xref linkend="T3-5" remap="3.5"/></link></emphasis></td><td>Requirements of the smartphone end-user applications</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-6">Table <xref linkend="T3-6" remap="3.6"/></link></emphasis></td><td>Technical requirements for the REMPARK server</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T3-7">Table <xref linkend="T3-7" remap="3.7"/></link></emphasis></td><td>Compiled requirements for the DMS</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-1">Table <xref linkend="T4-1" remap="4.1"/></link></emphasis></td><td>Sociodemographic data</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-2">Table <xref linkend="T4-2" remap="4.2"/></link></emphasis></td><td>Recorded time of the different motor periods</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-3">Table <xref linkend="T4-3" remap="4.3"/></link></emphasis></td><td>Video recording duration per symptom in the database</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-4">Table <xref linkend="T4-4" remap="4.4"/></link></emphasis></td><td>Summary of motor symptoms per motor phase</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-5">Table <xref linkend="T4-5" remap="4.5"/></link></emphasis></td><td>Dyskinesia algorithm results</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-6">Table <xref linkend="T4-6" remap="4.6"/></link></emphasis></td><td>Bradykinesia algorithm results</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-7">Table <xref linkend="T4-7" remap="4.7"/></link></emphasis></td><td>Tremor algorithm results</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T4-8">Table <xref linkend="T4-8" remap="4.8"/></link></emphasis></td><td>Freezing of Gait algorithm results</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T5-1">Table <xref linkend="T5-1" remap="5.1"/></link></emphasis></td><td>Estimated memory usage</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T5-2">Table <xref linkend="T5-2" remap="5.2"/></link></emphasis></td><td>Estimated processing time</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T6-1">Table <xref linkend="T6-1" remap="6.1"/></link></emphasis></td><td>Technology watch on mobile applications for PD management</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T6-2">Table <xref linkend="T6-2" remap="6.2"/></link></emphasis></td><td>Some important interview results</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T6-3">Table <xref linkend="T6-3" remap="6.3"/></link></emphasis></td><td>User interface design guidelines</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T6-4">Table <xref linkend="T6-4" remap="6.4"/></link></emphasis></td><td>Mean duration of a single tap for each participant</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T7-1">Table <xref linkend="T7-1" remap="7.1"/></link></emphasis></td><td>Technology watch on actuators for auditory cueing in Parkinson&#x02019;s Disease</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-1">Table <xref linkend="T9-1" remap="9.1"/></link></emphasis></td><td>Pre-pilot results on motor state detection</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-2">Table <xref linkend="T9-2" remap="9.2"/></link></emphasis></td><td>Recruitment and follow-up data by participant entity</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-3">Table <xref linkend="T9-3" remap="9.3"/></link></emphasis></td><td>Mental and chronic disease condition of the participants</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-4">Table <xref linkend="T9-4" remap="9.4"/></link></emphasis></td><td>Example of data stored in the REMPARK server</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-5">Table <xref linkend="T9-5" remap="9.5"/></link></emphasis></td><td>Performance analysis of the REMPARK system (some examples)</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-6">Table <xref linkend="T9-6" remap="9.6"/></link></emphasis></td><td>Average results according to the Original diary method and time-ensured method (Strict)</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-7">Table <xref linkend="T9-7" remap="9.7"/></link></emphasis></td><td>Non-motor symptoms selected answers sorted by frequency</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-8">Table <xref linkend="T9-8" remap="9.8"/></link></emphasis></td><td>Results of the cueing systems for participants with severe gait problems</td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="T9-9">Table <xref linkend="T9-9" remap="9.9"/></link></emphasis></td><td>Results for the QUEST questionnaire</td></tr>
</tbody>
</table>
</table-wrap>
</preface>
<preface class="preface" id="preface06">
<title>List of Abbreviations</title>
<table-wrap position="float">
<table cellspacing="5" cellpadding="5" frame="none" rules="none">
<tbody>
<tr><td valign="top">&#x003BC;C</td><td valign="top">Microcontroller</td></tr>
<tr><td valign="top">&#x003BC;SD</td><td valign="top">Micro Secure Digital</td></tr>
<tr><td valign="top">A2DP</td><td valign="top">Advanced Audio Distribution Profile</td></tr>
<tr><td valign="top">AAL</td><td valign="top">Ambient Assisted Living</td></tr>
<tr><td valign="top">ACS</td><td valign="top">Auditory Cueing System</td></tr>
<tr><td valign="top">ADL</td><td valign="top">Activity of Daily Living</td></tr>
<tr><td valign="top">AI</td><td valign="top">Artificial Intelligence</td></tr>
<tr><td valign="top">AIMS</td><td valign="top">Abnormal Involuntary Movement Scale</td></tr>
<tr><td valign="top">BADL</td><td valign="top">Basic Activities of Daily Living (e.g. bathing, toileting, feeding, transferring, dressing)</td></tr>
<tr><td valign="top">BAN</td><td valign="top">Body Area Network</td></tr>
<tr><td valign="top">BPM</td><td valign="top">Beats per minute</td></tr>
<tr><td valign="top">CDS</td><td valign="top">continuous dopaminergic stimulation</td></tr>
<tr><td valign="top">CP</td><td valign="top">Clinical Protocol</td></tr>
<tr><td valign="top">CPU</td><td valign="top">Central Processing Unit</td></tr>
<tr><td valign="top">CRF</td><td valign="top">Case Report Form</td></tr>
<tr><td valign="top">DAO</td><td valign="top">Data Access Object</td></tr>
<tr><td valign="top">DBS</td><td valign="top">deep brain stimulation</td></tr>
<tr><td valign="top">DG</td><td valign="top">Design Guideline</td></tr>
<tr><td valign="top">DMA</td><td valign="top">Direct Memory Access</td></tr>
<tr><td valign="top">DMA</td><td valign="top">Disease Management Application</td></tr>
<tr><td valign="top">DMS</td><td valign="top">Disease Management System</td></tr>
<tr><td valign="top">DSM</td><td valign="top">Diagnostic and Statistical Manual</td></tr>
<tr><td valign="top">DSP</td><td valign="top">Digital Signal Processor</td></tr>
<tr><td valign="top">EC</td><td valign="top">Ethical Committee</td></tr>
<tr><td valign="top">EHR</td><td valign="top">Electronic Health Record</td></tr>
<tr><td valign="top">FES</td><td valign="top">Functional Electrical Stimulation</td></tr>
<tr><td valign="top">FFT</td><td valign="top">Fast Fourier Transform</td></tr>
<tr><td valign="top">FOG</td><td valign="top">Freezing Of Gait</td></tr>
<tr><td valign="top">FP7</td><td valign="top">Framework Programme 7</td></tr>
<tr><td valign="top">GP</td><td valign="top">General Practitioners</td></tr>
<tr><td valign="top">GUI</td><td valign="top">Graphical User Interface</td></tr>
<tr><td valign="top">H&#x00026;Y</td><td valign="top">Hoehn and Yahr</td></tr>
<tr><td valign="top">HCI</td><td valign="top">Human-Computer Interaction</td></tr>
<tr><td valign="top">HER</td><td valign="top">Electronic Health Record</td></tr>
<tr><td valign="top">HTTPS</td><td valign="top">HyperText Transfer Protocol over SSL</td></tr>
<tr><td valign="top">I/O</td><td valign="top">Input/Output</td></tr>
<tr><td valign="top">IADL</td><td valign="top">Instrumental Activity of Daily Living</td></tr>
<tr><td valign="top">IC</td><td valign="top">form Informed Consent Form</td></tr>
<tr><td valign="top">ICT</td><td valign="top">Information and Communication Technologies</td></tr>
<tr><td valign="top">IMU</td><td valign="top">Inertial Measurement Unit</td></tr>
<tr><td valign="top">IQR</td><td valign="top">Interquartile Range</td></tr>
<tr><td valign="top">JSON</td><td valign="top">JavaScript Object Notation</td></tr>
<tr><td valign="top">LED</td><td valign="top">Light Emitting Diode</td></tr>
<tr><td valign="top">LSVT</td><td valign="top">Lee Silver voice treatment</td></tr>
<tr><td valign="top">MA</td><td valign="top">Medical Application</td></tr>
<tr><td valign="top">MC</td><td valign="top">Motor complication</td></tr>
<tr><td valign="top">MDT</td><td valign="top">Multidisciplinary treatment</td></tr>
<tr><td valign="top">MG</td><td valign="top">Mobile Gateway</td></tr>
<tr><td valign="top">MIPS</td><td valign="top">Mega-instructions per second</td></tr>
<tr><td valign="top">MMSE</td><td valign="top">Mini Mental State Examination</td></tr>
<tr><td valign="top">MS</td><td valign="top">Milli Seconds</td></tr>
<tr><td valign="top">URL</td><td valign="top">Uniform Resource Locator</td></tr>
<tr><td valign="top">MS</td><td valign="top">Motor Symptom</td></tr>
<tr><td valign="top">MVC</td><td valign="top">Model-View-Controller</td></tr>
<tr><td valign="top">SQL</td><td valign="top">Standardized Query Language</td></tr>
<tr><td valign="top">MWI</td><td valign="top">Medical Web Interface</td></tr>
<tr><td valign="top">NE</td><td valign="top">Non evaluated (state)</td></tr>
<tr><td valign="top">NMC</td><td valign="top">Non-motor complication</td></tr>
<tr><td valign="top">NMS</td><td valign="top">Non-motor Symptom</td></tr>
<tr><td valign="top">NMSQ</td><td valign="top">Non Motor Symptoms Questionnaire</td></tr>
<tr><td valign="top">OECD</td><td valign="top">Organisation for Economic Co-operation and Development</td></tr>
<tr><td valign="top">PD</td><td valign="top">Parkinson&#x02019;s Disease</td></tr>
<tr><td valign="top">PHS</td><td valign="top">Personal Health System</td></tr>
<tr><td valign="top">PHS</td><td valign="top">Personalized Health System</td></tr>
<tr><td valign="top">PT</td><td valign="top">Physical Therapy</td></tr>
<tr><td valign="top">PwP</td><td valign="top">People with PD</td></tr>
<tr><td valign="top">QoL</td><td valign="top">Quality of Life</td></tr>
<tr><td valign="top">QoLRH</td><td valign="top">quality of life related to health</td></tr>
<tr><td valign="top">QUEST</td><td valign="top">Quebec User Evaluation of Satisfaction with assistive Technology</td></tr>
<tr><td valign="top">RBD</td><td valign="top">REM sleep behaviour disorder</td></tr>
<tr><td valign="top">RBF</td><td valign="top">Radial Basis Function</td></tr>
<tr><td valign="top">RCS</td><td valign="top">REMPARK Central Server</td></tr>
<tr><td valign="top">RE</td><td valign="top">Rule Engine</td></tr>
<tr><td valign="top">REM</td><td valign="top">rapid eye movement</td></tr>
<tr><td valign="top">RFCOMM</td><td valign="top">Radio Frequency Communication</td></tr>
<tr><td valign="top">SP</td><td valign="top">Subcutaneous Pump</td></tr>
<tr><td valign="top">SPM</td><td valign="top">Steps per minute</td></tr>
<tr><td valign="top">SUS</td><td valign="top">System Usability Scale</td></tr>
<tr><td valign="top">TSN</td><td valign="top">Transaction Sequence Number</td></tr>
<tr><td valign="top">UI</td><td valign="top">User Interface</td></tr>
<tr><td valign="top">UPDRS</td><td valign="top">Unified Parkinson&#x02019;s Disease Rating Scale</td></tr>
<tr><td valign="top">UX</td><td valign="top">User eXperience</td></tr>
</tbody>
</table>
</table-wrap>
</preface>
<preface class="preface" id="preface07">
<title>Contents</title>
<table-wrap position="float">
<table cellspacing="5" cellpadding="5" frame="none" rules="none">
<tbody>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch01">1 Parkinson&#x02019;s Disease Management: Trends and Challenges</link></emphasis><?lb?>Angels Bay&#x00E9;s and Timothy J Counihan</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/01_Chapter_01.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch02">2 Objective Measurement of Symptoms in PD</link></emphasis><?lb?>Timothy J Counihan and Angels Bay&#x00E9;s</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/02_Chapter_02.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch03">3 The REMPARK System</link></emphasis><?lb?>Joan Cabestany, J. Manuel Moreno and Rui Castro</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/03_Chapter_03.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch04">4 Assessment of Motor Symptoms</link></emphasis><?lb?>Albert Sama, Carlos P&#x00E9;rez, Daniel Rodriguez-Martin, Alejandro Rodriguez-Molinero, Sheila Alcaine, Berta Mestre, Anna Prats and M. Cruz Crespo</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/04_Chapter_04.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch05">5 Sensor Sub-System</link></emphasis><?lb?>Carlos P&#x00E9;rez and Daniel Rodriguez-Martin</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/05_Chapter_05.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch06">6 User Interaction</link></emphasis><?lb?>Ana Correira de Barros, Jo&#x00E3;o Cevada and Ricardo Gra&#x00E7;a</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/06_Chapter_06.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch07">7 Actuator Sub-System: The Auditory Cueing</link></emphasis><?lb?>V&#x00E2;nia Guimar&#x00E3;es, Rui Castro, Angels Bay&#x00E9;s, Carlos P&#x00E9;rez and Daniel Rodriguez-Martin</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/07_Chapter_07.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch08">8 Disease Management System (DMS)</link></emphasis><?lb?>Hadas Lewy</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/08_Chapter_08.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch09">9 REMPARK System Assessment: Main Results</link></emphasis><?lb?>Albert Sama, J. Manuel Moreno, Carlos P&#x00E9;rez, Joan Cabestany, Angels Bay&#x00E9;s and Jordi Rovira</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/09_Chapter_09.pdf">Download As PDF</ulink></td></tr>
<tr><td valign="top"><emphasis role="strong"><link linkend="ch10">10 Epilogue and Some Conclusions</link></emphasis><?lb?>Roberta Annicchiarico, Angels Bay&#x00E9;s and Joan Cabestany</td><td valign="top" align="left" width="20%"><ulink url="http://riverpublishers.com/dissertations_xml/9788793519459/pdf/10_Chapter_10.pdf">Download As PDF</ulink></td></tr>
</tbody>
</table>
</table-wrap>
</preface>
<chapter class="chapter" id="ch01" label="1" xreflabel="1">
<title>Parkinson&#x02019;s Disease Management: Trends and Challenges</title>
<para role="author"><emphasis role="strong">Angels Bay&#x00E9;s<superscript><emphasis role="strong">1</emphasis></superscript> and Timothy J Counihan<superscript><emphasis role="strong">2</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<para><superscript>2</superscript>National University of Galway &#x2013; NUIG, Galway, Ireland</para>
<section class="lev1" id="sec1-1" label="1.1" xreflabel="1.1">
<title>Introduction</title>
<para>Parkinson&#x02019;s Disease (PD) is a common neurodegenerative disorder that mani- fests with motor symptoms (MS) and non-motor symptoms (NMS). These symptoms vary from one patient to another and throughout the course of the disease, affecting patients&#x02019; quality of life (QoL) progressively. Advanced PD represents a public health problem, given that it leads to the reduction in the capacity for self-care and deterioration of the QoL of those affected and their caregivers. The economic cost, including lost productivity and informal care, is about 20 billion euros in the world today.</para>
<para>Parkinson&#x02019;s Disease treatment is symptomatic and aims to alleviate the symptoms associated with the disease, through the precise adjustment of medication. The most widely used drug, levodopa, is effective usually across the lifespan. However, the onset of motor complications (MCs) a few years after starting treatment (e.g., ON&#x02013;OFF fluctuations and dyskinesias) detract from its value. Symptomatic control of these complications is difficult and must be often optimized because the obtained improvement after such adjustment is not stable over the long term.</para>
<para>Treatment is primarily addressed to reduce the time that the patient is in the OFF state (i.e., time without medication effects), while avoiding the appearance of MCs and NMS, such as hallucinations or impulse control disorder. Reducing OFF hours is, therefore, one of the main parameters used to evaluate the effectiveness of therapeutic interventions, both in medical practice and in clinical trials. Gathering accurate information about the patient&#x02019;s condition throughout the day is essential in order to determine the optimal treatment plan. In clinical practice, the only method available is based on diaries filled in by patients and their caregivers about the ON/OFF hours and dyskinesias. However, this method has certain limitations that make unreliable medium and long-term monitoring: motor difficulties, memory failures that hinder regular compliance and subjective evaluation. Therefore, solutions that can improve disease management are of great interest and occupy important part of current research.</para>
<para>Another important aspect of the symptomatic treatment of PD is the multidisciplinary treatment (MDT). The multiple impairments occurring in PD have diverse functional and psychosocial consequences. While the primary treatment is pharmacological, many symptoms do not respond to medication, such as on-period freezing and postural instability. Indeed, later stage disease may be dominated by such symptoms. In addition, there is growing evidence for the efficacy of rehabilitation therapies for specific symptoms, through the involvement of the multidisciplinary team. There is also emerging evidence for physiotherapy with external cueing for improving gait and balance; cognitive movement strategies; and strength and balance exercises. Intensive speech therapy [e.g., Lee Silverman Voice Treatment (LSVT)] has been shown to improve the loudness and intelligibility of speech in PD. Unfortunately, the MDT is only applied in a small number of PD patients for economical and logistic reasons.</para>
</section>
<section class="lev1" id="sec1-2" label="1.2" xreflabel="1.2">
<title>Impact and Strategies of PD at Different Stages</title>
<para>Parkinson&#x02019;s Disease is one of the chronic disorders with the most impact on patients&#x02019; lifestyle. Most patients survive many years after the first symptoms. The mean survival rate of patients with this disease (when diagnosed after age 50) is 26 years, not very different from the non-affected population.</para>
<para>This disease responds very well to treatment with levodopa and dopaminergic agonists during the first years (between 3 and 7 years). As the disease progresses, the patient encounters a limitation of the effect of medical treatment due to the appearance of motor and non-motor complications. These entail a progressive difficulty in carrying out activities of daily living and leading an independent life. During the first year, the doctor establishes the possible diagnosis and starts one treatment. In course of 2&#x02013;4 years, there is a relative normality and the medication is generally effective. Between the years 5 and 9, the effectiveness of medication usually decreases and treatment may need to be modified. Problems with driving, finances, and work may appear at this time. During years 10&#x02013;13, there is an increasing disability: 60&#x02013;75% of patients present some intellectual deficit, worsening immobility, incontinence, and increased risk of falling.</para>
<para>We can distinguish five evolutionary stages of the disease, although patients may not go through all of them. These are the stages of Hoehn and Yahr (<link linkend="T1-1">Table <xref linkend="T1-1" remap="1.1"/></link>).</para>
<table-wrap position="float" id="T1-1">
<label><link linkend="T1-1">Table <xref linkend="T1-1" remap="1.1"/></link></label>
<caption><para>Modified Hoehn and Yahr scale</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Scale</td>
<td valign="top" align="left">Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">1.0</td>
<td valign="top" align="left">Unilateral involvement only</td>
</tr>
<tr>
<td valign="top" align="left">1.5</td>
<td valign="top" align="left">Unilateral and axial involvement</td></tr>
<tr>
<td valign="top" align="left">2.0</td>
<td valign="top" align="left">Bilateral involvement without impairment of balance</td>
</tr>
<tr>
<td valign="top" align="left">2.5</td>
<td valign="top" align="left">Mild bilateral disease with recovery on pull test</td>
</tr>
<tr>
<td valign="top" align="left">3.0</td>
<td valign="top" align="left">Mild to moderate bilateral disease; some postural instability; physically independent</td>
</tr>
<tr>
<td valign="top" align="left">4.0</td>
<td valign="top" align="left">Severe disability; still able to walk or stand unassisted</td>
</tr>
<tr>
<td valign="top" align="left">5.0</td>
<td valign="top" align="left">Wheelchair bound or bed ridden unless aided</td></tr>
</tbody>
</table>
</table-wrap>
<para>The main problems presented by patients in the different evolutionary phases and the strategies currently recommended are explained in the following subsections.</para>
<section class="lev2" id="sec1-2-1" label="1.2.1" xreflabel="1.2.1">
<title>Patients in Early Stages</title>
<para>In stage 1 of PD, facial expression is generally normal and also the posture. Tremor of a limb is the most common initial manifestation. It is often quite annoying, and it is the symptom that draws the attention of both the doctor and the patient. Tremor rarely interferes with the activities of daily living (ADL), although it disturbs and distresses the patient. Patients sometimes report difficulties in performing activities such as buttoning, typing, or cutting food. In the careful exploration of these patients, other parkinsonian signs in a limb, such as bradykinesia or slow movement, and stiffness, which contribute to these fine motor difficulties, are detected in addition to tremor. Decreased arm swing or dragging of a leg when walking can also be observed. These symptoms, often present for several years, are better tolerated than tremor.</para>
<para>In Stage 2 of PD, the involvement is bilateral. There may be loss of facial expression with decreased blinking. Slight flexion of the body may be present and, in general, arm swing when walking is diminished, without altering balance. Patients slow down when performing ADLs, and they require more time to dress, clean themselves up, get up from a chair, or tie their shoes on their own.</para>
<para>Depressive symptoms are also frequent, and these are detected in between 30&#x02013;50% of the cases. Medical treatment, which is administered according to the severity of the symptoms, often produces side effects.</para>
<para>In these initial stages, patients are advised to learn about the disease, learn to speak naturally about their problems, learn to share difficulties, and go to the doctor accompanied by someone. Standardized psychoeducational programs, such as the &#x0201C;Edupark&#x0201D; program [1], are of great help during this transition. From the diagnosis, it is recommended to initiate MDT, which includes physical exercise and cognitive stimulation. It is better for patients to continue doing things by themselves, even if it is slowly, without rushing and with enough time. It is advisable to adapt the setting in which patients have to perform their ADLs and to be physically and mentally as active as possible.</para>
<para>Family members should also be informed and should know how to convey their support. It is recommended to see a doctor if depressive symptoms or side effects occur with medications.</para>
</section>
<section class="lev2" id="sec1-2-2" label="1.2.2" xreflabel="1.2.2">
<title>Moderately Affected Patients</title>
<para>People with PD in stages 3 and 4 already have a degree of moderate&#x02013;severe disability, as they experience difficulty walking and with balance. They explain that their gait is shortened, and that sometimes they have difficulties to make turns while they walk, in the corners of the rooms, or to cross doorways. Balance problems can cause falls. Sometimes while walking, they develop freezing of gait (FOG), or difficulty to stand, either forward, propulsion, or backward, retropulsion. The feeling of fatigue is a very frequent symptom. They have the feeling of needing a lot more effort to perform certain tasks, and often notice pains in the cervical, lumbar, or shoulder region. Symptoms of autonomic dysfunction may also be present in the form of orthostatic hypotension, extreme sensations of heat or cold, sweating not related to physical activity, sometimes in the form of crisis, and urinary or sexual dysfunction.</para>
<para>Many patients, at stage 3 or 4, experience side effects to chronic dopaminergic medication. The most annoying side effect for patients is the ON&#x02013;OFF phenomenon. This phenomenon is often disabling and causes fear and insecurity. During the ON phase, patients can enjoy good mobility and carry out activities outside the home, such as shopping or social activities. However, during the OFF phase the patient may be completely disabled, with difficulty walking, getting up from a chair, or manipulating objects with hands. The appearance of OFF phases limits the social activities of the patient, often preventing them from going out. In this state, patients may find themselves in really dangerous situations, such as if this phenomenon occurs when crossing a street.</para>
<para>Dyskinesia, or involuntary movements, are another important problem that many patients present with during stages 3 and 4. In general, they have a choreiform nature: creeping movements of the extremities, or masticatory movements of the lower jaw, protrusion of the tongue, oscillations as they walk, and head and neck movements. Dyskinesias are a secondary symptom of dopaminergic medication, which usually occurs during the levodopa peak dose. If they are mild, the family is more aware of these movements than the patients themselves, who usually associate it with free time of parkinsonian symptoms. When they are severe, they can become incapacitating as much as the symptoms themselves.</para>
<para>Non-motor symptoms may appear in the form of sleep disturbances, vivid dreams, and nocturnal vocalizations. Night-time vocalizations, reported by the bed partner, consist of loud cries during sleep often accompanied by agitation of arms and legs. It is called &#x0201C;Rapid eye movement (REM) behaviour disorder&#x0201D;. These events can disrupt sleep. Other frequent behavioural disorders in these stages are visual hallucinations, delusional ideas and confusional states of the paranoid type. Visual hallucinations in general are not very threatening in PD. They often describe the vision of family members, animals, or shadows that become animated objects.</para>
<para>The strategies recommended in these phases are aimed at understanding the MC&#x02019;s and NMC&#x02019;s and know how to monitor them. This will allow the patient to adjust the activities in each period. In case of ON-OFF fluctuations, dyskinesias, clinical worsening or behavioural disorders appear, the patient may inform the neurologist who will consider the possibility of a drug adjustment. It is, therefore, important to learn to do the patient&#x02019;s diary. This information will be crucial to optimize pharmacological treatment.</para>
<para>Patients, in these phases, should continue to maintain an active life and perform MDT, such as physical exercise, occupational therapy, speech therapy, and cognitive stimulation, according to individual needs. It is also recommended to the patient to continue doing things by himself, as long as possible.</para>
</section>
<section class="lev2" id="sec1-2-3" label="1.2.3" xreflabel="1.2.3">
<title>Severely Affected Patients</title>
<para>Patients with PD, stage 5, are severely affected. They are usually confined to a wheelchair or in bed and require great assistance to make transfers. They are totally dependent for the realization of ADLs and have a great limitation on a personal level. Difficulties in speech and voice are often accentuated: these patients are often difficult to understand due to their low volume and poor articulation of words. They may eventually develop contractures and present decubitus ulcers or recurrent urinary tract infections.</para>
<para>Since the emergence of effective therapies for the cure of this disease, not all patients reach a state of total dependence. However, they are experiencing a progressive reduction in ON time and an increase in dependency time. In the final stages of this disease, the presence of progressive dysphagia can cause recurrent aspiration pneumonia, which is a possible cause of death. Other conditions that may contribute to this outcome are infections of pressure ulcers or urinary tract.</para>
<para>Since a causal treatment of the disease is still not possible, the objective for an optimal treatment will be to obtain for the patient a good QoL and the maximum of independence possible. In the advanced stages, it is recommended to increase the hygiene, to take care of the mobilization, to adapt the feeding and above all to take care of communication. The LSVT method has demonstrated efficacy in the treatment of speech and speech disorders. However, in very severe situations, it is advisable to maintain communication, even if external technical support is necessary.</para>
<para>Possible conduct disorders should be addressed, while enhancing the hobbies and pleasures that can still take place, such as listening to music, reading, or watching movies.</para>
<para>Caregivers should make them feel their support, while they should seek a replacement that allows them to have their own space and thus, avoid the burden of care and better adaptation when the patient passes away.</para>
</section>
</section>
<section class="lev1" id="sec1-3" label="1.3" xreflabel="1.3">
<title>QoL in PD</title>
<para><emphasis>Quality of life</emphasis> means well-being or satisfaction with aspects of life that are important to the person according to social standards and personal judgments. Because of this latter characteristic (i.e., personal judgment), the QoL is understood differently by each person and, therefore, it is difficult to define. The World Health Organization (WHO) defines it as: &#x0201C;an individual perception of the position in a person&#x02019;s life, in the context of the culture and value system in which he lives, in relation to his goals, expectations, standards and concerns&#x0201D;.</para>
<para>Quality of Life, as related to Health (QoLRH), is the self-perception and assessment of the impact that the disease has on a patient&#x02019;s life and what its consequences are [2]. This assessment is extremely important because, when it is not possible to cure, maintaining the QoL of the patient is a priority of medical care. Among the different components of QoLRH, main attention must be paid on:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>physical aspects, which are related to symptoms and are functional (i.e., ability to perform activities);</para></listitem>
<listitem>
<para>mental aspects in relation to mood and cognition;</para></listitem>
<listitem>
<para>social aspects such as family role or social relations; and</para></listitem>
<listitem>
<para>economic aspects.</para></listitem>
</itemizedlist>
<para>In a recent study by Winter et al. [3], a baseline and 3, 6 and 12 months&#x02019; assessments were performed on 145 Parkinson&#x02019;s patients. The average annual cost was calculated at 20.095 per patient. The direct costs involved an expenditure of 13.185 on medication, 3.526 on hospital care, and 3.789 on residences. The indirect costs accounted for 34.5% of the total costs (6.937 ). The costs of home care for the family accounted for 20% of direct costs. Factors associated with a higher total cost were fluctuations, dyskinesias, and younger age.</para>
<para>To assess QoLRH in PD, 56 studies were reviewed [4]. The three most important factors determining QoLRH in PD were depression, stage of the disease, and the time that has elapsed since the onset of the disease.</para>
<para>In another study by S&#x00142;awek et al. [5], performed with 100 patients, the most important predictor for poor QoL was depression, followed by motor complications. Motor complications, especially nocturnal akinesia and dyskinesia, significantly decrease the QoL of Parkinson&#x02019;s patients [6]. Not only can dyskinesias affect QoL, but they can also increase health costs in patients with PD. This should be taken into account when planning treatment [7].</para>
<para>Despite the high impact of motor symptoms in Parkinson&#x02019;s, non-motor symptoms seem to influence patients&#x02019; QoL even more [8]. Non-motor symptoms tend to accumulate. The average was 10 symptoms per patient in the populations studied and symptoms tend to intensify over time. Depression, anxiety, fatigue, sleep disorders, pain, orthostatic hypotension, and profuse sweating are some of those that have shown an individual relationship with loss of QoL. In fact, any symptom that, due to its intensity, is installed as a central problem in the life of the patient has a direct and important impact on his or her QoL. For example: difficulty swallowing, persistent constipation, urinary urgency and night-time urination, delusions and hallucinations, memory problems, or a sense of choking when breathing. At the global level, the main factors influencing the poor QoL of those affected by PD are (in order):</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Depression</para></listitem>
<listitem>
<para>Overall disease severity (Hoehn and Yahr stage)</para></listitem>
<listitem>
<para>Dyskinesia</para></listitem>
<listitem>
<para>ON&#x02013;OFF fluctuations</para></listitem>
<listitem>
<para>Age</para></listitem>
<listitem>
<para>Insomnia</para></listitem>
<listitem>
<para>Tremor</para></listitem>
<listitem>
<para>Cognitive dysfunction</para></listitem>
</orderedlist>
<para>Another element that must be taken into account is the QoL in caregivers of patients with PD [9]. 40% of caregivers indicate that their health suffers from caring. Nearly half have increased depression, two-thirds report that their social life has suffered. The caregiver becomes burned out more (burden of care) if the patient has more disability, or affective problems, mental confusion, or falls. There is a correlation between those caregivers that are most affected and the degree of a patient&#x02019;s depression. The conclusion is that more attention should be given to caregivers&#x02019; care, particularly in advanced stages and/or with psychiatric and fall complications. These findings demonstrate that the QoL of both the patient and the caregiver depends, to a great extent, on the inclusion of the burden of care as one of the problems associated with PD [10].</para>
</section>
<section class="lev1" id="sec1-4" label="1.4" xreflabel="1.4">
<title>State of Art of Current Trends in PD Management</title>
<para>The current treatment of PD is symptomatic and is applied through pharmacological and/or surgical treatment, associated with MDT.</para>
<para>The pharmacological treatment of PD aims to alleviate the symptoms associated with the disease, through the precise adjustment of medication. During the first few years of treatment, dopaminergic drugs are usually very effective. When the ON&#x02013;OFF phenomena are already present, this objective is reached essentially by reducing the time during which the patient is in the OFF state, while avoiding the appearance of MCs and NMS. The reduction of OFF time is, therefore, one of the main parameters used to evaluate the effectiveness of therapeutic interventions, both in medical<emphasis role="strong"></emphasis>practice and in clinical trials. To determine the optimal treatment plan, gathering accurate information about a patient&#x02019;s condition throughout the day is essential. In clinical practice, the method currently available is based on diaries filled in by patients and their caregivers, recording hours of ON&#x02013;OFF and the presence of dyskinesia. However, this method has limitations that make it unreliable, such as motor difficulties, failures in memory and in compliance, and subjective evaluation. It is necessary to know precisely the effect of drugs on reducing OFF hours and increasing the ON hours in Parkinson&#x02019;s patients. Reliable tools are, therefore, needed for detecting the motor condition of patients.</para>
<para>In patients with advanced PD, in which it is very difficult to control MCs and NMS through pharmacological adjustment, interventional therapy strategies are increasingly applied. These treatment strategies are aimed at obtaining continuous dopaminergic stimulation (CDS), either by using an infusion pump to deliver medication or by deep brain stimulation (DBS). However, these techniques are expensive, and often difficult to manage by the patient. Well-designed clinical studies on these interventional therapeutic approaches provided evidence for the efficacy of DBS and CDS in advanced PD and opened new perspectives for their use in earlier disease stages also.</para>
<para>On the other hand, there is growing scientific evidence of the benefit of the application of MDT, such as physiotherapy, speech therapy (e.g., LSVT), occupational therapy, cognitive stimulation, and psychoeducation in the treatment of Parkinson&#x02019;s Disease. Intensive and multidisciplinary rehabilitation slows the progression of motor decay, and slows the need to increase treatment with levodopa, which is postulated to have a neuroprotective effect [11]. Therefore, the application of MDT from the moment of diagnosis seems of great interest. There are several studies of multidisciplinary care in PD comparing outcomes before and after the intervention. Outpatient multidisciplinary care programs have reported short-term improvements in UPDRS (Unified Parkinson Disease Rating Scale) motor score, gait speed and stride length, speech, depression and health-related QoLRH. Long-term improvements in motor function have also been reported, and the authors comment that a close collaboration among members of the multidisciplinary team was essential to obtain the best results.</para>
<para>Potential limitations to the implementation of effective MDT are: distance, insufficient expertise among health professionals, poor interdisciplinary collaboration, poor communication, and lack of financial support for a multidisciplinary team approach. Regular face-to-face team meetings are important for effective functioning of the team. These meetings allow sharing of pertinent information and ensure the team is working towards shared goals for any given patient. The meetings can be a forum and stimulus for staff education, driving up quality of care. This type of coordinated multidisciplinary approach is sometimes referred to as interdisciplinary.</para>
<para>Most hospitals in Europe do not have a multidisciplinary service for the care of people with PD. These types of therapies are expensive and in addition, their application requires patients to frequently go from one place to another. This entails a number of limitations, both economic and logistical, for those affected with PD before having access to these therapies.</para>
</section>
<section class="lev1" id="sec1-5" label="1.5" xreflabel="1.5">
<title>Needs and Challenges for Optimal PD Management</title>
<para>Current management of advanced PD is complicated and problems arising from poor QoL affect many patients. In 2001, <emphasis>the Committee on Quality of Health Care in America Institute of Medicine</emphasis> provided an objective analysis on healthcare. The report listed six aims, proposing that health care should be: safe, effective, patient-centred, timely, efficient, and equitable. However, current care for PD in the US, Europe, and likely the majority of the world, frequently does not meet these six aims [12]. PD care is often not safe. Individuals with PD who are hospitalized are often subjected to delayed treatment, contraindicated medications, prolonged immobility, lengthy stays, and high mortality [13, 14]. There are some comprehensive and distributed PD care models that are quite effective, but only few patients receive such care. Many PD-related hospitalizations are likely preventable. The patient-centred care that is timely has been rarely studied. Despite the limited evidence, focus groups and surveys suggest that individuals with PD want more personalized information from multiple disciplines that is delivered remotely in a timely manner [15]. PD care is very inefficient. Patients and their caregivers spend hours travelling and waiting in the clinic for routine follow-up appointments or for the application of complementary therapies.</para>
<para>Finally, and perhaps what may be most concerning, there exists inequity of current PD care. A primary determinant of the care that will be received is where you live. In the US, 42% of individuals with PD older than 65 and up to 100% of individuals in some rural areas do not see a neurologist soon after diagnosis [16]. In Europe, the first right expressed in the European Parkinson&#x02019;s Disease Association Charter is care from a physician with a special interest in PD. However, 44% of Europeans do not see a PD specialist in the first 2 years after diagnosis. Beyond neurological care, access to specialist nurses, occupational therapists, and counsellors is often more limited [17]. In less wealthy countries, the situation is even worse. China only has approximately 50 movement disorder specialists to care for more than 2 million individuals with PD and Bolivia only has 15. A door-to-door epidemiology study found that none of the individuals identified with PD had ever seen a physician, much less received treatment.</para>
<para>We can make the treatment safer, effective, patient-centred, efficient, and equitable only with the application of two conditions: that the treatment is applied mostly in the patient&#x02019;s home and with the use of tools, based on new technologies: sensors, communication platforms, and smartphones. This will overcome economic barriers and physical distance.</para>
<para>The simple fact of detecting accurately and reliably the clinical condition of the patient can mean a significant advance in the QoL of the patient, as this will affect a much more accurate adjustment of medication. In addition, with the help of adequate platforms, many more patients, as well as their caregivers, will receive more specialized medical care, complementary therapies, and psychoeducation as often as necessary, regardless of where they live.</para>
<para>In addition, reliable detection of the motor status of PD patients throughout the day can drastically change the value of drug clinical trials. Finally, the careful selection of patients amenable to the semi-invasive therapy options becomes more and more important and should be timely. An interdisciplinary setting is required to account for optimal patient information and awareness, selection of best individual treatment modality, training of relatives and caregivers, management of complications, and follow-up care.</para>
<para>The application of this type of tool is also of great interest in this section [18].</para>
<para>From a clinical point of view, the development of new technologies in the management of Parkinson&#x02019;s Disease must be validated so that the improvement of the QoL related to health is the main objective. Symptom-monitoring tools should be based on these premises: to provide a valid and accurate parameter of a clinically relevant characteristic of the disease; to find evidence that the parameter has an ecologically relevant effect on the specific clinical application; that a target interval can be defined in which the parameter reflects the appropriate treatment response; and finally, that the implementation is simple to allow repetitive use [19].</para>
<para>Remote monitoring from devices, such as wearable sensors, smartphones, platforms, disease management applications, smart beds, wall-mounted cameras, smart glasses, and even utensils, can monitor a patient&#x02019;s symptoms and function objectively in their environment, facilitating the delivery of highly personalized care.</para>
<para>Another aspect to improve PD care is that the most of it must be delivered at home. Current care models frequently require older individuals with impaired mobility, cognition, and driving ability to be driven by overburdened caregivers to large, complex urban medical centres. Moving care to the patient&#x02019;s home would make PD care more patient-centred. Demographic factors, including aging populations, and social factors, such as the splintering of the extended family, will increase the need for home-based care. Technological advances, especially the ability to assess and deliver care remotely, will enable the transition of care back to the home. However, despite its promise, this next generation of home-based care will have to overcome barriers, including outdated insurance models and a technological divide. Once these barriers are addressed, home-based care will increase access to high-quality care for the growing number of individuals with PD.</para>
<para>Emerging care models will combine remote monitoring, self-monitoring, and multidisciplinary care to enable the provision of patient-centred care at home and decrease the need for in-clinic assessments.</para>
<para>The demand for in-home care is likely to grow as a result of demographic, economic, social, and technological factors. Both the absolute number and proportion of older individuals with PD will increase.</para>
</section>
<section class="lev1" id="sec1-6" label="1.6" xreflabel="1.6">
<title>Conclusion</title>
<para>A system for PD management will be necessary in the near future. It must be able to reliably assess the symptoms, facilitate patient disease management, and give them independence and the best QoL. At the same time, the tools must help the patient to stay physically and mentally active as much as possible. Finally, they must provide the neurologist with disease management tools to optimize the treatment.</para>
</section>
<section class="lev1" id="sec1-7">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Smith, M., and Simons, G. (eds). (2006). <emphasis>Patient Education for People with Parkinson&#x02019;s Disease and Their Carers: A Manual</emphasis>. Hoboken, NJ: Wiley.</para></listitem>
<listitem>
<para>Mart&#x00ED;nez-Mart&#x00ED;n, P. (1998). <emphasis>Calidad de Vida relacionada con la Salud En La Enfermedad de Parkinson</emphasis>. Belgrade: Ars M&#x00E9;dica <ulink url="https://scholar.google.com/scholar?hl=en&amp;as_sdt=0,5&amp;q=Martinez-Martin,+P.+(1998).+Calidad+de+Vida+relacionada+con+la+Salud+En+La+Enfermedad+de+Parkinson.+Belgrade%3A+Ars+M%3Fdica" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Winter, Y, Balzer-Geldsetzer, M., Spottke, A., Reese, J. P., Baum, E., Klotsche, J., et al. (2010). Longitudinal study of the socioeconomic burden of Parkinson&#x02019;s disease in Germany. <emphasis>Eur</emphasis>. <emphasis>J</emphasis>. <emphasis>Neurol</emphasis>. 17, 1156&#x02013;1163. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Winter%2C+Y%2C+Balzer-Geldsetzer%2C+M%2E%2C+Spottke%2C+A%2E%2C+Reese%2C+J%2E+P%2E%2C+Baum%2C+E%2E%2C+Klotsche%2C+J%2E%2C+et+al%2E+%282010%29%2E+Longitudinal+study+of+the+socioeconomic+burden+of+Parkinson%27s+disease+in+Germany%2E+Eur%2E+J%2E+Neurol%2E+17%2C+1156-1163%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Forjaz, M. J., Frades-Payo, B., Mart&#x00ED;nez-Mart&#x00ED;n, P. (2009). The current state of the art concerning quality of life in Parkinson&#x02019;s disease: II. Determining and associated factors. <emphasis>Rev Neurol</emphasis>. 16&#x02013;31, 49, 655&#x02013;660. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Forjaz%2C+M%2E+J%2E%2C+Frades-Payo%2C+B%2E%2C+Mart%EDnez-Mart%EDn%2C+P%2E+%282009%29%2E+The+current+state+of+the+art+concerning+quality+of+life+in+Parkinson%27s+disease%3A+II%2E+Determining+and+associated+factors%2E+Rev+Neurol%2E+16-31%2C+49%2C+655-660%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>S&#x00142;awek, J., Derejko, M., and Lass, P. (2005) Factors affecting the quality of life of patients with idiopathic Parkinson&#x02019;s disease: a cross-sectional study in an outpatient clinic attendees. <emphasis>Parkinsonism Relat. Disord</emphasis>. 11, 465&#x02013;468. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Slawek%2C+J%2E%2C+Derejko%2C+M%2E%2C+and+Lass%2C+P%2E+%282005%29+Factors+affecting+the+quality+of+life+of+patients+with+idiopathic+Parkinson%27s+disease%3A+a+cross-sectional+study+in+an+outpatient+clinic+attendees%2E+Parkinsonism+Relat%2E+Disord%2E+11%2C+465-468%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Chapuis, S., Ouchchane, L., Metz, O., Gerbaud, L., and Durif, F. (2005). Impact of the motor complications of Parkinson&#x02019;s disease on the quality of life. <emphasis>Mov</emphasis>. <emphasis>Disord</emphasis>. 20, 224&#x02013;230. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Chapuis%2C+S%2E%2C+Ouchchane%2C+L%2E%2C+Metz%2C+O%2E%2C+Gerbaud%2C+L%2E%2C+and+Durif%2C+F%2E+%282005%29%2E+Impact+of+the+motor+complications+of+Parkinson%27s+disease+on+the+quality+of+life%2E+Mov%2E+Disord%2E+20%2C+224-230%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Pechevis, M., Clarke, C. E., Vieregge, P., Khoshnood, B., Deschaseaux-Voinet, C., Berdeaux, G., et al.; Trial Study Group. Effects of dyskinesias in Parkinson&#x02019;s disease on quality of life and health-related costs: a prospective European study. <emphasis>Eur. J. Neurol</emphasis>. 12, 956&#x02013;963. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Pechevis%2C+M%2E%2C+Clarke%2C+C%2E+E%2E%2C+Vieregge%2C+P%2E%2C+Khoshnood%2C+B%2E%2C+Deschaseaux-Voinet%2C+C%2E%2C+Berdeaux%2C+G%2E%2C+et+al%2E%3B+Trial+Study+Group%2E+Effects+of+dyskinesias+in+Parkinson%27s+disease+on+quality+of+life+and+health-related+costs%3A+a+prospective+European+study%2E+Eur%2E+J%2E+Neurol%2E+12%2C+956-963%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Mart&#x00ED;nez-Mart&#x00ED;n, P., Schapira, A. H., Stocchi, F., Sethi, K., Odin, P., MacPhee, G., et al. (2007). Prevalence of nonmotor symptoms in Parkinson&#x02019;s disease in an international setting; study using Non-Motor Symptoms Questionnaire in 545 patients. <emphasis>Mov. Disord</emphasis>. 22, 1623&#x02013;1629. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Mart%EDnez-Mart%EDn%2C+P%2E%2C+Schapira%2C+A%2E+H%2E%2C+Stocchi%2C+F%2E%2C+Sethi%2C+K%2E%2C+Odin%2C+P%2E%2C+MacPhee%2C+G%2E%2C+et+al%2E+%282007%29%2E+Prevalence+of+nonmotor+symptoms+in+Parkinson%27s+disease+in+an+international+setting%3B+study+using+Non-Motor+Symptoms+Questionnaire+in+545+patients%2E+Mov%2E+Disord%2E+22%2C+1623-1629%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Schrag, A., Hovris, A, Morley, D., Quinn, N., Jahanshahi, M. (2006). Caregiver-burden in Parkinson&#x02019;s disease is closely associated with psychiatric symptoms, falls, and disability. <emphasis>Parkinsonism Relat</emphasis>. <emphasis>Disord</emphasis>. 12, 35&#x02013;41. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Schrag%2C+A%2E%2C+Hovris%2C+A%2C+Morley%2C+D%2E%2C+Quinn%2C+N%2E%2C+Jahanshahi%2C+M%2E+%282006%29%2E+Caregiver-burden+in+Parkinson%27s+disease+is+closely+associated+with+psychiatric+symptoms%2C+falls%2C+and+disability%2E+Parkinsonism+Relat%2E+Disord%2E+12%2C+35-41%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Schrag, A., Hovris, A., Morley, D., Quinn, N., and Jahanshahi, M. (2006). Caregiver-burden in Parkinson&#x02019;s disease is closely associated with psychiatric symptoms, falls, and disability. <emphasis>Parkinsonism Relat</emphasis>. <emphasis>Disord</emphasis>. 12, 35&#x02013;41. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Schrag%2C+A%2E%2C+Hovris%2C+A%2E%2C+Morley%2C+D%2E%2C+Quinn%2C+N%2E%2C+and+Jahanshahi%2C+M%2E+%282006%29%2E+Caregiver-burden+in+Parkinson%27s+disease+is+closely+associated+with+psychiatric+symptoms%2C+falls%2C+and+disability%2E+Parkinsonism+Relat%2E+Disord%2E+12%2C+35-41%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Frazzitta, G. et al. (2015). Intensive rehabilitation treatment in early Parkinson&#x02019;s disease: a randomized pilot study with a 2-year follow-up. <emphasis>Neurorehabil. Neural. Repair</emphasis> 29, 123&#x02013;131<emphasis>.</emphasis> <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Frazzitta%2C+G%2E+et+al%2E+%282015%29%2E+Intensive+rehabilitation+treatment+in+early+Parkinson%27s+disease%3A+a+randomized+pilot+study+with+a+2-year+follow-up%2E+Neurorehabil%2E+Neural%2E+Repair+29%2C+123-131%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Institute of Medicine (US) and Committee on Quality of Health Care in America. (2001). <emphasis>Crossing the Quality Chasm: A New Health System for the 21st Century</emphasis>. Washington, DC: National Academy Press. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Institute+of+Medicine+%28US%29+and+Committee+on+Quality+of+Health+Care+in+America%2E+%282001%29%2E+Crossing+the+Quality+Chasm%3A+A+New+Health+System+for+the+21st+Century%2E+Washington%2C+DC%3A+National+Academy+Press%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Gerlach, O. H., Winogrodzka, A., and Weber, W. E. (2011). Clinical problems in the hospitalized Parkinson&#x02019;s disease patient: systematic review. Mov Disord. 26, 197&#x02013;208. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Gerlach%2C+O%2E+H%2E%2C+Winogrodzka%2C+A%2E%2C+and+Weber%2C+W%2E+E%2E+%282011%29%2E+Clinical+problems+in+the+hospitalized+Parkinson%27s+disease+patient%3A+systematic+review%2E+Mov+Disord%2E+26%2C+197-208%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Aminoff, M. J., Christine, C. W., Friedman, J. H., et al. (2011). Management of the hospitalized patient with Parkinson&#x02019;s disease: current state of the field and need for guidelines. <emphasis>Parkinsonism Relat. Disord.</emphasis> 17, 139&#x02013;145. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Aminoff%2C+M%2E+J%2E%2C+Christine%2C+C%2E+W%2E%2C+Friedman%2C+J%2E+H%2E%2C+et+al%2E+%282011%29%2E+Management+of+the+hospitalized+patient+with+Parkinson%27s+disease%3A+current+state+of+the+field+and+need+for+guidelines%2E+Parkinsonism+Relat%2E+Disord%2E+17%2C+139-145%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>van der Eijk, M., Faber, M. J., Post, B., et al. (2015). Capturing patients&#x02019; experiences to change Parkinson&#x02019;s disease care delivery: a multicenter study. <emphasis>J</emphasis>. <emphasis>Neurol</emphasis>. 262, 2528&#x02013;2538. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=van+der+Eijk%2C+M%2E%2C+Faber%2C+M%2E+J%2E%2C+Post%2C+B%2E%2C+et+al%2E+%282015%29%2E+Capturing+patients%27+experiences+to+change+Parkinson%27s+disease+care+delivery%3A+a+multicenter+study%2E+J%2E+Neurol%2E+262%2C+2528-2538%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Willis, A. W., Schootman, M., Evanoff, B. A., Perlmutter, J. S., and Racette, B. A. (2011). Neurologist care in Parkinson disease: a utilization, outcomes, and survival study. <emphasis>Neurology</emphasis> 77, 851&#x02013;857. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Willis%2C+A%2E+W%2E%2C+Schootman%2C+M%2E%2C+Evanoff%2C+B%2E+A%2E%2C+Perlmutter%2C+J%2E+S%2E%2C+and+Racette%2C+B%2E+A%2E+%282011%29%2E+Neurologist+care+in+Parkinson+disease%3A+a+utilization%2C+outcomes%2C+and+survival+study%2E+Neurology+77%2C+851-857%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Stocchi, F., and Bloem, B. R. (2013). Move for change part II: a European survey evaluating the impact of the EPDA Charter for people with Parkinson&#x02019;s disease. <emphasis>Eur. J. Neurol</emphasis>. 20, 461&#x02013;472.</para></listitem>
<listitem>
<para>Dorsey, E. R., Vlaanderen, F. P., Engelen, L., Kieburtz, K., Zhu, W., Biglan, K. M. (2016). Moving Parkinson care to the home. <emphasis>Mov. Disord</emphasis>. 31, 1258&#x02013;1262. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Dorsey%2C+E%2E+R%2E%2C+Vlaanderen%2C+F%2E+P%2E%2C+Engelen%2C+L%2E%2C+Kieburtz%2C+K%2E%2C+Zhu%2C+W%2E%2C+Biglan%2C+K%2E+M%2E+%282016%29%2E+Moving+Parkinson+care+to+the+home%2E+Mov%2E+Disord%2E+31%2C+1258-1262%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Maetzler, W., Klucken, J., and Horne, M. (2016). A clinical view on the development of technology-based tools in managing Parkinson&#x02019;s Disease. <emphasis>Mov. Disord.</emphasis> 31, 1263&#x02013;1271. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Maetzler%2C+W%2E%2C+Klucken%2C+J%2E%2C+and+Horne%2C+M%2E+%282016%29%2E+A+clinical+view+on+the+development+of+technology-based+tools+in+managing+Parkinson%27s+Disease%2E+Mov%2E+Disord%2E+31%2C+1263-1271%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch02" label="2" xreflabel="2">
<title>Objective Measurement of Symptoms in PD</title>
<para role="author"><emphasis role="strong">Timothy J Counihan<superscript>1</superscript> and Angels Bay&#x00E9;s<superscript>2</superscript></emphasis></para>
<para><superscript>1</superscript>National University of Galway &#x2013; NUIG, Galway, Ireland</para>
<para><superscript>2</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<section class="lev1" id="sec2-1" label="2.1" xreflabel="2.1">
<title>Advancing Parkinson&#x02019;s Disease: Motor and Non-Motor Fluctuations</title>
<para>The triad of rest tremor, slowness of movement (bradykinesia), and limb rigidity constitute the clinical hallmarks of idiopathic Parkinson&#x02019;s Disease (PD). However, the majority of patients will develop an increasing number of more complex symptoms over time. These symptoms include variability in the patient&#x02019;s mobility, so-called motor fluctuations, as well as variability in other non-motor symptoms (NMSs). Much of this variability is accounted for by a change in the patient&#x02019;s response to dopaminergic medication over time, such that the duration of benefit for a given dose of dopaminergic medication shortens. The following section will elaborate further on these motor and non-motor fluctuations and how they affect patients&#x02019; ability to function. It is important to note, however, that not all motor fluctuations are the result of changing responses to dopaminergic medication.There is increasing recognition that several progressive motor symptoms such as postural instability and freezing of gait (FOG) are the result of non-dopaminergic dysfunction and, therefore, unlikely to respond to standard pharmacologic modifications. The clinical picture of advancing disease is further complicated by the emergence of other symptoms including cognitive dysfunction, sleep disturbances, and blood pressure instability, all of which combine to contribute to the increasing risk of falls in patients with PD. These emergent symptoms probably are a reflection of the underlying pathogenesis in PD, which is thought to involve spread of neuronal degeneration not only to dopaminergic neurons but also autonomic and cholinergic pathways. The result of advancing PD, therefore, is a tendency for patients to develop motor and non-motor fluctuations, postural and autonomic instability, cognitive impairment, and increasing falls risk. As we shall see in the following section, the task for the clinician is to accurately document the emergence of these symptoms, so that appropriate treatment strategies may be initiated to restore patients&#x02019; quality of life (QoL).</para>
<section class="lev2" id="sec2-1-1" label="2.1.1" xreflabel="2.1.1">
<title>Motor Fluctuations</title>
<para>Over 70% of patients with PD will develop increasing variability in their motor response to dopaminergic treatment after 5 years [1]. These &#x0201C;motor fluctuations&#x0201D; typically appear insidiously and are often initially unnoticed by the patient. The first evidence of an emerging fluctuating medication response is the &#x0201C;wearing-off&#x0201D; phenomenon, where the patient reports slowing up or increasing stiffness as the time approaches for their next dose of medication. This commonly is apparent overnight as the patient develops difficulty turning over and getting comfortable in bed (nocturnal akinesia). Patients report that they feel the first morning dose of medication &#x0201C;kick in&#x0201D; around half an hour after taking it (&#x0201C;morning benefit&#x0201D;). Over time, patients may notice end of dose &#x0201C;wearing-off&#x0201D;. This may be ultimately quite dramatic to the point where they &#x0201C;freeze&#x0201D; and become effectively immobile until such time as their next dose &#x0201C;kicks in&#x0201D;. Furthermore, the time needed for the subsequent dose to start working may be strongly influenced by several factors including dietary intake of protein, which may result in a delayed time before the patient turns ON. Motor fluctuations can become so severe as to result in the ON&#x02013;OFF phenomenon, where the patient may cycle rapidly between being ON (mobile) and OFF (immobile or frozen). As mentioned above, these fluctuations are the result of alterations in dopamine receptor sensitivity to exogenous dopamine. The increasingly attenuated motor response to dopaminergic medication is further complicated by an exaggerated sensitivity of the motor response, resulting in excessive involuntary movements (dyskinesia), typically during the time of peak plasma levels of dopamine. Less commonly, painful twisting (dystonic) movements occur as dopamine levels rise or fall (biphasic dyskinesia). The OFF state may be so severe in patients as to cause painful &#x0201C;off dystonia&#x0201D; or FOG. It will be apparent, therefore, that there is a wide repertoire of variability in a given patient&#x02019;s motor state, ranging from complete immobility to flinging choreic movements, and that these fluctuations may occur cyclically many times throughout the day. Furthermore, the occurrence of motor fluctuations is influenced by many factors, including the dose and formulation of dopaminergic drug, diet, anxiety, and use of concurrent medications. It is essential that the treating clinician documents an accurate account of these motor fluctuations, so as to guide further treatment to minimize their disruption to the patient (<link linkend="T2-1">Table <xref linkend="T2-1" remap="2.1"/></link>).</para>
<table-wrap position="float" id="T2-1">
<label><link linkend="T2-1">Table <xref linkend="T2-1" remap="2.1"/></link></label>
<caption><para>Common motor and non-motor fluctuations in PD</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Motor</td>
<td valign="top" align="left">Non-motor</td></tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left"><para>Wearing-off</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Morning benefit</para></listitem> <listitem><para>Nocturnal akinesia</para></listitem> <listitem><para>ON/OFF</para></listitem>
</itemizedlist></td>
<td valign="top" align="left"><para>Sensory</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Paresthesias</para></listitem> <listitem><para>Hyposmia</para></listitem>
</itemizedlist></td>
</tr>
<tr>
<td valign="top" align="left"><para>Freezing of gait (FOG)</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Start hesitation</para></listitem> <listitem><para>Festination</para></listitem>
</itemizedlist></td>
<td valign="top" align="left"><para>Autonomic</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Sweating</para></listitem> <listitem><para>Constipation</para></listitem> <listitem><para>Orthostatic Hypotension</para></listitem>
</itemizedlist></td>
</tr>
<tr>
<td valign="top" align="left"><para>Dyskinesia</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Peak dose</para></listitem> <listitem><para>Biphasic</para></listitem>
</itemizedlist></td>
<td valign="top" align="left"><para>Neuropsychiatric</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Anxiety</para></listitem> <listitem><para>Depression</para></listitem> <listitem><para>Psychosis</para></listitem>
</itemizedlist></td>
</tr>
<tr>
<td valign="top" align="left">OFF dystonia</td>
<td valign="top" align="left"><para>Sleep</para>
<itemizedlist mark="bullet" spacing="normal"><listitem><para>Rapid eye movement (REM) sleep behavior disorder</para></listitem> <listitem><para>Excess daytime sleepiness</para></listitem>
</itemizedlist></td>
</tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec2-1-2" label="2.1.2" xreflabel="2.1.2">
<title>Non-Motor Fluctuations</title>
<para>It has been increasingly recognized that while much of the day to day disability in PD relates to motor dysfunction, many patients experience a variety of NMSs, including paresthesias, fluctuating mood, and anxiety, autonomic disturbances such as constipation, postural hypotension, sleep disturbances, as well as cognitive slowing (bradyphrenia) [2, 3]. As alluded to above, many of these symptoms reflect the underlying degenerative process, which affects several neurotransmitter systems. However, it is also apparent that many of these NMSs occur as a result of dopaminergic dysregulation, and are, therefore, fluctuant in the same way as motor symptom fluctuation. NMSs typically affect one or more of four domains: neuropsychiatric, autonomic, sensory, or sleep (<link linkend="T2-1">Table <xref linkend="T2-1" remap="2.1"/></link>). Many NMSs are now recognized to precede the development of motor symptoms in PD, and hence, can be seen as intrinsic to the disease process. Other NMSs are likely to be due to medication effects. The importance of recognizing fluctuations in non-motor dopaminergic symptoms (such as OFF-related paresthesias or anxiety) is that their management will be entirely different to similar symptoms that may not be dopaminergic in origin. For instance, many patients will develop acute onset anxiety symptoms as the first symptom of wearing-off of their dopaminergic medication. Treatment of this symptom will involve modifications in their l-dopa intake rather than prescribing anxiolytics. It will be again apparent that it is essential for the clinician to accurately document these symptoms so as make appropriate alterations in therapy may be made. Teasing out non-motor symptomatology can be challenging even for the experienced clinician. Adding to the complexity of this assessment is the fact that cognitive dysfunction develops in the majority of PD patients over time, so that after 15 years, 80% of patients experience significant cognitive impairment [4]. Moreover, chronic sleep disturbances due to nocturnal akinesia, rapid eye movement (REM) sleep behavior disorder and psychosis frequently result in excessive daytime somnolence. Each of these factors contributes to the difficulty that many patients have in recognizing fluctuations in MS and NMS.</para>
</section>
</section>
<section class="lev1" id="sec2-2" label="2.2" xreflabel="2.2">
<title>Challenges in Documenting &#x0201C;Real-World&#x0201D; Fluctuating PD Symptoms</title>
<para>The complexity of evolving motor and non-motor fluctuations in PD poses a significant challenge to the treating clinician. It will be apparent from the previous discussion that accurate identification of true dopaminergic motor and non-motor fluctuations is paramount to the future management strategy for each patient. In the context of a busy hospital or clinic-based environment with its restrictions on the face-to-face patient time, as well as patient anxiety and fatigue, all contribute to the problem of accurate documentation of a patient&#x02019;s clinical status. The clinician has a number of well-worn skills at their disposal so as to become informed of how a patient is coping. The traditional history taking and detailed examination techniques provide invaluable information not only about the patient&#x02019;s motor function, but importantly about the patient&#x02019;s understanding of the different motor states. The latter is a critical aspect of the clinical encounter. Is the patient able to distinguish tremor (a manifestation of the OFF state) from dyskinesia (an ON phenomenon)? What is the patient&#x02019;s understanding of the terms OFF and ON? While the clinician examination will usually help in determining the patient&#x02019;s motor status, it is only a snapshot of a patient&#x02019;s daily life, and even at that, often not a particularly reliable one, as a visit to the doctor&#x02019;s office is not representative of a patient&#x02019;s daily activity, and the added burden of long travel to the clinic, a degree of patient anxiety about the encounter, as well as forgotten tablets, may all contribute to a distorted account of a patient&#x02019;s &#x0201C;real-life&#x0201D; clinical status.</para>
<para>A number of additional tools are available to help the clinician acquire the necessary data to inform therapeutic decision-making. The availability of an informed family member provides a useful narrative regarding the patient&#x02019;s home life, although too often the patient may live alone or a spouse is unavailable or unable to provide helpful information. A variety of clinical rating scales and questionnaires have been developed which provide a degree of objectivity to the patient&#x02019;s assessment, though all have their own limitations. Although the Unified Parkinson&#x02019;s Disease Rating Scale (UPDRS) remains the gold standard clinical rating scale especially in a research setting, it suffers from subjectivity and variable clinician competence in using it. For many years patient diaries have provided the backbone of &#x0201C;real-world&#x0201D; interrogation of patient motor states. Diaries allow for frequent recording of a patient&#x02019;s motor state (OFF, ON, ON with dyskinesia; and asleep) as determined by the patient or caregiver. However, patient reported diaries are known to lack consistency and can be associated with variable adherence. In addition, patients may have physical difficulty filling in the diary due to micrographia and severe akinesia. Similarly, many patients have difficulty distinguishing tremor from dyskinesia, or may erroneously record the state they are in at the moment of documentation, rather than their predominant motor state over the preceding hour or two. What is certainly clear in relation to the accurate assessment of motor fluctuations is that the patient&#x02019;s motor state as determined in the clinic is rarely representative of their quotidian state; indeed, it is not uncommon for the patient to cycle from extreme akinesia to severe dyskinesias during the course of the clinic encounter. The situation regarding accurate detection of non-motor fluctuations is even more difficult, and relies mostly on obtaining a careful history from the patient and their family regarding any possible periodicity of such symptoms (<link linkend="T2-1">Table <xref linkend="T2-1" remap="2.1"/></link>). The NMS questionnaire [5, 6] is a 30-questions assessment tool which can be useful in highlighting symptoms not previously recognized as potentially related to PD. Such questionnaires may lack the ability to identify non-motor fluctuations as part of a medication effect and are impractical for clinical routine use.</para>
</section>
<section class="lev1" id="sec2-3" label="2.3" xreflabel="2.3">
<title>Emerging Technologies to Monitor Symptom Fluctuations</title>
<para>In an attempt to improve the ability to detect and monitor the occurrence of motor fluctuations, a variety of new technologies have emerged which is beginning to transform the management of Parkinson&#x02019;s Disease. Two technologies have recently been combined which promise to radically change the daily management of PD: so-called &#x0201C;wearables&#x0201D; and machine-learning based techniques [7]. Suffice it to say here that these technologies can provide objective, high frequency, sensitive, and continuous data on motor and non-motor phenomena in PD [7]. In particular, the development of wearable inertial sensors has introduced a level of objectivity in the recording of patients&#x02019; motor function in daily life, so-called <emphasis>free-living</emphasis> monitoring [8]. The explosion of interest in the quantitative assessment and management of PD using technology-based tools has been usefully summarized in a series of reviews in the journal <emphasis>Movement Disorders</emphasis> [9]. Several large-scale studies on wearable technologies have reported preliminary results, along with over a dozen smaller series using a variety of machine learning algorithms for wearable sensor-based data acquisition in PD (summarized by Kubota et al. [7]). The obvious appeal of wearable technology (WT) is that it allows for community-based data acquisition over a continuous time period. In addition, the collected data is free from observer bias and the so-called attentional compensation (Hawthorne effect). The newer devices are relatively low cost with user-friendly technology. Continuous monitoring allows for the accumulation of large amounts of data, which may be analyzed at both a macro- or micro-level [10]. At a micro-level, data is available on motor state, frequency and severity of motor fluctuations, gait as well as response to medications. In the case of patients with PD, data can be acquired on the number and intensity of multiple activities, including the frequency and amplitude of movements throughout the day and night, the frequency and duration of tremor, dyskinesia, as well as impairments of gait including FOG and balance impairment [11]. There is also the possibility that detailed interrogation of data obtained at regular intervals may disclose important subclinical physiological changes that might predict a subsequent clinical change in motor state, allowing potentially for preemptive therapeutic intervention. This appears to be especially relevant in the detection of FOG [12, 13]. A big challenge, however, for any emerging sensor technology aiming to supersede existing clinical motor assessments (such as the UPDRS) is the requirement for clinimetric algorithm validation. Testing of such objective algorithms must include a test/re-test protocol to ensure reliability.</para>
<para>At a macro-level, general levels of activity, inactivity or sleep are available. The information obtained from WT is available both to the clinician and the patient, and importantly it allows the patient to become actively involved in their condition and learn about their level of activity as well as therapeutic efficacy. An important aspect of a WT system is that it allows remote monitoring of symptoms with its obvious potential advantage for patients and health economics (REMPARK system, presented in this book, is an example).</para>
<para>It should be apparent that the ability to quantify clinical phenomena using WT is not simply because &#x0201C;<emphasis>we can</emphasis>&#x0201D;, but that the ability to reliably capture such data is a major advance on the standard qualitative clinical examination. Espay et al. [11] point out that whatever is measured must be directed toward a therapeutic target. Despite these technological advances, however, their application in a clinical setting has been slower to evolve. As Del Din et al. [10] pointed out, there remains no gold standard against which remote monitoring WT can be compared. Moreover, simply measuring a litany of motor and non-motor phenomena should not necessarily lead to reflexly acting on such data with therapeutic intervention. What matters for one patient may cause little functional impairment for another. For instance, a common experience for the clinician is to observe a patient with severe, ballistic dyskinesias, but for whom the involuntary movements are non-disabling [14]. This dichotomy becomes even starker when one attempts to take into account various non-motor measurements (such as hyperhidrosis or anxiety), which may cause substantial disability for the patient, but remain less overt than motor recordings. A number of attempts have been made to record non-motor symptomatology using sensor technology, chiefly relating to sleep-related symptoms [15]. These sensors can provide valuable real-world insight into a variety of nocturnal sleep difficulties including RBD (REM sleep behavior disorder), nocturnal akinesia, and restless legs syndrome. Moreover, information on excessive daytime somnolence is also recordable on inertial devices. In recognition of this, several commentators have called for a &#x0201C;multidomain&#x0201D; integrated technology as the template for individualized, personalized therapeutic approach to care [11]. The REMPARK system is an attempt to provide an integrated system of personalized management of PD.</para>
</section>
<section class="lev1" id="sec2-4" label="2.4" xreflabel="2.4">
<title>Challenges in the Use of Inertial Sensor Technology in Monitoring PD Symptoms</title>
<para>There exist some specific challenges in the use of technology for an objective monitoring of PD and the contribution to increase QoL of patients. A set of them are discussed below:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para><emphasis>Limitations of Motor Sensors</emphasis>: Currently available commercial sensor technologies have been demonstrated to accurately measure a variety of motor symptoms in PD including tremor, bradykinesia, dyskinesia, and gait impairment [16]. However, much of the validation testing of such technology was derived from laboratory-based experimentation. Clinicians have raised a concern that this is not an accurate reflection of &#x0201C;real-world&#x0201D; situations. For example, sensor data fails to discriminate accurately whether bradykinesia is the result of fatigue, anxiety, or motor wearing-off [12]. Hence, the <emphasis>context</emphasis> in which sensor data is derived has a large influence on its interpretation. While the freedom to record continuous data in an ambulatory home setting has obvious advantages over the laboratory, the trade-off is a substantial loss of experimental control over the data collection [7]. The REMPARK system and others have attempted to provide a degree of context to the sensor data by the provision of smartphone technology, which allows the patient or carer to interact with a web-based application to input subjective data, such as a non-motor questionnaire [13]. Another potential limitation of inertial sensor measurements is that their resolution may be affected by their anatomical location, and that while this may be mitigated to some extent by the application of multiple sensors, this adds to the complexity of the algorithms to interpret the data, as well as adding more complexity and discomfort for the patient [17]. Currently, most available sensors rely on single sensors applied to the most affected side in patients.</para></listitem>
<listitem>
<para><emphasis>NMS Monitoring</emphasis>: The development of WT to monitor PD symptoms has primarily focused on motor aspects of the disease [11]. However, it has been apparent even using older established clinical scales of motor disability (UPDRS) that there is at best only a modest correlation between the degree of motor impairment and QoL. There is an emerging recognition that a substantial daily burden for patients derives from non-motor symptomatology [5], including symptoms such as anxiety, sweating, fatigue, sleep disturbances, etc. While some technologies are available to address this, such as sweat sensors, blood pressure and heart rate monitors, as well as the application of inertial sensors to monitor for sleep disturbances, clearly further refinement of this technology is needed.</para></listitem>
<listitem>
<para><emphasis>Clinimetrics and data validation</emphasis>: There is a natural tendency to consider the development of &#x0201C;objective&#x0201D; sensor technology as ultimately replacing previously validated subjective rating scales such as the UPDRS. However, Espay et al. [11] have pointed out that the clinician integrates many sources of &#x0201C;data&#x0201D; to reach a subjective score or opinion, and that technological sensor measurements should complement clinical measures rather than act as surrogate markers.</para></listitem>
<listitem>
<para><emphasis>Disease Progression</emphasis>: The advent of WT has opened the door to their use in clinical trials of emerging therapies as surrogate markers of efficacy. But investigators need to be cognizant that improved sensor &#x0201C;data&#x0201D; following institution of a therapy may not translate into improved QoL for patients. Moreover, use of WT longitudinally will need to take into account that PD is a progressive disease and that the parameters by which improvement must be measured will change over time. For instance, for many patients with advanced disease, the priority of maintaining cognitive function may come at the expense of a desirable motor outcome, at which point motor sensor data becomes moot.</para></listitem>
<listitem>
<para><emphasis>Data Analysis</emphasis>: Existing technology-based objective measures require a robust method of data analysis to ensure that the data collected is an accurate reflection of the clinical phenomena under scrutiny. The development of algorithms to appropriately interrogate the data requires close cooperation between clinicians and technical personnel. For instance, a sensor that detects &#x0201C;severe bradykinesia&#x0201D; at one measurement and &#x0201C;severe dyskinesia&#x0201D; at a second measurement within a two-minuteepoch is likely to be spurious, unless data from other sources can be factored in. In this case, the data suggesting &#x0201C;severe bradykinesia&#x0201D; is likely to be strengthened in its validity if such data is accompanied by a contemporaneous finding of &#x0201C;severe tremor&#x0201D;. Development of reliable algorithms to interpret data requires input from clinicians so that appropriate weighting can be given to such data.</para></listitem>
<listitem>
<para><emphasis>User Engagement</emphasis>: Despite enthusiasm from technologists and clinicians for the incorporation of WT into practice, current research suggests only modest patient and carer engagement [18]. Giving feedback to patients on the relevance and importance of wearing sensors seems to influence adherence.</para></listitem>
</orderedlist>
</section>
<section class="lev1" id="sec2-5" label="2.5" xreflabel="2.5">
<title>Conclusion</title>
<para>There is little doubt that the rapid development of continuous WT with the ability to generate objective measurements relating to the evolving clinical state of PD patients has provided a tremendous opportunity to improve patient care, as well as learn more about the disease as it affects patients in their own environment. In the long term, these technologies will have to be sufficiently reliable and robust to allow for the remote personalized management of PD, including treatment delivery.</para>
</section>
<section class="lev1" id="sec2-6">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Aquino,C. C., and Fox, S. H. (2015). The clinical spectrum of levodopa-induced complications. <emphasis>Mov. Disord</emphasis>. 30, 80&#x02013;89. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Aquino%2CC%2E+C%2E%2C+and+Fox%2C+S%2E+H%2E+%282015%29%2E+The+clinical+spectrum+of+levodopa-induced+complications%2E+Mov%2E+Disord%2E+30%2C+80-89%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Lim, S.-Y., and Lang, A. E. (2010). The non-motor symptoms of Parkinson&#x02019;s disease: an overview. <emphasis>Mov. Disord</emphasis>. 25, S123&#x02013;S130. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Lim%2C+S%2E-Y%2E%2C+and+Lang%2C+A%2E+E%2E+%282010%29%2E+The+non-motor+symptoms+of+Parkinson%27s+disease%3A+an+overview%2E+Mov%2E+Disord%2E+25%2C+S123-S130%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Martinez-Fernandez, R., Schmitt, E., Martinez-Martin, P., and Krack P. (2016). The hidden sister of motor fluctuations in Parkinson&#x02019;s disease: a review on non-motor fluctuations. <emphasis>Mov. Disord</emphasis>. 31, 1080&#x02013;1094. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Martinez-Fernandez%2C+R%2E%2C+Schmitt%2C+E%2E%2C+Martinez-Martin%2C+P%2E%2C+and+Krack+P%2E+%282016%29%2E+The+hidden+sister+of+motor+fluctuations+in+Parkinson%27s+disease%3A+a+review+on+non-motor+fluctuations%2E+Mov%2E+Disord%2E+31%2C+1080-1094%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Hely, M. A., Reid, W. G., Adena, M. A., Halliday, G. M., and Morris, J. G. (2008). The Sydney Multicenter Study of Parkinson disease: the inevitability of dementia at twenty years. <emphasis>Mov. Disord</emphasis>. 23, 837&#x02013;844. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Hely%2C+M%2E+A%2E%2C+Reid%2C+W%2E+G%2E%2C+Adena%2C+M%2E+A%2E%2C+Halliday%2C+G%2E+M%2E%2C+and+Morris%2C+J%2E+G%2E+%282008%29%2E+The+Sydney+Multicenter+Study+of+Parkinson+disease%3A+the+inevitability+of+dementia+at+twenty+years%2E+Mov%2E+Disord%2E+23%2C+837-844%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Chaudhuri, K. R., Martinez-Martin, P., Schapira, A. H. V., Stocchi, F., Sethi, K., and Odin, P. et al. (2006). An international multicentre pilot study of the first comprehensive self-completed non motor symptoms questionnaire for Parkinson&#x02019;s disease: The NMSQuest study. <emphasis>Mov. Disord</emphasis>. 21, 916&#x02013;923. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Chaudhuri%2C+K%2E+R%2E%2C+Martinez-Martin%2C+P%2E%2C+Schapira%2C+A%2E+H%2E+V%2E%2C+Stocchi%2C+F%2E%2C+Sethi%2C+K%2E%2C+and+Odin%2C+P%2E+et+al%2E+%282006%29%2E+An+international+multicentre+pilot+study+of+the+first+comprehensive+self-completed+non+motor+symptoms+questionnaire+for+Parkinson%27s+disease%3A+The+NMSQuest+study%2E+Mov%2E+Disord%2E+21%2C+916-923%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Romenets, S. R.,Wolfson, C., Galatas, C., Pelletier, A., Altman, R., Wadup, L., Postuma, R. B., et al. (2012).Validation of the non-motor symptoms questionnaire (NMS-Quest). <emphasis>Parkinsonism Relat. Disord.</emphasis>18, 54&#x02013;58. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Romenets%2C+S%2E+R%2E%2CWolfson%2C+C%2E%2C+Galatas%2C+C%2E%2C+Pelletier%2C+A%2E%2C+Altman%2C+R%2E%2C+Wadup%2C+L%2E%2C+Postuma%2C+R%2E+B%2E%2C+et+al%2E+%282012%29%2EValidation+of+the+non-motor+symptoms+questionnaire+%28NMS-Quest%29%2E+Parkinsonism+Relat%2E+Disord%2E18%2C+54-58%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Kubota, K. J., Chen, J. A., and Little, M. A. (2016). Machine learning for large scale wearable sensor data in Parkinsons disease; concepts, prospect&#x02019;s, pitfalls and futures. <emphasis>Mov. Disord</emphasis>. 31, 1314&#x02013;1326. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Kubota%2C+K%2E+J%2E%2C+Chen%2C+J%2E+A%2E%2C+and+Little%2C+M%2E+A%2E+%282016%29%2E+Machine+learning+for+large+scale+wearable+sensor+data+in+Parkinsons+disease%3B+concepts%2C+prospect%27s%2C+pitfalls+and+futures%2E+Mov%2E+Disord%2E+31%2C+1314-1326%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Lowe, S. A., and O&#x02019;Laighin, G. (2014). Monitoring human health behavior in one&#x02019;s living environment: a technological review. <emphasis>Med. Eng. Phys</emphasis>. 36, 147&#x02013;168. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Lowe%2C+S%2E+A%2E%2C+and+O%27Laighin%2C+G%2E+%282014%29%2E+Monitoring+human+health+behavior+in+one%27s+living+environment%3A+a+technological+review%2E+Med%2E+Eng%2E+Phys%2E+36%2C+147-168%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Sanchez-Ferro, A., and Maetzler, W. (2016). Advances in sensor and wearable technologies for Parkinson&#x02019;s disease. <emphasis>Mov. Disord</emphasis>. 31, 1257. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Sanchez-Ferro%2C+A%2E%2C+and+Maetzler%2C+W%2E+%282016%29%2E+Advances+in+sensor+and+wearable+technologies+for+Parkinson%27s+disease%2E+Mov%2E+Disord%2E+31%2C+1257%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Del Din, S., Godfrey, A., Mazza, C., Lord, S., and Rochester, L. (2016). Free-living monitoring of Parkinson&#x02019;s disease: lessons from the field. <emphasis>Mov. Disord</emphasis>. 31, 1293&#x02013;1313. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Del+Din%2C+S%2E%2C+Godfrey%2C+A%2E%2C+Mazza%2C+C%2E%2C+Lord%2C+S%2E%2C+and+Rochester%2C+L%2E+%282016%29%2E+Free-living+monitoring+of+Parkinson%27s+disease%3A+lessons+from+the+field%2E+Mov%2E+Disord%2E+31%2C+1293-1313%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Espay, A. J., Bonato, P., Nahab, F. P., et al. (2016). Technology in Parkinson&#x02019;s disease: challenges and opportunities. <emphasis>Mov. Disord</emphasis>. 31, 1272&#x02013;1282. <ulink url="https://scholar.google.com/scholar?q=Espay%2C+A.+J.%2C+Bonato%2C+P.%2C+Nahab%2C+F.+P.%2C+et+al.+%282016%29.+Technology+in+Parkinson%27s+disease%3A+challenges+and+opportunities.&amp;btnG=&amp;hl=en&amp;as_sdt=0%2C5" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Maetzler, W., Klucken, J., and Horne, M. (2016). A clinical view on the development of technology-based tools in managing Parkinson&#x02019;s disease. <emphasis>Mov. Disord</emphasis>. 31, 1263&#x02013;1271. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Maetzler%2C+W%2E%2C+Klucken%2C+J%2E%2C+and+Horne%2C+M%2E+%282016%29%2E+A+clinical+view+on+the+development+of+technology-based+tools+in+managing+Parkinson%27s+disease%2E+Mov%2E+Disord%2E+31%2C+1263-1271%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Ahlrichs C,Sam&#x00E0;, A., Lawo, M., Cabestany, J., Rodr&#x00ED;guez-Mart&#x00ED;n, D., P&#x00E9;rez-L&#x00F3;pez, C. et al. (2016). Detecting freezing of gait with a tri-axial accelerometer in Parkinson&#x02019;s disease patients. <emphasis>Med. Biol. Eng. Comput</emphasis>. 54, 223&#x02013;233. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Ahlrichs+C%2CSam%E0%2C+A%2E%2C+Lawo%2C+M%2E%2C+Cabestany%2C+J%2E%2C+Rodr%EDguez-Mart%EDn%2C+D%2E%2C+P%E9rez-L%F3pez%2C+C%2E+et+al%2E+%282016%29%2E+Detecting+freezing+of+gait+with+a+tri-axial+accelerometer+in+Parkinson%27s+disease+patients%2E+Med%2E+Biol%2E+Eng%2E+Comput%2E+54%2C+223-233%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Hung, S. W., Adeli, G. M., Arenovitch, T., Fox, S. H., and Lang, A. E. (2010). Patient perception of dyskinesia in Parkinson Disease. <emphasis>J. Neurol. Neurosurg. Psychiatry</emphasis> 81, 1112&#x02013;1115. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Hung%2C+S%2E+W%2E%2C+Adeli%2C+G%2E+M%2E%2C+Arenovitch%2C+T%2E%2C+Fox%2C+S%2E+H%2E%2C+and+Lang%2C+A%2E+E%2E+%282010%29%2E+Patient+perception+of+dyskinesia+in+Parkinson+Disease%2E+J%2E+Neurol%2E+Neurosurg%2E+Psychiatry+81%2C+1112-1115%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Klingelhoefer, L., Rizos, A., Sauerbier, A., et al. (2016). Night-time sleep in Parkinson&#x02019;s disease; the potential use of Parkinsons KinetiGraph: a prospective comparative study. <emphasis>Eur. J. Neurol</emphasis>. 23, 1275&#x02013;1288. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Klingelhoefer%2C+L%2E%2C+Rizos%2C+A%2E%2C+Sauerbier%2C+A%2E%2C+et+al%2E+%282016%29%2E+Night-time+sleep+in+Parkinson%27s+disease%3B+the+potential+use+of+Parkinsons+KinetiGraph%3A+a+prospective+comparative+study%2E+Eur%2E+J%2E+Neurol%2E+23%2C+1275-1288%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>van Uem, J. M. T., Maier, K. S., Hucker, S., et al. (2016). Twelve week sensor assessment in Parkinson&#x02019;s disease: impact on quality of life. <emphasis>Mov. Disord</emphasis>. 31, 1337&#x02013;1338. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=van+Uem%2C+J%2E+M%2E+T%2E%2C+Maier%2C+K%2E+S%2E%2C+Hucker%2C+S%2E%2C+et+al%2E+%282016%29%2E+Twelve+week+sensor+assessment+in+Parkinson%27s+disease%3A+impact+on+quality+of+life%2E+Mov%2E+Disord%2E+31%2C+1337-1338%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Fisher, J. M., Hammerla, N. Y., Rochester, L., and Andras, P., and Walker, R. W. (2016). Body-worn sensors in Parkinson&#x02019;s disease: evaluating their acceptability to patients. <emphasis>Telemed. J. E Health</emphasis> 22, 63&#x02013;69. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Fisher%2C+J%2E+M%2E%2C+Hammerla%2C+N%2E+Y%2E%2C+Rochester%2C+L%2E%2C+and+Andras%2C+P%2E%2C+and+Walker%2C+R%2E+W%2E+%282016%29%2E+Body-worn+sensors+in+Parkinson%27s+disease%3A+evaluating+their+acceptability+to+patients%2E+Telemed%2E+J%2E+E+Health+22%2C+63-69%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch03" label="3" xreflabel="3">
<title>The REMPARK System</title>
<para role="author"><emphasis role="strong">Joan Cabestany<superscript><emphasis role="strong">1</emphasis></superscript>, J. Manuel Moreno<superscript><emphasis role="strong">1</emphasis></superscript> and Rui Castro<superscript><emphasis role="strong">2</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<para><superscript>2</superscript>Fraunhofer Portugal AICOS &#x2013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</para>
<section class="lev1" id="sec3-1" label="3.1" xreflabel="3.1">
<title>Introduction</title>
<para>As it has been presented and described in previous chapters, Parkinson&#x02019;s Disease is a progressive neurological condition. Unfortunately, there is no known cure for the disease and only treatments focused to the management and mitigation of the different symptoms are available to patients.</para>
<para>A well-designed and adapted technological approach (mainly based on WT and machine learning, as suggested in <link linkend="ch02">Chapter <xref linkend="ch2" remap="2"/></link>) can help both, the patients and their neurologists, for a better management and follow-up of the disease evolution. This will open the possibility to more effective therapies in order to improve patients&#x02019; daily activities. From the beginning, with this specific aim, REMPARK project proposed four main objectives to be covered:</para>
<para>Objective 1: <emphasis role="strong">Real-time motor status identification</emphasis>.</para>
<para>To develop a minimum set of wearable inertial, electronic, intelligent sensors, to register in real-time the ambulatory movements of the patient and to clearly identify the relevant number of parameters, or types of motor disorders associated with Parkinson&#x02019;s Disease.</para>
<para>Objective 2: <emphasis role="strong">Gait improvement system</emphasis>.</para>
<para>To develop a self-calibrating gait guidance system to prevent the gait impairments and therefore minimize the appearance of FOG episodes and falls. The development will be mainly focused on auditory cueing, based on a system able to generate an auditory or acustic signal when necessary (Auditory Cueing System ACS), in order to help patients to improve their gait.</para>
<para>Objective 3: <emphasis role="strong">User interface to get patient&#x02019;s feedback</emphasis>.</para>
<para>To develop and implement a specific user interface on a smartphone to collect feedback directly from the patient. This feedback provided by the patient must have, at least, the following functionalities:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Introduction of routine information such as the medications&#x02019; intake time, quantity and quality of the sleep and other NMS.</para></listitem>
<listitem>
<para>Answer to specific prompts to validate some situations detected by the REMPARK system. For instance, periodically completing medical tailored tests designed by the doctors (based on the UPDRS scale) in order to assess the evolution of the patient with time regarding the non-motor symptoms.</para></listitem>
</itemizedlist>
<para>Objective 4: <emphasis role="strong">REMPARK service for remote management of the disease</emphasis>.</para>
<para>A central server service (REMPARK Server) organized to act as a repository of the processed ambulatory data of the patients, to ease the combination of these data with the Electronic Health Record (EHR) and to facilitate interaction with the neurologist (or medical service), the patient and/or the caregiver.</para>
<para>The present chapter introduces a deeper view of the presented approach, describing the details of the implemented and used system for the works carried out during the evolution of REMPARK project.</para>
</section>
<section class="lev1" id="sec3-2" label="3.2" xreflabel="3.2">
<title>REMPARK System Overview</title>
<para>The developed REMPARK system has been worked-on and designed as a Personal Help System (PHS) that provides a closed-loop detection and treatment capabilities for an improved management of Parkinson&#x02019;s Disease (PD) patients.</para>
<para>From the beginning, the REMPARK architecture was conceived and organized in two different levels:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">The immediate level (BAN &#x02013; Body Area Network)</emphasis>. A minimum set of wearable monitoring sensors should be able to identify in real time the motor status of the patient. The identification of the status is made autonomously using embedded algorithms in the sensor. The sensitivity and specificity of these sensors are better than 80%. A gait guidance system, based on an auditory cueing system ACS, was envisioned as part of this level to help the patients in real time during their daily activities.</para>
<para>The immediate level is also including actuation capabilities that will be triggered by certain conditions detected by the sensors:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem><para>activation of the ACS;</para></listitem>
<listitem><para>automatic administration of a questionnaire;</para></listitem>
<listitem><para>possible remote control of a delivering medication pump.</para></listitem>
</itemizedlist>
<para>A possible inclusion of a remotely-controlled pump was done in REMPARK project as a laboratory exercise with no real tests in the trials with patients. This is a challenging work aiming to give a response to the need of a more accurate and adapted dose control for infusion pump systems. It must be considered as a step forward in the improvement of the QoL of patients with advanced PD.</para>
<para>All the information from and to the immediate level are carried out by a smartphone which is used as a gateway.</para></listitem>
<listitem>
<para><emphasis role="strong">The mid-term level</emphasis> (based on a server). This is where the data provided by the sensors are partially analyzed, along with disease management done automatically or/and by neurologists. This part of the REMPARK system provides interconnection between analysis performed in the sensor and data provided by the neurologist, caregivers or the patient. An important tool at this stage is the Disease Management System (described in <link linkend="ch08">Chapter <xref linkend="ch8" remap="8"/></link>) that opens the possibility to a high level management of PD and to the establishment of interaction between concerned people.</para></listitem>
</itemizedlist>
<para>These two levels and their relationship are represented in <link linkend="F3-1">Figure <xref linkend="F3-1" remap="3.1"/></link>. Below, <link linkend="F3-2">Figure <xref linkend="F3-2" remap="3.2"/></link> shows a more detailed content of the described levels, together with the associated functionality. In these levels, two different groups of algorithms are running. The first group is located in the Immediate level (BAN), mainly in the sensor and smartphone, and it is responsible for the ON/OFF detection, the different symptoms identification and the implementation of the gait guidance system. A second group of algorithms is responsible of the implementation of the Rule Engine at the second level.</para>
<fig id="F3-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-1">Figure <xref linkend="F3-1" remap="3.1"/></link></label>
<caption><para>Hierarchical organization of REMPARK system.</para></caption>
<graphic xlink:href="graphics/ch03_fig001.jpg"/>
</fig>
<fig id="F3-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-2">Figure <xref linkend="F3-2" remap="3.2"/></link></label>
<caption><para>System architecture overview.</para></caption>
<graphic xlink:href="graphics/ch03_fig002.jpg"/>
</fig>
<section class="lev2" id="sec3-2-1" label="3.2.1" xreflabel="3.2.1">
<title>The Immediate Level</title>
<para>The Immediate Level corresponds to the Body Area Network (BAN) and acts in the short-term. It is composed of the sensors, the actuators and the smartphone, which also acts as GPS for providing context-aware information and as an interface for the PD patient, to record their direct feedback especially regarding the non-motor symptoms.</para>
<para>Communications among the elements of the BAN is done through Bluetooth V2.1, allowing enough autonomy for the patient. This level operates autonomously and it is a real operative closed loop. It is auto-adaptive by means of a constant evaluation of the actuator&#x02019;s effect, correcting its behavior in the short-term. The configuration of this level can be changed according to different patients&#x02019; needs.</para>
<para>Considering the details indicated in the Figures 3.1 and 3.2, the main components or sub-systems having a direct interaction with the PD patient are the following:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Sensor module</emphasis>: It is in charge, using appropriate technology, of the continuous monitoring of the patient&#x02019;s movement behaviour. It is able to detect and identify in real-time the different motor-related symptoms suffered by the patient.</para></listitem>
<listitem>
<para><emphasis role="strong">Mobile gateway</emphasis>: As it is inferred from <link linkend="F3-1">Figure <xref linkend="F3-1" remap="3.1"/></link>, it plays a central role in the system. It does not only interact with the remaining components, but also drives their behaviour by setting their functional parameters. In the REMPARK system the mobile gateway is implemented using a commercial smartphone and specifically developed software.</para></listitem>
<listitem>
<para><emphasis role="strong">Drug pump</emphasis>: It is intended to administer an appropriate drug dose depending on the patient&#x02019;s movement parameters (in REMPARK project, this part was only considered, for a feasibility demonstration and was treated from a theoretical point of view with a laboratory proof of concept).</para></listitem>
<listitem>
<para><emphasis role="strong">Auditory cueing system (ACS)</emphasis>: This component provides an auditory pattern intended to assist the patient in the case of abnormal movement patterns (such as FOG or shortened stride length).</para></listitem>
</itemizedlist>
</section>
<section class="lev2" id="sec3-2-2" label="3.2.2" xreflabel="3.2.2">
<title>The Mid-Term Level</title>
<para>The Mid-term Level (also called the Level 2), refers to the actuation in the medium-long term and constitutes a closed semi-automatic loop, as it will allow the intervention of medical professionals. The system is able to send data to the server, allowing the patient&#x02019;s neurologist to regularly follow the evolution of the patient&#x02019;s disease in a more effective manner, as well as being able to take better informed decisions about the adjustment of the pharmacological treatment of the patient using the Disease Management System (DMS). The system is also able to generate alerts, according personalized thresholds, related to the status and evolution of the disease.</para>
<para>Data on the server can be automatically included in an Electronic Health Record (EHR). This way, the correct intelligent data treatment will help to evaluate and predict the evolution of the disease of a particular patient.</para>
<para>Below, the sub-systems responsible for the storage of the data generated at Immediate Level as well as for its high-level analysis are listed. The results of the high-level analysis are available to both the patient and the neurologist or clinician. The clinician can also interact with the system by changing/updating the medication profile of the patient.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Mobile gateway</emphasis>: At this level, it is responsible for sending the data generated at the first level to the REMPARK server and to get the feedback test to be presented to the patient.</para></listitem>
<listitem>
<para><emphasis role="strong">REMPARK server</emphasis>: It is in charge of storing the data provided by the mobile gateway and of making this data available to the Rule Engine, described below.</para></listitem>
<listitem>
<para><emphasis role="strong">Rule Engine</emphasis>: This component filters the raw data stored in the server and makes it available to the patient and the caregiver using an appropriate interface. Through this interface, both the PD patient and the clinician/neurologist can be interconnected. The patient is able to access the personal record stored in the server. The neurologist can access the personal records of the supervised patients and eventually update their treatment plan based on this information.</para></listitem>
</itemizedlist>
</section>
</section>
<section class="lev1" id="sec3-3" label="3.3" xreflabel="3.3">
<title>Definition of the REMPARK System Main Characteristics</title>
<para>This section includes a description of the main characteristics of the system. Some characteristics were included according considerations already contained in the proposal of the project and after the analysis of the results obtained from the answers provided by potential users of the REMPARK system (patients, neurologists and carers) to specific questionnaires elaborated by the consortium [1, 2]. These will imply concrete requirements and constraints for the system that were considered and included in the final version of the tested system.</para>
<para>The indicated references [1, 2] are publicly available reports on these activities which contain details of the administered questionnaires, the constraints of this administration, obtained answers and their analysis. As it is indicated in [1], there are three main conclusions derived from the answers provided by patients to the REMPARK questionnaire:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The most prevalent motor disorders among patients are: ON/OFF phenomena, dyskinesia and FOG.</para></listitem>
<listitem>
<para>The most prevalent gait problems among patients are: &#x0201C;reduced walking speed&#x0201D;, &#x0201C;small steps&#x0201D; and &#x0201C;shu&#x0FB04;ing&#x0201D;. These problems appear both at home and outdoors, and nearly half of the patients use a strategy to improve them.</para></listitem>
<listitem>
<para>Over 80% of patients are familiar with the use of a mobile phone for making calls and sending SMS. However, they are not so familiar with smartphones based on a touch interface.</para></listitem>
</itemizedlist>
<para>Regarding the answers provided by caregivers, as stated in [2], four main conclusions can be derived:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>&#x0201C;Reduced walking speed&#x0201D; and &#x0201C;small steps&#x0201D; are the most clinically relevant symptoms in the mild stages of PD. &#x0201C;Freezing of gait&#x0201D; and &#x0201C;difficulty in turning&#x0201D; are the most clinically relevant symptoms in the moderate stages of PD. In the advanced stages of PD, &#x0201C;falls&#x0201D; arises as a new main clinical occurrence.</para></listitem>
<listitem>
<para>Patients use strategies to improve symptoms mainly in the moderate-advanced stages of PD. However, the strategies that PD patients adopt (mostly the use of a stick) are not considered as useful as verbal cueing (auditory).</para></listitem>
<listitem>
<para>&#x0201C;Reduced walking speed&#x0201D; should be considered a symptom as relevant as &#x0201C;freezing of gait&#x0201D;.</para></listitem>
<listitem>
<para>The moderate stages of PD are the best target for the REMPARK system. This means that the system should pay special attention to the multifaceted clinical expression of PD during these stages.</para></listitem>
</itemizedlist>
<para><link linkend="T3-1">Table <xref linkend="T3-1" remap="3.1"/></link> summarises the requirements for the REMPARK system derived from the feedback got from the final users through the proposed questionnaires.</para>
<table-wrap position="float" id="T3-1">
<label><link linkend="T3-1">Table <xref linkend="T3-1" remap="3.1"/></link></label>
<caption><para>Technical specifications derived from the user feedback</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Symptom detection</td>
<td valign="top" align="left">The system must be able to detect at least the following symptoms: &#x0201C;reduced walking speed&#x0201D;, &#x0201C;small steps&#x0201D;, &#x0201C;freezing of gait&#x0201D;, &#x0201C;dyskinesia&#x0201D;, &#x0201C;bradykinesia&#x0201D; and &#x0201C;falls&#x0201D;.</td>
</tr>
<tr>
<td valign="top" align="left">Patient interface</td>
<td valign="top" align="left">The user interface in the mobile gateway must be operated by a PD patient in any stage of PD.</td>
</tr>
<tr>
<td valign="top" align="left">Symptom mitigation</td>
<td valign="top" align="left">The system must provide auditory cueing upon detection of &#x0201C;reduced walking speed&#x0201D;, &#x0201C;small steps&#x0201D; and &#x0201C;freezing of gait&#x0201D; symptoms.</td>
</tr>
</tbody>
</table>
</table-wrap>
<para>It is worth noting that first and third requirements in <link linkend="T3-1">Table <xref linkend="T3-1" remap="3.1"/></link> were already considered in the original goals and specifications of the REMPARK project, but second one was only detected after the evaluation of the questionnaires.</para>
<para>Concerning the symptom detection requirements of the system, the motor status of the patients will be evaluated based on the following parameters:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Tremor</para></listitem>
<listitem>
<para>Bradykinesia</para></listitem>
<listitem>
<para>Freezing of gait (FOG)</para></listitem>
<listitem>
<para>Stride length</para></listitem>
<listitem>
<para>Gait speed</para></listitem>
<listitem>
<para>Fall indicator</para></listitem>
<listitem>
<para>Dyskinesia</para></listitem>
</itemizedlist>
<para>The final conclusion on ON/OFF state is achieved by a real time execution of the included algorithms and an evaluation of their combination or presence during a given time period.</para>
</section>
<section class="lev1" id="sec3-4" label="3.4" xreflabel="3.4">
<title>Subsystems Specification</title>
<para>In previous sections, main components of the REMPARK system and the processes that enable their interaction have been identified. Based on this, the present section elaborates the main technical specification for each individual component: the sensor module, the ACS Auditory cueing sub-system, the smartphone and the REMPARK platform.</para>
<para>As it will be discussed in <link linkend="ch04">Chapter <xref linkend="ch4" remap="4"/></link>, a very important part of REMPARK project was devoted to the gathering and construction of a Database, with the cooperation of a number of patients in order to extract the necessary knowledge for the development and implementation of the corresponding algorithms to be embedded in the processing part of the final sensor module. These embedded algorithms in the sensor module will be able to process and to determine in real time the presence of specific symptoms in a patient. It must be clarified here that the presented and mentioned sensors hereafter (the wrist and the waist ones) have been used for data gathering and construction of the Database, but after discussion and final conclusions of REMPARK, the wrist sensor was finally not considered in the pilots, where only the sensor module located in the waist of the patient was finally used.</para>
<section class="lev2" id="sec3-4-1" label="3.4.1" xreflabel="3.4.1">
<title>Sensor Module</title>
<para>The sensor module is the subsystem in charge of determining in real time if a specific indicator (of a concrete symptom) appears in the PD patient movement pattern. The detection of the indicators is obtained after a local process of the data acquired by the sensors included in the module. These indicators are sent at regular time intervals to the mobile gateway subsystem, that will thereafter decide the action to be performed based on their values.</para>
<para>The type and number of sensors to be used depend on the specific movement disorders to be detected. As it has been stated in the previous section, the movement disorders to be addressed by the REMPARK system are the following: Tremor, Stride length, Gait speed, Bradykinesia, Falls, Dyskinesia and FOG.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Tremor consists in an involuntary, rhythmical, forward and backwards movements of a body part, which are Caused by the rapid alternating contraction and relaxation of muscles. For three out of every four people who develop Parkinson&#x02019;s Disease (PD), the disease begins with a trembling or shaking in one of the hands. It can also appear in the feet, face or jaw. This rhythmic movement of the extremities in PD patients has a frequency typically between 4&#x02013;7 Hz. Therefore, in order to detect this movement disorder, the REMPARK system should include a sensor unit to be placed in the wrist. This unit should contain a triaxial accelerometer and a data processing unit. In order to provide an indicator whose value is related to the presence of tremor in the hand the data processing unit should be able to carry out sensor readings with a frequency of at least 20 Hz.</para></listitem>
<listitem>
<para>The determination of indicators related to stride length, gait speed and bradykinesia are interrelated, since the gait speed is given by the number of strides in a specified time window, and once stride length and gait speed are determined it is possible to derive an indicator for bradykinesia. Even if the stride length has been determined in the past using gyroscopes placed in the leg [3], it has been demonstrated [4] that a single triaxial accelerometer placed on the patient&#x02019;s waist can be used to accurately measure stride length, gait speed, bradykinesia and falls.</para></listitem>
<listitem>
<para>Dyskinesia is a medication side effect experienced by patients with Parkinson&#x02019;s Disease and shown in the form of involuntary movements. There are many papers in the literature that manage to successfully detect dyskinesia using inertial sensors. The most prominent research work in this area is performed by Manson et al. [5] which uses a triaxial accelerometer placed on the shoulder. The analysis is based on the comparison of a signal&#x02019;s characteristic with the severity of dyskinesia assessed by Abnormal Involuntary Movement Scale (AIMS) while the patient performs the following activities: sitting, talking, writing, drinking, preparing food, eating and walking. Characterizing the signal consists of obtaining the average value of the accelerations in the range of 1 to 3 Hz, obtained through a band-pass filter. This characteristic of the signal is demonstrated to be correlated with the value of the AIMS score. The study included 26 patients with Parkinson&#x02019;s Disease who were monitored for 20 minutes. Since a triaxial accelerometer placed on the waist will be used to measure stride length, gait speed and falls, the data provided by this sensor unit will also be used for detecting dyskinesia.</para></listitem>
<listitem>
<para>Regarding the detection of FOG episodes, the first work that analysed the relationship between the frequency content of the signals generated by triaxial accelerometers and the presence of a FOG episode was presented in [6]. Two accelerometers were placed in the ankles of both healthy people and PD patients. It was observed that normal walking has a principal frequency around 2 Hz, while FOG episodes are characterized by a principal frequency in the range of 6&#x02013;8 Hz. A second study was carried out in [7] with PD patients. In this study, a single triaxial accelerometer was placed on the patient&#x02019;s shin, and the signal was measured on the vertical axis (parallel to the leg). It was found that FOG episodes caused the appearance of frequency components in the range 3&#x02013;8 Hz. This study was continued in [8, 9], where the analysis presented in [7] was extended to accelerometers placed in the patient&#x02019;s thigh and waist. Regarding the results obtained when the sensor was placed on the waist, it was found that they were similar and even better than those obtained when using other body locations. Therefore, the REMPARK system will use the waist accelerometer to derive an indicator related to the rising of a FOG episode. In order to cope with the different measurements that this unit has to carry out the minimum sampling frequency should be 40 Hz.</para></listitem>
</itemizedlist>
<para>From the previous explanation, a decision was initially taken and the sensor module to be used in the REMPARK system was constituted by two sensor units. One of these sensor units must be placed on the patient&#x02019;s wrist and the other on the patient&#x02019;s waist. These sensor units must contain, in principle, a triaxial accelerometer and a data processing unit. However, in order to provide additional contextual information to the acceleration data, it is considered convenient to include sensors too providing information related to the speed (gyroscope) and the orientation (compass). This information may improve the sensitivity and specificity of the measurements related to the movement disorder indicators to be generated by the REMPARK system.</para>
<para>As previously indicated, the sensor module has to communicate using a wireless link, such as Bluetooth, with the mobile gateway of the REMPARK system, in order to make the measurements accessible to both the patient and the caregiver. Therefore, in order to simplify the overall system and to make it more user-friendly it is envisioned that the sensor units placed in the waist and the wrist should establish a communication using the same wireless communication protocol.</para>
<para>It is important to bear in mind that during the construction of the already mentioned REMPARK database the raw data captured by the sensors will not be processed by the sensor units, since the goal of this project phase is to get enough representative data in order to develop efficient processing and detection algorithms. Thus, the sensor module should have some amount of local storage in order to save the sensor recordings. This local memory unit should be easily accessible in order to retrieve the data once the experiments with patients are finished.</para>
<para>Another important aspect to be considered is that the sensor module has to be operated by people with no technical knowledge. Hence, it has to offer a very simple procedure to start/stop its operation and to analyse its status at any time (preferably using visual information). Additionally, it has to be worn during extended periods of time (approximately eight hours during the experiments). This poses a constraint to the physical features (weight and size) of the sensor module, to the materials that have to be in contact with the patient&#x02019;s skin.</para>
<para>According to the above considerations, <link linkend="T3-2">Table <xref linkend="T3-2" remap="3.2"/></link> summarizes some of the main requirements for the sensor module derived from operational features to be exhibited by this subsystem.</para>
<table-wrap position="float" id="T3-2">
<label><link linkend="T3-2">Table <xref linkend="T3-2" remap="3.2"/></link></label>
<caption><para>Some important technical requirements for the sensor module</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Structure</td>
<td valign="top" align="left">The sensor module must contain a sensor unit placed in the patient&#x02019;s waist and a sensor unit placed in the patient&#x02019;s wrist.</td>
</tr>
<tr>
<td valign="top" align="left">Size &#x02013; waist sensor unit</td>
<td valign="top" align="left">The dimensions of the waist sensor unit must be smaller than 150&#x000D7;70&#x000D7;30 mm.</td>
</tr>
<tr>
<td valign="top" align="left">Size &#x02013; wrist sensor unit</td>
<td valign="top" align="left">The dimensions of the wrist sensor unit must be smaller than 80&#x000D7;70&#x000D7;30 mm.</td>
</tr>
<tr>
<td valign="top" align="left">Weight &#x02013; waist and wrist sensor units</td>
<td valign="top" align="left">The weight of the sensor units must be low (around 200 g. for the waist unit and 150 g. for the wrist one)</td>
</tr>
<tr>
<td valign="top" align="left">Battery capacity</td>
<td valign="top" align="left">The battery on the sensor units must permit a normal continuous operation for at least 8 hours.</td>
</tr>
<tr>
<td valign="top" align="left">Operation &#x02013; waist and wrist sensor units</td>
<td valign="top" align="left">The sensor units must be turned on/off using a single button.</td>
</tr>
<tr>
<td valign="top" align="left">User interface</td>
<td valign="top" align="left">The sensor unit must use a single led to display its state.</td>
</tr>
<tr>
<td valign="top" align="left">Communication</td>
<td valign="top" align="left">The sensor must be able to establish a wireless link with the mobile gateway. This requirement is only for the operative part and not used during the database construction phase.</td>
</tr>
<tr>
<td valign="top" align="left">Communication &#x02013; additional specs</td>
<td valign="top" align="left">The waist and wrist sensors must be able to send to the mobile gateway its battery status. The waist sensor must be able to send to the mobile gateway data containing indicators for the following movement patterns: stride length, gait speed, bradykinesia, falls, dyskinesia and FOG.</td>
</tr>
<tr>
<td valign="top" align="left">Communication &#x02013; security</td>
<td valign="top" align="left">The data sent by the waist and wrist sensor units to the mobile gateway must be encrypted.</td>
</tr>
<tr>
<td valign="top" align="left">Sensors &#x02013; waist sensor unit</td>
<td valign="top" align="left">The waist sensor unit must contain a triaxial accelerometer, a triaxial gyroscope and a compass.</td>
</tr>
<tr>
<td valign="top" align="left">Sensors &#x02013; wrist sensor</td>
<td valign="top" align="left">The wrist sensor unit must contain a triaxial accelerometer.</td>
</tr>
<tr>
<td valign="top" align="left">Data sampling rate</td>
<td valign="top" align="left">The waist sensor unit must be able to sample data from the sensors with a frequency of at least 40 Hz.<?lb?> The wrist sensor unit must be able to sample data from the sensors with a frequency of at least 20 Hz. <?lb?>It must be noted that during the Database construction, used frequency was higher (200 Hz for the waist sensor and 80 Hz for the wrist sensor).</td>
</tr>
<tr>
<td valign="top" align="left">Data processing</td>
<td valign="top" align="left">The waist sensor unit must contain a data processing unit able to calculate indicators for the following movement patterns: stride length, gait speed, bradykinesia, falls, dyskinesia and FOG.<?lb?> The wrist sensor unit must contain a data processing unit able to calculate indicators for the following movement patterns: tremor.</td>
</tr>
<tr>
<td valign="top" align="left">Comfort</td>
<td valign="top" align="left">The parts of the sensor unit in contact with the patient&#x02019;s skin must be constructed with a biocompatible material.</td>
</tr>
<tr>
<td valign="top" align="left">Battery certification</td>
<td valign="top" align="left">The Li-ion batteries used in the sensor module must have test certificate according to standard UL 1642.</td>
</tr>
<tr>
<td valign="top" align="left">Battery charger certification</td>
<td valign="top" align="left">The battery chargers used for the sensor module must have a test certificate demonstrating compliance with IEC 60950.</td>
</tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec3-4-2" label="3.4.2" xreflabel="3.4.2">
<title>Auditory Cueing Subsystem</title>
<para>This section describes the REMPARK Auditory Cueing System (ACS) system for gait-cueing and FOG intervention. This system intends to be a self-calibrating/adaptive gait guidance system for helping PD patients in real time, during their daily activities.</para>
<para>PD patients are usually affected by symptoms associated with a reduced motor performance and gait disturbances that affect their ability to walk independently and safely [10]. One of the key problems of PD patient&#x02019;s gait is the particular difficulty with the internal regulation of stride length, reflected as an inability to generate sufficient stride length, even though the control of cadence (or step rate) is intact and can be easily modulated under a variety of conditions [11, 12]. Some patients may increase the stepping frequency to compensate the reduced stride length [12&#x02013;14]. With the disease&#x02019;s progression, other episodic gait disturbances can appear, e.g. start hesitation and FOG episodes [12]. Festination of gait, characterized by small and rapid steps, is also a common symptom of advanced PD [15]. By applying adequate external regulatory rhythmic stimulations, movements&#x02019; speed and amplitude can be modified [16], so that gait performance is improved, even under complex environments [9, 12, 17, 18].</para>
<para>The ACS systems would therefore be able to adapt the rhythm of cueing to the specific needs of each patient and each situation, being activated and deactivated at the adequate times, taking into account the real time feedback sent by inertial sensors (i.e. relative to the gait&#x02019;s quality), as well as the feedback provided by the patient (i.e. a subjective feedback related with the quality of cueing that is being applied).</para>
<section class="lev3" id="sec3-4-2-1" label="3.4.2.1" xreflabel="3.4.2.1">
<title>Gait guidance ACS functional description</title>
<para>The cueing system is intended to be used every day, during daily activities. The smartphone (seen at this point as a control unit) will be responsible for the control of the auditory cueing actuator, and will be able to program the cue parameters taking into consideration the specific needs of the patient in each situation, in a self-adaptive way (<link linkend="F3-3">Figure <xref linkend="F3-3" remap="3.3"/></link>).</para>
<fig id="F3-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-3">Figure <xref linkend="F3-3" remap="3.3"/></link></label>
<caption><para>Simplified representation of the ACS functionalities.</para></caption>
<graphic xlink:href="graphics/ch03_fig003new.jpg"/>
</fig>
<para>The system must be mainly controlled in a self-adaptive way and should not require user intervention to trigger or adapt a cueing response. Thus, it is required that the system operates in real time, together with the feedback provided by inertial sensors.</para>
<para>Since continuous auditory cueing might not be acceptable for PD patients [9] the system will provide the cueing automatically only when required, i.e. when the patient is walking and a context of impaired performance or an inefficient walking pattern is perceived (based on the available REMPARK sensor subsystem measures).</para>
<para>In concrete, the final parameters and symptoms considered for triggering of the ACS system are the presence of a bradykinetic walk and FOG episodes, suffered by the patient (see <link linkend="T3-3">Table <xref linkend="T3-3" remap="3.3"/></link>).</para>
<table-wrap position="float" id="T3-3">
<label><link linkend="T3-3">Table <xref linkend="T3-3" remap="3.3"/></link></label>
<caption><para>Parameters/Measures considered by the ACS</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Parameter/Measure</td>
<td valign="top" align="left">Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Bradykinesia</td>
<td valign="top" align="left">Slow movements, slow walk</td>
</tr>
<tr>
<td valign="top" align="left">FOG episodes</td>
<td valign="top" align="left">Transient period in which gait is halted.</td></tr>
</tbody>
</table>
</table-wrap>
<para>The detection of gait impairments is performed through a real-time comparison with the baseline data characterizing the normal range of walking parameters values for a specific individual patient.</para>
<para>It must be clear that, according to the previous explanation, there exists a very close relationship between stride length, speed of walking, cadence and bradykinetic walk. Hence, changes in these parameters, characterizing a bradykinetic walk, must be referred to baseline measurements of a patient [19]. This means that even if a low stride length is detected, this parameter can be considered normal if the baseline walking speed is also low.</para>
<para>The determination of &#x0201C;normal values&#x0201D; needs to be done carefully, so that meaningful values are considered for impairments detection. To get this information, some initial tests (called here the calibration sessions) can be performed with each patient before starting to use the REMPARK system. The therapist/doctor must be the responsible for conducting these tests, in order to accurately control the protocols and the results. The REMPARK system will also be able to detect the FOG episodes, which are also considered as an input for the ACS subsystem.</para>
<para>Based on the detection of the triggering symptoms and their comparison with the baseline values, the ACS automatically activates or deactivates the cueing. Also given these measures, the cueing rates must be automatically adjusted to the specific needs of the patient in each situation. This autonomy requires a constant evaluation of the effects of cueing on the patient, and the automatic adjustment of cueing rates according to the patient&#x02019;s response. The requirements related to the specific situations are detailed on <link linkend="T3-4">Table <xref linkend="T3-4" remap="3.4"/></link>.</para>
<table-wrap position="float" id="T3-4">
<label><link linkend="T3-4">Table <xref linkend="T3-4" remap="3.4"/></link></label>
<caption><para>General functional requirements of the ACS system</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Cueing type</td>
<td valign="top" align="left">ACS must provide cueing automatically, in a self-adaptive, non-continuous way, taking into account the specific needs of the patient in each situation.</td>
</tr>
<tr>
<td valign="top" align="left">Operation mode</td>
<td valign="top" align="left">Cueing must operate only when the patient is walking.</td>
</tr>
<tr>
<td valign="top" align="left">System interaction</td>
<td valign="top" align="left">ACS must be able to work in real time, together with the feedback provided by sensors.</td>
</tr>
<tr>
<td valign="top" align="left">Functional requirements</td>
<td valign="top" align="left">ACS must be able to detect a bradykinetic gait based on walking speed, stride length and the occurrence of FOG episodes, as measured by movement sensors.</td>
</tr>
<tr>
<td valign="top" align="left">Stimulus type</td>
<td valign="top" align="left">ACS must provide stimulus in the form of sounds.</td>
</tr>
<tr>
<td valign="top" align="left">Sound rhythm</td>
<td valign="top" align="left">Sounds must pace both left and right footfalls.</td>
</tr>
<tr>
<td valign="top" align="left">Alerts</td>
<td valign="top" align="left">ACS must be able to provide voice recordings with alerts and instructions, when required.</td>
</tr>
<tr>
<td valign="top" align="left">Configurability</td>
<td valign="top" align="left">ACS must be able to program the activation and deactivation of sound stimulus at the adequate times/situations.</td>
</tr>
<tr>
<td valign="top" align="left">Adaptation</td>
<td valign="top" align="left">ACS must be able to automatically adapt the rhythm of cues (sound stimulus) to the specific needs of each patient in each situation.</td>
</tr>
<tr>
<td valign="top" align="left">Evaluation and Rating</td>
<td valign="top" align="left">ACS must be able to constantly evaluate the effect of cueing on the patient and to enable the patient to rate the cueing session.</td>
</tr>
</tbody>
</table>
</table-wrap>
<para>The ACS will provide the cueing in the form of sounds. Once the patient hears these sounds, he/she will try to synchronize the rhythm of steps with the rate of the sounds provided. Sound beats can be single (i.e. pace one step per stride) or double (i.e. pace both steps per stride). According to [20], gait is more effectively modulated when both footfalls are paced, which means that a double beat must be used. Specific voice recordings of alerts and information must be produced when the patient is not able to synchronize with the rhythm of cues. These alerts must help the patient to synchronize with cueing rate and ask for some patient&#x02019;s feedback.</para>
<para>The ACS implemented and used in REMPARK (see additional information in <link linkend="ch07">Chapter <xref linkend="ch7" remap="7"/></link>) is comprised of two physical components &#x02013; headphones and the smartphone &#x02013; that will interact (directly or indirectly) with other sub-systems. The smartphone will be able to decide when and how to actuate in each specific situation; headphones are placed on the patient&#x02019;s ear and will produce the sounds acting as cueing. The above <link linkend="F3-3">Figure <xref linkend="F3-3" remap="3.3"/></link> is presenting this architecture.</para>
<para>A headset (ear-set) was selected to be included in the auditory cueing system. Ear-sets are usually small and aesthetic and, as they are placed in a single ear, they enable the patient not only to hear the auditory cueing but also to perceive the auditory stimulus from the surrounding environment.</para>
<para>The auditory stimulus will be provided in the form of metronome sounds. Since different rhythms of stimulus are going to be produced, the easiest way to apply cueing is to use metronome sounds, because its rate is easier to be adapted than, e.g., the music.</para>
<para>Since the headset will produce the sounds streamed by the smartphone, it must therefore be compatible with Advanced Audio Distribution Profile (A2DP). This profile defines how audio can be streamed from one device to another over a Bluetooth connection. A2DP is designed to transfer a unidirectional 2-channel stereo audio stream.</para>
<para>Alternatively, audio can be produced by a non-A2DP device, by channelling the audio to the stream that carries phone call audio to the headset. This option was, also, considered as an option.</para>
</section>
<section class="lev3" id="sec3-4-2-2" label="3.4.2.2" xreflabel="3.4.2.2">
<title>Need of an adaptive ACS</title>
<para>When an external rhythmic auditory pacing is applied, the patient tries to couple his/her footfalls with the beats, which helps to normalize the walking pace (cadence) [20, 21]. As stride length and stride frequency tend to change as a function of walking speed, this adaptation of cadence might offer a strategy to indirectly influence the stride length regulation in these patients, while controlling for walking speed [19].</para>
<para>The effects of auditory cueing may, however, differ for patients with or without FOG, referred as &#x0201C;freezers&#x0201D; and &#x0201C;non-freezers&#x0201D;, respectively [18]. It is well known that cueing rates higher than baseline walking rate are contraindicated for freezers. Based on the study by [22], it is recommended the use of a lower rate setting for freezers and an increase of up to 10% for non-freezers. In both cases, the latest goal of training with the ACS is to maximize stride length while walking at as fast a cadence as possible. If these two variables are increased during training, then walking speed is also increased [16].</para>
<para>The cueing rate settings need, then, a careful consideration, i.e. the intended speed of walking and the quality of movements, and the different responses to the cues by different subgroups of patients suffering from PD. Given these conditions, a set of requirements related with the auditory cueing rate must be carefully considered:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Preference</para></listitem>
<listitem>
<para>Safety</para></listitem>
<listitem>
<para>Walking rhythm</para></listitem>
<listitem>
<para>Different modalities</para></listitem>
<listitem>
<para>Adaptation to the user</para></listitem>
</itemizedlist>
<para>As the person can dictate his/her own preferred walking rhythm, the perception of this baseline rhythm is crucial, so that REMPARK ACS can be the most fitted and comfortable as possible to each situation. The comfortable walking rate is used as a basis to establish the auditory cueing tempo being provided if it is necessary.</para>
<para>The baseline rhythm can be perceived when gait is considered normal (without evident motor symptoms). After the person has started to walk a few strides, it is possible to estimate this rhythm (at least 3 strides are required to reach a steady-state walking in healthy young subjects [23]). When this estimation is not possible, the normal cadence at the preferred speed, as calculated during the calibration session, can be used. When setting the cueing rates, it is important to guarantee that the applied rates will never compromise the safety of the person, both during dual task and walk alone.</para>
<para>Therefore, gait cannot be stimulated beyond the person&#x02019;s limits and the stimulus cannot provide a negative effect on the walking pattern of the individual. A too high cueing rate, for example, may lead to small steps (low stride length) at a high cadence, which is an inefficient walking pattern.</para>
<para>As PD patients face different problems and intensities of problems considering the different stages of the disease and medication states (i.e. ON/OFF state and freezer/non-freezer classification) [24, 25], the ACS system must enable the introduction of different settings/configurations for different patients.</para>
<para>The self-adaptive cueing system will have the possibility to be adjusted/modified in several ways by the patient and by the doctor/therapist. The ACS system must offer the following characteristics regarding user&#x02019;s interaction: configurability to the specific needs of different patients, configuration of different parameters done by caregivers (rate, modality, baseline, rate change &#x02026;), voluntary deactivation, adjustment of the volume and the tone.</para>
</section>
</section>
<section class="lev2" id="sec3-4-3" label="3.4.3" xreflabel="3.4.3">
<title>Drug Delivery Pump Considerations</title>
<para>The development of a wireless communication module for subcutaneous infusion pumps of liquid medicines opens an opportunity for real-time control of the applied dose. A system of closed-loop control would be possible for the case of some diseases in which the result of treatment can be measured by a sensor, i.e. the drug infusion could be adjusted to the needs of the patient in real time.</para>
<para>This idea has been explored in the case of diabetes, in which the glucose level in plasma can be measured accurately and thus this information may be used to control the basal dose of insulin to be delivered via a subcutaneous pump infusion. From this hypothesis, various feedback systems that include automatic and semi-automatic (with a doctor in the decision loop) feedback have been successfully developed, in which insulin infusion is controlled according to the level of glucose in the blood. In contrast, drugs for Parkinson&#x02019;s treatment are often given using a pre-established scheduling and dosage. However, regardless of the route of administration, intermittent delivery of the programmed dosage produces fluctuations in the level of the drug in plasma (known as &#x02018;peaks and valleys&#x02019;) that produce variations in the effects of the drug in the central nervous system.</para>
<para>The amount of drug in each administration and the time between administrations is calculated so that the peaks of plasma do not exceed the upper therapy limit (which may produce unwanted side effects) and that the valleys do not fall below the lower therapy limit (which may cause the therapeutic effect to disappear). Unfortunately, it is not always possible to maintain drug levels in plasma within the therapeutic range. What is more, as the disease progresses, the goal of staying in the therapeutic range is increasingly difficult to achieve and therefore, the time intervals between administration of drug become shorter and the doses higher. Contradictory to this, such doses and time intervals seldom completely control symptoms and therefore, the OFF periods and dyskinesias occur eventually.</para>
<para>Recently, it has been hypothesized that if the drug levels are maintained within the therapeutic range, control of symptoms associated with Parkinson&#x02019;s Disease will be improved substantially [26].</para>
<para>To this end, therapeutic solutions are being developed, aimed at eliminating the programming/intermittent administration of medication and replacing it by a continuous, controlled administration. It is precisely for this reason that subcutaneous administration of dopaminergic drugs was made possible by the development of infusion pumps that maintain drug levels in plasma in the desired range for as long as possible.</para>
<para>The purpose of using these pumps is to maintain the level of drug in plasma within the desired range, and, at least, change the dose on a schedule based on time (different doses depending on the time of day, assuming the needs of the patient). The development of &#x0201C;automatic&#x0201D; infusion pumps, able to adjust the drug dose based on the patient&#x02019;s symptoms will be welcomed both by patients and by doctors as a breakthrough in controlling the symptoms of Parkinson&#x02019;s Disease.</para>
<para>Apomorphine is an agonist dopaminergic with a very short average life, which is administered subcutaneously. There is extensive experience in the use of apomorphine for the treatment of Parkinson&#x02019;s Disease, including its administration in the form of bolus or flow for the release of &#x0201C;lock states&#x0201D; and the corresponding basal treatment.</para>
<para>In order to address the symptoms in real time with apomorphine, a subcutaneous infusion pump that can adapt to them is required, that is, it should receive orders from a device capable of monitoring symptoms.</para>
<para>Even if drug infusion pumps were not tested with patients within the framework of the REMPARK project, one of the project goals was to test if the REMPARK system may be useful to create an automatic or semi-automatic feedback loop that will improve the treatment of PD patients. For this purpose, a commercial apomorphine infusion pump was used in the REMPARK system. The pump was modified with the necessary electronic components so that it was able to communicate with the mobile gateway so as to receive commands related to the drug dose to be administered. The pump should be able to operate both in bolus and in infusion mode. Additionally, the electronic system added to the pump should permit a manual user interaction.</para>
<para>In REMPARK project, the organization of a specific pilot action, with real patients, using a drug delivery system control was discarded because it was out of the real possibilities of the project activity. Alternatively, it was decided to consider this effective possibility, preparing all the requirements and conditions from a technical and functional point of view. This activity was based on an already developed experience by some of the participants [27].</para>
</section>
<section class="lev2" id="sec3-4-4" label="3.4.4" xreflabel="3.4.4">
<title>The smartphone Technical Requirements</title>
<para>The smartphone is at the core of the REMPARK BAN, receiving data from sensors and sending instructions to actuators. Furthermore, it serves as a gateway between the BAN and the server, by receiving settings and preferences from the server and sending the data gathered in the BAN. In consequence, the smartphone is a critical device in the BAN, as without it the system would be unusable. <link linkend="F3-4">Figure <xref linkend="F3-4" remap="3.4"/></link> shows the connections of the smartphone on the REMPARK system, as well as the directions of the information exchanged.</para>
<fig id="F3-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-4">Figure <xref linkend="F3-4" remap="3.4"/></link></label>
<caption><para>Smartphone connectivity and information flows.</para></caption>
<graphic xlink:href="graphics/ch03_fig004.jpg"/>
</fig>
<para>We split the requirements of the smartphone into hardware and software. The hardware requirements are mainly related to the characteristics of the smartphone including connectivity. It must provide battery life, as well as other usability requirements.</para>
<para>Connectivity-wise, the smartphone should be able to form the BAN itself, connecting to all sensors and actuators using Bluetooth protocol. To connect to the caretaker server, it will need an Internet access enabled. Here, cellular connectivity is mandatory (GMS or UMTS) and Wi-Fi will be used whenever possible. Although most smartphones in the market today already come with all these radio interfaces, we need to ensure that they are present and available; for instance, we need to ensure that the smartphone has a SIM card with a data plan enabled, so that cellular data is available. As this is a critical component of the system, we need to ensure that it is always on, or at least minimize its downtime. To this end, it is critical to have a suitable battery that will last for the whole day while the patient is away from a power source. We expect the system to last at least 8 hours working on battery power alone, as this is the maximum expected time a person will be away from a power source.</para>
<para>With regards to the usability of the smartphone, we expect it to be big enough and have enough resolution so that older adults with some visual difficulties can use it. Furthermore, the device needs a touch screen interface to provide direct interaction and a more reduced learning curve.</para>
<para>As a result of a review of relevant literature, and interviews with doctors and relatives, we identified major changes on PD affected people&#x02019;s fine motor skills, changes that makes it very hard for them to do precise movements both on ON and OFF stages. Hence, we need a screen large enough to accommodate buttons as big as necessary in order to offer them good interaction experience.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>On/OFF state, they have their fine motor movements mostly conditioned by Bradykinesia and rigidity. Causing slower movements and loss of agility thus precise movements become very difficult. Possibly they can do some precise selections but with great effort. Whereas tremor although being generally a rest tremor, sometimes can still be active while on movement, and thus makes a precise movement even harder.</para></listitem>
<listitem>
<para>While on ON state even when most PD symptoms are gone, on later stages of the disease, PD affected people have dyskinesia which can be impairing as the other symptoms, since it make them do involuntary movements and thus making it very difficult to do precise selections as well.</para></listitem>
</itemizedlist>
<para>Moreover, with the aim of interacting with a touch screen, a user does not need to apply much pressure to activate it, which is also beneficial to PD affected people since they also have lack of strength and are much more comfortable with smooth gestures.</para>
<para>In order to ensure these preconditions and to guarantee that we can extend the smartphone functionality in any way we require it to have an open-source operating system and main drivers, so that we can access, change and compile them to any software version we need.</para>
<para>Concerning the smartphone related software aspects, they will consist of distinct components:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Server Communication:</emphasis> The smartphone will need to exchange information with the REMPARK Server.</para></listitem>
<listitem>
<para><emphasis role="strong">End-user Applications:</emphasis> The smartphone will provide a number of applications related to the management of the disease or the REMPARK system.</para></listitem>
<listitem>
<para><emphasis role="strong">Data Processing and Event Detector:</emphasis> The smartphone will analyse the data received from the sensors and will raise specific events.</para></listitem>
<listitem>
<para><emphasis role="strong">Sensor Communication:</emphasis> The smartphone will gather information from waist sensor.</para></listitem>
<listitem>
<para><emphasis role="strong">Actuator Communication:</emphasis> The smartphone will control the actuators upon receiving orders from the Server, an input from the user or after processing the data gathered by the sensors.</para></listitem>
</itemizedlist>
<para>In regards of the Server Communication, the smartphone must guarantee the communication with the REMPARK server, establishing a communication channel with the caretaker server whenever needed, and use encryption methods that must ensure:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Data integrity:</emphasis> both the smartphone and the server must guarantee that the information they receive was correctly transmitted and unaltered.</para></listitem>
<listitem>
<para><emphasis role="strong">Data security:</emphasis> the mechanism must ensure that no one else can have access to the information being transmitted, as well as ensure that no one can alter the information while it is being transmitted.</para></listitem>
<listitem>
<para><emphasis role="strong">Authentication:</emphasis> both the smartphone and the server will be able to authenticate themselves to each other, thus guaranteeing that information is being transmitted to the right party.</para></listitem>
<listitem>
<para><emphasis role="strong">Non-repudiation:</emphasis> tightly coupled to the authentication mechanism, non-repudiation aims at guaranteeing that: (1) every message is signed, so that the sender cannot deny that it had sent the message; (2) no one else can impersonate the sender. This will guarantee that every message is accounted for.</para></listitem>
</itemizedlist>
<para>The final set of the smartphone requirements is related to provide a set of applications, both giving users and medical caretaker&#x02019;s tools to better manage this disease. To the users, it provides assistive applications to help them with their daily lives and to the medical caretakers it provides valuable medical information of the state of the disease. These applications range from actuators controllers (e.g. for auditory cueing), assistive applications to help the users with their daily living (e.g. medication reminders) questionnaires to input medical or routine information and prompts to validate specific situations detected when acute events are detected.</para>
<table-wrap position="float" id="T3-5">
<label><link linkend="T3-5">Table <xref linkend="T3-5" remap="3.5"/></link></label>
<caption><para>Requirements of the smartphone end-user applications</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Questionnaires</td>
<td valign="top" align="left">The smartphone must enable the user to answer medical questionnaires sent by the doctor.</td>
</tr>
<tr>
<td valign="top" align="left">User answers</td>
<td valign="top" align="left">The smartphone must enable the user to answer specific prompts to validate alerting detected situations.</td>
</tr>
<tr>
<td valign="top" align="left">User input</td>
<td valign="top" align="left">The smartphone should enable the user to input routine information such as the time of intake of the medications, quantity and quality of the sleep or other information.</td>
</tr>
<tr>
<td valign="top" align="left">Actuators</td>
<td valign="top" align="left">The smartphone should enable the user to adjust the behaviour of the auditory cueing.</td>
</tr>
</tbody>
</table>
</table-wrap>
<para>The smartphone is also the interface to the caretaker server, so it must provide a way for patients to use the services provided by the server, e.g., check health status, contact the doctor, see appointments. <link linkend="T3-5">Table <xref linkend="T3-5" remap="3.5"/></link> provides an overview of these requirements.</para>
<para>The REMPARK smartphone must receive and process the data from the sensors. The processing will be achieved through a set of algorithms to assess the status of the patient and control the BAN actuators. These algorithms will be adapted to the particular needs of each user. As such, the smartphone will fine-tune the algorithms by updating its information with the caretaker server. Furthermore, after analysing the data, the smartphone should decide on the action, or event, to trigger. These actions can be:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>to enable an actuator for the interaction with the patient</para></listitem>
<listitem>
<para>to raise an alarm so that medical staff can respond</para></listitem>
<listitem>
<para>to ask some input, or confirmation, to the patient.</para></listitem>
</itemizedlist>
<para>The smartphone will also provide an Actuator Communication component to interact with the actuators. The actuator actions must be triggered either by the smartphone in the cases described above, or directly by the server if, for instance the medical staff decides that the patient should receive some input in real time (e.g., a medical questionnaire). Furthermore, when communicating with the actuators, the smartphone must ensure that: (1) messages sent to the actuator are not replicated, so that the actuator does not trigger the same action twice; (2) no messages for the actuator are lost, to guarantee that the actuator really acts; (3) actions of the actuator are personalized for each patient, for instance, the auditory cueing system uses the frequencies that better suit the patient.</para>
</section>
<section class="lev2" id="sec3-4-5" label="3.4.5" xreflabel="3.4.5">
<title>The REMPARK Platform Architecture and Functionality</title>
<para>The REMPARK platform is composed of all the services that will store and process information, namely, the server and the Rule Engine blocks. While the so-called server will have the role of keeping the database and hosting all the services, the Rule Engine will use these data to make further analysis and store new processed-data. All this information will be used by the medical application to show relevant information to clinical professionals that is why it is got an interaction with the server. Likewise, the Mobile Gateway will also interface the server to store measures and alerts. <link linkend="F3-5">Figure <xref linkend="F3-5" remap="3.5"/></link> shows an overall architecture view of the main blocks that make up the REMPARK&#x02019;s platform and its main interactions.</para>
<fig id="F3-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-5">Figure <xref linkend="F3-5" remap="3.5"/></link></label>
<caption><para>Platform functional architecture.</para></caption>
<graphic xlink:href="graphics/ch03_fig005.jpg"/>
</fig>
<para>An important element of the REMPARK platform is the server, enabling the potential service. There are two main functionalities. The first one deals with measures and the second one with alerts. Both functions are deployed as REMPARK&#x02019;s services in the server and they will provide also methods to insert and extract both measures and alerts of any type. These services will be exposed so that the blocks that interface the Server (i.e. Rule Engine, Medical Application and Mobile Gateway) can use them.</para>
<para>Other identified service is the Patient Service. The Server must provide a way to register new patients and associate them with their information (i.e. measures, alerts) as well as providing some basic information report about them and their associated hospital, if necessary. Finally, it might be useful to have questionnaires&#x02019; information available and that is why a specific service dealing with this functionality should be implemented. <link linkend="F3-6">Figure <xref linkend="F3-6" remap="3.6"/></link> shows the services that the server will expose to their interfaces.</para>
<fig id="F3-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F3-6">Figure <xref linkend="F3-6" remap="3.6"/></link></label>
<caption><para>Server services.</para></caption>
<graphic xlink:href="graphics/ch03_fig006.jpg"/>
</fig>
<para><link linkend="T3-6">Table <xref linkend="T3-6" remap="3.6"/></link> summarizes the main technical requirements of the REMPARK server</para>
<table-wrap position="float" id="T3-6">
<label><link linkend="T3-6">Table <xref linkend="T3-6" remap="3.6"/></link></label>
<caption><para>Technical requirements for the REMPARK server</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Service</td>
<td valign="top" align="left">Server must expose some public services so that the Mobile Gateway, the Rule Engine and the Professional Application can access the generated data.</td>
</tr>
<tr>
<td valign="top" align="left">Service</td>
<td valign="top" align="left">Server must provide services that are able to store and extract for each specific patient.</td>
</tr>
<tr>
<td valign="top" align="left">Measures</td>
<td valign="top" align="left">Server must provide a service to store measures which will be used by the Mobile Gateway, Rule Engine and the Professional&#x02019;s application.</td>
</tr>
<tr>
<td valign="top" align="left">Measures</td>
<td valign="top" align="left">New measures must be able to be added in a simple fashion.</td>
</tr>
<tr>
<td valign="top" align="left">Getting Measures</td>
<td valign="top" align="left">Server must provide a service that allows receiving measures and is accessible by the Mobile Gateway, Rule Engine and Professional Application.</td>
</tr>
<tr>
<td valign="top" align="left">Alerts</td>
<td valign="top" align="left">Server must provide a service to notify about alerts which will be used by the Mobile Gateway, Rule Engine and the Professional&#x02019;s application.</td>
</tr>
<tr>
<td valign="top" align="left">Alerts</td>
<td valign="top" align="left">New alerts must be able to be added in a simple fashion</td>
</tr>
<tr>
<td valign="top" align="left">Storing Alerts &#x02013; Mobile Gateway</td>
<td valign="top" align="left">
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Patient has fallen.</para></listitem>
<listitem>
<para>No connection with motion sensor.</para></listitem>
<listitem>
<para>Emergency button.</para></listitem>
<listitem>
<para>Sensor is running out of battery.</para></listitem>
<listitem>
<para>Mobile phone is running out of battery.</para></listitem>
</itemizedlist></td>
</tr>
<tr>
<td valign="top" align="left">Storing Alerts &#x02013; Rule Engine</td>
<td valign="top" align="left">
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Mobile Gateway has lost connection with the platform.</para></listitem>
<listitem>
<para>Mobile Gateway has resumed connection with the platform.</para></listitem>
</itemizedlist></td>
</tr>
</tbody>
</table>
</table-wrap>
<section class="lev3" id="sec3-4-5-1" label="3.4.5.1" xreflabel="3.4.5.1">
<title>Important functional parts</title>
<para>As it was indicated in <link linkend="F3-2">Figure <xref linkend="F3-2" remap="3.2"/></link>, there is a set of important functional pieces embedded in the REMPARK server that are crucial for the implementation of its final functionality. They are the Rule Engine sub-system (RE), the Disease Management System (DMS) and the user-Web interface.</para>
<section class="lev4" id="sec3-4-5-1-1" label="3.4.5.1.1" xreflabel="3.4.5.1.1">
<title>Rule Engine</title>
<para>The Rule Engine (RE) is a subsystem which is intended to analyze and process data from sensors at regular time intervals. The main idea is to perform tasks, such as post processing (e.g. filtering and transformation) or data analysis (e.g. verify that the most recent pulse and/or blood pressure measurement was within an acceptable range), at regular time intervals. The tasks and their timing were defined by medical and technical partners along the project.</para>
<para>Four components make up the RE: (1) a timer, (2) a processing service, (3) a task manager and (4) a data manager. The data manager encapsulates the access to the main REMPARK database. It is the main interface to REMPARK system and provides the means to read and write data (i.e. measures and alerts). The task manager will decide when a task needs to be executed at a certain point in time. The processing service is fed with a set of tasks which it executes. A timer is used to (re-)initialize the processing of tasks at regular time intervals.</para>
<para>In order to implement the tasks, it must be specified: (1) how often a particular task needs to be performed (e.g. every minute, every five minutes), (2) the data that the performance of this particular task requires (e.g. pulse data or data from the inertial sensor), (3) how recent the data needs to be (e.g. last fifteen minutes, at least two hours old or just the most recent value) and (4) the task itself (e.g. check whether pulse is within acceptable range).</para>
</section>
<section class="lev4" id="sec3-4-5-1-2" label="3.4.5.1.2" xreflabel="3.4.5.1.2">
<title>Disease Management System</title>
<para>The Disease Management System (DMS) is an application for managing the patient&#x02019;s health by the medical staff. Data and medical information are integrated into the DMS to support medical decisions. These decisions have influence on changes in the treatment plan and raising alerts to the medical team who has to take care of it. The DMS for REMPARK was developed as a web application using the .NET platform with C# as the programming language.</para>
<para>The DMS is based on the REMPARK database as the resource for every data coming from the patient. The information is sent through the communication module and written to the database. The DMS will have access to the data as a raw data and to the processed data coming from the RE.</para>
<para>Every user of the DMS will be linked to a specific user profile. Every profile will be exposed to the relevant data according to pre-defined specifications. Four profiles have been defined:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Supervisor &#x02013; The main authority in the site (Doctor, nurse or other) that will have access to the management parts of the system. The supervisor can register new users and manage the profiles.</para></listitem>
<listitem>
<para>Doctor &#x02013; The Doctor is the highest medical authority in the call center/ point of care. Therefore, the doctor will have full access to the treatment plans of the patients related to the specific patients&#x02019; doctor.</para></listitem>
<listitem>
<para>Nurse &#x02013; Every nurse will be assigned to several patients who will be monitored by another specific nurse. The supervisor will have the ability to allow one nurse to access another nurse&#x02019;s patient in case of absence of the nurses. This exceptional access will be time limited. A nurse can be assigned also to all patients at the call center.</para></listitem>
<listitem>
<para>Patient &#x02013; The patient will be related as a DMS user in order to allow the patient access a web interface/web site for watching the information related to him/her. A patient cannot be deleted from the database. Instead, the patient&#x02019;s status can be changed to &#x0201C;Not Active&#x0201D; and it will not be shown in the DMS lists (or report) but will remain in the database.</para></listitem>
</itemizedlist>
<para>Important operative tools, included in the DMS are:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Patient&#x02019;s Record. The patient&#x02019;s record must include the patient details, patient relative details (a contact person in case of emergency), a technical part with documentation of the equipment implemented in the patient&#x02019;s home (ID, IP, etc.) and a treatment plan.</para></listitem>
<listitem>
<para>Treatment Plan. For each patient registered in the REMPARK program a treatment plan is created by the neurologist according to the patient&#x02019;s evaluation and clinical history. The treatment plan will include the necessary exercises, medications, normal ranges for every measurement the patient will have the sensors connected to the Mobile Gateway at the patient&#x02019;s home.</para></listitem>
<listitem>
<para>All of the above will be documented in the DMS. The treatment plan can be viewed by any of the medical team assigned to the patient but only the doctor can change an existing medication treatment plan. In some cases, a nurse could also be able to change the treatment plan. These special cases, if any, will be defined in the Clinical Protocol. A change in the treatment plan can be a result of changes in the patient&#x02019;s health, patient&#x02019;s environment, etc.</para></listitem>
<listitem>
<para>Alerts. The alerts will be raised in two ways.</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Alerts that were sent by the Rule Engine after processing raw data.</para></listitem>
<listitem>
<para>Alerts that came directly from the Mobile Gateway without any pre-processing.</para></listitem>
</orderedlist>
</listitem>
<listitem>
<para>Clinical protocols. The clinical protocols can be described as set of flow charts allowing the neurologists to make decisions according to the collected information. It is actually a set of medical instructions for every situation, change (or lack of change) in the patient status. These protocols can be updated or changed from time to time according to the medical considerations.</para></listitem>
</itemizedlist>
<para><link linkend="T3-7">Table <xref linkend="T3-7" remap="3.7"/></link> compiles the requirements of the DMS according to the description.</para>
<table-wrap position="float" id="T3-7">
<label><link linkend="T3-7">Table <xref linkend="T3-7" remap="3.7"/></link></label>
<caption><para>Compiled requirements for the DMS</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Requirement Heading</td>
<td valign="top" align="left">Requirement Description</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">BAN data</td>
<td valign="top" align="left">DMS will store all data from the BAN.</td></tr>
<tr>
<td valign="top" align="left">Medical monitoring</td>
<td valign="top" align="left">DMS will monitor medical aspects of the patient.</td>
</tr>
<tr>
<td valign="top" align="left">Technical monitoring</td>
<td valign="top" align="left">DMS will monitor technical aspects of the patient regarding the REMPARK project.</td>
</tr>
<tr>
<td valign="top" align="left">Alerts</td>
<td valign="top" align="left">DMS will raise alerts when information about irregular behaviour or measurement will come from the gateway.</td>
</tr>
<tr>
<td valign="top" align="left">Questionnaires</td>
<td valign="top" align="left">DMS will allow managing questionnaires.</td>
</tr>
<tr>
<td valign="top" align="left">Treatment plan</td>
<td valign="top" align="left">The treatment plan will be created in the DMS.</td>
</tr>
<tr>
<td valign="top" align="left">Data integrity</td>
<td valign="top" align="left">No data could be deleted from the database.</td>
</tr>
<tr>
<td valign="top" align="left">Monitoring interface</td>
<td valign="top" align="left">The DMS will have a monitoring interface.</td>
</tr>
<tr>
<td valign="top" align="left">Data interface</td>
<td valign="top" align="left">The DMS will have an interface for showing patient&#x02019;s data.</td>
</tr>
<tr>
<td valign="top" align="left">Website</td>
<td valign="top" align="left">The DMS will have a patient personal website.</td>
</tr>
<tr>
<td valign="top" align="left">Reports</td>
<td valign="top" align="left">The DMS will be able to publish reports.</td></tr>
</tbody>
</table>
</table-wrap>
</section>
</section>
<section class="lev3" id="sec3-4-5-2" label="3.4.5.2" xreflabel="3.4.5.2">
<title>Platform technical constraints</title>
<para>Before analysing the different services that must be supported by the server, it is important to estimate important parameters that can compromise the performance of the whole system, such as the maximum storage, the maximum number of simultaneous transactions and the bandwidth.</para>
<para>Just as an example, calculations were made considering the constraints imposed by the pilots organized in REMPARK project. Final technical decisions were:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Maximum storage requirement of 100 Gbytes, permitting to operate with 60 patients during 1,5 years, considering that a probable transmission rate of 1 Kbyte per minute should be necessary, with the sensor connected during 12 hours a day.</para></listitem>
<listitem>
<para>Concerning the bandwidth, it was estimated that 1 Mbps channel is more than enough for the requirements of REMPARK.</para></listitem>
<listitem>
<para>The maximum number of parallel transactions, considering the previous figures, overcome the necessary characteristics.</para></listitem>
</itemizedlist>
</section>
</section></section>
<section class="lev1" id="sec3-5" label="3.5" xreflabel="3.5">
<title>Conclusion</title>
<para>The present chapter has presented and described the architecture, functionality and technical requirements of the REMPARK system, organized along some different sub-systems specifically designed for fulfilling the functional objectives of the proposed project, finally implemented and tested in real piloting experiences.</para>
</section>
<section class="lev1" id="sec3-6">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>REMPARK Deliverable D1.1 &#x02013; Questionnaire addressed to patients. Answers and statistical results. Publicly available.</para></listitem>
<listitem>
<para>REMPARK Deliverable D1.2 &#x02013; Questionnaire addressed to doctors/physiotherapists. Answers and statistical results. Publicly available.</para></listitem>
<listitem>
<para>A. Salarian et al., &#x0201C;Gait Assessment in Parkinson&#x02019;s Disease: Toward an Ambulatory System for Long-Term Monitoring,&#x0201D; <emphasis>IEEE Transactions on Biomedical Engineering</emphasis>, vol. 51, no. 8, pp. 1434&#x02013;1443, August 2004. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+Salarian+et+al%2E%2C+%22Gait+Assessment+in+Parkinson%27s+Disease%3A+Toward+an+Ambulatory+System+for+Long-Term+Monitoring%2C%22+IEEE+Transactions+on+Biomedical+Engineering%2C+vol%2E+51%2C+no%2E+8%2C+pp%2E+1434-1443%2C+August+2004%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. Rodr&#x00ED;guez-Molinero et al., &#x0201C;Detection of Gait Parameters, Bradykinesia, and Falls in Patients with Parkinson&#x02019;s Disease by Using a Unique Triaxial Accelerometer,&#x0201D; <emphasis>Movement Disorders</emphasis>, vol. 22, no. S3, p. S646, September 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+Rodr%EDguez-Molinero+et+al%2E%2C+%22Detection+of+Gait+Parameters%2C+Bradykinesia%2C+and+Falls+in+Patients+with+Parkinson%27s+Disease+by+Using+a+Unique+Triaxial+Accelerometer%2C%22+Movement+Disorders%2C+vol%2E+22%2C+no%2E+S3%2C+p%2E+S646%2C+September+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. J. Manson et al., &#x0201C;An Ambulatory Dyskinesia Monitor,&#x0201D; <emphasis>J. Neurol Neurosurg Psychiatry</emphasis>, vol. 68, no. 2, pp. 196&#x02013;201, February 2000. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+J%2E+Manson+et+al%2E%2C+%22An+Ambulatory+Dyskinesia+Monitor%2C%22+J%2E+Neurol+Neurosurg+Psychiatry%2C+vol%2E+68%2C+no%2E+2%2C+pp%2E+196-201%2C+February+2000%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. H. Han, W. J. Lee, T. B. Ahn, B. S. Jeon, and K. S. Park, &#x0201C;Gait Analysis for Freezing Detection in Patients with Movement Disorder Using Three Dimensional Acceleration System,&#x0201D; in <emphasis>Proceedings of 25th IEEE EMBS</emphasis>, Cancun, 2003, pp. 1863&#x02013;1865. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+H%2E+Han%2C+W%2E+J%2E+Lee%2C+T%2E+B%2E+Ahn%2C+B%2E+S%2E+Jeon%2C+and+K%2E+S%2E+Park%2C+%22Gait+Analysis+for+Freezing+Detection+in+Patients+with+Movement+Disorder+Using+Three+Dimensional+Acceleration+System%2C%22+in+Proceedings+of+25th+IEEE+EMBS%2C+Cancun%2C+2003%2C+pp%2E+1863-1865%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>S. T. Moore, H. G. MacDougall, and W. G. Ondo, &#x0201C;Ambulatory Monitoring of Freezing of Gait in Parkinson&#x02019;s,&#x0201D; vol. 167, no. 2, pp. 340&#x02013;348, January 2008. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=S%2E+T%2E+Moore%2C+H%2E+G%2E+MacDougall%2C+and+W%2E+G%2E+Ondo%2C+%22Ambulatory+Monitoring+of+Freezing+of+Gait+in+Parkinson%27s%2C%22+vol%2E+167%2C+no%2E+2%2C+pp%2E+340-348%2C+January+2008%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. B&#x00E4;chlin et al., &#x0201C;Online Detection of Freezing of Gait in Parkinson&#x02019;s Disease Patients: A Performance Characterization,&#x0201D; in <emphasis>Proceedings of the 4th International Conference on Body Area Networks</emphasis>, Los Angeles, 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+B%E4chlin+et+al%2E%2C+%22Online+Detection+of+Freezing+of+Gait+in+Parkinson%27s+Disease+Patients%3A+A+Performance+Characterization%2C%22+in+Proceedings+of+the+4th+International+Conference+on+Body+Area+Networks%2C+Los+Angeles%2C+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. B&#x00E4;chlin et al., &#x0201C;A wearable system to assist walking of Parkinson&#x02019;s disease patients,&#x0201D; <emphasis>Methods of Information in Medicine</emphasis>, vol. 49, no. 1, pp. 88&#x02013;95, January 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+B%E4chlin+et+al%2E%2C+%22A+wearable+system+to+assist+walking+of+Parkinson%27s+disease+patients%2C%22+Methods+of+Information+in+Medicine%2C+vol%2E+49%2C+no%2E+1%2C+pp%2E+88-95%2C+January+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. E. Morris, F. Huxham, J. McGinley, K. Dodd, and R. Iansek, &#x0201C;The biomechanics and motor control of gait in Parkinson disease,&#x0201D; <emphasis>Clinical Biomechanics</emphasis>, vol. 16, no. 6, pp. 459&#x02013;470, July 2001. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+E%2E+Morris%2C+F%2E+Huxham%2C+J%2E+McGinley%2C+K%2E+Dodd%2C+and+R%2E+Iansek%2C+%22The+biomechanics+and+motor+control+of+gait+in+Parkinson+disease%2C%22+Clinical+Biomechanics%2C+vol%2E+16%2C+no%2E+6%2C+pp%2E+459-470%2C+July+2001%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. M. Hausdorff, &#x0201C;Gait dynamics in Parkinson&#x02019;s disease: common and distinct behavior among stride length, gait variability, and fractal-like scaling,&#x0201D; <emphasis>Chaos (Woodbury, N.Y.)</emphasis>, vol. 19, no. 2, pp. 1&#x02013;14, June 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+M%2E+Hausdorff%2C+%22Gait+dynamics+in+Parkinson%27s+disease%3A+common+and+distinct+behavior+among+stride+length%2C+gait+variability%2C+and+fractal-like+scaling%2C%22+Chaos+%28Woodbury%2C+N%2EY%2E%29%2C+vol%2E+19%2C+no%2E+2%2C+pp%2E+1-14%2C+June+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. F. del Olmo and J. Cudeiro, &#x0201C;Temporal variability of gait in Parkinson disease: effects of a rehabilitation programme based on rhythmic sound cues,&#x0201D; <emphasis>Parkinsonism &#x00026; Related Disorders</emphasis>, vol. 11, no. 1, pp. 25&#x02013;33, January 2005. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+F%2E+del+Olmo+and+J%2E+Cudeiro%2C+%22Temporal+variability+of+gait+in+Parkinson+disease%3A+effects+of+a+rehabilitation+programme+based+on+rhythmic+sound+cues%2C%22+Parkinsonism+%26+Related+Disorders%2C+vol%2E+11%2C+no%2E+1%2C+pp%2E+25-33%2C+January+2005%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>D. Schaafsma et al., &#x0201C;Gait dynamics in Parkinson&#x02019;s disease: relationship to Parkinsonian features, falls and response to levodopa,&#x0201D; <emphasis>Journal of the Neurological Sciences</emphasis>, vol. 212, pp. 47&#x02013;53, 2003. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+Schaafsma+et+al%2E%2C+%22Gait+dynamics+in+Parkinson%27s+disease%3A+relationship+to+Parkinsonian+features%2C+falls+and+response+to+levodopa%2C%22+Journal+of+the+Neurological+Sciences%2C+vol%2E+212%2C+pp%2E+47-53%2C+2003%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>E. van Wegen et al., &#x0201C;The effect of rhythmic somatosensory cueing on gait in patients with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Journal of the Neurological Sciences</emphasis>, vol. 248, no. 1&#x02013;2, pp. 210&#x02013;214, October 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=E%2E+van+Wegen+et+al%2E%2C+%22The+effect+of+rhythmic+somatosensory+cueing+on+gait+in+patients+with+Parkinson%27s+disease%2C%22+Journal+of+the+Neurological+Sciences%2C+vol%2E+248%2C+no%2E+1-2%2C+pp%2E+210-214%2C+October+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>N. Giladi, H. Shabtai, E. Rozenberg, and E. Shabtai, &#x0201C;Gait festination in Parkinson&#x02019;s disease,&#x0201D; <emphasis>Parkinsonism &#x00026; Related Disorders</emphasis>, vol. 7, pp. 135&#x02013;138, 2001. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=N%2E+Giladi%2C+H%2E+Shabtai%2C+E%2E+Rozenberg%2C+and+E%2E+Shabtai%2C+%22Gait+festination+in+Parkinson%27s+disease%2C%22+Parkinsonism+%26+Related+Disorders%2C+vol%2E+7%2C+pp%2E+135-138%2C+2001%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. P. Ford, L. A. Malone, I. Nyikos, R. Yelisetty, and C. S. Bickel, &#x0201C;Gait Training With Progressive External Auditory Cueing in Persons With Parkinson&#x02019;s Disease,&#x0201D; <emphasis>Archieves of Physical Medicine and Rehabilitation</emphasis>, vol. 91, no. 8, pp. 1254&#x02013;1261, August 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+P%2E+Ford%2C+L%2E+A%2E+Malone%2C+I%2E+Nyikos%2C+R%2E+Yelisetty%2C+and+C%2E+S%2E+Bickel%2C+%22Gait+Training+With+Progressive+External+Auditory+Cueing+in+Persons+With+Parkinson%27s+Disease%2C%22+Archieves+of+Physical+Medicine+and+Rehabilitation%2C+vol%2E+91%2C+no%2E+8%2C+pp%2E+1254-1261%2C+August+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Y. Baram and A. Miller, &#x0201C;Auditory feedback control for improvement of gait in patients with Multiple Sclerosis,&#x0201D; <emphasis>Journal of the Neurological Sciences</emphasis>, vol. 254, no. 1&#x02013;2, pp. 90&#x02013;94, March 2007. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Y%2E+Baram+and+A%2E+Miller%2C+%22Auditory+feedback+control+for+improvement+of+gait+in+patients+with+Multiple+Sclerosis%2C%22+Journal+of+the+Neurological+Sciences%2C+vol%2E+254%2C+no%2E+1-2%2C+pp%2E+90-94%2C+March+2007%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>W. Nanhoe-Mahabier et al., &#x0201C;The possible price of auditory cueing: Influence on obstacle avoidance in Parkinson&#x02019;s disease,&#x0201D; <emphasis>Movement Disorders</emphasis>, vol. 0, no. 0, pp. 1&#x02013;5, February 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=W%2E+Nanhoe-Mahabier+et+al%2E%2C+%22The+possible+price+of+auditory+cueing%3A+Influence+on+obstacle+avoidance+in+Parkinson%27s+disease%2C%22+Movement+Disorders%2C+vol%2E+0%2C+no%2E+0%2C+pp%2E+1-5%2C+February+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>E. Wegen et al., &#x0201C;The effects of visual rhythms and optic flow on stride patterns of patients with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Parkinsonism and Related Disorders</emphasis>, vol. 12, no. 1, pp. 21&#x02013;27, June 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=E%2E+Wegen+et+al%2E%2C+%22The+effects+of+visual+rhythms+and+optic+flow+on+stride+patterns+of+patients+with+Parkinson%27s+disease%2C%22+Parkinsonism+and+Related+Disorders%2C+vol%2E+12%2C+no%2E+1%2C+pp%2E+21-27%2C+June+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. Roerdink, P. J. Bank, C. Peper, and P. J. Beek, &#x0201C;Walking to the beat of different drums: Practical implications for the use of acoustic rhythms in gait rehabilitation,&#x0201D; <emphasis>Gait &#x00026; Posture</emphasis>, vol. 33, no. 4, pp. 690&#x02013;694, March 2011. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+Roerdink%2C+P%2E+J%2E+Bank%2C+C%2E+Peper%2C+and+P%2E+J%2E+Beek%2C+%22Walking+to+the+beat+of+different+drums%3A+Practical+implications+for+the+use+of+acoustic+rhythms+in+gait+rehabilitation%2C%22+Gait+%26+Posture%2C+vol%2E+33%2C+no%2E+4%2C+pp%2E+690-694%2C+March+2011%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>E. Cubo, S. Leurgans, and C. G. Goetz, &#x0201C;Short-term and practice effects of metronome pacing in Parkinson&#x02019;s disease patients with gait freezing while in the &#x02018;on&#x02019; state: randomized single blind evaluation,&#x0201D; <emphasis>Parkinsonism and Related Disorders</emphasis>, vol. 10, no. 8, pp. 507&#x02013;510, May 2004. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=E%2E+Cubo%2C+S%2E+Leurgans%2C+and+C%2E+G%2E+Goetz%2C+%22Short-term+and+practice+effects+of+metronome+pacing+in+Parkinson%27s+disease+patients+with+gait+freezing+while+in+the+%27on%27+state%3A+randomized+single+blind+evaluation%2C%22+Parkinsonism+and+Related+Disorders%2C+vol%2E+10%2C+no%2E+8%2C+pp%2E+507-510%2C+May+2004%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. M. Willems et al., &#x0201C;The use of rhythmic auditory cues to influence gait in patients with Parkinson&#x02019;s disease, the differential effect for freezers and non-freezers, an explorative study,&#x0201D; <emphasis>Disability and Rehabilitation</emphasis>, vol. 28, no. 11, pp. 721&#x02013;728, June 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+M%2E+Willems+et+al%2E%2C+%22The+use+of+rhythmic+auditory+cues+to+influence+gait+in+patients+with+Parkinson%27s+disease%2C+the+differential+effect+for+freezers+and+non-freezers%2C+an+explorative+study%2C%22+Disability+and+Rehabilitation%2C+vol%2E+28%2C+no%2E+11%2C+pp%2E+721-728%2C+June+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>B. Najafi, D. Miller, B. Jarrett, and J. Wrobel, &#x0201C;Does footwear type impact the number of steps required to reach gait steady-state?: An innovative look at the impact of foot orthoses on gait initiation,&#x0201D; <emphasis>Gait and Posture</emphasis>, vol. 32, no. 1, pp. 29&#x02013;33, May 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=B%2E+Najafi%2C+D%2E+Miller%2C+B%2E+Jarrett%2C+and+J%2E+Wrobel%2C+%22Does+footwear+type+impact+the+number+of+steps+required+to+reach+gait+steady-state%B4%3A+An+innovative+look+at+the+impact+of+foot+orthoses+on+gait+initiation%2C%22+Gait+and+Posture%2C+vol%2E+32%2C+no%2E+1%2C+pp%2E+29-33%2C+May+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>G. McIntosh, S. Brown, and R. Rice, &#x0201C;Rhythmic auditory-motor facilitation of gait patterns in patients with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Journal of Neurology, Neurosurgery, and Psychiatry</emphasis>, vol. 62, pp. 22&#x02013;26, 1997. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=G%2E+McIntosh%2C+S%2E+Brown%2C+and+R%2E+Rice%2C+%22Rhythmic+auditory-motor+facilitation+of+gait+patterns+in+patients+with+Parkinson%27s+disease%2C%22+Journal+of+Neurology%2C+Neurosurgery%2C+and+Psychiatry%2C+vol%2E+62%2C+pp%2E+22-26%2C+1997%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. Delval, V. Weerdesteyn, J. Duysens, and S. Overeem, &#x0201C;Walking patterns in Parkinson&#x02019;s disease with and without freezing of gait,&#x0201D; <emphasis>Neuroscience</emphasis>, vol. 182, pp. 217&#x02013;224, 2011. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+Delval%2C+V%2E+Weerdesteyn%2C+J%2E+Duysens%2C+and+S%2E+Overeem%2C+%22Walking+patterns+in+Parkinson%27s+disease+with+and+without+freezing+of+gait%2C%22+Neuroscience%2C+vol%2E+182%2C+pp%2E+217-224%2C+2011%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>D. Deleu, Y. Hanssens, and M. G. Northway, &#x0201C;Subcutaneous apomorphine: an evidence-based review of its use in Parkinson&#x02019;s disease,&#x0201D; <emphasis>Drugs Aging</emphasis>, vol. 21, no. 11, pp. 687&#x02013;709, 2004. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+Deleu%2C+Y%2E+Hanssens%2C+and+M%2E+G%2E+Northway%2C+%22Subcutaneous+apomorphine%3A+an+evidence-based+review+of+its+use+in+Parkinson%27s+disease%2C%22+Drugs+Aging%2C+vol%2E+21%2C+no%2E+11%2C+pp%2E+687-709%2C+2004%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. Rodr&#x00ED;guez-Molinero, D. A. P&#x00E9;rez-Mart&#x00ED;nez, et al. &#x0201C;Remote control of apomorphine infusion rate in Parkinson&#x02019;s disease: Real-time dose variations according to the patients&#x02019; motor state. A proof of concept&#x0201D;. <emphasis>Parkinsonism Related Disorders</emphasis> (8), pp. 996&#x02013;998, 2015. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+Rodr%EDguez-Molinero%2C+D%2E+A%2E+P%E9rez-Mart%EDnez%2C+et+al%2E+%22Remote+control+of+apomorphine+infusion+rate+in+Parkinson%27s+disease%3A+Real-time+dose+variations+according+to+the+patients%27+motor+state%2E+A+proof+of+concept%22%2E+Parkinsonism+Related+Disorders+%288%29%2C+pp%2E+996-998%2C+2015%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch04" label="4" xreflabel="4">
<title>Assessment of Motor Symptoms</title>
<para role="author"><emphasis role="strong">Albert Sama<superscript><emphasis role="strong">1</emphasis></superscript>, Carlos P&#x00E9;rez<superscript><emphasis role="strong">1</emphasis></superscript>, Daniel Rodriguez-Martin<superscript><emphasis role="strong">1</emphasis></superscript>, Alejandro Rodriguez-Molinero<superscript><emphasis role="strong">2</emphasis></superscript>, Sheila Alcaine<superscript><emphasis role="strong">3</emphasis></superscript>, Berta Mestre<superscript><emphasis role="strong">3</emphasis></superscript>, Anna Prats<superscript><emphasis role="strong">3</emphasis></superscript> and M. Cruz Crespo<superscript><emphasis role="strong">3</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<para><superscript>2</superscript>National University of Galway &#x2013; NUIG, Galway, Ireland</para>
<para><superscript>3</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<section class="lev1" id="sec4-1" label="4.1" xreflabel="4.1">
<title>Introduction</title>
<para>This chapter describes the methodology developed and used to obtain the elements of the REMPARK system devoted to monitor the related PD motor symptoms, according to the specifications discussed in the previous chapter. The monitoring part basically consists in the waist-worn device and its embedded algorithms for the analysis of the PD patients&#x02019; movement and gait.</para>
<para>The development of such a device to assess motor symptoms has been divided into several steps that are summarised below:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>First, different questionnaires were administered to professionals and cargiveers to identify some system requirements and the most important symptoms to be monitored. This step has been already partially presented and used for the purpose of <link linkend="ch03">Chapter <xref linkend="ch3" remap="3"/></link>. The present chapter describes the details of these questionnaires and the obtained results.</para></listitem>
<listitem>
<para>A methodology was developed to detect these symptoms, which is based on inertial sensors and machine learning techniques. This methodology is presented in Section 4.3.</para></listitem>
<listitem>
<para>A database of signals was collected in order to develop automatic detection methods based on the mentioned methodology. The design of the experiment to collect such data and a summary of the data obtained are also detailed in Section 4.3.</para></listitem>
<listitem>
<para>The algorithmic approach to exploit the database of signals based on machine learning techniques is presented in Section 4.4. Each symptom and parameter detected by an algorithm is described in a different subsection.</para></listitem>
<listitem>
<para>Finally, some conclusions are drawn.</para></listitem>
</itemizedlist>
</section>
<section class="lev1" id="sec4-2" label="4.2" xreflabel="4.2">
<title>Decision on the Most Relevant Symptoms to Be Detected and Assessed</title>
<para>During REMPARK project, specific tasks were devoted both to the collection of clinical information and to understand aspects that may be relevant for the REMPARK system. These tasks were carried out during the first months of the project through the administration of two questionnaires addressed to patients and related professionals [1]. Their results were included in the system design to set the technical specification of the system (partially discussed in <link linkend="ch03">Chapter <xref linkend="ch3" remap="3"/></link>).</para>
<para>The most relevant issues addressed in the questionnaires administered to professionals are summarised below:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>First, on the salient clinical features of PD in the different stages of the disease. Here, for instance, professionals were requested to indicate the symptoms with higher priority for treatment, to report which monitored symptoms may have a greater impact on daily living, and which are the most frequent symptoms according to a mild, moderate or severe PD.</para></listitem>
<listitem>
<para>Second, information was collected on how the professional expects to be helped by REMPARK system in the therapeutic management of the individuals with PD. &#x0201C;<emphasis>At which PD stages do you think REMPARK may be useful?</emphasis>&#x0201D;, &#x0201C;<emphasis>For the improvement of which symptoms do you think REMPARK may be useful?</emphasis>&#x0201D;, are examples of the related questions made to the professionals to acquire valuable information at this level of analysis.</para></listitem>
<listitem>
<para>The third issue addressed consisted on how data had to be organised for an optimal use and updating of the PD treatment in the disease course. At this level professionals were required to express their opinion on the usability of REMPARK in PD patients as a function of symptoms severity.</para></listitem>
</itemizedlist>
<para>Furthermore, the interviews helped the consortium to understand the perspective, the expectations and the general attitude of the care service (i.e., clinical professional) against the REMPARK approach. At this regard, emphasis was paid in capturing different perspectives. For this reason, the questionnaires were administered to different kind of professionals belonging to the medical (i.e., neurologists, geriatricians) and technical rehabilitative (i.e., physiotherapist, occupational therapist) areas.</para>
<section class="lev2" id="sec4-2-1" label="4.2.1" xreflabel="4.2.1">
<title>Subjects</title>
<para>Some characteristics of the 57 professionals recruited for the administration of the questionnaires are reported in <link linkend="F4-1">Figure <xref linkend="F4-1" remap="4.1"/></link>. The average number of years of clinical expertise with PD patients was 13.7 (SD=4.6). Most of the clinicians were employed in Public Health Service (n=36) while 18 of them were employed in private or &#x0201C;intermediate&#x0201D; health care system.</para>
<fig id="F4-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-1">Figure <xref linkend="F4-1" remap="4.1"/></link></label>
<caption><para>Illustration of the number of professional who filled the questionnaire divided according to their country of origin. Years of clinical practice in PD area are also reported in the average, also in this case individually for each country. Vertical bars represent the standard deviation.</para></caption>
<graphic xlink:href="graphics/ch04_fig1.jpg"/>
</fig>
<para>Across the different countries/sites, it must be noted that the three kinds of professional who took part in the study were neurologists, geriatricians and physiotherapists. The majority of participating professionals were neurologists (n=23), followed by physiotherapists (n=22) and, then, by geriatricians (n=10).</para>
</section>
<section class="lev2" id="sec4-2-2" label="4.2.2" xreflabel="4.2.2">
<title>Questionnaire</title>
<para>The characteristics of the questionnaire including the formulation of the items and methodology for answering questions were developed through a continuous consultation between the four medical partners participating in REMPARK: Centro Medico Teknon (Spain), Fondazione Santa Lucia (Italy), Maccabi Healthcare Services (Israel) and the National University of Ireland at Galway (Ireland).</para>
<para>The questionnaire is composed of three main sections.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>An initial social-demographic section in which the participant is required to provide personal information regarding, for instance, own specialty, the country of origin and the years of clinical experience with PD patients.</para></listitem>
<listitem>
<para>A second central section that addresses clinical issues related to PD. This is the section in which participants indicate the clinical relevance of PD symptoms according to the three disease stages (i.e., mild, moderate and advanced). Questions such as the following ones were posed:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis>What do you consider are the three most characteristic motor symptoms of this phase?</emphasis></para></listitem>
<listitem>
<para><emphasis>What do you consider are the 3 motor symptoms that interfere the most, with the quality of life of people with Parkinson&#x02019;s at this stage of the disease?</emphasis></para></listitem>
<listitem>
<para><emphasis>What do you consider are the three priorities to treat symptoms at this stage of the disease?</emphasis></para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>The professional was asked to answer by ticking a square box in a mixed multiple alternative forced choice paradigm. In fact, for most questions, if the professional feels that the right answer does not fit with the proposed alternatives he can tick the square box corresponding to &#x0201C;other&#x0201D; and, then, is allowed to better specify his response.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The third and final section of the questionnaire aimed at investigating the potential utility of REMPARK system for the clinical management of PD, as it is perceived by professionals. Questions like the following ones were proposed here:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis>Do you consider that a system such as REMPARK would be useful to improve motor problems of your people with Parkinson&#x02019;s?</emphasis></para></listitem>
<listitem>
<para><emphasis>In your clinical practice, do you consider that a system such as REMPARK would be a useful system for monitoring motor problems of your people with Parkinson&#x02019;s?</emphasis></para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>In the case of the professional expressing a positive judgment about REMPARK utility by ticking the &#x0201C;yes&#x0201D; box, he is required to indicate both the PD stage for which REMPARK could be better applicable (i.e., mild, moderate or advanced stages) and which PD symptoms would benefit from REMPARK utilisation. Also for these questions the professional has to respond by ticking a square box in a mixed multiple alternative forced choice paradigm.</para>
</section>
<section class="lev2" id="sec4-2-3" label="4.2.3" xreflabel="4.2.3">
<title>Results</title>
<section class="lev3" id="sec4-2-3-1" label="4.2.3.1" xreflabel="4.2.3.1">
<title>Analysis of the correlation between responses on clinical questions</title>
<para>A first item analysis was performed to investigate the coherence of the professionals&#x02019; response relating the clinical answers. More specifically, the participant is required to evaluate the clinical relevance of a PD symptom by indicating:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The three most characteristic motor symptoms of PD.</para></listitem>
<listitem>
<para>The three motor symptoms that interfere more with the quality of life of people with PD.</para></listitem>
<listitem>
<para>The three symptoms that have priority for treatment.</para></listitem>
</itemizedlist>
<para>All three questions were individually addressed for mild, moderate and advanced PD stage. The three questions are apparently related since it can be reasonably posited that the most characteristic symptoms of PD have a great probability to be those symptoms that interfere with quality of life and, furthermore, those for which a treatment is imperative. Therefore, from the statistical point of view, the existence of a significant correlation between the responses on these items could be a parameter to verify the reliability of responses themselves.</para>
<para>In order to examine the correlation between the professionals&#x02019; responses on the above three items/questions, Pearson&#x02019; r statistic was performed. For the purpose of these analyses, in order to quantify the relative weight of each symptom, the responses were classified according to a Likert-type scale ranging from 0 to 3, resulting in most of the correlations analysed being significant. In these cases, the r value ranged from 0.27 to 0.72 being > 0.40 in about 67% of all cases. The significance of the correlation was only approached in one case relating to the analysis that involved the &#x0201C;Difficulty in Turning&#x0201D; symptom (i.e., the correlation between the score attributed to &#x0201C;most characteristic symptoms&#x0201D; and to the &#x0201C;priority for treatment items&#x0201D;).</para>
<para>Therefore, the correlation analyses, by confirming the existence of a significant relationship between the professionals&#x02019; response, indicate a global coherence of the responses themselves.</para>
</section>
<section class="lev3" id="sec4-2-3-2" label="4.2.3.2" xreflabel="4.2.3.2">
<title>Investigation of the clinical relevance of the motor symptoms in the three PD phases (i.e., mild, moderate and advanced)</title>
<para>The clinical relevance of the PD symptoms as reported by professionals was investigated by means of descriptive analyses firstly without taking into consideration the particular country/site where the data were collected and, then, in a second step, individually for each country/site. This was made in order to have both a general view on data and to evidence possible differences as a function of the country/site the professional belongs to.</para>
<para>For the purpose of these analyses, a unique score was computed by collapsing the score attributed to each individual item in the three clinical questions mentioned in the previous sub-section:</para>
<para>An index of clinical relevance for each symptom was, thus, computed by averaging the score attributed by professionals to that symptom in the three questions. For instance, the index of clinical relevance for &#x0201C;small steps&#x0201D; was represented by averaging the scores attributed to it in questions <emphasis>1</emphasis>), <emphasis>2</emphasis>) and <emphasis>3)</emphasis>. Also in this case, for the purpose of these analyses, in order to quantify the relative weight of each symptom a score of 3 was attributed to the symptoms the professional indicated as first, a score of 2 was attributed to a symptom indicated as second, a score of 1 was given to the symptom indicated as third and, finally, a score of 0 was attributed to the symptoms not included in the first three symptoms list.</para>
<para>As showed in <link linkend="F4-2">Figure <xref linkend="F4-2" remap="4.2"/></link>, independently from the countries/sites where data were collected, the analysis of the index of clinical relevance computed for PD motor symptoms evidence some differences according to the PD stage considered.</para>
<fig id="F4-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-2">Figure <xref linkend="F4-2" remap="4.2"/></link></label>
<caption><para>Indices of clinical relevance for each PD motor symptoms examined referred to the mild (blue columns), moderate (red columns) and advanced (green columns) PD stages. Vertical bars represent standard errors.</para></caption>
<graphic xlink:href="graphics/ch04_fig002.jpg"/>
</fig>
<para>In fact, in the mild stage (represented by blue columns in the figure), &#x0201C;reduced walking speed&#x0201D;, &#x0201C;small steps&#x0201D;, &#x0201C;difficulty in turning&#x0201D; and &#x0201C;shu&#x0FB04;e&#x0201D; were the four symptoms with the higher index of clinical relevance with and index value of 1.74, 1.24, 0.68 and 0.66, respectively.</para>
<para>In the moderate stage (represented by red columns in the figure), the most clinically relevant symptoms were &#x0201C;freezing of gait&#x0201D;, &#x0201C;difficulty in turning&#x0201D;, &#x0201C;falls&#x0201D; and &#x0201C;reduced walking speed&#x0201D; with an index value of 1.19, 1.05, 0.91 and 0.87, respectively.</para>
<para>Finally, as for the advanced stage (represented by green columns in the figure), the symptoms with a higher index of clinical relevance were &#x0201C;falls&#x0201D;, &#x0201C;freezing of gait&#x0201D;, &#x0201C;difficulty in turning&#x0201D; and &#x0201C;shu&#x0FB04;e&#x0201D; with an index value of 1.91, 1.50, 0.84 and 0.56, respectively.</para>
<para>According to the majority of professionals, patients with PD adopt some specific strategies to improve gait difficulties particularly in the moderate-advanced stages of the disease. More specifically, more than 80% (n=48) and about 91% (n=52) of professionals indicates that PD patients use strategies to improve gait in the moderate and advanced phases, respectively, compared to the 33% who report this behaviour in the mild stages of the disease. <emphasis>The strategies more frequently adopted by patients in the moderate-advance disease stages would be stick use, verbal cueing, attention focus on walking and steps counting</emphasis>. These strategies have been indicated by about 79% (n=38) of professionals for the moderate stage and by the 80% (n=42) of them for the advanced stage.</para>
<para>However, according to professionals, the most useful strategies to be adopted in the moderate-advanced PD would be the use of verbal cueing for about 32% (n=18), steps counting for about 16% (n=9) and stick use for about 14% (n=8) of them. As for the advanced stage, also in this case the majority of professionals indicated verbal cueing as the most useful strategy to be adopted (about 26% of responses; n=15) followed by stick (about 23% of responses; n=13) and metronome (about 12% of responses; n=7) use.</para>
</section>
<section class="lev3" id="sec4-2-3-3" label="4.2.3.3" xreflabel="4.2.3.3">
<title>Analysis of REMPARK utility for PD patients</title>
<para>A large majority of professionals considered REMPARK potentially useful for PD management. More specifically, about 96% of professionals (n=55) judged REMPARK a useful system for symptoms improvement and 93% (n=53) considered REMPARK potentially useful for symptoms monitoring. The REMPARK utility for both symptoms improvement and monitoring, was perceived by professionals for the intervention in the moderate stages (49% and 40% of responses, respectively) and at a lesser extent in the mild (about 21% and 23% of responses, respectively) and advanced (about 9% and 19% of responses) stages. However, the presence of missing data (n=13) related to the lack of responses on the specification of the PD phase for which the application of REMPARK system would be more useful, reduces the reliability of these findings.</para>
<para>In order to quantify the professionals&#x02019; judgements about which symptoms REMPARK system would be more useful, in terms of both improvement and monitoring, the professionals&#x02019; responses were classified on a Likert-type scale ranging from 0 to 3, where 0 represents the minimum value assigned to the effect of REMPARK system on a specified symptom and, conversely, 3 indicates the highest value.</para>
<para>As <link linkend="F4-3">Figure <xref linkend="F4-3" remap="4.3"/></link> illustrates, a substantial coherence is noted about the symptoms that would better benefit from the application of the REMPARK system in terms of symptoms improvement and monitoring. Indeed, according to professionals&#x02019; opinions, the symptoms on which the REMPARK system would have a greater positive impact would be &#x0201C;freezing of gait&#x0201D; and &#x0201C;reduced walking speed&#x0201D;.</para>
<fig id="F4-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-3">Figure <xref linkend="F4-3" remap="4.3"/></link></label>
<caption><para>Subjective judgment expressed by professionals about the utility of REMPARK system for both improvement and monitoring of motor symptoms. Vertical bars represent standard errors.</para></caption>
<graphic xlink:href="graphics/ch04_fig2.jpg"/>
</fig>
</section>
</section>
<section class="lev2" id="sec4-2-4" label="4.2.4" xreflabel="4.2.4">
<title>Discussion and Conclusive Remarks</title>
<para>A first critical issue the questionnaires are focussed on is the understanding of the salient clinical features of PD in the different stages of the disease. The answers should also give valuable information about clinicians&#x02019; expectations on the REMPARK utility and usability in the clinical management of PD.</para>
<para>A first preliminary comment has to be devoted to the reliability of the professional&#x02019;s answers. Regarding this aspect, some indicators such as the absence of missing data on content questions as well as a substantial coherence of responses on clinical questions suggests that the questionnaires have been filled correctly and congruently.</para>
<para>The descriptive and inferential statistics applied to data allowed us to evidence some main points of interest.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>First, as expected, different symptoms achieve a clinical relevance and require a therapeutic intervention as a function of different PD phase considered and, thus, in particular in the mild stage of PD &#x0201C;<emphasis role="strong">reduced walking speed</emphasis>&#x0201D; and &#x0201C;<emphasis role="strong">small steps</emphasis>&#x0201D;, were the most clinically relevant symptoms whereas in the moderate stages &#x0201C;<emphasis role="strong">freezing of gait</emphasis>&#x0201D; and &#x0201C;<emphasis role="strong">difficulty in turning</emphasis>&#x0201D; appear to be more important clinical signs. Moreover, in the advanced stages, &#x0201C;<emphasis role="strong">falls</emphasis>&#x0201D; arises as a new main clinical occurrence. As mentioned above, this finding is expected on the basis of the neurological characteristics of PD [2]. Indeed, PD is a neurodegenerative disease that progressively affects different motor and non-motor brain circuitries with a related modification of both the qualitative and quantitative (i.e., severity) clinical features of the disease [3&#x02013;5]. An interesting aspect to be remarked is that according to professionals, PD patients use strategies to improve symptoms mainly in the moderate-advanced stages, rather than in the mild ones. This finding is obviously expected on the basis of the greater impact that symptoms severity progressively exerts on daily living. However, according to professionals, <emphasis role="strong"><emphasis>the strategies that PD patients seem to adopt for improving their gait difficulties do not appear to be the most useful</emphasis></emphasis>. In particular, professionals judge to be useful strategies to be adopted in both the moderate and advanced stages the verbal cueing whereas it seems that PD patients tend to use stick more frequently.</para></listitem>
</itemizedlist>
<para>Furthermore, the analysis of questionnaires outlines a substantial convergence of the professionals&#x02019; clinical judgements between the different countries/sites for mild and advanced stages of the disease. However, it should be noted that the same judgements appear to be more heterogeneous when applied to moderate PD stages. A possible interpretation of this heterogeneity is related to the objective difficulty to clinically define the moderate stages in respect to mild and advanced ones.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>A second main point evidenced by the analysis is that <emphasis role="strong"><emphasis>REMPARK system is perceived by professionals as a potentially useful instrument for the management and treatment of PD</emphasis></emphasis>. This is particularly observed in the moderate stages of the disease. As a matter of fact, the majority of professionals indicated the moderate phases of the disease as the best target phase for REMPARK. In this regard, it should be noted here that, as previously discussed, the moderate stage of the disease is the stage for which the judgment on the clinical relevance of symptoms is more heterogeneous. This provides a clear indication for REMPARK. Indeed, the multifaceted clinical expression of PD during this phase should be taken into account carefully to develop a functional system.</para></listitem>
<listitem>
<para>Finally, as for the advanced stage, the symptoms with a higher index of clinical relevance were &#x0201C;falls&#x0201D;, &#x0201C;freezing of gait&#x0201D;, &#x0201C;difficulty in turning&#x0201D; and &#x0201C;shu&#x0FB04;e&#x0201D; with an index value of 1.91, 1.50, 0.84 and 0.56, respectively.</para></listitem>
</itemizedlist>
<para>In conclusion, from the analysis and considerations done, the <emphasis role="strong"><emphasis>REMPARK system appears to be perceived particularly useful to be applied for both monitoring and improving PD symptoms in the moderate-advanced stages of the disease</emphasis></emphasis>.</para>
<para>REMPARK system might be a useful and well accepted instrument for the therapeutic management of PD. Additionally, there exists evidence that PD patients spontaneously adopt strategies to improve gait disorders by using external aids.</para>
</section>
</section>
<section class="lev1" id="sec4-3" label="4.3" xreflabel="4.3">
<title>Methodology and Database to Monitor Motor Symptoms</title>
<para>This section presents the implemented methodology in REMPARK system for the detection of the main motor symptoms discussed above. As this methodology will be based on an artificial intelligence approach, it is necessary the construction of a specific database for the required knowledge extraction.</para>
<section class="lev2" id="sec4-3-1" label="4.3.1" xreflabel="4.3.1">
<title>An Artificial Intelligence Approach and the Need of Relevant Data</title>
<para>The main objective of the REMPARK project is to obtain a system capable of assessing PD motor and non-motor symptoms. This is a clinical goal that is intended to be solved through technological solutions.</para>
<para>Firstly, REMPARK system involves inertial sensors to monitor PD motor symptoms given their nature. Since motor symptoms affect movement, inertial sensors capable of measuring such movement are used to automatically detect these symptoms. Secondly, the techniques used to determine their presence come from the Artificial Intelligence (AI) field; more concretely, machine learning techniques are well-known to provide high accuracies in these tasks. In this case, REMPARK work was focused on supervised learning methods.</para>
<para>Supervised learning techniques for classification tasks are mathematical and statistical methods that are capable of recognising patterns to associate them with specific classes. These methods require sets of labelled data in which patterns and their corresponding class labels are given. In the case of REMPARK, inertial signals labelled with the presence of symptoms are needed. In consequence, a specific data capture is required to gather such <emphasis role="strong">labelled datasets</emphasis>.</para>
<para>Machine learning techniques require the maximum amount of data and the most variability in them in order to properly generalise an automatic detection from them. In addition, labels must be as accurate as possible. Through these data, highly accurate models capable of automatically classifying the patterns can be obtained. In consequence, REMPARK envisaged the construction of a database of labelled inertial signals from 90 PD patients from 4 different countries.</para>
<para>It must be taken into account that the usage of supervised learning techniques creates some restrictions into the algorithmic development, which will be carried out after the database collection. Data collection must follow a strict protocol designed according to clinical restrictions in order to capture the required variety of PD symptoms in different severities. The statistical representability of the data will enable supervised learning techniques to extract the embedded knowledge and, thus, precisely detect the presence of symptoms into the signals provided by inertial sensors.</para>
</section>
<section class="lev2" id="sec4-3-2" label="4.3.2" xreflabel="4.3.2">
<title>Protocol for the Database Construction</title>
<para>The data for the database were collected in the most homogeneous possible way, and under the best conditions to ensure good enough generalization capabilities. It is a very relevant task since the validity of the REMPARK system for assessing a patient&#x02019;s motor status relies on the quality of the data in the database.</para>
<para>A specific clinical study was designed and carried out in order to collect the database. It was a multicentre international study that was conducted in four European settings: Centro M&#x00E9;dico Teknon (Spain), National University of Ireland, Galway (Ireland), Fondazione Santa Lucia (Italy) and Maccabi (Israel).</para>
<para>The primary objectives of the study that collected the data were:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To obtain a database of properly identified inertial signals, which will allow the training of processing <emphasis role="strong">algorithms for motor phase</emphasis> detection (ON/OFF) in PD patients.</para></listitem>
<listitem>
<para>To obtain a database of properly identified inertial signals, which will allow to train processing <emphasis role="strong">algorithms for motor symptoms</emphasis> detection in PD patients.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To obtain identified inertial signals of hand tremor.</para></listitem>
<listitem>
<para>To obtain identified inertial signals of freezing of gait.</para></listitem>
<listitem>
<para>To obtain identified inertial signals of bradykinesia of the lower and upper limbs.</para></listitem>
<listitem>
<para>To obtain identified inertial signals of dyskinesia of the trunk and limbs.</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To obtain a database of properly identified inertial signals corresponding to movements and activities that can be mistaken for PD <emphasis role="strong">motor symptoms</emphasis> (potential <emphasis role="strong">false positives</emphasis>).</para></listitem>
<listitem>
<para>To obtain a database of properly identified inertial signals corresponding to <emphasis role="strong">gait parameters</emphasis>.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To obtain identified inertial signals of gait speed.</para></listitem>
<listitem>
<para>To obtain identified inertial signals of step/stride length.</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To obtain a database of properly identified inertial signals corresponding to movements and activities that can be mistaken for <emphasis role="strong">falls</emphasis> (potential <emphasis role="strong">false positives</emphasis>).</para></listitem>
</itemizedlist>
<para>The reference population was that formed by Parkinson&#x02019;s patients with moderate to severe disease and motor symptoms (Hoehn and Yahr greater or equal to 2.5 including ON/OFF phases, FOG or dyskinesia). The total number of recruited patients was 92, distributed among the clinical centres (26 in Spain, 16 in Ireland, 24 in Italy and 26 in Israel). A convenience sampling stratified by symptoms was conducted, keeping desired minimum proportions of patients with different motor symptoms. At least 50% of the sample were set to have ON/OFF motor fluctuations, with the OFF state characterized by bradykinesia. Furthermore, at least 25% of the sample had to present FOG episodes and, finally, at least 25% of the sample was set to present dyskinesia (at least 15% will present trunk dyskinesia).</para>
<para>The inclusion criteria for these patients were:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>to have a clinical diagnosis of Idiopathic Parkinson&#x02019;s Disease according to the UK Parkinson&#x02019;s Disease Society Brain Bank [6]</para></listitem>
<listitem>
<para>disease in moderate-severe phase (Hoehn and Yahr greater or equal to 2.5) with motor fluctuations with bradykinesia, FOG and/or dyskinesia</para></listitem>
<listitem>
<para>aged between 50 and 75 years and willing to participate in the study and wanting to co-operate in all its parts</para></listitem>
<listitem>
<para>accepting the performance regulations and procedures provided by the researchers.</para></listitem>
</itemizedlist>
<para>Patients fulfilling the following criteria were excluded from the study:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>other health problems that hamper physical activity</para></listitem>
<listitem>
<para>rheumatologic, neuromuscular, respiratory, cardiologic problems or significant pain</para></listitem>
<listitem>
<para>carriers of implanted electronic devices: cardiac pacemaker, implantable automatic defibrillator &#x02026;</para></listitem>
<listitem>
<para>patients receiving continuous therapy using intestinal duodopa or apomorphine</para></listitem>
<listitem>
<para>patients who have received deep cerebral stimulation therapy (neurosurgical procedure)</para></listitem>
<listitem>
<para>chronic consumption of psychotropic drugs and/or alcohol</para></listitem>
<listitem>
<para>known mental disease, such as dementia, according to clinical criteria -DSM-IV-TR and MMSE score &#x02264; 24 or neuropsychiatric disorders</para></listitem>
<listitem>
<para>patients who are participating in another clinical trial</para></listitem>
<listitem>
<para>patients unable to fully understand the potential risks and benefits of the study and give informed consent</para></listitem>
<listitem>
<para>subjects who are unable or unwilling to cooperate with study procedures.</para></listitem>
</itemizedlist>
<para>The data capture was conducted in two visits. The first visit comprised both the inclusion and basal visit, where the inclusion criteria were confirmed, and initial clinical and socio-demographic data of the patient were gathered. The second visit was devoted to the experimental procedures, where the maximum number of physical signs related to the disease were recorded using the inertial sensors and standard methods. This visit had two types of experiments that will happen in interleaved manner (according to the symptoms that the patient may present in each moment).</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The first type of experiments consists in short controlled tests, where the patient was asked to perform certain activities, with the aim of capturing specific motor symptoms (bradykinesia, dyskinesia, freezing of gait, etc.). These tests were closely controlled, using video recording as a gold standard.</para></listitem>
<listitem>
<para>The second kind of experiments that took place in this visit involved monitoring of the free activity of the patient, and recording the natural symptoms that he/she spontaneously may present. This monitoring lasted hours, and the activity and symptoms were electronically recorded by trained observers (using a tabled and specific software).</para></listitem>
</itemizedlist>
<para>The two types of experiments took place alternatively, according to the motor state and the symptoms that the patient presented. That is to say that when the patient was in an OFF phase, the specific controlled tests for the OFF symptoms were conducted (e.g., FOG) and the remaining OFF state time was used for monitoring their free-natural activity. Similarly, when the patient entered the ON phase, some specific short tests for capturing ON symptoms (e.g., dyskinesia) were performed, with the rest of the time devoted to monitoring the free natural activity of the patient in this state. <link linkend="F4-4">Figure <xref linkend="F4-4" remap="4.4"/></link> summarizes the experiment done.</para>
<fig id="F4-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-4">Figure <xref linkend="F4-4" remap="4.4"/></link></label>
<caption><para>Design of the experimental visit.</para></caption>
<graphic xlink:href="graphics/ch04_fig004.jpg"/>
</fig>
<para>All participants were trained to follow the specific study procedures, according to a common protocol that was the same for all the study sites. Patients also received specific training for recognizing their own OFF state. For this purpose, specific videos showing other patients in ON and OFF states were displayed, and detailed explanations on symptoms defining the OFF state were provided.</para>
<para>The investigators received a 3-day training session, comprising theoretical sessions including guidelines and instructions of all the instruments and questions of the Case Report Form (CRF), and practical sessions with pretended patients who behaved according a number of pre-established situations which served an example of the most relevant cases. The entire experimental test was performed at least twice by all the researchers, and every researcher conducted an example free monitoring session of at least 60 minutes.</para>
<para>During this training session, investigators were also trained into the usage of the designed labelling tools:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Labelling for the controlled experiments was done once the data capturing with the patients had finished. Researchers were trained into the usage of the tool, that allowed, first, the synchronisation of the inertial signals with the videos, and, second, the labelling of the different symptoms that were listed in the objective of the study.</para></listitem>
<listitem>
<para>Labelling of the free-monitoring experiment was done in-situ by the investigators. A tablet with a specific application were used by them. This application enabled the annotation of the different symptoms at the same time that the inertial signals were captured.</para></listitem>
</itemizedlist>
<para>Finally, the Principal Investigator, or his designee, in accordance with institutional policy, obtained an Informed Consent that was reviewed and accepted by the Ethics Committee. A written consent form bearing the full name, date and signature of the patient and the local investigator were obtained from each patient. The signed Informed Consent constitutes a confidential document and therefore was archived in the study binder. A copy of the consent was also given to the patient.</para>
<para>The inertial signals captured during this data collection phase were obtained through two sensors: a waist sensor and a wrist sensor. The waist sensor was worn inside a pocket within a neoprene belt. The wrist sensor was worn through a strap. Figures 4.5 and 4.6 present both devices.</para>
<fig id="F4-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-5">Figure <xref linkend="F4-5" remap="4.5"/></link></label>
<caption><para>Waist sensor.</para></caption>
<graphic xlink:href="graphics/ch04_fig005.jpg"/>
</fig>
<fig id="F4-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-6">Figure <xref linkend="F4-6" remap="4.6"/></link></label>
<caption><para>Wrist sensor.</para></caption>
<graphic xlink:href="graphics/ch04_fig006.jpg"/>
</fig>
</section>
<section class="lev2" id="sec4-3-3" label="4.3.3" xreflabel="4.3.3">
<title>Gathered Database Description</title>
<para>The following data were included in the database for each patient:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Socio-demographic data: Age, Sex, Educational level and Marital status</para></listitem>
<listitem>
<para>Parkinson&#x02019;s Disease related information:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Parkinson&#x02019;s severity, as measured by Hoehn and Yahr scale</para></listitem>
<listitem>
<para>Date of symptoms&#x02019; onset</para></listitem>
<listitem>
<para>Date of PD diagnosis</para></listitem>
<listitem>
<para>Motor section of UPDRS in OFF phase</para></listitem>
<listitem>
<para>Motor section of UPDRS in ON phase</para></listitem>
<listitem>
<para>Information on OFF periods characteristics and duration (UPDRS motor complications section &#x02013; motor fluctuations)</para></listitem>
<listitem>
<para>Information on FOG presence, characteristics and duration (FOG questionnaire)</para></listitem>
<listitem>
<para>Information on dyskinesia presence, characteristics and duration (UPDRS motor complications section &#x02013; dyskinesia)</para></listitem>
<listitem>
<para>List of treatments</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Co-morbidity related information. Cognitive status: Mini-Mental State Examination, Test of Attentional Performance and List of conditions.</para></listitem>
<listitem>
<para>Inertial signals labelled according to the following motor symptoms:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Motor phases. Signals were labelled among the three following options: ON, OFF and Intermediate state.</para></listitem>
<listitem>
<para>Dyskinesia severity and location. Dyskinesia is a side effect of medication, not a PD symptom, and signals were labelled according to the following modalities: Weak Trunk dyskinesia, Weak Foot/Leg dyskinesia, Weak Hand/Arm dyskinesia, Weak Head dyskinesia, Strong Trunk dyskinesia, Strong Foot/Leg dyskinesia, Strong Hand/Arm dyskinesia, Strong Head dyskinesia.</para></listitem>
<listitem>
<para>Bradykinetic gait (presence/absence). This symptom describes a difficulty to walk and slow gait, including small steps, shu&#x0FB04;ing and difficulty to turn.</para></listitem>
<listitem>
<para>FOG type. Episodes were labelled according to their type: Start Hesitation FOG, Straight Line FOG, Turning FOG, Tight FOG, Destination FOG.</para></listitem>
<listitem>
<para>Tremor location and severity: Modalities labelled were: Right Hand/Arm tremor, Right Foot/Leg tremor, Trunk tremor, Left Hand/Arm tremor, Left Foot/Leg tremor.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para>Inertial signals labelled according to body postures and activities: sitting, standing, walking, going upstairs, going downstairs, elevator (down), elevator (up), walk with FOG, carrying delicate object, carrying heavy object, lying, jumping, running</para></listitem>
<listitem>
<para>Other information from inertial signals:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Falls</para></listitem>
<listitem>
<para>Walking aids: scooter, walking stick, walker, crutch, crutches, lean on furniture, tripod walking stick</para></listitem>
</itemizedlist>
</listitem>
</orderedlist>
<para>Organization of the complete set of data from each patient is summarised in <link linkend="F4-7">Figure <xref linkend="F4-7" remap="4.7"/></link>.</para>
<fig id="F4-7" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-7">Figure <xref linkend="F4-7" remap="4.7"/></link></label>
<caption><para>Data structure collected from each patient.</para></caption>
<graphic xlink:href="graphics/ch04_fig3.jpg"/>
</fig>
<para>Database contains clinical data from 92 participants with idiopathic Parkinson&#x02019;s Disease. Regarding the sociodemographic data, as <link linkend="T4-1">Table <xref linkend="T4-1" remap="4.1"/></link> shows, fifty-six of them are male (60.9%) and 36 (39.1%) are female. The average age of the participants is 68 (SD 7.9). Seventy-four patients are married or live with a couple (80.5%), 10 (10.8%) single or divorced, and 8 (8.7%) widow.</para>
<table-wrap position="float" id="T4-1">
<label><link linkend="T4-1">Table <xref linkend="T4-1" remap="4.1"/></link></label>
<caption><para>Sociodemographic data</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Age (Mean &#x000B1; SD)</td>
<td valign="top" align="center">68 (7.9)</td>
</tr>
</thead>
<tbody>
<tr style="border-bottom:1px solid;">
<td valign="top" align="left">Gender</td>
<td valign="top" align="center"></td>
</tr>
<tr>
<td valign="top" align="left">Female</td>
<td valign="top" align="center">36 (39.1%)</td>
</tr>
<tr>
<td valign="top" align="left">Male</td>
<td valign="top" align="center">56 (60.9%)</td>
</tr>
<tr style="border-bottom:1px solid; border-top:1px solid;">
<td valign="top" align="left" colspan="2">Marital Status</td></tr>
<tr>
<td valign="top" align="left">Single</td>
<td valign="top" align="center">5 (5.4%)</td>
</tr>
<tr>
<td valign="top" align="left">Married/partner</td>
<td valign="top" align="center">74 (80.5%)</td>
</tr>
<tr>
<td valign="top" align="left">Widowed</td>
<td valign="top" align="center">8 (8.7%)</td>
</tr>
<tr>
<td valign="top" align="left">Separated/divorced</td>
<td valign="top" align="center">5 (5.4%)</td></tr>
</tbody>
</table>
</table-wrap>
<para>All the participants in the database construction are patients with moderate disease, having a Hoehn and Yahr scale of 2 or more. Average Hoehn and Yahr score is 3 (IQR 0.5). The average time from diagnosis of the disease was 10.5 years (SD 12.2). Eighty-nine patients (96.7%) of the database have OFF periods, according to the &#x0201C;motor complications&#x0201D; section of the UPDRS. Sixty-eight (73.9%) had predictable off periods, 54 (58.7%) had unpredictable off periods and 33 (35.9%) had sudden off periods. Most of them spend less than a quarter of the day in OFF. 34.7% of the total declared to spend more than 50% of the daytime in off.</para>
<para>Sixty-four patients (69.6%) present some degree of dyskinesia, being non-disabling dyskinesia in 54.3% and non-painful in 78.3%. Twenty-five patients have dystonia (27.2%). Only 5 patients have a 0 score in the FOG-Q, meaning that the rest of them present some gait problems.</para>
<para>The database contains inertial signals properly identified and labelled according to Parkinson&#x02019;s motor symptoms and body postures and activities. In total, the database contains 406 hours of inertial signals. Information on the motor status of the participant is available for 346 hours of inertial signals of the database (see <link linkend="T4-2">Table <xref linkend="T4-2" remap="4.2"/></link>).</para>
<table-wrap position="float" id="T4-2">
<label><link linkend="T4-2">Table <xref linkend="T4-2" remap="4.2"/></link></label>
<caption><para>Recorded time of the different motor periods</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Motor Phase</td>
<td valign="top" align="center">Time Recorded (hours)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">ON</td>
<td valign="top" align="center">163</td>
</tr>
<tr>
<td valign="top" align="left">OFF</td>
<td valign="top" align="center">111</td>
</tr>
<tr>
<td valign="top" align="left">Intermediate</td>
<td valign="top" align="center">&#x00A0;&#x00A0;72</td></tr>
</tbody>
</table>
</table-wrap>
<para>A total of 175 hours of motor symptoms are recorded and identified in the database (including bradykinesia, dyskinesia, FOG and tremor). Thirty-two of them correspond to inertial signals labelled against a video record gold standard, and the rest correspond to inertial signals which have been labelled using the real-time notations of an observer (tablet-PC annotations). <link linkend="T4-3">Table <xref linkend="T4-3" remap="4.3"/></link> summarizes the time (hours) of symptoms recorded and labelled in the database.</para>
<table-wrap position="float" id="T4-3">
<label><link linkend="T4-3">Table <xref linkend="T4-3" remap="4.3"/></link></label>
<caption><para>Video recording duration per symptom in the database</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="center">Dyskinesia</td>
<td valign="top" align="center">Bradykinesia</td>
<td valign="top" align="center">FOG</td>
<td valign="top" align="center">Tremor</td>
<td valign="top" align="center">TOTAL</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Video</td>
<td valign="top" align="center">&#x00A0;&#x00A0;8,10 h</td>
<td valign="top" align="center">15,78 h</td>
<td valign="top" align="center">2,45 h</td>
<td valign="top" align="center">&#x00A0;&#x00A0;5,60 h</td>
<td valign="top" align="center">&#x00A0;&#x00A0;31,92 h</td>
</tr>
<tr>
<td valign="top" align="left">Tablet-PC</td>
<td valign="top" align="center">62,82 h</td>
<td valign="top" align="center">31,82 h</td>
<td valign="top" align="center">2,96 h</td>
<td valign="top" align="center">45,82 h</td>
<td valign="top" align="center">143,43 h</td>
</tr>
<tr>
<td valign="top" align="left">Total</td>
<td valign="top" align="center">70,93 h</td>
<td valign="top" align="center">47,60 h</td>
<td valign="top" align="center">&#x00A0;&#x00A0;5,41 h</td>
<td valign="top" align="center">51,42 h</td>
<td valign="top" align="center">175,36 h</td></tr>
</tbody>
</table>
</table-wrap>
<para><link linkend="T4-4">Table <xref linkend="T4-4" remap="4.4"/></link> shows the amount of motor symptoms (bradykinesia, dyskinesia, FOG and tremor) recorded in each motor phase (ON, OFF or &#x0201C;Intermediate&#x0201D;), according to the gold standard used (video records vs tablet-PC annotations).</para>
<table-wrap position="float" id="T4-4">
<label><link linkend="T4-4">Table <xref linkend="T4-4" remap="4.4"/></link></label>
<caption><para>Summary of motor symptoms per motor phase</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="center" colspan="2">On <?lb?>(minutes)<emphasis role="cline"/></td>
<td valign="top" align="center" colspan="2">Off <?lb?>(minutes)<emphasis role="cline"/></td>
<td valign="top" align="center" colspan="2">Intermediate <?lb?>(minutes)<emphasis role="cline"/></td>
<td valign="top" align="center" colspan="2">Motor Phase <?lb?>Not Available<emphasis role="cline"/></td>
<td valign="top" align="center" colspan="2">TOTAL <?lb?>(minutes)<emphasis role="cline"/></td></tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="center">Video</td>
<td valign="top" align="center">Tablet</td>
<td valign="top" align="center">Video</td>
<td valign="top" align="center">Tablet</td>
<td valign="top" align="center">Video</td>
<td valign="top" align="center">Tablet</td>
<td valign="top" align="center">Video</td>
<td valign="top" align="center">Tablet</td>
<td valign="top" align="center">Video</td>
<td valign="top" align="center">Tablet</td></tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Dyskinesia</td>
<td valign="top" align="center">355</td>
<td valign="top" align="center">2500</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;28</td>
<td valign="top" align="center">&#x00A0;&#x00A0;431</td>
<td valign="top" align="center">18</td>
<td valign="top" align="center">&#x00A0;&#x00A0;712</td>
<td valign="top" align="center">&#x00A0;&#x00A0;85</td>
<td valign="top" align="center">126</td>
<td valign="top" align="center">486</td>
<td valign="top" align="center">3769</td>
</tr>
<tr>
<td valign="top" align="left">Bradykinesia</td>
<td valign="top" align="center">&#x00A0;&#x00A0;50</td>
<td valign="top" align="center">&#x00A0;&#x00A0;122</td>
<td valign="top" align="center">&#x00A0;&#x00A0;790</td>
<td valign="top" align="center">1394</td>
<td valign="top" align="center">25</td>
<td valign="top" align="center">&#x00A0;&#x00A0;308</td>
<td valign="top" align="center">&#x00A0;&#x00A0;81</td>
<td valign="top" align="center">&#x00A0;&#x00A0;85</td>
<td valign="top" align="center">947</td>
<td valign="top" align="center">1909</td>
</tr>
<tr>
<td valign="top" align="left">FOG</td>
<td valign="top" align="center">&#x00A0;&#x00A0;21</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;33</td>
<td valign="top" align="center">&#x00A0;&#x00A0;113</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;76</td>
<td valign="top" align="center">&#x00A0;&#x00A0;7</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;36</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;6</td>
<td valign="top" align="center">&#x00A0;&#x00A0;34</td>
<td valign="top" align="center">147</td>
<td valign="top" align="center">&#x00A0;&#x00A0;178</td>
</tr>
<tr>
<td valign="top" align="left">Tremor</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94</td>
<td valign="top" align="center">&#x00A0;&#x00A0;789</td>
<td valign="top" align="center">&#x00A0;&#x00A0;224</td>
<td valign="top" align="center">1200</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">680</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;2</td>
<td valign="top" align="center">&#x00A0;&#x00A0;80</td>
<td valign="top" align="center">336</td>
<td valign="top" align="center">2749</td>
</tr>
<tr>
<td valign="top" align="left">Total</td>
<td valign="top" align="center">520</td>
<td valign="top" align="center">3444</td>
<td valign="top" align="center">1155</td>
<td valign="top" align="center">3100</td>
<td valign="top" align="center">65</td>
<td valign="top" align="center">1737</td>
<td valign="top" align="center">174</td>
<td valign="top" align="center">325</td>
<td valign="top" align="center"></td>
<td valign="top" align="center"></td></tr>
</tbody>
</table>
</table-wrap>
</section>
</section>
<section class="lev1" id="sec4-4" label="4.4" xreflabel="4.4">
<title>Algorithmic Approach and Results</title>
<para>Once presented the complete scenario of the objective motor symptoms to be studied from a clinical perspective, it is necessary to propose an algorithmic methodological approach to bring all this knowledge closer to the achievement of machine-learning classifiers (algorithms) for the motor states monitoring tasks.</para>
<para>The methodological proposal to estimate the motor state (ON or OFF periods) of a PD patient wearing an inertial device is based on the use of a hierarchical system. In a first level, the system permits to put in context the patient&#x02019;s activity and a second level is in charge of the detection of the symptomatology of interest. The hierarchical system uses the output of the detection algorithms in this second level for the assessment of the patient&#x02019;s motor status. Some details are presented in <link linkend="F4-8">Figure <xref linkend="F4-8" remap="4.8"/></link>.</para>
<fig id="F4-8" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-8">Figure <xref linkend="F4-8" remap="4.8"/></link></label>
<caption><para>Outline of the structure defined for the algorithms for detecting symptoms of PD.</para></caption>
<graphic xlink:href="graphics/ch04_fig008.jpg"/>
</fig>
<para>The contextualization of the patient&#x02019;s activity and posture is very important because the evaluation of the different PD symptoms is related to the activity developed by the patient. Thus, evaluation of bradykinesia will only be performed when the patient is walking, since it is during self-executing activities when this symptom is clearly manifested. In this way, the inertial signals from the primary accelerometer sensor are analysed using temporary windowing with a set of algorithms that determines if the patient is walking and, if so, signals are analysed to determine the presence of Bradykinesia. This strategy is applied in a similar way for Dyskinesia, where the detection is performed only in the case that the contextualization algorithms determine that the patient is not walking during the windowed analysis, since it is considered that the gait hides dyskinetic movements.</para>
<para>The information obtained from the detectors of bradykinesia and dyskinesia, together with the FOG detector results will be analysed through a set of additional algorithms, which will determine the final motor state of the PD patient (ON/OFF states). At this stage, as it is indicated in <link linkend="F4-8">Figure <xref linkend="F4-8" remap="4.8"/></link>, it is necessary to use some personal parameters of the patient (basically obtained from previous medical history information).</para>
<para>The development of the different detection algorithms, corresponding to each considered symptom was done independently, taking as a starting point some relevant papers published so far, analysing them, exploiting the acquired signals contained in the REMPARK database and trying to improve, when possible, the previous published results. As it has been already mentioned, the methodology used is based on a machine-learning approach, mainly using supervised learning techniques. The available database described in the above Section 4.3 was used for this purpose.</para>
<para>In the machine-learning area, it is a common practice to divide the Database into different sub-sets. One sub-set is strictly used for algorithmic training purposes and other sub-set is only used for testing. Related works performed in REMPARK project used this approach and the results of the different techniques were evaluated with the patients&#x02019; data not used in the training process of the supervised learning algorithms.</para>
<para>The signals labelled according to the symptoms listed in <link linkend="T4-4">Table <xref linkend="T4-4" remap="4.4"/></link> were used to train the different supervised learning models. It must be considered that all the included algorithms process accelerometer measurements sampled at 40 Hz. In addition to the symptoms listed in <link linkend="T4-4">Table <xref linkend="T4-4" remap="4.4"/></link> (dyskinesia, bradykinesia, FOG, and tremor), there is another subsection devoted to describe the estimation of gait parameters. A description of the algorithmic work done is presented in the following subsections.</para>
<section class="lev2" id="sec4-4-1" label="4.4.1" xreflabel="4.4.1">
<title>Dyskinesia Detection Algorithm</title>
<para>A processing method based on a frequency analysis of the signal was implemented and used for Dyskinesia detection. The method considers the power spectrum of the concrete band between 1 and 4 Hz for the detection of Dyskinesia, provided that information corresponding to higher frequency band (from 8 to 20 Hz) could correspond to false positives such as walking or climbing stairs. Additionally, a number of conditions are added in order to allow a better contextualization of the patient&#x02019;s movement and consequently, to improve the specificity of the algorithm. The algorithm has been subdivided into two steps (detailed below), one at window level and one at the minute level.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>In the first step (at window level), the evaluation of the presence of Dyskinesia is done through the analysis of three separate frequency bands:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Dyskinesia Band</emphasis>: A high spectral power density in this band is a clear indication that the patient is suffering Dyskinesia, although it may also mean that the patient is walking or climbing stairs. This band is covering from 0.68 Hz to 4 Hz.</para></listitem>
<listitem>
<para><emphasis role="strong">Non-dyskinetic band</emphasis>: It is considered that this band covers from 8 to 20 Hz. This frequency band allows to discriminate if an increase of spectral power in the band of Dyskinesia is due to the appearance of a Dyskinesia or because the patient is walking (or doing similar activities).</para></listitem>
<listitem>
<para><emphasis role="strong">Postural transition band</emphasis>: This is the band from 0 to 0.68 Hz. The posture transition is a very common action and involves very low frequencies that can generate harmonics in the Dyskinesia band, which may provoke false positives.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para>The detection of Dyskinesia, based on frequency band analysis allows us to know, in a given time window, whether or not the patient has Dyskinesia. However, Dyskinesia is a symptom that is repeated over time for many minutes, this fact can be used to minimize, using an aggregation process, the presence of false positives. This method of aggregation allows us to examine the appearance of Dyskinesia in several consecutive windows over time by performing an aggregation of the output of each window providing a unique output in a given time slot (it has been considered a period of 1 minute in the implemented algorithms).</para></listitem>
</itemizedlist>
<para>This signal processing method was applied to the database of signals by using a leave-one-patient-out scheme on the minute-basis output of the algorithm.</para>
<para>The main reference for this work is [7] and a summary of the results obtained is provided in <link linkend="T4-5">Table <xref linkend="T4-5" remap="4.5"/></link>. The results were obtained with REMPARK&#x02019;s database of video-labelled signals from 92 PD patients.</para>
<para>Specificities and sensitivities are provided for each different type of dyskinesia. With regards to the most important in the clinical sense, i.e. the strong trunk dyskinesia, the algorithm achieves a specificity of 95% and a sensitivity of 100%.</para>
<table-wrap position="float" id="T4-5">
<label><link linkend="T4-5">Table <xref linkend="T4-5" remap="4.5"/></link></label>
<caption><para>Dyskinesia algorithm results</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="center" colspan="2">Type of Choreic Dyskinesia<emphasis role="cline"/></td>
<td valign="bottom" align="center" rowspan="2">Num. of Patients with This Type of Choreic Dyskinesia</td>
<td valign="bottom" align="center" colspan="3">Equal Weight per Minute<emphasis role="cline"/></td></tr>
<tr>
<td valign="top" align="left">Severity</td>
<td valign="top" align="left">Body Part</td>
<td valign="top" align="center">Specificity (%)</td>
<td valign="top" align="center">Sensitivity (%)</td>
<td valign="top" align="center">Total Minutes</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Weak</td>
<td valign="top" align="left">Trunk</td>
<td valign="top" align="center">16</td>
<td valign="top" align="center">95</td>
<td valign="top" align="center">78</td>
<td valign="top" align="center">953</td>
</tr>
<tr>
<td valign="top" align="left">Strong</td>
<td valign="top" align="left">Trunk</td>
<td valign="top" align="center">4</td>
<td valign="top" align="center">95</td>
<td valign="top" align="center">100</td>
<td valign="top" align="center">895</td>
</tr>
<tr>
<td valign="top" align="left">Weak</td>
<td valign="top" align="left">No-trunk</td>
<td valign="top" align="center">32</td>
<td valign="top" align="center">95</td>
<td valign="top" align="center">39</td>
<td valign="top" align="center">1110</td>
</tr>
<tr>
<td valign="top" align="left">Strong</td>
<td valign="top" align="left">No-trunk</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">95</td>
<td valign="top" align="center">90</td>
<td valign="top" align="center">917</td></tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec4-4-2" label="4.4.2" xreflabel="4.4.2">
<title>Bradykinesia Detection Algorithm</title>
<para>Bradykinesia appears when plasma&#x02019;s dopamine level is low, seriously complicating the general mobility of the patient and, in particular, causing changes and compromising the way of walking.</para>
<para>The analysis done has been based on the gait cycles characterization. The detector algorithm identifies, on the one hand, the strides that the patient is currently carrying out and, on the other hand, characterizes these gait cycles, allowing the analysis of Bradykinesia through specific characteristics that correlate with the presence of a pathological alteration.</para>
<para>In the analysis of the database, it was concluded that the most important feature that helps to diagnose the occurrence of Bradykinesia is the <emphasis>fluidity</emphasis> <emphasis>of movement</emphasis> when walking. Fluidity is a <emphasis role="strong">highly subjective variable</emphasis> that is not currently objectively measurable. When a patient presents a very low movement fluidity, the probability of manifesting Bradykinesia is very high. This principle allows to generate an algorithmic approach that objectively measures characteristics associated with the fluidity of the movement and, furthermore, enables the detection of the symptom based on comparative thresholds, which determines when the symptom is present.</para>
<para>The bradykinesia detection algorithm is structured using a three-stage scheme (see <link linkend="F4-9">Figure <xref linkend="F4-9" remap="4.9"/></link>). In the first one, the contextualization of the movement is realized, detecting if the patient is walking or not. In the second block, a process of recognition and identification of strides/steps is performed, and the last block performs the analysis of the characteristics of strides/steps that may be representative of the occurrence of Bradykinesia.</para>
<fig id="F4-9" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-9">Figure <xref linkend="F4-9" remap="4.9"/></link></label>
<caption><para>Scheme of the bradykinesia detection algorithm.</para></caption>
<graphic xlink:href="graphics/ch04_fig009.jpg"/>
</fig>
<para>The walking detection done at the first stage is performed through a process of pattern recognition from the obtained accelerometer signals. A binary-classification procedure has been approached to detect gait through the use of Support Vector Machines (SVM). The input of the SVM consists of a group of features, which are extracted from a temporary window of signal obtained from the accelerometer. The training set for the SVM was generated through the windows obtained from the signals corresponding to a group of 10 patients, which were acquired from a previously obtained database and its associated gold standard. It should be noted that these patients were not used, later, in the validation group of the final implemented algorithm. The most relevant considered characteristics for the detection of the gait are the power spectra in the three spatial axes, for the bands from 0.1 to 3 Hz and from 0.1 to 10 Hz.</para>
<para>The step detection process is launched when the SVM walking detection has been positive on a given window. This step detection is carried out by recognizing the biomechanical characteristics of walking in the acceleration measurements taken from the sensor (located in the waist).</para>
<para>The interest of the analysis focuses on the strides (two consecutive steps of each feet) and their characterization, in order to represent the fluidity of the patient&#x02019;s movement. Several statistical markers have been studied and evaluated for this purpose, bearing in mind that the best marker is the one maximizing the separation between the presence and absence of Bradykinesia.</para>
<para>Additionally, it must be considered that the states (Bradykinesia presence or not) are very dependent on the user and, therefore, the threshold that correctly separates the states of a particular patient may have a value different from the threshold of another patient. The main reference of this work is [8] and a summary of results is provided in <link linkend="T4-6">Table <xref linkend="T4-6" remap="4.6"/></link>. These results were obtained by analysing the data from the 92 PD patients who participated in the database construction.</para>
<table-wrap position="float" id="T4-6">
<label><link linkend="T4-6">Table <xref linkend="T4-6" remap="4.6"/></link></label>
<caption><para>Bradykinesia algorithm results</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="center">Specificity</td>
<td valign="top" align="center">Sensitivity</td>
<td valign="top" align="center">PPV</td>
<td valign="top" align="center">NPV</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="center">81%</td>
<td valign="top" align="center">88%</td>
<td valign="top" align="center">89%</td>
<td valign="top" align="center">84%</td></tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec4-4-3" label="4.4.3" xreflabel="4.4.3">
<title>Tremor Detection Algorithm</title>
<para>Tremor was evaluated by analysing the signals provided by the wrist sensor included in the REMPARK system. A frequency analysis of the signals was performed, permitting the extraction of several characteristic features in order to determine the presence of the symptom. The process is based on a SVM model.</para>
<para>The signal processing approach is divided into two different phases: the window level in which tremor is recognized based on short duration signals and the meta-analysis level that aggregates several window detections.</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>At the window level, frequency related features of the signals are used, because this is one of the most common methods. We observed that frequencies in the band from 4 to 6 Hz appear when Parkinsonian tremor is present, and these frequencies are not observed when this type of tremor is absent (which is in agreement with current literature).</para>
<para>Given the main frequency behaviour of this sort of tremor, it could be theoretically detected only using frequency characteristics. However, a list of other features has been used in the literature for this purpose (for instance, Fast Fourier Transform (FFT), Peak frequency and its amplitude, Entropy of signal, Sum of first, second and third harmonic . . .). In order to measure the impact of non-frequency features in the accurate detection of tremor, two approaches were defined. On the one hand, a first method only used frequency features while, on the other hand, the second approach also included non-frequency features that were previously used in the literature (see reference [9] for additional details).</para>
<para>Both approaches are composed of two phases in order to determine if tremor is present in a certain time window:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Feature extraction phase. Features are defined depending on the used approach: frequency features alone or combined with those mentioned above. Frequency features from three axes were obtained, and their amplitudes were summed up without taking into account the amplitude of the zero-frequency harmonic. Thus, dependence on the sensor&#x02019;s orientation is avoided. From this, the previously described features were acquired.</para></listitem>
<listitem>
<para>Learning phase. An SVM classifier is trained to distinguish tremor and non-tremor windows based on the chosen feature set.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para>At the meta-analysis level, since it is very important to minimize the resources needed for tremor detection, time windows must be as short as possible (i.e. about few seconds). However, short windows are likely to produce false positives (e.g. a single segment with tremor surrounded by non-tremor segments) since short movement may be confused with tremor (e.g. teeth brushing). Thus, a meta-analysis is added in order to enhance the reliability of the proposed approaches.</para>
<para>The employed meta-analysis method considers the algorithm&#x02019;s outputs in a set of several consecutive windows covering a period of several seconds. These outputs are aggregated into a value representing the probability of having tremor in the corresponding period. This period is considered as tremor if the probability is greater than a certain threshold.</para></listitem>
</orderedlist>
<para>Following the common procedure in the field, the database was split into three non-overlapping sub-datasets: training, holdout and test. A SVM classifier was trained to distinguish tremor and non-tremor windows, using the training sub-dataset. The final evaluation was done on the test dataset and indicates the performance of the developed algorithms.</para>
<table-wrap position="float" id="T4-7">
<label><link linkend="T4-7">Table <xref linkend="T4-7" remap="4.7"/></link></label>
<caption><para>Tremor algorithm results as presented in [9]</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="center">RBF+Freq.</td>
<td valign="top" align="center">Lin.+Freq.</td>
<td valign="top" align="center">RBF+All</td>
<td valign="top" align="center">Lin.+All</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Sensitivity (holdout)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">90,00%</td>
</tr>
<tr>
<td valign="top" align="left">Specificity (holdout)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,50%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;99,50%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;99,30%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;97,20%</td>
</tr>
<tr>
<td valign="top" align="left">Data Usage (holdout)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;57,70%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;41,10%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;42,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;82,10%</td>
</tr>
<tr>
<td valign="top" align="left">Sensitivity (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;97,30%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;91,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,10%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;92,10%</td>
</tr>
<tr>
<td valign="top" align="left">Specificity (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;96,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;99,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,60%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;97,50%</td>
</tr>
<tr>
<td valign="top" align="left">Data Usage (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;55,50%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;40,80%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;42,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;79,90%</td>
</tr>
<tr>
<td valign="top" align="left">Geometric Mean (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;97,10%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,40%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,80%</td>
</tr>
<tr>
<td valign="top" align="left">Accuracy (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;96,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,60%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,60%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;97,30%</td></tr></tbody>
</table>
</table-wrap>
<para>In total two feature sets (i.e. only frequency features vs. commonly employed features) and two SVM kernels (i.e. linear vs. Radial Basis Function (RBF)) were evaluated.</para>
<para>The main reference for the tremor algorithmic approach is [9] and a summary of results is provided in <link linkend="T4-7">Table <xref linkend="T4-7" remap="4.7"/></link>, where each column represents a different learning model: &#x0201C;RBF+ Freq.&#x0201D; corresponds to a SVM with RBF kernel and frequency features, &#x0201C;Lin+Freq.&#x0201D; corresponds to a SVM with linear kernel and frequency features, &#x0201C;RBF+All&#x0201D; corresponds to a SVM with RBF kernel and both frequency and temporal features, and, finally, &#x0201C;Lin+All&#x0201D; corresponds to a SVM with linear kernel and both temporal and frequency features. These results were obtained by training the method with data from 18 patients and validating it with data from 74 patients.</para>
</section>
<section class="lev2" id="sec4-4-4" label="4.4.4" xreflabel="4.4.4">
<title>Freezing of Gait (FOG) Detection Algorithm</title>
<para>Freezing of Gait (FOG) is a widely studied and evaluated symptom from the point of view of automatic detection methodology, since it is one of the most disabling symptoms for the patients and one of the most difficult to be evaluated by clinicians.</para>
<para>As it is clear from the current literature, detection techniques for the laboratory setting are highly developed at the moment, and they have had relatively high success rates. However, many problems arise when we tried to apply these methods to the daily living activities, because many false positive appeared due to the new situations and movements appearing under non-controlled scenarios.</para>
<para>In the literature, it has been identified a frequency band on the acceleration signals from the lower limbs of PD patients associated with FOG episodes and ranged between 3 and 8 Hz. In consulted work, a freezing index is defined based on the ratio of the square of the spectral power of these frequencies associated with the freezing band to the square of the spectral power of the frequency band corresponding to the act of walking, (between 0.5 and 3 Hz).</para>
<para>Since FOG mainly occurs when starting, during or at the end of the gait, it is essential to contextualize the patient&#x02019;s activity through a gait detection algorithm. We can take advantage of the gait detector based on the SVM presented in the Subsection 4.4.2 (for Bradykinesia detection). Some points must be considered:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Contextualization was implemented in the sense that positive FOG detection is validated when the algorithm detected that the patient is walking or has been walking for the last 5 seconds.</para></listitem>
<listitem>
<para>The onset of gait is a complex detection since, in the case of a <emphasis>posteriori</emphasis> detection, the condition that validates the detection may never occur because probably the patient would experiment a fall, or because the patient&#x02019;s FOG lasts longer than the imposed temporary condition.</para></listitem>
<listitem>
<para>In addition to adding the validation condition of 5 seconds walking to the formulation, some significant detectable events were considered to know when a patient is rising from the sit position (transition from sitting to standing). This action is very important for the contextualization of FOG since a large number of episodes occurs some moments after the patient is performing this action and try to walk. With this objective, the postural transition band was used for the detection of these events.</para></listitem>
</itemizedlist>
<table-wrap position="float" id="T4-8">
<label><link linkend="T4-8">Table <xref linkend="T4-8" remap="4.8"/></link></label>
<caption><para>Freezing of Gait algorithm results</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr style="border-bottom:1px solid;">
<td valign="top" align="left">Kernel</td>
<td valign="top" align="center">RBF</td>
<td valign="top" align="center">Linear</td>
<td valign="top" align="center">RBF</td>
<td valign="top" align="center">Linear</td>
</tr>
<tr>
<td valign="top" align="left">Features</td>
<td valign="top" align="center">Freq.</td>
<td valign="top" align="center">Freq.</td>
<td valign="top" align="center">All</td>
<td valign="top" align="center">All</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Sensitivity (train)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;92,30%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;92,30%</td>
</tr>
<tr>
<td valign="top" align="left">Specificity (train)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
</tr>
<tr>
<td valign="top" align="left">Data Usage (train)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;69,60%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;89,10%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;90,60%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,60%</td>
</tr>
<tr>
<td valign="top" align="left">Geometric Mean (train)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;96,10%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;96,10%</td>
</tr>
<tr>
<td valign="top" align="left">Accuracy (train)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,70%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,50%</td>
</tr>
<tr>
<td valign="top" align="left">True Positives</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;9</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;8</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;9</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;12</td>
</tr>
<tr>
<td valign="top" align="left">False Positives</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;0</td>
</tr>
<tr>
<td valign="top" align="left">True Negatives</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;55</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;82</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;65</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;65</td>
</tr>
<tr>
<td valign="top" align="left">False Negatives</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;1</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;1</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;1</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;1</td>
</tr>
<tr>
<td valign="top" align="left">Sensitivity (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;90,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;88,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;90,00%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;92,30%</td>
</tr>
<tr>
<td valign="top" align="left">Specificity (test)</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
<td valign="top" align="center">100,00%</td>
</tr>
<tr>
<td valign="top" align="left">Data Usage (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;82,30%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;91,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,70%</td>
</tr>
<tr>
<td valign="top" align="left">Geometric Mean (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,30%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;94,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;96,10%</td>
</tr>
<tr>
<td valign="top" align="left">Accuracy (test)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,50%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,90%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,70%</td>
<td valign="top" align="center">&#x00A0;&#x00A0;98,70%</td></tr></tbody>
</table>
</table-wrap>
<para>In summary, this symptom is detected based on a set of both temporal and frequency features, similarly to the tremor detection algorithm, although the presented contextualisation is added. The main reference for the algorithmic approach is [10] and a summary of results is provided in <link linkend="T4-8">Table <xref linkend="T4-8" remap="4.8"/></link>, where each column represents a different learning model: &#x0201C;RBF freq.&#x0201D; corresponds to a SVM with RBF kernel and frequency features, &#x0201C;Linear Freq.&#x0201D; corresponds to a SVM with linear kernel and frequency features, &#x0201C;RBF All&#x0201D; corresponds to a SVM with RBF kernel and both frequency and temporal features, and, finally, &#x0201C;Linear All&#x0201D; corresponds to a SVM with linear kernel and both temporal and frequency features.</para>
<para>In this case, a subset of the whole REMPARK database was used. More specifically, these results were obtained by using signals from 15 patients as a training set and the resulting model being evaluated with signals from other 5 patients. Training was done with patients who had FOG episodes. Validation was done with both patients with FOG and patients without FOG.</para>
</section>
<section class="lev2" id="sec4-4-5" label="4.4.5" xreflabel="4.4.5">
<title>Gait Parameters Estimation</title>
<para>Algorithms for the correct estimation of the gait parameters were included in the sensor embedded software. Some previous activity and the collection of a labelled database was performed in order to implement the most suitable approach.</para>
<fig id="F4-10" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F4-10">Figure <xref linkend="F4-10" remap="4.10"/></link></label>
<caption><para>(a) The inertial system prototype (9 &#x000D7; 2, Version 6) positioned in a neoprene belt on left lateral side of waist. Acceleration signals obtained from (a) Lumbosecaral point of waist and (b) left lateral side of waist.</para></caption>
<graphic xlink:href="graphics/ch04_fig0010a.jpg"/>
</fig>
<para>As part of a series of controlled tests, patients performed a gait test in which their average step length and average step velocity was measured. These values were estimated through the waist-sensor signals and a novel inverted-pendulum model. The sensor location used in REMPARK provides a different kind and shape of signals than those previously obtained in the literature, that commonly are using the Anterior Superior Iliac Spine position for the reported experiments.</para>
<para><link linkend="F4-10">Figure <xref linkend="F4-10" remap="4.10"/></link>(b) and 4.10(c) show the acceleration signal from lower back (around L4&#x02013;L5) and left lateral side (near ASIS) of waist, obtained with the REMPARK sensor. It can be seen that the symmetry among left-right steps is lost in signals obtained from the lateral side. Signals from the left leg are more prominent than those from the right leg which impose new restriction on step detection and step length estimation.</para>
<para>The signals from the lateral side differ from those from the lower back of waist. A newly developed step detection method called SWAT [11] was developed, combined with an adapted step length estimator based to accurately estimate the step lengths from this position. From the left lateral point of view, the proposed gait model considers vertical displacement of waist as an inverted pendulum (IP) model during right step and during single support phase of left step.</para>
<para>Step detection performs an average window that is calculated over the magnitude of the acceleration signals. Mean is removed from this average window signal, and, then, the resulting signal is used to identify left and right initial contacts (IC) and toe-offs (TO) events. When the foot&#x02019;s heal touches the ground, the event is called as IC, and when the foot leaves it is called as toe-off (TO).</para>
<para>The initial contact and toe-off events of left and right legs are noted here as LIC, LTO, RIC and RTO respectively. As the sensor was placed on the left lateral side, the local maximum lateral signal can be used to identify incidents of LICs immediately before or after it. For every local maximum in the SWAT signal, if there was no incident of LIC in the lateral signal immediate before or after it, then it is determined to be a RIC. If there is an incident of LIC, the mid-point from the local maximum to zero is considered to be a LIC. For each detected RIC, the next zero crossing point is considered as a LTO. For each LIC, the mid-point of next zero to the local minimum are searched and considered as a RTO.</para>
<para>The main reference for this work is [11], where it is shown that the results obtained by the proposed method in 28 patients from the REMPARK database show that gait parameters can be estimated with an average RMSE error below 0,04 meters.</para>
</section>
<section class="lev2" id="sec4-4-6" label="4.4.6" xreflabel="4.4.6">
<title>Fall Detection Algorithm</title>
<para>The set of algorithms developed and implemented in the REMPARK project is complemented by a fall detection algorithm that was previously developed by one of the partners (UPC). This algorithm enables the detection of falls based on specific computations through accelerometer measurements sampled at 40 Hz. This algorithm is included in the set of algorithms implemented in order to provide more information through the REMPARK system and include the possibility of raising alarms.</para>
<para>The fall detection algorithm has been successfully validated in the &#x0201C;Fall Detection for the Elderly&#x0201D; (FATE) project (CIP-ICT-PSP-2011-5-297178) [12]. It has shown a sensitivity and specificity above 95% along a pilot in which more than 200 users from three countries (Spain, Italy and Ireland) participated.</para>
</section>
<section class="lev2" id="sec4-4-7" label="4.4.7" xreflabel="4.4.7">
<title>ON/OFF Motor State Estimation</title>
<para>The algorithmic part for determining the motor state (ON/OFF state) of a person with Parkinson is very complex, because the high degree of subjectivity included in the construction process of a correct model to be used. A main problem is due to the fact that patients, sometimes, are not able to correctly identify their own symptoms and, in some cases, may confuse them with non-motor symptoms. Additionally, when non-motor symptoms are present, it is even more difficult for these persons a correct identification.</para>
<para>This could be a very compromising situation when a machine learning approach is intended to be used, since the most common gold-standard, in these cases, is the patient-diary where the patient should annotate the experimented symptoms every hour, along the day.</para>
<para>In order to be able to implement an objective algorithmic approach to the problem, the related medical literature was reviewed and useful discussions were organized with professionals for determining as much as possible the set of objective conditions characterizing the ON/OFF states. The most widespread definition of the OFF state is to refer to those periods in which low dopaminergic levels occur, in which Bradykinesia is the most correlated symptom. In addition, one can also use the fact that the appearance of Chorea Dyskinesia is commonly produced by high levels of dopamine.</para>
<para>This approach makes possible, based on the algorithms of motor symptoms that have been discussed along this section, to approximate the motor states of the patient with the help of a decision tree technique:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The algorithm determines that the patient is in ON state when either non-bradykinetic gait or Dyskinesia are detected.</para></listitem>
<listitem>
<para>OFF state is assumed when bradykinetic gait is detected.</para></listitem>
</itemizedlist>
<para>This algorithmic approach was tested in the final pilots of REMPARK and its output was compared to the diaries annotated by patients during 3 days. Results are presented in the <link linkend="ch09">Chapter <xref linkend="ch9" remap="9"/></link> and the original public deliverable document (with the reference D9.2) is available at the REMPARK website. The specificity and sensitivity on detecting OFF and ON motor states in 33 PD patients was 89% and 98%, respectively.</para>
</section>
</section>
<section class="lev1" id="sec4-5" label="4.5" xreflabel="4.5">
<title>Conclusions</title>
<para>This chapter has presented a huge effort made by REMPARK consortium in order to develop a system capable of monitoring PD motor symptoms in ambulatory conditions. A highly accurate database of labelled signals and clinical questionnaires were collected from 92 PD patients, with more than 340 hours of recorded signals. The labelled signals have been used to train different machine learning methods. The resulting approaches have shown that the selected PD motor symptoms can be accurately monitored through the corresponding sensors, with specificities and sensitivities about 90% in most cases.</para>
<para>Many different algorithms and their results have been presented. The algorithms covering Bradykinesia, Dyskinesia, Tremor, Freezing of Gait (FOG) and gait parameters, employing the collected REMPARK database have been commented and their results presented. However, the ON/OFF algorithm was only tested in the final pilots, since it had to be validated with ON/OFF diaries filled by the patients, used as gold-standard.</para>
</section>
<section class="lev1" id="sec4-6">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>REMPARK Deliverable D1.2 &#x02013; Questionnaire addressed to doctors/ physiotherapists. Answers and statistical results. Publicly available.</para></listitem>
<listitem>
<para>Agid, Y., Ruberg, M., Hirsch, E., Raisman-Vozari, R., Vyas, S., Faucheux, B., Michel, P., Kastner, A., Blanchard, V., Damier., P., Villares, J., &#x00026; Zhang, P. (1993). Are dopaminergic neurons selectively vulnerable to Parkinson&#x02019;s disease? Advances in Neurology, 60, 148&#x02013;164. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Agid%2C+Y%2E%2C+Ruberg%2C+M%2E%2C+Hirsch%2C+E%2E%2C+Raisman-Vozari%2C+R%2E%2C+Vyas%2C+S%2E%2C+Faucheux%2C+B%2E%2C+Michel%2C+P%2E%2C+Kastner%2C+A%2E%2C+Blanchard%2C+V%2E%2C+Damier%2E%2C+P%2E%2C+Villares%2C+J%2E%2C+%26+Zhang%2C+P%2E+%281993%29%2E+Are+dopaminergic+neurons+selectively+vulnerable+to+Parkinson%27s+disease%B4+Advances+in+Neurology%2C+60%2C+148-164%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Braak, H., Del Tredici, K., Rub, U. et al. (2003). Staging of brain pathology related to sporadic Parkinson&#x02019;s disease. Neurobiol Aging 24: 197&#x02013;211. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Braak%2C+H%2E%2C+Del+Tredici%2C+K%2E%2C+Rub%2C+U%2E+et+al%2E+%282003%29%2E+Staging+of+brain+pathology+related+to+sporadic+Parkinson%27s+disease%2E+Neurobiol+Aging+24%3A+197-211%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Chase, T. N., Juncos, J. L. Fabbrini, G., Mouradian, M. M. (1988). Motor response complication in advanced Parkinson&#x02019;s disease. Function Neurol 3(4): 429&#x02013;436. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Chase%2C+T%2E+N%2E%2C+Juncos%2C+J%2E+L%2E+Fabbrini%2C+G%2E%2C+Mouradian%2C+M%2E+M%2E+%281988%29%2E+Motor+response+complication+in+advanced+Parkinson%27s+disease%2E+Function+Neurol+3%284%29%3A+429-436%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Dauer, W., &#x00026; Przedborski, S. (2003). Parkinson&#x02019;s disease: Mechanism and models. Neuron, 39, 889&#x02013;909. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Dauer%2C+W%2E%2C+%26+Przedborski%2C+S%2E+%282003%29%2E+Parkinson%27s+disease%3A+Mechanism+and+models%2E+Neuron%2C+39%2C+889-909%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Hughes, A. J., Daniel, S. E., Kilford, L., Lees, A. J. Accuracy of clinical diagnosis of idiopathic Parkinson&#x02019;s disease: a clinico-pathological study of 100 cases. J Neurol Neurosurg Psychiatry 1992; 55: 181&#x02013;184. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Hughes%2C+A%2E+J%2E%2C+Daniel%2C+S%2E+E%2E%2C+Kilford%2C+L%2E%2C+Lees%2C+A%2E+J%2E+Accuracy+of+clinical+diagnosis+of+idiopathic+Parkinson%27s+disease%3A+a+clinico-pathological+study+of+100+cases%2E+J+Neurol+Neurosurg+Psychiatry+1992%3B+55%3A+181-184%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>P&#x00E9;rez-L&#x00F3;pez, C., Sam&#x00E0;, A., Rodr&#x00ED;guez-Mart&#x00ED;n, D., Moreno-Ar&#x00F3;stegui, J. M., Cabestany, J., Bayes, A., . . . &#x00026; Sweeney, D. (2016). Dopaminergic-induced dyskinesia assessment based on a single belt-worn accelero- meter. <emphasis>Artificial intelligence in medicine</emphasis>, <emphasis>67</emphasis>, 47&#x02013;56. <ulink url="https://scholar.google.com/scholar?q=Dopaminergic-induced+dyskinesia+assessment+based+on+a+single+belt-worn+accelero-+meter.+Artificial+intelligence+in+medicine%2C+67%2C&amp;btnG=&amp;hl=en&amp;as_sdt=0%2C5" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Sam&#x00E0;, A., Perez-Lopez, C., Romagosa, J., Rodriguez-Martin, D., Catala, A., Cabestany, J., . . . &#x00026; Rodriguez-Molinero, A. (2012, August). Dyskinesia and motor state detection in Parkinson&#x02019;s disease patients with a single movement sensor. In <emphasis>2012 Annual International Conference of the IEEE Engineering in Medicine and Biology Society</emphasis> (pp. 1194&#x02013;1197). IEEE. <ulink url="https://scholar.google.com/scholar?q=Dyskinesia+and+motor+state+detection+in+Parkinson%27s+disease+patients+with+a+single+movement+sensor.+In+2012+Annual+Inte&amp;btnG=&amp;hl=en&amp;as_sdt=0%2C5" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Ahlrichs, C., &#x00026; Sam&#x00E0;, A. (2014, May). Is frequency distribution enough to detect tremor in PD patients using a wrist worn accelerometer? In <emphasis>Proceedings of the 8th International Conference on Pervasive Computing Technologies for Healthcare</emphasis> (pp. 65&#x02013;71). ICST (Institute for Computer Sciences, Social-Informatics and Telecommunications Engineering). <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Ahlrichs%2C+C%2E%2C+%26+Sam%E0%2C+A%2E+%282014%2C+May%29%2E+Is+frequency+distribution+enough+to+detect+tremor+in+PD+patients+using+a+wrist+worn+accelerometer%B4+In+Proceedings+of+the+8th+International+Conference+on+Pervasive+Computing+Technologies+for+Healthcare+%28pp%2E+65-71%29%2E+ICST+%28Institute+for+Computer+Sciences%2C+Social-Informatics+and+Telecommunications+Engineering%29%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Ahlrichs, C., Sam&#x00E0;, A., Lawo, M., Cabestany, J., Rodr&#x00ED;guez-Mart&#x00ED;n, D., P&#x00E9;rez-L&#x00F3;pez, C., . . . &#x00026; Browne, P. (2016). Detecting freezing of gait with a tri-axial accelerometer in Parkinson&#x02019;s disease patients. <emphasis>Medical &#x00026; biological engineering &#x00026; computing</emphasis>, <emphasis>54</emphasis>(1), 223&#x02013;233. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Ahlrichs%2C+C%2E%2C+Sam%E0%2C+A%2E%2C+Lawo%2C+M%2E%2C+Cabestany%2C+J%2E%2C+Rodr%EDguez-Mart%EDn%2C+D%2E%2C+P%E9rez-L%F3pez%2C+C%2E%2C+%2E+%2E+%2E+%26+Browne%2C+P%2E+%282016%29%2E+Detecting+freezing+of+gait+with+a+tri-axial+accelerometer+in+Parkinson%27s+disease+patients%2E+Medical+%26+biological+engineering+%26+computing%2C+54%281%29%2C+223-233%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Sayeed, T., Sam&#x00E0;, A., Catal&#x00E0;, A., Rodr&#x00ED;guez-Molinero, A., &#x00026; Cabestany, J. (2015). Adapted step length estimators for patients with Parkinson&#x02019;s disease using a lateral belt worn accelerometer. <emphasis>Technology and Health Care</emphasis>, <emphasis>23</emphasis>(2), 179&#x02013;194. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Sayeed%2C+T%2E%2C+Sam%E0%2C+A%2E%2C+Catal%E0%2C+A%2E%2C+Rodr%EDguez-Molinero%2C+A%2E%2C+%26+Cabestany%2C+J%2E+%282015%29%2E+Adapted+step+length+estimators+for+patients+with+Parkinson%27s+disease+using+a+lateral+belt+worn+accelerometer%2E+Technology+and+Health+Care%2C+23%282%29%2C+179-194%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>FATE project website. <ulink url="http://www.project-fate.eu">www.project-fate.eu</ulink>. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=FATE+project+website%2E+www%2Eproject-fate%2Eeu%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch05" label="5" xreflabel="5">
<title>Sensor Sub-System</title>
<para role="author"><emphasis role="strong">Carlos P&#x00E9;rez and Daniel Rodriguez-Martin</emphasis></para>
<para>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<section class="lev1" id="sec5-1" label="5.1" xreflabel="5.1">
<title>Introduction</title>
<para>The sensor is an important part of REMPARK since it is in charge of capturing relevant inertial data from the patient&#x02019;s movement pattern. The location of the sensor is the left side of the waist and its operation is autonomous and done in real-time. The sensor, described along the present chapter, has an embedded set of algorithms, already introduced in precedent chapters, and able to determine indicators for specific movement disorders related to PD, mainly Dyskinesia, Freezing of Gait (FOG) and Bradykinesia.</para>
<para>Following the requirements derived for this sub-system (discussed in <link linkend="ch03">Chapter <xref linkend="ch3" remap="3"/></link>), the main design principles, among many others, are:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>the achievement of a device with a reasonable operating autonomy (adjusted power consumption), but keeping a small physical size;</para></listitem>
<listitem>
<para>a device capable of being worn comfortably, permitting the regular activities along the day; and</para></listitem>
<listitem>
<para>the local execution, in real-time, of the embedded algorithmic set for symptoms&#x02019; detection.</para></listitem>
</itemizedlist>
<para>The system includes the classical elements of an Inertial Measurement Unit (IMU), together with a dedicated part for battery control and energy consumption optimisation. The battery level and the status of the main application process are indicated to the user using a LED.</para>
<para>A microcontroller (&#x00B5;C) is in the nucleus of the sensor, being responsible for the real-time and local execution of the developed algorithms on the acquired data. This microcontroller is also responsible for handling and controlling the rest of the components.</para>
</section>
<section class="lev1" id="sec5-2" label="5.2" xreflabel="5.2">
<title>Sensor&#x02019;s Data Processing Flow</title>
<para>Before entering into the details of the sensor sub-system, it is necessary to establish the Processing Data flow implemented within the sensor device for executing the symptoms&#x02019; detection algorithms in real-time.</para>
<para>Developed algorithms operate on acquired samples on inertial sensors, and <link linkend="F5-1">Figure <xref linkend="F5-1" remap="5.1"/></link> shows a data flow compatible with the previously presented processing specifications. Since many of the implemented algorithms are based on a windowed analysis of the related signals, the figure distinguishes three main parts:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>A first one is a set of calculations performed after acquiring a sample, which mainly consist in the filtering of the signals to condition them, followed by the execution of the fall detection algorithm.</para></listitem>
<listitem>
<para>A second one comprising the calculations performed at the end of a window time, which comprises the main computations for the monitoring of the motor symptoms (detection of Bradykinesia, Dyskinesia and FoG).</para></listitem>
<listitem>
<para>The third part comprises the computations done once per minute, in which the final output of the algorithms is obtained and shared through the mobile phone.</para></listitem>
</itemizedlist>
<fig id="F5-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-1">Figure <xref linkend="F5-1" remap="5.1"/></link></label>
<caption><para>Data flow for the algorithms implementation.</para></caption>
<graphic xlink:href="graphics/ch05_fig1.jpg"/>
</fig>
</section>
<section class="lev1" id="sec5-3" label="5.3" xreflabel="5.3">
<title>Hardware Requirements</title>
<para>According to the introductory section, the internal organization of the sensor sub-system used in REMPARK appears in <link linkend="F5-2">Figure <xref linkend="F5-2" remap="5.2"/></link>. This section will introduce the requirements of some critical hardware parts, together with a timing analysis before the specification of the concrete components chosen for the physical implementation.</para>
<fig id="F5-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-2">Figure <xref linkend="F5-2" remap="5.2"/></link></label>
<caption><para>Internal organisation of the sensor unit.</para></caption>
<graphic xlink:href="graphics/ch05_fig002.jpg"/>
</fig>
<para>It must be noted that during the REMPARK database collection phase, the indicated three triaxial sensors (accelerometer, gyroscope and magnetometer) were used to collect a complete set of signals from as many physical magnitudes related to movement as possible. However, in the algorithm development phase, acceleration signals were identified to be enough to monitor motor symptoms. In this way, it must be indicated that the final sub-system only includes the 3D accelerometer as a sensor.</para>
<para>The most relevant requirements are:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The concrete component chosen as the correct accelerometer must fulfil the needed range for the acceleration measurements (i.e. full scale values) and to be able to operate at the necessary sampling frequency.</para></listitem>
<listitem>
<para>A main constraint for the concrete microcontroller to be used is the online implementation of the algorithms, so the most important characteristics are memory capacity and the exhibiting computational capacity (throughput).</para></listitem>
</itemizedlist>
<para>Memory needs were determined by estimating how many resources should be used by the algorithmic set, in terms of program and data memory. An additional space managed by the firmware, necessary for the storage of the acquired data was also considered.</para>
<para>The theoretical approximation of the required microcontroller computation time is difficult to be done, and for this reason a measurement strategy was organized at the laboratory. Measurements were done around a microprocessor based platform allowing the equivalent simulation of the algorithms.</para>
<section class="lev2" id="sec5-3-1" label="5.3.1" xreflabel="5.3.1">
<title>Memory Requirements</title>
<para>The calculations of the memory size required by the execution of the algorithms and the firmware operation were performed by estimating the online deployment of the algorithms, according the different blocks indicated in <link linkend="F5-1">Figure <xref linkend="F5-1" remap="5.1"/></link>. In concrete, it was considered:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>A combination of algorithms executed on each acquired sample (detection of a fall, conditioning and filtering of the signal).</para></listitem>
<listitem>
<para>A set of algorithms executed per window.</para></listitem>
<listitem>
<para>An estimated need of the window management and the communication system.</para></listitem>
<listitem>
<para>An estimation of the local storage system, using a local &#x003BC;SD card.</para></listitem>
</itemizedlist>
<table-wrap position="float" id="T5-1">
<label><link linkend="T5-1">Table <xref linkend="T5-1" remap="5.1"/></link></label>
<caption><para>Estimated memory usage</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Description</td>
<td valign="top" align="left">Memory Type</td>
<td valign="top" align="center">Memory Usage (bytes)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Basic System with window Management and communication</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">6,5 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">&#x00A0;&#x00A0;5 KB</td>
</tr>
<tr>
<td valign="top" align="left">Bradykinesia Algorithm Memory Usage</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">3,5 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">0,5 KB</td>
</tr>
<tr>
<td valign="top" align="left">FoG Algorithm Memory Usage</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">3,5 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">0,5 KB</td>
</tr>
<tr>
<td valign="top" align="left">Dyskinesia Algorithm Memory Usage (FFT included)</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">3,5 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">0,7 KB</td>
</tr>
<tr>
<td valign="top" align="left">Filters+FallDetection Algorithm Memory Usage</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">1,2 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">0,5 KB</td>
</tr>
<tr>
<td valign="top" align="left">SD for Debug purposes Memory Usage</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">2,8 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">4,2 KB</td>
</tr>
<tr>
<td valign="top" align="left">TOTAL</td>
<td valign="top" align="left">Program Memory</td>
<td valign="top" align="center">20 KB</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">Data Memory</td>
<td valign="top" align="center">11 KB</td></tr>
</tbody>
</table>
</table-wrap>
<para><link linkend="T5-1">Table <xref linkend="T5-1" remap="5.1"/></link> shows the results of these estimations, in terms of necessary minimum size and type of memory (program or data memory).</para>
</section>
<section class="lev2" id="sec5-3-2" label="5.3.2" xreflabel="5.3.2">
<title>Sampling Frequency and Full-Scale Values</title>
<para>Sampling frequency and full scale values are key characteristics for choosing the correct accelerometer. Frequency also imposes specific time restrictions on the online implementation of the algorithms, which finally creates important constraints on the specific microcontroller to be used for the implementation.</para>
<para>Going along the different developed algorithms, it is necessary to evaluate the necessary sampling frequency to be applied. For this purpose, and also for considering the main frequency characteristics related to human movement the following points are considered:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>In the case of Dyskinesia, it was observed that this symptom increases the power spectra in the lower frequencies up to 4 Hz.</para></listitem>
<listitem>
<para>In the detection of FOG episodes, it was observed that normal walking has a principal frequency around 2 Hz, while FOG episodes are characterised by a principal frequency in the range of 3&#x02013;8 Hz.</para></listitem>
<listitem>
<para>The developed method for detecting Bradykinesia uses the accelerometer signals associated with the patients&#x02019; gait. The frequency content of gait is known to be below 20 Hz.</para></listitem>
</itemizedlist>
<para>According the Nyquist theorem, the minimum sampling frequency should be 40 Hz. Therefore, the waist sensor must incorporate an accelerometer with a sampling frequency of at least 40 Hz. In order to keep the computing resources as low as possible, this minimum frequency is set as the real-time acquisition frequency.</para>
<para>Moreover, regarding the full-scale range of the sensor, according to the measurements obtained in the signals collected along the project, it is determined that a Full Scale of 6 g (where 1 g = 9,8 m/s<superscript>2</superscript>) for the accelerometer is enough for the analysis of human movement with a sensor worn in the waist.</para>
</section>
<section class="lev2" id="sec5-3-3" label="5.3.3" xreflabel="5.3.3">
<title>Time Restrictions on the On-Line Implementation</title>
<para>As previously mentioned, the estimate for the processing time requirement was made on a set of measurements of processing time spent by a microprocessor, configured to work at 40 MIPS, and running specific algorithms that have an equal or greater burden compared with the algorithms developed in the project for symptoms&#x02019; detection. This is an indirect way to fix minimum processing requirements for the microcontroller to be included in the sub-system.</para>
<para>Considering that some operations must be done after acquiring a sample or when a time window has been completed, <link linkend="F5-3">Figure <xref linkend="F5-3" remap="5.3"/></link> shows the temporal organization of the different computations included in the online implementation of the algorithms, according the data flow presented in <link linkend="F5-1">Figure <xref linkend="F5-1" remap="5.1"/></link>.</para>
<para>The timing of the accelerometer data collection is represented in orange (related to a sampling frequency of 40 Hz, with a time between samples of 25 ms). In the sample zoom (top section of the figure), it is shown the time necessary to both acquire the accelerometer measurements and to perform the algorithm&#x02019;s calculations that are done at every sample.</para>
<fig id="F5-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-3">Figure <xref linkend="F5-3" remap="5.3"/></link></label>
<caption><para>Timing for the online algorithms implementation.</para></caption>
<graphic xlink:href="graphics/ch05_fig003.jpg"/>
</fig>
<para>The duration of a window, which is 3.2 seconds corresponding to 128 samples, is represented in blue at the bottom section. Note that a new window starts every 64 samples (every half a window), as described in <link linkend="ch04">Chapter <xref linkend="ch4" remap="4"/></link>. In the zoomed window, the computations done at the end of an acquired window are shown. These computations start from those provided by the processing done after each sample. Most of the time spent in the window computations correspond to the feature extraction. Once obtained, the bradykinesia, dyskinesia and FoG algorithms are applied. In order to ensure a correct processing, their results are obtained before the end of the next window is reached.</para>
<table-wrap position="float" id="T5-2">
<label><link linkend="T5-2">Table <xref linkend="T5-2" remap="5.2"/></link></label>
<caption><para>Estimated processing time</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left">Description</td>
<td valign="top" align="left">Timing</td>
<td valign="top" align="center">Time (ms)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Sampling Frequency</td>
<td valign="top" align="left">Between Samples</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;25</td>
</tr>
<tr>
<td valign="top" align="left">Adquisition</td>
<td valign="top" align="left">Every Sample</td>
<td valign="top" align="center">&#x00A0;&#x00A0;0,014</td>
</tr>
<tr>
<td valign="top" align="left">Filters + Fall detection algorithm</td>
<td valign="top" align="left">Every Sample</td>
<td valign="top" align="center">0,0318</td>
</tr>
<tr>
<td valign="top" align="left">Windowing time</td>
<td valign="top" align="left">Between Windows</td>
<td valign="top" align="center">&#x00A0;&#x00A0;1600</td>
</tr>
<tr>
<td valign="top" align="left">Feature Extraction</td>
<td valign="top" align="left">Every Window (max)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;151</td>
</tr>
<tr>
<td valign="top" align="left">Bradykinesia Algorithm</td>
<td valign="top" align="left">Every Window (max)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;55</td>
</tr>
<tr>
<td valign="top" align="left">FoG Algorithm</td>
<td valign="top" align="left">Every Window (max)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;3</td>
</tr>
<tr>
<td valign="top" align="left">Dyskinesia Algorithm</td>
<td valign="top" align="left">Every Window (max)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;3</td></tr>
</tbody>
</table>
</table-wrap>
<para><link linkend="T5-2">Table <xref linkend="T5-2" remap="5.2"/></link> presents an estimation of the processing time for each part in which the algorithms are divided. This estimation is based on the necessary operations to accomplish each computation in terms of memory usage and the inherent complexity of the calculus.</para>
</section>
</section>
<section class="lev1" id="sec5-4" label="5.4" xreflabel="5.4">
<title>Sensor Device Components</title>
<para>This section describes the selection of the components for the sensor sub-system according to the presented requirements.</para>
<section class="lev2" id="sec5-4-1" label="5.4.1" xreflabel="5.4.1">
<title>Microcontroller</title>
<para>The microcontroller (labelled as dsPIC33F in <link linkend="F5-2">Figure <xref linkend="F5-2" remap="5.2"/></link>) is responsible for the management of the data acquisition with a fixed sampling frequency, the analysis of the raw data applying the corresponding online algorithm and sending the processed data (or, alternatively, the creation of a local log in the &#x003BC;SD card).</para>
<para>The selected microcontroller in the project, for these purposes, was the Microchip<superscript>&#xAE;</superscript> dsPIC33FJ64MC804. One of the main advantages of this device is the availability of an integrated DSP engine, which enables advanced computations in short time, when compared with regular microcontrollers (e.g., 32F, 24F, 18F and 16F). The microcontroller memory includes 44KB for program memory while the memory dedicated to RAM reaches 16KB (both are according the requirements indicated in <link linkend="T5-1">Table <xref linkend="T5-1" remap="5.1"/></link>).</para>
<para>This dsPIC architecture is known as &#x0201C;Modified Harvard&#x0201D; which uses 16 bits-long data and 24 bits-long instructions and it processes 40 Mega-instructions per second (MIPS). The DSP engine enhances the operational capacities of the &#x00B5;C. It allows 16-bit data multiplications for both fractional and integers, and it also allows inverse multiplication among 32 and 16 bits of data. The DSP, despite its relative small size, becomes useful when computation power is required, saving time to the main &#x00B5;C threat.</para>
<para>The dsPIC operational voltage range is 3.0 to 3.6 V (the whole system voltage supply is 3.3 V). Working at 40 MIPS and supplied with 3.3 V, the microprocessor consumption is 60 mA in &#x0201C;run mode&#x0201D; (normal operation mode), while in &#x0201C;idle mode&#x0201D; (special waiting state) its power consumption drops to 20 mA, and in energy safe mode (&#x0201C;sleep&#x0201D;) maximum current peaks reach 28 &#x00B5;A.</para>
<para>An internal DMA (Direct Memory Access) module allows the communication between the CPU, the memory and the peripherals independently from the process being executed in the main thread of the program, enabling the execution of this process in parallel. The dsPIC has 8 DMA channels that may be associated to any peripheral I/O port. The DMA allows the parallel execution of various processes interrelated among them through asynchronous events (interrupts).</para>
<para>The whole operation of the system is effectively managed by the CPU using some internal specific peripherals, allowing:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Data acquisition.</para></listitem>
<listitem>
<para>Communication with the wireless module.</para></listitem>
<listitem>
<para>Communication with the digital sensor.</para></listitem>
</itemizedlist>
<para>Each peripheral has two associated DMA channels (transmission and reception) that provide access to a shared memory block.</para>
</section>
<section class="lev2" id="sec5-4-2" label="5.4.2" xreflabel="5.4.2">
<title>Accelerometer Details</title>
<para>The selected accelerometer is the LIS3LV02DQ (LIS) manufactured by ST Microelectronics [1] which was, at the moment of the design, the only available Microelectromechanical System device (MEMS) using a digital interface within the device. The inclusion of the sensors, the signal conditioning and the converters within the same packaging ensures a very good performance against perturbations. Besides, the inclusion of the three axis (3D) in the same package also provides a better functional and geometrical symmetry. Finally, it is important to highlight that the accelerometer includes a signal compensation based on internal calibration curves, which compensates the measured signal based on the temperature sensor also included in the accelerometer integrated circuit.</para>
<para>The bandwidth used by the LIS is 640 Hz for each axis. Given the particularities of human motion, the sample frequency required for it is 40 Hz, therefore, an excessively small sample period is avoided. One of the main advantages offered by LIS is that the full scale may be chosen between two values (&#x000B1;2 g or &#x000B1;6 g). The higher full scale allows a sensitivity of 340 LSB/g, which is the selected one for the device. The precision of the accelerometer is 2.9 mg for every bit change.</para>
</section>
<section class="lev2" id="sec5-4-3" label="5.4.3" xreflabel="5.4.3">
<title>Bluetooth Module</title>
<para>According to the REMPARK system requirements, the movement sensor device has to communicate wirelessly with, at least, a mobile phone to share the output of the algorithms. The system has been developed including a wireless communication Bluetooth v2.1 + EDR (IEEE 802.15.1) chip to implement the communication channel. For this purpose, the sub-system includes a WT12 Bluegiga<superscript>&#xAE;</superscript> communication module, with an on-chip integrated antenna.</para>
<para>The communication is organised through the UART port of the system. When the system boots the connection and communication parameters are configured; once communication is established, and because the SPP profile is used, the module works as a bridge between the UART port and the Bluetooth unit. This module works at 115200 bps and its consumption is 31.5 mA according to its technical specifications [2].</para>
</section>
<section class="lev2" id="sec5-4-4" label="5.4.4" xreflabel="5.4.4">
<title>Power Management</title>
<para>The sensor includes a battery management system that tries to save as much energy as possible. As shown in <link linkend="F5-4">Figure <xref linkend="F5-4" remap="5.4"/></link>, the operation is based on 3 low-dropout regulators and each of them powers selected parts of the sensor: first regulator supplies energy to the microcontroller, which manages the operation of the remaining regulators. The additional two regulators supply the analogue and the wireless circuitry.</para>
<fig id="F5-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-4">Figure <xref linkend="F5-4" remap="5.4"/></link></label>
<caption><para>Power Management block diagram.</para></caption>
<graphic xlink:href="graphics/ch05_fig004.jpg"/>
</fig>
<para>The system is powered by an 1130 mAh Lithium-Ion battery. According to the functional requirements for REMPARK system, sensor usage is suggested to be similar to a mobile phone. The system has a peak of 100 mA instantaneous current consumption; therefore, the worst case estimated life of the battery is a minimum of 20 hours. Then, the device should be charged a maximum of once per day, and normally during night.</para>
<para>The system incorporates a battery charger and a battery monitor. The battery monitor indicates to the user its current state through a RGB-LED. When the battery is very low, an interrupt is produced in the microcontroller and the system automatically closes all its peripherals and communications and enters in the &#x0201C;sleep&#x0201D; mode.</para>
</section>
<section class="lev2" id="sec5-4-5" label="5.4.5" xreflabel="5.4.5">
<title>External Memory Unit</title>
<para>The sensor system contains an external memory unit in the form of a &#x003BC;SD card, as it has been introduced, managed through one of the available microcontroller SPI channels. This memory unit is intended to store, if desired, the raw data captured by the sensors. After extracting the &#x003BC;SD card from the sensor unit, it is possible to get the generated log file in order to analyse the inertial data. This functionality was especially useful during the REMPARK database construction process.</para>
</section>
</section>
<section class="lev1" id="sec5-5" label="5.5" xreflabel="5.5">
<title>Sensor Casing and Operation</title>
<para>All the described electronic components of the sensor unit plus the Li-ion battery are encapsulated in a 99 &#x000D7; 53 &#x000D7; 19 mm plastic case. The total weight is 125 g (including the battery). The prototype also includes a wall battery charger. <link linkend="F5-5">Figure <xref linkend="F5-5" remap="5.5"/></link> shows the casing view of the sensor unit.</para>
<fig id="F5-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-5">Figure <xref linkend="F5-5" remap="5.5"/></link></label>
<caption><para>Sensor unit casing.</para></caption>
<graphic xlink:href="graphics/ch05_fig005.jpg"/>
</fig>
<para>As parts of the user interface, four elements can be externally identified in the unit: the main switch, an action button, the indicator LED and a charger connector. <link linkend="F5-6">Figure <xref linkend="F5-6" remap="5.6"/></link> indicates the location of these components.</para>
<fig id="F5-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-6">Figure <xref linkend="F5-6" remap="5.6"/></link></label>
<caption><para>External components of the sensor unit.</para></caption>
<graphic xlink:href="graphics/ch05_fig006.jpg"/>
</fig>
<para>The behaviour of the sensor unit is determined by two states: Off and On. These states are mutually exclusive; a third state, related to the battery supervision, is compatible with the previous ones and may be understood as an independent state. <link linkend="F5-7">Figure <xref linkend="F5-7" remap="5.7"/></link> represents graphically the relations between the states of the sensor unit.</para>
<fig id="F5-7" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-7">Figure <xref linkend="F5-7" remap="5.7"/></link></label>
<caption><para>Status of the sensor unit.</para></caption>
<graphic xlink:href="graphics/ch05_fig007.jpg"/>
</fig>
<para>In the OFF state the sensor cannot work, no battery consumption exists and no battery level may be presented. Besides, the device does not react when the action button is pressed. In the ON state the sensor initializes the microcontroller. When the sensor has already initialized all the internal devices it is ready to start the sensing process. When ready, the sensor reads inertial signals and processes them. Data are sent every minute to the mobile gateway as described above.</para>
<para>The state of the sensor is indicated using a unique multicolour LED by taking advantage of its blinking light. Different states can be distinguished due to the diversity of the colour code of the LED. For example, a blinking green/yellow light means the sensor is in a sense and analysis process. A blinking green/blue light means the sensor is sending data. If the sensor is charging the battery, it will be indicated with a fixed orange light. Otherwise, a fixed green light will notify battery if fully charged. Finally, error state will be indicated by means of a fixed red light.</para>
<para>The sensor unit case is surrounded by a retention mechanism (belt) able to fix the sensor unit on the patient&#x02019;s waist, as depicted in <link linkend="F5-8">Figure <xref linkend="F5-8" remap="5.8"/></link>. The part of the belt that is in direct contact with the patient&#x02019;s skin has been manufactured using a biocompatible neoprene material.</para>
<fig id="F5-8" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F5-8">Figure <xref linkend="F5-8" remap="5.8"/></link></label>
<caption><para>Special belt and REMPARK final sensor.</para></caption>
<graphic xlink:href="graphics/ch05_fig008.jpg"/>
</fig>
</section>
<section class="lev1" id="sec5-6" label="5.6" xreflabel="5.6">
<title>Conclusion</title>
<para>The specification of the concrete requirements has been done along the chapter, allowing the selection of the most convenient components integrating the sensor unit of the REMPARK system. The microcontroller is capable to embed all the developed algorithms and to execute them in real-time and considering all the restrictions related with the data capturing timing.</para>
<para>The system is light and small, being suitable to be worn in a belt without being intrusive for the patient. Furthermore, the system is capable to store raw data and to send messages to an external device. In this way, the developed sensor complies, thus, largely with all the established requirements, becoming the heart of the REMPARK system.</para>
</section>
<section class="lev1" id="sec5-7">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>STMicroelectronics, Inc. LIS3LV02DQ datasheet. MEMS Inertial Sensor., (2005).</para></listitem>
<listitem>
<para>Bluegiga. WT12 data sheet versi&#x00F3;n 2.5., (2008).</para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch06" label="6" xreflabel="6">
<title>User Interaction</title>
<para role="author"><emphasis role="strong">Ana Correira de Barros, Jo&#x00E3;o Cevada and Ricardo Gra&#x00E7;a</emphasis></para>
<para>Fraunhofer Portugal AICOS &#x2013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</para>
<section class="lev1" id="sec6-1" label="6.1" xreflabel="6.1">
<title>Introduction</title>
<para>One of the components of the REMPARK system is the smartphone, which represents the main communication channel between the system and the user. Within the project, the main goals in the development of the smartphone applications were to complement and confirm information coming from the system&#x02019;s sensors through patient feedback tests and to design user interfaces specifically tailored to the needs and abilities of users with Parkinson&#x02019;s Disease (PD).</para>
<para>Given the nature of a device such as the smartphone and its potential benefits in daily life outside a medical scope, the design and development went beyond the single focus on medical issues to encompass other services, such as the usual communication features offered by a smartphone.</para>
<para>The need for a strong collaboration with end-users was defined at the project onset, which led to an iterative design process. This not only informed choices about patterns of interaction suited for people with Parkinson&#x02019;s Disease (PwP), such as target sizes or suitable gestures, but also about the kind of features main stakeholders would like to see in the REMPARK smartphone. The structure of this chapter will then reflect the two main blocks mentioned above: 1) the research on guidelines regarding visual, interaction and navigation patterns; and 2) the design and validation of the smartphone applications.</para>
<para>The smartphone is increasingly recognized as a viable instrument to be applied in medical diseases with movement disorders [1]. Main applications currently refer to the possibility of monitoring symptom changes over time through the use of relatively economic software. This could potentially represent a significant advance particularly for the management of chronic conditions.</para>
<para>The direct use of smartphones with PD patients should take into account the presence of the motor and non-motor symptoms that could potentially affect the usability of the smartphone applications. It should also be noted that people involved in REMPARK were, mainly, older adults. It was then taken into account that these individuals might not show high familiarity with smartphones, and, more generally, with the use of most modern technologies.</para>
<para>With the exception of a few studies regarding interaction of PwP with desktop solutions or desktop peripherals [2, 3], software [4] or pen-tablet devices [5, 6], at the beginning of project activities, there were few studies on the interaction of PwP with smartphones. There were official guidelines for the sizing of target buttons for people with disabilities and studies on both the sizing and element gap for people with disabilities [7]. Nevertheless, none specifically focused on PwP. This, then, constituted an opportunity for relevant research on and beyond the scope of the REMPARK project, which would likely:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>help future practice in the development of ICT solutions for this particular target group;</para></listitem>
<listitem>
<para>help the development of more inclusive guidelines;</para></listitem>
<listitem>
<para>help contribute to reducing the digital divide through promoting enhanced access to smartphone solutions.</para></listitem>
</orderedlist>
<para>The sub-goals defined for this task were:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>to find suitable patterns for the REMPARK smartphone applications which would enhance accessibility and usability;</para></listitem>
<listitem>
<para>to design the applications themselves under collaborative processes with users so that these applications would be: easily used by people with PD, non-stigmatizing, user-friendly and foster adherence to the medical treatment.</para></listitem>
</itemizedlist>
<para>All the user interfaces were successfully designed and the most relevant issues evaluated with end-users. The process also took into account possible extensions to the REMPARK services, which led to specific user interfaces leaving room to future features and additions. The results from the field trials are listed and discussed in this chapter, followed by possibilities for future work.</para>
</section>
<section class="lev1" id="sec6-2" label="6.2" xreflabel="6.2">
<title>State of the Art/Competitive Analysis</title>
<para>As part of the REMPARK activities, a systematic search was conducted in order to capture and analyse relevant information about mobile applications that could assist PwP in managing the disease. The search was organized to find market products and Research &#x00026; Development (R&#x00026;D) technology related to this topic, including technology being developed and described in published and publicly available papers and conference proceedings. The search also included currently registered patents to verify the existence of innovative solutions. In terms of products or prototypes, the search was limited to mobile solutions for either Android or iOS smartphones.</para>
<para><link linkend="T6-1">Table <xref linkend="T6-1" remap="6.1"/></link> summarizes the results of said search for R&#x00026;D and market-ready products. The different evaluated parameters are those appearing in the top row of the table.</para>
<table-wrap position="float" id="T6-1">
<label><link linkend="T6-1">Table <xref linkend="T6-1" remap="6.1"/></link></label>
<caption><para>Technology watch on mobile applications for PD management</para></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="graphics/tab6-1.jpg"/>
</table-wrap>
<para>Some applications, like <emphasis>Parkinson&#x02019;s Central</emphasis>, the <emphasis>Parkinson&#x02019;s Disease by WAGmog</emphasis> and <emphasis>Parkinson&#x02019;s Disease Facts</emphasis> are small applications that provide very useful information about the disease, but do not contemplate any kind of interaction with the user. <emphasis>PD Warrior</emphasis> also offers information about the disease and combines it with rehabilitation exercises. <emphasis>Parkinson&#x02019;s Home Exercises</emphasis> focuses on the physical side of the disease, providing rehabilitation exercises and cueing support. It does not address the psychological and disease managing sides. <emphasis>Parkinson&#x02019;s Disease Manager</emphasis> is an application that provides a relation between the doctor and the patient. It has doctor reminders and questionnaires that allow the doctor to better diagnose the state of the disease continuously.</para>
<para><emphasis>DAF Professional</emphasis>, <emphasis>Speech Companion</emphasis> and <emphasis>Parkinson&#x02019;s Speech Aid</emphasis> solely focus on speech therapy, and no other application has approached this method in conjunction with other features. It is an innovative method that is rising among the possible therapies for PD. The <emphasis>Apple Health Kit</emphasis> is the only solution we found that can assess PD stage by analysing the voice of the patient. It also covers other features like recording all motor data, questionnaires and, like REMPARK, the Tap games.</para>
<para><emphasis>Parkinson&#x02019;s Easy Call</emphasis> is the only solution we have found that overhauled the default smartphone applications and adapted them to users with PD. However, it does not include any other extra feature.</para>
<para>Some applications, like <emphasis>ListenMee,</emphasis> <emphasis>Musical Therapy Service Portland</emphasis>, <emphasis>MoveApp</emphasis> and <emphasis>Beats Medical Parkinson&#x02019;s Treatment</emphasis> contain an auditory cueing solution; however the last two also incorporated a few extra features. <emphasis>Beats Medical<superscript>TM</superscript></emphasis> also tracks medical intake history and the <emphasis>MoveApp</emphasis> is one of the most complete solutions found that includes medication reminders, information about PD, a diary, rehabilitation exercises, an auditory cueing solution and questionnaires. There seems to have been less focus on the usability of the system in favour of the rehabilitation methods.</para>
<para>The <emphasis>Fox Insight App</emphasis> focuses on the daily management of the disease with medication reminders and a diary. This information is combined with a record of all motor data detected by the smartphone.</para>
<para>In the course of the chapter, it will become clear that, overall, the REMPARK system offers most of the features represented by all solutions, however it has more focus on the management of the disease, physical and psychological monitoring and improvement of patient Quality of Life (QoL) while using the smartphone applications actively or passively. It does not have any kind of approach regarding rehabilitation or speech related techniques. It also does not provide any kind of general information about the disease. While the lack of these features may be seen as a downside of REMPARK, it is important to state that the REMPARK system was developed as a monitoring system with an Auditory Cueing System (ACS) as actuator that offers assistance in case motor symptoms are detected.</para>
<para>The search in patent databases retrieved the following relevant examples:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="underline">WO2011088307 A2 (Application, filing date 2011) [8]</emphasis>. &#x0201C;A medical monitoring and surveillance system uses a server communicating with a general purpose personal device running an application. The application may be downloadable. The application is configured by the server, i.e. the application configures the device to perform medical tests using the sensors, pre-existing capabilities, and functionality built into the device. The device may be a cellular phone with data communication and other functionality, a personal digital organizer, a portable entertainment device, or another similar personal device. The application reports the results of the medical tests to the server or a third-party device. Various trigger events and associated tasks may be incorporated in the server or in the application residing on the device. A trigger event may occur, for example, in response to the test results meeting one or more predetermined criteria. Once a trigger event occurs, a task associated with the trigger event is performed.&#x0201D;</para></listitem>
<listitem>
<para><emphasis role="underline">US8669864 B1 (Grant, filing date 2013)</emphasis>. [9] &#x0201C;A mobile terminal is used to assist individuals with disabilities. A mobile terminal such as a &#x0201C;smartphone&#x0201D; or other commercially available wireless handheld device may be loaded with software. The software may be configured to: (i) store criteria for managing communications between a disabled user of the mobile terminal and a remote caregiver, (ii) determine whether a criterion is satisfied, and if so (iii) initiate a communication from the mobile terminal to the remote caregiver, and (iv) receive a response from the remote caregiver. Thus, through this software, the mobile terminal may dynamically facilitate communications with specific remote caregivers based on specific situations that may confront disabled individuals.&#x0201D;</para></listitem>
<listitem>
<para><emphasis role="underline">US20130345524 A1 (Application, filing date 2013)</emphasis>. [10] &#x0201C;Methods and systems are disclosed for sensing and assessing patients&#x02019; responses to tests using a device that may include tactile input, voice input, still image analysis, and responses to visual and auditory stimuli. In one example, a method includes obtaining interactive clinical assessment data using a remote client device and a computer-based control device, the method including providing on a display of a remote client device one or more test prompts for conducting an interactive clinical assessment, each displayed test prompt instructing a user to perform an action using the remote client device in response to the test prompt, and providing on the display of the remote client device one or more potential responses of actions that may be performed in response to the test prompt.&#x0201D;</para></listitem>
</itemizedlist>
<para>Analysing the patents found, it is possible to see that none is completely oriented to PwP, however all three describe different methods to manage a system similar to REMPARK. WO2011088307 A2 describes a system similar to REMPARK where a smartphone gathers data from different devices and sends it to the server. After that, some triggers may be configured in both the server and the smartphone. The REMPARK system works differently, as the triggers are preconfigured and the server only calculates the thresholds that activate them. The US8669864 B1 patent describes a simple system of communication between caregivers and patients, also not focusing in PwP. Their focus was in general disabled people, and therefore the applications are adapted accordingly. Given that REMPARK is a monitoring system, the communication between the caregiver and the patient, using the tools developed for REMPARK, is strictly restricted to the management of the disease (medication intakes, medical appointments scheduling, etc.), even though the patient may use REMPARK&#x02019;s smartphone as a normal phone in his/her daily living to establish and receive phone calls, text messages, access the Internet, etc. The last patent (US20130345524 A1) describes the usage of a device&#x02019;s input methods, like touch, voice, gestures, etc. and how they can be used to perform an interactive clinical assessment. The REMPARK system makes use of this method in the Tap games.</para>
</section>
<section class="lev1" id="sec6-3" label="6.3" xreflabel="6.3">
<title>Interaction Guidelines for Users with Parkinson&#x02019;s Disease</title>
<para>The first step towards the design of adequate user interfaces for PwP was understanding which and how specific symptoms of the disease affect the interaction with touchscreen handheld devices such as smartphones; secondly, understanding how said interaction with the smartphone can be improved in order to accommodate the characteristics of the disease [11].</para>
<para>After an intensive literature review on the topic, eight semi-structured interviews with health care professionals who worked with PwP on a daily basis were organized. They were complemented with observation sessions in which two PwP showed their symptoms to their neurologist, as if it was a consultation. The interviews were audio-recorded, coded and analysed, which enabled to understand which symptoms of PD could affect the interaction with the smartphone. <link linkend="T6-2">Table <xref linkend="T6-2" remap="6.2"/></link> shows some interesting Interview Results (IR) to be considered.</para>
<table-wrap position="float" id="T6-2">
<label><link linkend="T6-2">Table <xref linkend="T6-2" remap="6.2"/></link></label>
<caption><para>Some important interview results</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left" colspan="2">Motor Characteristics</td></tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">IR1</td>
<td valign="top" align="left">Bradykinesia can slow repetitive movements.</td>
</tr>
<tr>
<td valign="top" align="left">IR2</td>
<td valign="top" align="left">Rigidity makes interaction more imprecise and slower.</td>
</tr>
<tr>
<td valign="top" align="left">IR3</td>
<td valign="top" align="left">Dyskinesia can make the interaction very difficult.</td>
</tr>
<tr>
<td valign="top" align="left">IR4</td>
<td valign="top" align="left">PD may hinder speech.</td>
</tr>
<tr>
<td valign="top" align="left">IR5</td>
<td valign="top" align="left">Some PwP may experience visual disabilities.</td>
</tr>
<tr>
<td valign="top" align="left">IR6</td>
<td valign="top" align="left">PwP are likely to use the phone while standing still or sitting.</td>
</tr>
<tr>
<td valign="top" align="left">IR7</td>
<td valign="top" align="left">The impact of PD hands&#x02019; tremor is limited.</td>
</tr>
<tr style="border-bottom:1px solid; border-top:1px solid;">
<td valign="top" align="left" colspan="2">Cognitive Characteristics</td></tr>
<tr>
<td valign="top" align="left">IR1</td>
<td valign="top" align="left">Short-term memory loss is accentuated on PwP.</td>
</tr>
<tr>
<td valign="top" align="left">IR2</td>
<td valign="top" align="left">Thought is slowed by PD.</td>
</tr>
<tr>
<td valign="top" align="left">IR3</td>
<td valign="top" align="left">Depression and apathy are common in PD.</td>
</tr>
<tr>
<td valign="top" align="left">IR4</td>
<td valign="top" align="left">Dementia cases are often observed on later stages of the disease.</td>
</tr>
<tr style="border-bottom:1px solid; border-top:1px solid;">
<td valign="top" align="left" colspan="2">General Characteristics</td></tr>
<tr>
<td valign="top" align="left">IR1</td>
<td valign="top" align="left">Symptoms significantly vary across different PwP.</td>
</tr>
<tr>
<td valign="top" align="left">IR2</td>
<td valign="top" align="left">Symptoms vary between ON and OFF phases.</td>
</tr>
<tr>
<td valign="top" align="left">IR3</td>
<td valign="top" align="left">The disease progresses differently from person to person.</td>
</tr>
<tr>
<td valign="top" align="left">IR4</td>
<td valign="top" align="left">Autonomy is gradually lost.</td></tr>
</tbody>
</table>
</table-wrap>
<para>To actually measure the extent to which PD symptoms affect the interaction with the smartphone, usability experiments were created. Thirty-nine participants (17 females, 22 males) took part of the usability experiments. Participants average age was 64 (Median: 66; STD: 7.4) and had been diagnosed as having PD since for at least 10 years (Median: 8; STD: 5.8). All participants took part of the experiment while in ON phase. Regarding participant&#x02019;s self-reported motor symptoms: 59% had tremor, 59% had rigidity, and 26% had dyskinesia. Some of them (13%) had undergone deep brain stimulation surgery. The recruitment was done through two delegations of the Parkinson&#x02019;s disease patient association in Porto and Lisbon, as well as the Hospital of S&#x00E3;o Jo&#x00E3;o (Porto) in Portugal.</para>
<fig id="F6-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-1">Figure <xref linkend="F6-1" remap="6.1"/></link></label>
<caption><para>Sequence of interaction of different experiments. a) Participants had to touch the target, which appeared in different sizes, at different positions and surrounded by distractions of different sizes; b) Participants had to slide a rug which appeared in different heights with different spaces to the distractions; c) Participants had to control the water level, by filling the pipette by touching the arrow up until the water reached the green mark; d) Participants had to use the seek bar with a ball as a selector to drag the ball to the boy; scale and mark&#x02019;s position changed with test progression.</para></caption>
<graphic xlink:href="graphics/ch06_fig001.jpg"/>
</fig>
<para>As it can be seen in <link linkend="F6-1">Figure <xref linkend="F6-1" remap="6.1"/></link>, four different tests were developed to evaluate the following PwP abilities:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>select targets of different sizes using the Tap gesture</para></listitem>
<listitem>
<para>do swipes</para></listitem>
<listitem>
<para>perform repetitive taps</para></listitem>
<listitem>
<para>accomplish drag gestures</para></listitem>
</orderedlist>
<para>Tap and Swipe were chosen due to their heavy use on today&#x02019;s smartphones. Multiple-tap and Drag were chosen because they were adequate for building smartphone interfaces for medical questionnaires with scales, a requirement of the REMPARK project. Experiments were developed for the Android platform and designed to run on the Samsung Google Nexus S (4-inch capacitive touchscreen, with 480 &#x000D7; 480 pixels of resolution and 123.9&#x000D7;63&#x000D7;10.9 mm dimensions). All relevant interaction data were logged during the experiments and conveniently analysed.</para>
<para>The results of the usability experiment showed that Tap test results were significant both regarding touch accuracy and reaction time. The results showed that mean touch accuracy tends to decrease with button size, and the highest accuracies were observed with targets with 14 mm size (98% of accuracy). Results also showed that the spacing to surrounding elements does not influence the accuracy of the Tap.</para>
<para>It was observed that PwP are able to perform swipes and distinct participants swipe at very different speeds. Despite target size and spacing between the target and surrounding elements being irrelevant, our results showed that to accommodate 95% of the participants&#x02019; swipes one should accept movements of 24 mm/s.</para>
<para>PwP were also able to perform successive taps with no significant reduction in speed, which challenged the data from the interviews that anticipated PwP would be strongly affected by bradykinesia. However, as participants performed the tests while in ON phase, this might not be the case.</para>
<para>Regarding the Drag gestures, it was shown that participants were able to drag objects with precision, but they were slow to reach the goal. However, the increased frustration expressed by the participants with the Drag, allows us to say that Multiple-tap is more comfortable to perform than Drag.</para>
<para>By reflecting on the findings of this short study, 12 user interface design guidelines (DG) for creating smartphone applications for PwP were considered and are listed in <link linkend="T6-3">Table <xref linkend="T6-3" remap="6.3"/></link>.</para>
<table-wrap position="float" id="T6-3">
<label><link linkend="T6-3">Table <xref linkend="T6-3" remap="6.3"/></link></label>
<caption><para>User interface design guidelines</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="left" colspan="2">Design Guidelines</td></tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">DG1</td>
<td valign="top" align="left">Usetap targets with 14 mm of side.</td>
</tr>
<tr>
<td valign="top" align="left">DG2</td>
<td valign="top" align="left">Use the swipe gesture, preferably without activation speed.</td>
</tr>
<tr>
<td valign="top" align="left">DG3</td>
<td valign="top" align="left">Employ controls that use multiple-taps.</td>
</tr>
<tr>
<td valign="top" align="left">DG4</td>
<td valign="top" align="left">Use drag gesture with parsimony.</td>
</tr>
<tr>
<td valign="top" align="left">DG5</td>
<td valign="top" align="left">Prefer multiple-tap over drag.</td>
</tr>
<tr>
<td valign="top" align="left">DG6</td>
<td valign="top" align="left">Adapt interfaces to the momentary characteristics of the user.</td>
</tr>
<tr>
<td valign="top" align="left">DG7</td>
<td valign="top" align="left">Use high contrast coloured elements.</td>
</tr>
<tr>
<td valign="top" align="left">DG8</td>
<td valign="top" align="left">Select the information to display carefully.</td>
</tr>
<tr>
<td valign="top" align="left">DG9</td>
<td valign="top" align="left">Provide clear information of current location at all times.</td>
</tr>
<tr>
<td valign="top" align="left">DG10</td>
<td valign="top" align="left">Avoid time dependent controls.</td>
</tr>
<tr>
<td valign="top" align="left">DG11</td>
<td valign="top" align="left">Prefer multi-modality over a single interaction medium.</td>
</tr>
<tr>
<td valign="top" align="left">DG12</td>
<td valign="top" align="left">Consider smartphone design guidelines for older adults.</td>
</tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev1" id="sec6-4" label="6.4" xreflabel="6.4">
<title>User Research and User-Centred Design Processes</title>
<para>The choice was to provide the users of the REMPARK system not only with the REMPARK applications, but also common functionalities of mobile phones. The REMPARK applications could have been designed as stand-alone applications which could be downloaded and be amongst the smartphone&#x02019;s existing applications. Two performance-based reasons discouraged this approach:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>The REMPARK system is a medical one containing sensors and actuators which play a serious role in users&#x02019; lives. Therefore, the system should have some control over its performance, which means having, amongst others, control over battery duration or some means of preventing external applications&#x02019; interference with REMPARK&#x02019;s applications.</para></listitem>
<listitem>
<para>As described in the previous sections, users with PD are generally older adults who, nowadays, are likely to be less tech-savvy and who, additionally, due to the disease itself, have motor and non-motor constraints which might hinder the interaction with the smartphone. These users then require simple user interfaces which are furthermore adapted to their abilities.</para></listitem>
</orderedlist>
<para>These reasons have led the partners to develop a set of applications which would work within a launcher. In a nutshell, launchers enable developers to create a custom home screen through which one also has the possibility to control what the user will or will not see and interact with. The advantage of the launcher is that it answers the above listed reasons in the sense that it allows to control which applications the user has access to and, furthermore, in what usability and user experience are concerned, it allows for the design of a single interaction experience. All applications within the launcher obey the same principles and patterns and, once the user has learned how to use one, he or she will most likely be able to use the others, as the language is kept identical.</para>
<para>The processes followed a human-centred approach in that main stakeholders were called to be part of the design process from onset. Following the above described reasoning, the initial list of applications to design and implement within REMPARK was set amongst the partners in the consortium as follows:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Messaging</para></listitem>
<listitem>
<para>Emergency call</para></listitem>
<listitem>
<para>Calling</para></listitem>
<listitem>
<para>Contacts</para></listitem>
<listitem>
<para>Show disease status</para></listitem>
<listitem>
<para>Medication</para></listitem>
<listitem>
<para>Agenda</para></listitem>
<listitem>
<para>Auditory Cueing System (ACS) controller</para></listitem>
<listitem>
<para>Medical questionnaires</para></listitem>
<listitem>
<para>My data</para></listitem>
<listitem>
<para>Settings</para></listitem>
<listitem>
<para>Tutorials</para></listitem>
</itemizedlist>
<para>After this definition, a process of interaction with users was scheduled in order to cope with main usability requirements, not previously considered.</para>
<para>Apart from the health-related benefits arising from the ACS, the value proposition for this set of REMPARK applications would be that PwP could have all their Parkinson&#x02019;s-related mobile needs satisfied, while not hindering the use of the main purpose of a smartphone: communication. All aspects of the applications &#x02013; ranging from button sizes to workflows &#x02013; were taken into account from users&#x02019; perspective in order to insure a positive user experience.</para>
<para>After informal discussions with the experts within the REMPARK project, who provided insights about PwP&#x02019;s needs and abilities, app design was approached first through an exploratory methodology, in semi-structured interviews to people with Parkinson&#x02019;s disease, informal caregivers and physical therapists. The analysis of these results informed a second phase for which a collaborative and participatory approach was considered, mainly involving people with Parkinson&#x02019;s disease and their caregivers.</para>
<para>The results were not conclusive regarding most issues (medication/ appointment reminders, preferred activities or physical therapy). On the one hand the samples were fairly small and, on the other hand, participants with PD gave ambiguous answers to the questions posed by the researcher. Nevertheless, there was a clear concern with moving around outside (especially in places further away from home) and with having emergency mechanisms at PwP&#x02019;s disposal in case something happens.</para>
<para>These interviews helped to structure the next steps in user research and to add a new requirement for the smartphone: that it should provide others the information that the smartphone owner has PD.</para>
<para>The material up until this point had enabled the design of the user interfaces and some screen flows. The choices for the UIs and, specifically, the GUIs were made based on Fraunhofer Portugal&#x02019;s existing knowledge and expertise on UIs for older adults, topped with the findings regarding specific requirements for users with PD.</para>
<para>The background was kept dark to prevent glare and increase battery life and all buttons size complied with the recommendations mentioned in <link linkend="T6-3">Table <xref linkend="T6-3" remap="6.3"/></link>. The approach was to avoid the need for scrolling actions to the widest extent possible. Therefore, activities were sometimes divided into layers and, consequently, sub-activities. All screens consistently displayed the same Back button, appearing at all times and in the same location. All action buttons were consistent in displaying, whenever possible, an icon along with an action verb + name, so that the user would be surer of his or her input. For instance, whenever possible, instead of &#x0201C;Save&#x0201D;, the button would read action verb plus the element being saved, e.g. &#x0201C;Save Appointment&#x0201D;.</para>
<para>Regarding navigation, the screen flows were kept with as few layers as possible, wording was sought to adapt to terms which were familiar to users and which could have relation to the physical world. For the composition of the screens we have opted to design a set of patterns for a number of situations/functions, which allowed to be grouped according to each situation. <link linkend="F6-2">Figure <xref linkend="F6-2" remap="6.2"/></link> shows some examples of the designed patterns.</para>
<fig id="F6-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-2">Figure <xref linkend="F6-2" remap="6.2"/></link></label>
<caption><para>Some examples of UI patterns and gestures.</para></caption>
<graphic xlink:href="graphics/ch06_fig002a.jpg"/>
</fig>
<para>In order to allow for as simple as possible an interaction, the text input created a new activity so as to allow for a simple screen which would not demand too much of the users&#x02019; attention. As seen in <link linkend="F6-3">Figure <xref linkend="F6-3" remap="6.3"/></link>, once activating a textbox, the user is led to a screen with a title reminding the input action, a textbox, a save button and the keyboard. In this way, the user was offered step-by-step guidance on information input.</para>
<fig id="F6-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-3">Figure <xref linkend="F6-3" remap="6.3"/></link></label>
<caption><para>Sequence for text input.</para></caption>
<graphic xlink:href="graphics/ch06_fig003.jpg"/>
</fig>
<para>Scoping sessions with stakeholders provided additional ideas for features which would enhance the REMPARK smartphone, such as the different ways to trigger an emergency alert, the importance of showing information about the disease, along with some clues on what to show, the importance of having clear information on medication reminders in order to reduce error, or the usefulness of keeping a detailed record which both the medical doctor and the PwP/caregivers can consult.</para>
<para>With all the compiled information and generated inputs, the partners proceeded to redefine parameters in the REMPARK applications. At this time, the screen flows for the following applications had been re-defined:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Medication</para></listitem>
<listitem>
<para>appointments</para></listitem>
<listitem>
<para>calls</para></listitem>
<listitem>
<para>messages</para></listitem>
<listitem>
<para>contacts</para></listitem>
<listitem>
<para>&#x02018;my data&#x02019;.</para></listitem>
</itemizedlist>
<para>A specific interaction session with PwP was organized at this point with the objective of clarifying some issues within the medication application, namely the amount and type of information being displayed (in <emphasis>medication</emphasis>, <emphasis>disease status</emphasis>, <emphasis>appointments</emphasis> and <emphasis>my data</emphasis> applications) and to check whether or not the flow was easily followed. The session also aimed to discuss the options for emergency calls with the participants, the option of having SMS templates and the option for the appointments application to have a rough prediction of OFF states. Finally, participants were asked about what they thought would be the best icon for the Auditory Cueing System controller. Some comments on this session:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">About the medication.</emphasis> Participants were asked to state their opinions regarding the proposed solutions and also to contribute with their critical thinking and experience with the disease. For the most part, the solutions were welcomed by participants with minor remarks. For instance, regarding the &#x02018;Medication Details&#x02019;, participants thought there would be no point in displaying the name of the active substance along with the medication name. Participants agreed that the possibility to add notes to the medication details was useful and that these should show on the reminders (e.g. &#x02018;Sinemet 10/100 mg, Take before eating&#x02019;).</para></listitem>
<listitem>
<para><emphasis role="strong">About emergency situations.</emphasis> Facilitators discussed the ideas of having one lateral hardware button reconfigured to act as quick dial to an emergency number on long press. They also discussed the quick dial to a caregiver and the permanent presence of a quick dial to an emergency number through an icon on the smartphone&#x02019;s main screens as it is shown in <link linkend="F6-4">Figure <xref linkend="F6-4" remap="6.4"/></link>. Participants tried out long presses to the lateral hardware buttons and agreed that it would be an easy action for them to complete. They envisioned that a possible use case would be an emergency during bathing.</para>
</listitem>
<listitem>
<para><emphasis role="strong">On &#x0201C;My data&#x0201D;.</emphasis> Participants were also happy about the possibility to have a quick access to their health information under &#x02018;My Data&#x02019;. At this point in time, the &#x02018;My Data&#x02019; flow would first show a pop-up with a warning to inform that the smartphone owner had PD, followed by a screen with the owner&#x02019;s picture, a quick dial button to the caregiver and a list of current medication. Participants mostly cherished the possibility to carry with them the list of medication they were under at any point in time.</para>
<para>After the advice of medical partners, the adopted solution is presented in <link linkend="F6-5">Figure <xref linkend="F6-5" remap="6.5"/></link>, where all relevant information is shown at once (preferable avoiding scroll).</para></listitem>
<listitem>
<para><emphasis role="strong">On the Disease Status.</emphasis> Participants welcomed the idea of visualizing their disease status. They would appreciate it if the application would be able to record involuntary movements (dyskinesia). One caregiver in the group had already her paper version of this disease status visualization, which she would take with her every time she accompanied her sister (PwP) to the doctor.</para>
<para>According with medical partners, one of the main drivers for choosing to include such an application was to promote treatment compliance. Several studies show the nefarious consequences brought about by non-compliance with medical treatments [12, 13]; nevertheless, controlling medical compliance without being intrusive and tiresome to users is a difficult task. Our hypothesis was that, by allowing users to easily visualize the relation between their disease status and their medical treatment adherence, they would be compelled to follow the medical prescriptions and advice. However, medical doctors pointed out that, if a PwP is not doing well, visualizing a poor health state might have the contrary effect.</para>
<para>Therefore, the choice was to present simple data gathered by the system, which PwP usually try to collect in order to show to their physician. The features to be shown in this application were: ON/OFF periods, FOG, dyskinesia, festination and falls. Along with this, the visualization tool would also show <emphasis>failed medication intakes</emphasis>, rather than all data about medication. The final result may be seen in <link linkend="F6-6">Figure <xref linkend="F6-6" remap="6.6"/></link>.</para>
</listitem>
<listitem>
<para><emphasis role="strong">On the Appointments.</emphasis> The idea brought forth about warning the user whenever he or she was setting up an appointment which most likely overlapped an OFF phase was not popular. After some initial discussion, participants agreed this might be dangerous not only because &#x02013; given the several variables involved &#x02013; it is quite difficult to predict an OFF timeframe, but also because having this information beforehand could most likely create unnecessary anxiety.</para></listitem>
<listitem>
<para><emphasis role="strong">On the ACS icon.</emphasis> Participants decided the best icon to convey the idea of auditory cueing between some elaborated and proposed ideas.</para></listitem>
</itemizedlist>
<fig id="F6-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-4">Figure <xref linkend="F6-4" remap="6.4"/></link></label>
<caption><para>Screenshots of the home screens: Applications screen (to the left) and Favourites screen (to the right).</para></caption>
<graphic xlink:href="graphics/ch06_fig004.jpg"/>
</fig>
<fig id="F6-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-5">Figure <xref linkend="F6-5" remap="6.5"/></link></label>
<caption><para>Screen flow for the &#x02018;My Data&#x02019; application.</para></caption>
<graphic xlink:href="graphics/ch06_fig005.jpg"/>
</fig>
<fig id="F6-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-6">Figure <xref linkend="F6-6" remap="6.6"/></link></label>
<caption><para>Screenshot of the &#x02018;My Day&#x02019; app.</para></caption>
<graphic xlink:href="graphics/ch06_fig006.jpg"/>
</fig>
<para>Despite the effort placed onto adopting inclusive design for UI design, the users&#x02019; concerns about the response of the touch screen led to conduct more research into the touch patterns of PwP in order to try to define what characterizes an intentional tap, and thus optimize interaction with the smartphone by reducing error. For the purpose, a specific test was designed and carried out with 4 participants with PD.</para>
<para>The tests were designed to explore the possibility of creating an algorithm to differentiate voluntary from involuntary taps using the touch data provided by the Android API. For that a little game was designed to persuade PwP to do voluntary taps on the smartphone&#x02019;s screen, consisting in basic math operations where the user had to answer a question by tapping one of 3 possible answers (<link linkend="F6-7">Figure <xref linkend="F6-7" remap="6.7"/></link>a). This game allowed to easily observe when a person would intentionally tap an option or tap on another part of the screen by chance.</para>
<fig id="F6-7" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-7">Figure <xref linkend="F6-7" remap="6.7"/></link></label>
<caption><para>a) Initial screen; b) Number indicating the tap counting; c) Custom display of a tap event.</para></caption>
<graphic xlink:href="graphics/ch06_fig007.jpg"/>
</fig>
<para>It was planned to achieve at least 11 voluntary taps per participant, in this way 11 questions were presented and if they failed solving the problem at the first time they would need at least one more tap to get the next question. However, we could not induce any involuntary taps from the participants; therefore, no minimum number of involuntary taps per participant was set. The tests were recorded on video and each tap would increment a number on the screen (<link linkend="F6-7">Figure <xref linkend="F6-7" remap="6.7"/></link>b), so after the test was done it was possible to discriminate if a tap was voluntary or not.</para>
<para>The data provided by the Android API consisted of tap time, area of touch, pressure of touch and dislocation of the finger during the tap event which could be used to both perceive the orientation of the finger. The area of touch and pressure were only estimated by the Android API by measuring the change in capacitance on the screen, therefore not corresponding to real measures. As a result, a visual representation on the screen of these measures was created, as a means to test their correspondence to real measures. The pressure was represented by an ellipse that we then stretched and rotated accordingly the perceived orientation of the tap event, the area by a square and the orientation by a red line (<link linkend="F6-7">Figure <xref linkend="F6-7" remap="6.7"/></link>c).</para>
<para>Despite inconclusive, the results suggested that there should be room for improvement and that this analysis should be pursued further in the future. An interesting correlation between the contact time in voluntary and involuntary taps was found. However, the pressure and area had little fluctuations; the direction of tap also did not prove effective because PwP lacked a consistent movement that was necessary to detect correctly the orientation of the tap gesture. But nevertheless, the information about the dislocation of the finger could be used to mark involuntary taps if the finger moves too far away from the first point of touch. Hence, the most probable outcome of future tests will be a time-distance frame where a voluntary tap is considered as a tap that respects that time-distance frame, and involuntary tap as one that does not respect that time frame. This timeframe would be necessarily adjusted by the user in order to better suit his/her needs.</para>
<fig id="F6-8" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-8">Figure <xref linkend="F6-8" remap="6.8"/></link></label>
<caption><para>Arrow buttons as an alternative to the scroll gesture.</para></caption>
<graphic xlink:href="graphics/ch06_fig008.jpg"/>
</fig>
<para>Following these very concerns in optimizing interaction and preventing errors, the velocity of scroll was adapted in order to better control for the presence of dyskinesia. Furthermore, it was added the option to replace the scroll gesture by tap buttons with upward and downward (<link linkend="F6-8">Figure <xref linkend="F6-8" remap="6.8"/></link>).</para>
</section>
<section class="lev1" id="sec6-5" label="6.5" xreflabel="6.5">
<title>Final Usability Tests</title>
<para>For the purpose of conducting comprehensive usability tests with PwP, participants were recruited through Hospital de S&#x00E3;o Jo&#x00E3;o, in Oporto (Portugal). The documentation was sent to the Ethics Committee and approval was obtained in due time upon documentation submission.</para>
<section class="lev2" id="sec6-5-1" label="6.5.1" xreflabel="6.5.1">
<title>Research Questions</title>
<para>The main questions left unanswered were related to touch interaction, ease of navigation and the affordances of particular patterns. Regarding navigation, most questions were brought about by the two most complex applications: Medication and Appointments. These, it was supposed, will be frequently used and imply an array of activities and tasks which might be difficult to handle, such as interacting with reminders, introducing new data, browsing and searching for specific data, amongst others. Therefore, usability tests focused on evaluating the ease of understanding of the navigation experience, while, assessing the touch and gesture interactions on the background.</para>
</section>
<section class="lev2" id="sec6-5-2" label="6.5.2" xreflabel="6.5.2">
<title>Sample</title>
<para>The sample was recruited from the neurology department, a group of a physiotherapist&#x02019;s patients and a day care centre. No exclusion criteria were set, except for the presence of concomitant health conditions which caused motor or cognitive impairments beyond those owing to PD. A total of 12 participants were recruited, although three were excluded for not being able to finish the usability tests due to poor mental state. Consequently, the sample was reduced to nine participants, which resulted on five tests for Appointments, five tests for Medication and four tests for scroll accessibility. The sample had an average age of 71.3 years old, &#x000B1;STD 10.4, (median: 73) and participants had had PD for an average of 9 &#x000B1;STD 8.6 years (median: 6).</para>
</section>
<section class="lev2" id="sec6-5-3" label="6.5.3" xreflabel="6.5.3">
<title>Protocol, Script and Metrics</title>
<para>As there were many items in need of evaluation, there was the risk that usability sessions would be too lengthy and hard on participants. Therefore, the session was devised into two different session tests, one for each application: Medication and Appointments. In this way, beyond avoiding wearing out the participants, bias was also avoided to some extent, as participants would not learn visual and interaction patterns from one application to the next.</para>
<para>The protocol followed the usual steps in usability testing: researcher presentation, project presentation, material presentation, study presentation and goals, obtaining informed consent, session tasks and debrief.</para>
<para>The variables being measured were as follows: tap button precision, tap length time (evaluated with FUSAMI [14]), task completion, number of errors and scroll errors (measured afterwards through video observation and with the specific test). Additionally, in order to continue to adapt the sensibility of the screen to better fit PwP the touch data from the appointment tests was catalogued in voluntary taps and involuntary taps.</para>
<para>The scroll test was done at the end of the &#x02018;Appointments&#x02019; session and it had a simple design, it consisted of a contact list with thrice the number of contacts supported by a screen with no need for scroll and the person had to tap on a contact which was only accessible through scrolling. For the 3 types of scroll all the names of the contacts changed, but in all of them the contact was in the last position of the second scrolling panel, thus being required to do an entire scroll to see it; scrolling all the way to the end of the list would hide the referred contact once more. The measures used were: number of touches on the screen and time to find the contact.</para>
<para>The test material, protocol and script were subjected to pilot testing with two participants with PD for each test, who were recruited through Fraunhofer&#x02019;s contacts with day-care centres and who signed the informed consents to take part in the pilot tests. After the pilot tests the session plan was refined.</para>
</section>
<section class="lev2" id="sec6-5-4" label="6.5.4" xreflabel="6.5.4">
<title>Results</title>
<para>Some results obtained on the main issues addressed during the set of usability tests are discussed:</para>
<section class="lev3" id="sec6-5-4-1" label="6.5.4.1" xreflabel="6.5.4.1">
<title>Appointment test</title>
<para><emphasis role="strong">Using the calendar and reading an appointments list.</emphasis> Overall the participants recognized which days contained appointments (<link linkend="F6-9">Figure <xref linkend="F6-9" remap="6.9"/></link>), even though some had more difficulties than others. In the end, all participants identified the days correctly. Current day is also visually distinct from the remaining month days, but only one participant noticed this.</para>
<fig id="F6-9" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-9">Figure <xref linkend="F6-9" remap="6.9"/></link></label>
<caption><para>Calendar screens: a) Calendar; b) Week list.</para></caption>
<graphic xlink:href="graphics/ch06_fig009a.jpg"/>
</fig>
<para>As expected, when asked to see more information about an appointment they had on a specific day, participants tried to press on that day, despite being too small for participants to accurately tap it. Participants were able to read the correct event. They only had difficulties when the event did not show immediately on the list and they had to scroll to get the correct appointment. When the facilitator scrolled to the right position they read it without effort.</para>
<para><emphasis role="strong">Tapping on an appointment to see more details.</emphasis> In general, the participants were able to correctly identify the name of the appointments as a clickable element and tapped them without almost any problem (<link linkend="F6-9">Figure <xref linkend="F6-9" remap="6.9"/></link>).</para>
<para><emphasis role="strong">Editing/creating an appointment.</emphasis> Here the participants had more difficulties to know what they had to do in order to edit an appointment (<link linkend="F6-10">Figure <xref linkend="F6-10" remap="6.10"/></link>). Creating a new appointment was the most complex task on the tests and the participants were only able to accomplish it with assistance. Generally, the editable elements were easy to identify, however when they were &#x02018;hidden&#x02019; by the scroll, participants needed help to find them. Additionally, the pop-ups confused some participants. When the pop-ups of date and hour appeared on the screen some participants instinctively tried to tap on &#x02018;Set&#x02019; before using the controls on the pop-up to set a different hour/date.</para>
<fig id="F6-10" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-10">Figure <xref linkend="F6-10" remap="6.10"/></link></label>
<caption><para>New/Edit appointment screen.</para></caption>
<graphic xlink:href="graphics/ch06_fig0010.jpg"/>
</fig>
<para><emphasis role="strong">Using scroll.</emphasis> No participant, with the exception of the one who was used to touch technology, had the initiative to use scroll. After its use was shown to them, participants were able to replicate it in that situation but rarely used it afterwards. Even though they were able to do the gesture, they would only perceive the information currently displayed on the screen and would not seek more information. Participants did not notice the visual marking on the screen indicating the scroll.</para>
</section>
<section class="lev3" id="sec6-5-4-2" label="6.5.4.2" xreflabel="6.5.4.2">
<title>Medication test</title>
<para><emphasis role="strong">Reading the medication list</emphasis>. Almost all participants correctly identified the medication names and notes with almost no effort (see <link linkend="F6-11">Figure <xref linkend="F6-11" remap="6.11"/></link>).</para>
<para><emphasis role="strong">Tapping on a medication to see more details</emphasis>. When asked to see more details, the majority of the participants correctly tapped on the medication to disclose more details about it, but they had difficulty in correctly reading the intake hours for that particular medication. As the intakes were on a different list from that of other elements, only after reading all the details regarding that medication (or getting some hints from the facilitator to seek more information), did they finally read the intakes; again, with difficulties.</para>
<fig id="F6-11" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-11">Figure <xref linkend="F6-11" remap="6.11"/></link></label>
<caption><para>Medication apps screens: a) medication list; b) medication details; c) edit intake.</para></caption>
<graphic xlink:href="graphics/ch06_fig0011a.jpg"/>
</fig>
<para><emphasis role="strong">Edit intake hour and frequency</emphasis>. After understating the concept of intake, it was easy for the participants to tap over the intake event to edit it. Concerning the editing mechanisms, and despite some initial confusion, participants were able to use them correctly. After some taps they understood what the &#x02018;+&#x02019; and &#x02018;&#x02013;&#x02019; controllers were for and used them. Participants were also able to recognize the spinner to change the frequency of the intake, and choose the correct days although with hesitation on what the options: &#x0201C;Custom interval&#x0201D; and &#x0201C;Custom week days&#x0201D; would do. Again, they were not able to scroll down to tap the &#x02018;Save&#x02019; button.</para>
<para><emphasis role="strong">Read the medication schedule and list of missed intakes</emphasis>. Despite the majority of the participants having correctly identified the hours and medication which they had to take, some had difficulties associating the hours appearing on the list with the correct medicament. Generally, participants that understood the concept of missed intakes were able to say which medicaments were not taken.</para>
<para><emphasis role="strong">Interact with the medication alerts</emphasis>. Overall, the participants understood clearly which medicaments they had to take, but some had difficulty understanding what they had to do in order to inform the system that they only had taken one medicament of the displaced list (<link linkend="F6-12">Figure <xref linkend="F6-12" remap="6.12"/></link>). However, with the help of the facilitator showing them how tapping on a medicament would mark it with a check icon, they would then proceed to tap over &#x02018;Taken&#x02019; to finish the task.</para>
<fig id="F6-12" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F6-12">Figure <xref linkend="F6-12" remap="6.12"/></link></label>
<caption><para>Notification pop-up screen (medication reminder).</para></caption>
<graphic xlink:href="graphics/ch06_fig0012a.jpg"/>
</fig>
<para><emphasis role="strong">Voluntary and involuntary taps differences</emphasis><emphasis>.</emphasis> The test allowed us to observe differences in touching times between some involuntary and voluntary taps (<link linkend="T6-4">Table <xref linkend="T6-4" remap="6.4"/></link>), though many times those differences were not present, making it not possible to differentiate them in an automatic way. However, it is possible to do it if the PwP intentionally changes his/her behaviour while touching the screen. Since most of the time the involuntary taps are quick (when one has tremor and just passes the finger over the screen, or low dexterity and notices that he/she is touching intentionally on the screen and moves the finger right away), a minimum time threshold could be settled to discard those taps and PwP would always have to press the button above that threshold to have a valid tap. Additionally, a maximum time threshold could be also settled for the case that the person is touching on the screen and does not notice it, thus also discarding this possibility of involuntary tapping.</para>
<table-wrap position="float" id="T6-4">
<label><link linkend="T6-4">Table <xref linkend="T6-4" remap="6.4"/></link></label>
<caption><para>Mean duration of a single tap for each participant</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="top" align="center"></td>
<td valign="top" align="center" colspan="2">Involuntary<emphasis role="cline"/></td>
<td valign="top" align="center" colspan="2">Voluntary<emphasis role="cline"/></td></tr>
<tr>
<td valign="top" align="center"></td>
<td valign="top" align="center">Mean</td>
<td valign="top" align="center">Std. Deviation</td>
<td valign="top" align="center">Mean</td>
<td valign="top" align="center">Std. Deviation</td>
</tr>
<tr>
<td valign="top" align="center">Participant</td>
<td valign="top" align="center">of Time (ms)</td>
<td valign="top" align="center">of Time (ms)</td>
<td valign="top" align="center">of Time (ms)</td>
<td valign="top" align="center">of Time (ms)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="center">1</td>
<td valign="top" align="center">166.62</td>
<td valign="top" align="center">197.38</td>
<td valign="top" align="center">133.19</td>
<td valign="top" align="center">&#x00A0;&#x00A0;90.64</td>
</tr>
<tr>
<td valign="top" align="center">2</td>
<td valign="top" align="center">355.00</td>
<td valign="top" align="center">295.57</td>
<td valign="top" align="center">373.06</td>
<td valign="top" align="center">250.11</td>
</tr>
<tr>
<td valign="top" align="center">3</td>
<td valign="top" align="center">322.78</td>
<td valign="top" align="center">481.36</td>
<td valign="top" align="center">241.67</td>
<td valign="top" align="center">217.59</td>
</tr>
<tr>
<td valign="top" align="center">4</td>
<td valign="top" align="center">413.53</td>
<td valign="top" align="center">456.89</td>
<td valign="top" align="center">193.50</td>
<td valign="top" align="center">&#x00A0;&#x00A0;87.46</td>
</tr>
<tr>
<td valign="top" align="center">5</td>
<td valign="top" align="center">703.25</td>
<td valign="top" align="center">281.18</td>
<td valign="top" align="center">292.92</td>
<td valign="top" align="center">178.22</td></tr></tbody>
</table>
</table-wrap>
</section>
</section></section>
<section class="lev1" id="sec6-6" label="6.6" xreflabel="6.6">
<title>Conclusions after the User-Centred Process</title>
<para>This section presents a list of some generic conclusions after the user-centred design approach process organized in the frame of REMPARK, giving, in this way, the opportunity to generate a good solution for the interface implemented on the used Smartphone along the pilots:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Concerning the Screen Interaction:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>There were no noticeable difficulties on the accuracy of the tapping action when buttons size was reduced (elements measuring 10,5 mm in height were tested).</para></listitem>
<listitem>
<para>Concerning the test on the best approach to scrollable screens speed (normal or reduced), participants were able to use both. There were no enough data to conclude something relevant.</para></listitem>
<listitem>
<para>When participants were using button arrows as an alternative to scroll gestures, they were able to learn and subsequently use the arrows approach. In principle, it was noticed that it was not intuitive for them.</para></listitem>
<listitem>
<para>It is not possible to discriminate voluntary taps from involuntary ones although it might be possible to induce new tap behaviour to PwP in order to make that distinction possible.</para></listitem>
<listitem>
<para>In general, the users had no problems using spinners either on the Medication or the Appointments applications under test.</para></listitem>
<listitem>
<para>Concerning the action produced when clicking on &#x0201C;+ and &#x02013;&#x0201D; buttons, some users had difficulties using them at first, but after some time or after getting some hints, they got used to them and were able to finish the tasks using these.</para></listitem>
<listitem>
<para>Participants were able to use the pop-up dialogues to change date and time. Some were confused at first and used the down arrows to increment the values instead of the up arrows; but then quickly learned from the mistake.</para></listitem>
<listitem>
<para>No user had problems tapping over the checkboxes.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><emphasis role="strong">Concerning the Medication:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>In general, the participants were able to read the medication list and details. The main difficulty was in reading the intakes list for a given medicament.</para></listitem>
<listitem>
<para>The most part of participants had no problems reading the medication that they supposedly had to take for the current day.</para></listitem>
<listitem>
<para>After some hesitation on the options &#x02018;Custom interval&#x02019; and &#x02018;Custom week days&#x02019;, users were able to understand the intake repetition options.</para></listitem>
<listitem>
<para>Most participants were able to identify the medication that they had missed.</para></listitem>
<listitem>
<para>After some interaction with the researchers, users were able to understand that they can modify a missed intake by inputting the real intake hour.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><emphasis role="strong">Concerning the Appointments:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Participants were able to read correctly which days had appointments, although they missed the current week and the current day markings.</para></listitem>
<listitem>
<para>It was difficult to understand the tree view of Month > Week > Day. Nevertheless, they were able to use the calendar and read the appointments for a specific day.</para></listitem>
<listitem>
<para>Overall participants were able to correctly read the date of the events presented on a list, although there were some exceptions. Users were able to understand that an event can be repeated multiple times on the calendar by editing it.</para></listitem>
<listitem>
<para>When users tried to add a new appointment, they needed help to type on the phone, and scroll down to see more options and the save button.</para></listitem>
<listitem>
<para>In general, it was difficult to use and to add alarms to an event.</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</section>
<section class="lev1" id="sec6-7" label="6.7" xreflabel="6.7">
<title>Characteristics of REMPARK Smartphone Applications</title>
<para>Considering all the previous presented user-centred process and the preliminary conclusions obtained, a final implementation of the smartphone applications and user interface was organized according with the following main ideas:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">On Home Screen</emphasis></para>
<para>In order to avoid scroll and allow users to have a quick overview of each block of applications, the home screen was divided into three main blocks: General applications, Favourites and REMPARK applications.</para></listitem>
<listitem>
<para><emphasis role="strong">On Medication</emphasis></para>
<para>The Medication application retrieves and displays the neurologist prescriptions. At the same time it allows the user to add other medication which is not Parkinson&#x02019;s-related. Users can edit this latter medication, but not the one which has been placed into the system by the medical doctor.</para>
<para>The application shows the list of current medications the user is on, missed intakes, a schedule of intakes and a record of intakes.</para>
<para>The application shows medication reminders at intake time and the user may choose to keep track of his intakes. In this case, the medication reminder displays an option reading &#x02018;Taken&#x02019;. The option for the wording was to prompt users to press the option &#x02018;Taken&#x02019; only after they have taken the medication. This was done to provide users with a mechanism to help them know whether or not they have taken the medication. If, by some chance, the user has taken the medication but forgot to record the event on the smartphone, he or she can go to the &#x02018;Missed Intakes&#x02019; list and edit it by choosing that particular missed intake and editing it by inserting the hour at which the medication was indeed taken.</para></listitem>
<listitem>
<para><emphasis role="strong">On Appointments</emphasis></para>
<para>As with the Medication application, this application retrieves the information from the REMPARK server on existing appointments made by the doctor, while allowing the user to add their own. Again, users are only allowed to edit the information which has been inputted through the smartphone itself.</para>
<para>The Appointments application allows the users to access a calendar view (and reach their appointments from there), shows a list of events ordered by date and allows the user to create new events from the main menu.</para></listitem>
<listitem>
<para><emphasis role="strong">On Auditory Cueing System Controller</emphasis></para>
<para>The auditory cueing system controller application has a single screen and allows the following basic options: turn on/off, change volume and change rhythm. Users may also choose to change the sound type by previewing and selecting it and predefine the settings for the auditory cueing. This is done through the settings application.</para></listitem>
<listitem>
<para><emphasis role="strong">On Medical Questionnaires</emphasis></para>
<para>Medical questionnaires pop-up as they are fed into the system. Nevertheless, the user may opt to dismiss the questionnaire and answer it later. In this case, the Questionnaires application icon displays a notification showing the number of questionnaires waiting to be completed.</para>
<para>Due to the limited available space in a single screen (i.e. without scroll), there will be limits imposed to the number of characters for questions and answers. The reasoning behind this choice lays in the fact that the smartphone is one of the possible ways to answer medical questionnaires. The use cases predict that more complex or longer questionnaires may be answered through the web interface.</para></listitem>
<listitem>
<para><emphasis role="strong">On My Data</emphasis></para>
<para>The My Data application is meant for emergencies or for a quick overview of the user&#x02019;s health data to display, for instance, in a visit to the doctor who is not part of the REMPARK system. After a pop-up with a warning about the person&#x02019;s disease (meant for emergency scenarios), it shows the smartphone owner&#x02019;s picture, his or her name and phone number, along with health information: blood type, medication list, concomitant illnesses and specific data about Parkinson&#x02019;s disease.</para></listitem>
<listitem>
<para><emphasis role="strong">On My Day</emphasis></para>
<para>The My Day application refers to what was at first called &#x02018;Disease Status&#x02019; application. The name was changed to a more user friendly working. It has a single screen displaying information of the user&#x02019;s state over the previous day: ON/OFF periods, FOGs, festination episodes, missed medication intakes, falls and dyskinesia.</para></listitem>
<listitem>
<para><emphasis role="strong">On Quick Emergency Call</emphasis></para>
<para>This application works as a quick dial to an emergency number and is displayed both at the Applications and Favourites screens.</para></listitem>
<listitem>
<para><emphasis role="strong">On Calls</emphasis></para>
<para>The Calls application allows the user to make a phone call through a list of contacts or by typing in the number using an extra-large dial pad. It also allows checking missed calls and call history.</para></listitem>
<listitem>
<para><emphasis role="strong">On Contacts</emphasis></para>
<para>This application displays a regular contacts list and allows the user to define favourite contacts, call or send a message to a given contact, add new contacts and delete existing contacts.</para></listitem>
<listitem>
<para><emphasis role="strong">On Messages</emphasis></para>
<para>This application allows the users to simply read, listen to and send messages (through text or speech). It also supports sending and receiving pictures.</para></listitem>
<listitem>
<para><emphasis role="strong">On Settings</emphasis></para>
<para>The Settings application allows the user to set his or her preferences regarding Sounds, Vibration, Wi-Fi, Accessibility, Language, Auditory Cueing Settings, to set a Caregiver (which will show at the Favourites home screen and to Add a new device. In order to allow for troubleshooting, this menu shows an option which allows users to check the status of the sensors and actuators in the REMPARK system.</para></listitem>
<listitem>
<para><emphasis role="strong">On Status Bar, Notifications and Shortcuts</emphasis></para>
<para>The status bar is shown at the top of all screens and it displays information about the time, the battery status, the Wi-Fi connection status and strength of cellular signal. Furthermore, the status bar is used to host shortcuts for cueing controllers and to provide users with straightforward information about their status. When ACS cueing icons is on display in the status bar, they act as buttons to the applications. The notifications pertaining to each application will be shown on the home screens, on top of the corresponding application icon.</para></listitem>
</itemizedlist>
</section>
<section class="lev1" id="sec6-8" label="6.8" xreflabel="6.8">
<title>Some Concluding Remarks</title>
<para>The presented interface was completely integrated in the smartphone and used as part of the whole REMPARK system during the complete trials organized as one of the main activities at the end of the project. Participants were given the smartphone along with a user manual and, in the end, were asked to fill in SUS (System Usability Scale) and QUEST 2.0 (Quebec User Evaluation of Satisfaction with assistive Technology) questionnaires. Therefore, participants evaluated the whole system, not just the smartphone user interfaces.</para>
<para>The results indicate that there are some issues in terms of learnability, which should be looked at in the future. As it was reported during evaluation of REMPARK, &#x0201C;&#x02026;<emphasis>managing all that REMPARK has to offer at once can be quite overwhelming, especially if one is using the system for a short period of time and if the user&#x02019;s level of familiarity with technology is not very high. REMPARK is a completely new and innovative system and it is only natural that these barriers emerge. In the future, however, we could try to work on this part of introducing the system to new users, covering the unboxing experience as well. But this is for the future, as it was never part of the goals for our project&#x0201D;.</emphasis></para>
<para>It should also be noted that each participant interacted with the system for four days, which could explain why, at the end of the trials, participants were not completely familiarised with all the REMPARK apps. Nevertheless, satisfaction levels, as reported in the scales used, were quite high &#x02013; for the participants, the REMPARK system was comfortable, secure and safe.</para>
<para>Finally, one of the most interesting found discoveries during the field trials had to do with the &#x02018;My Day&#x02019; application. The app was not planned at first and was born from listening to PwP&#x02019;s conversations about their symptoms. During the field trials, screen interaction was analysed. The &#x02018;My Day&#x02019; screen showed a high activity with taps on the date and on the elements related to symptoms. This seems to suggest that participants wanted to interact with their own data.</para>
<para>On REMPARK&#x02019;s final workshop, we had the opportunity of showing the apps to Sara Riggare, a PD advocate and PwP herself. We commented on these results and findings, which did not surprise her. However, she recommended to focus on displaying the positive events, rather than the negative ones. Further work on the &#x02018;My Day&#x02019; app following the field trials and the experts&#x02019; advice was considered by us to be relevant work for the future</para>
</section>
<section class="lev1" id="sec6-9">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>N. Kostikis, D. Hristu-Varsakelis, M. Arnaoutoglou, C. Kotsavasiloglou e S. Baloyiannis, &#x0201C;Towards remote evaluation of movement disorders via smartphones,&#x0201D; em <emphasis>IEEE Eng Med Biol Soc</emphasis>, 2011. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=N%2E+Kostikis%2C+D%2E+Hristu-Varsakelis%2C+M%2E+Arnaoutoglou%2C+C%2E+Kotsavasiloglou+e+S%2E+Baloyiannis%2C+%22Towards+remote+evaluation+of+movement+disorders+via+smartphones%2C%22+em+IEEE+Eng+Med+Biol+Soc%2C+2011%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>L. M. Cunningham, D. D. Finlay, G. Moore e D. Craig, &#x0201C;A review of assistive technologies for people with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Technology and Health Care,</emphasis> vol. 17, no. 3, pp. 269&#x02013;279, 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=L%2E+M%2E+Cunningham%2C+D%2E+D%2E+Finlay%2C+G%2E+Moore+e+D%2E+Craig%2C+%22A+review+of+assistive+technologies+for+people+with+Parkinson%27s+disease%2C%22+Technology+and+Health+Care%2C+vol%2E+17%2C+no%2E+3%2C+pp%2E+269-279%2C+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>S. Keates e S. Trewin, &#x0201C;Effect of age and Parkinson&#x02019;s disease on cursor positioning using a mouse,&#x0201D; em <emphasis>ASSETS 2005</emphasis>, 2005. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=S%2E+Keates+e+S%2E+Trewin%2C+%22Effect+of+age+and+Parkinson%27s+disease+on+cursor+positioning+using+a+mouse%2C%22+em+ASSETS+2005%2C+2005%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. L. Levine e M. A. Shappert, &#x0201C;A mouse adapter for people with hand tremor,&#x0201D; <emphasis>IBM Systems Journal,</emphasis> vol. 44, no. 3, pp. 621&#x02013;628, 2005. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+L%2E+Levine+e+M%2E+A%2E+Shappert%2C+%22A+mouse+adapter+for+people+with+hand+tremor%2C%22+IBM+Systems+Journal%2C+vol%2E+44%2C+no%2E+3%2C+pp%2E+621-628%2C+2005%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>P. Maziewski, P. Suchomski, B. Kostek e A. Czyzewski, &#x0201C;An intuitive graphical user interface for the Parkinson&#x02019;s disease patients,&#x0201D; em <emphasis>4th International IEEE/EMBS Conference on Neural Engineering</emphasis>, 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=P%2E+Maziewski%2C+P%2E+Suchomski%2C+B%2E+Kostek+e+A%2E+Czyzewski%2C+%22An+intuitive+graphical+user+interface+for+the+Parkinson%27s+disease+patients%2C%22+em+4th+International+IEEE%2FEMBS+Conference+on+Neural+Engineering%2C+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>B. G&#x00F6;ransson, &#x0201C;The re-design of a PDA-based system for supporting people with Parkinson&#x02019;s disease,&#x0201D; em <emphasis>People and Computers XVIII &#x02013; Design for Life</emphasis>, Lodon, Springer, 2005, pp. 181&#x02013;196. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=B%2E+G%F6ransson%2C+%22The+re-design+of+a+PDA-based+system+for+supporting+people+with+Parkinson%27s+disease%2C%22+em+People+and+Computers+XVIII+-+Design+for+Life%2C+Lodon%2C+Springer%2C+2005%2C+pp%2E+181-196%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>K. B. Chen, A. B. Savage, A. O. Chourasia, D. A. Wiegmann e M. E. Sesto, &#x0201C;Touch screen performance by individuals with and without motor control disabilities,&#x0201D; <emphasis>Applied Ergonomics,</emphasis> vol. 44, pp. 297&#x02013;302, 2013. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=K%2E+B%2E+Chen%2C+A%2E+B%2E+Savage%2C+A%2E+O%2E+Chourasia%2C+D%2E+A%2E+Wiegmann+e+M%2E+E%2E+Sesto%2C+%22Touch+screen+performance+by+individuals+with+and+without+motor+control+disabilities%2C%22+Applied+Ergonomics%2C+vol%2E+44%2C+pp%2E+297-302%2C+2013%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>B. Gutekunst, &#x0201C;System and method for medical surveillance through personal communication device&#x0201D;. United States of America Patente WO2011088307 A2, 14 January 2011.</para></listitem>
<listitem>
<para>D. E. Tedesco, R. C. Tedesco e J. A. Jorasch, &#x0201C;Methods for remote assistance of disabled persons&#x0201D;. United States of America Patente US8669864 B1, 11 March 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+E%2E+Tedesco%2C+R%2E+C%2E+Tedesco+e+J%2E+A%2E+Jorasch%2C+%22Methods+for+remote+assistance+of+disabled+persons%22%2E+United+States+of+America+Patente+US8669864+B1%2C+11+March+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>B. C. Meyer e J. Zivin, &#x0201C;Device and methods for mobile monitoring and assessment of clinical function through sensors and interactive patient responses&#x0201D;. United States of America Patente US20130345524 A1, 16 December 2013. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=B%2E+C%2E+Meyer+e+J%2E+Zivin%2C+%22Device+and+methods+for+mobile+monitoring+and+assessment+of+clinical+function+through+sensors+and+interactive+patient+responses%22%2E+United+States+of+America+Patente+US20130345524+A1%2C+16+December+2013%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Nunes, F., Silva, P. A., Cevada, J., Correia de Barros, A., Teixeira, L. (2014). &#x0201C;User interface design guidelines for smartphone applications for people with Parkinson&#x02019;s disease&#x0201D;. Universal Access in the Information Society, 16(2). <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Nunes%2C+F%2E%2C+Silva%2C+P%2E+A%2E%2C+Cevada%2C+J%2E%2C+Correia+de+Barros%2C+A%2E%2C+Teixeira%2C+L%2E+%282014%29%2E+%22User+interface+design+guidelines+for+smartphone+applications+for+people+with+Parkinson%27s+disease%22%2E+Universal+Access+in+the+Information+Society%2C+16%282%29%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>L. R. Martin, S. L. Williams, K. B. Haskard e M. R. DiMatteo, &#x0201C;The challenge of patient adherence,&#x0201D; <emphasis>Therapeutics and Clinical Risk Management,</emphasis> vol. I, no. 3, pp. 189&#x02013;199, 2005. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=L%2E+R%2E+Martin%2C+S%2E+L%2E+Williams%2C+K%2E+B%2E+Haskard+e+M%2E+R%2E+DiMatteo%2C+%22The+challenge+of+patient+adherence%2C%22+Therapeutics+and+Clinical+Risk+Management%2C+vol%2E+I%2C+no%2E+3%2C+pp%2E+189-199%2C+2005%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. Viswanathan, C. E. Golin, C. D. Jones, M. Ashok, S. Blalock, R. Wines, C. M., E. J. L. Coker-Schwimmer, D. L. Rosen, P. L. Sista e N. thleen, &#x0201C;Interventions to improve adherence to self-administered medications for chronic diseases in the United States,&#x0201D; <emphasis>Annals of Internal Medicine,</emphasis> vol. 157, pp. 785&#x02013;795, 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+Viswanathan%2C+C%2E+E%2E+Golin%2C+C%2E+D%2E+Jones%2C+M%2E+Ashok%2C+S%2E+Blalock%2C+R%2E+Wines%2C+C%2E+M%2E%2C+E%2E+J%2E+L%2E+Coker-Schwimmer%2C+D%2E+L%2E+Rosen%2C+P%2E+L%2E+Sista+e+N%2E+thleen%2C+%22Interventions+to+improve+adherence+to+self-administered+medications+for+chronic+diseases+in+the+United+States%2C%22+Annals+of+Internal+Medicine%2C+vol%2E+157%2C+pp%2E+785-795%2C+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>FUSAMI is a web platform developed by Fraunhofer AICOS to perform analytics on user interaction, by collecting data on this interaction and analysing it with analytical algorithms. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=FUSAMI+is+a+web+platform+developed+by+Fraunhofer+AICOS+to+perform+analytics+on+user+interaction%2C+by+collecting+data+on+this+interaction+and+analysing+it+with+analytical+algorithms%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch07" label="7" xreflabel="7">
<title>Actuator Sub-System: The Auditory Cueing</title>
<para role="author"><emphasis role="strong">V&#x00E2;nia Guimar&#x00E3;es<superscript><emphasis role="strong">1</emphasis></superscript>, Rui Castro<superscript><emphasis role="strong">1</emphasis></superscript>, Angels Bay&#x00E9;s<superscript><emphasis role="strong">2</emphasis></superscript>, Carlos P&#x00E9;rez<superscript><emphasis role="strong">3</emphasis></superscript> and Daniel Rodriguez-Martin<superscript><emphasis role="strong">3</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>Fraunhofer Portugal AICOS &#x2013; Assistive Information and Communication Solutions, FhP-AICOS, Porto, Portugal</para>
<para><superscript>2</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<para><superscript>3</superscript>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<section class="lev1" id="sec7-1" label="7.1" xreflabel="7.1">
<title>Introduction</title>
<para>Patients with Parkinson&#x02019;s Disease (PD) are usually affected by clinical symptoms associated to a reduced motor performance that frequently compromises their ability to walk independently and safely [1]. While a number of pharmacological solutions help to manage the symptoms of PD, some gait-related problems appear resistant to such treatments and, over time, movement-related disturbances turn out to be the most incapacitating symptoms of the disease [2].</para>
<para>The internal regulation of step length is generally affected, which is reflected as an inability to generate sufficient amplitude of movement, even though the control of cadence, or step rate, is intact. This is in fact the foundation for the use of external rhythmic stimuli, or cueing, as a way to ameliorate the impact of the disease on rhythmic movement-based tasks, as is the case of walking [3, 4].</para>
<para>Typically, to compensate for the reduced step length, patients may increase the stepping frequency. These symptoms are usually referred to as &#x0201C;<emphasis>continuous gait problems</emphasis>&#x0201D;, since the changes in walking patterns are more or less consistent from one step to the next. With disease progression, &#x0201C;<emphasis>episodic gait disturbances</emphasis>&#x0201D; may appear which result in intermittent and occasional episodes, such as start hesitation, Freezing of Gait (FOG) episodes and festination [3&#x02013;5].</para>
<para>Several cueing strategies, including acoustic and visual cues, can be applied being capable of modifying movements&#x02019; speed and amplitude, as well as reducing or shortening the occurrence of episodic gait disturbances, such as FOG episodes [2, 6, 7].</para>
<para>Rhythmic auditory stimulation, in particular, enable people to involuntarily synchronize the rhythm of the steps with the rate of the sounds, therefore, enhancing the sense of &#x0201C;taking a step&#x0201D;, and the sense of &#x0201C;rhythm&#x0201D;, which are both affected by the disease [2, 7&#x02013;10].</para>
<para>Multiple studies have found a positive impact of the rhythmic sounds on steps length [8, 11, 12], walking speed [9, 10, 12, 13], variability [3, 9] and FOG episodes [2, 14&#x02013;16]. In addition to the positive impact observed on gait, it was found that rhythmic sounds can also enhance the performance of other tasks involving perceptual and motor timing [17].</para>
<para>Many external cueing approaches are described in the literature; however, several limitations can be identified. Current solutions typically provide interventions continuously (i.e., even when no specific gait symptoms are present), and require cueing to be triggered manually, which limits its applicability in people&#x02019;s everyday life [2]. Also, the application of a continuous cueing means that stimuli are presented without considering whether the patient is suffering from walking problems or not, which can lead to a possible habituation effect that reduces cueing efficacy [18].</para>
<para>To address some of the limitations encountered on previous approaches, an automatic Auditory Cueing System (ACS) was developed throughout the project REMPARK. The developed solution used a smartphone and a headset available in the market, and could provide external cues automatically each time a relevant motor symptom was detected requiring cueing activation. For that purpose, the REMPARK sensor sub-system was used.</para>
<para>This chapter is focused on the Auditory Cueing System (ACS) developed for REMPARK as part of the project implementation. Last part of the chapter is devoted to a technical discussion on the possible future use of the REMPARK developed sub-systems (mainly, the sensor) for an automatic control of the dosage of drug (apomorphine) delivered by an infusion pump, when integrated into the reaction loop around the patient. This technical validation opens the door to future experiences in the way to a better management of the PD symptoms, meaning an improvement on patients&#x02019; quality of life.</para>
</section>
<section class="lev1" id="sec7-2" label="7.2" xreflabel="7.2">
<title>Cueing Strategies for Gait in Parkinson&#x02019;s Disease</title>
<para>Human beings are particularly sensitive to the temporal characteristics of sound, therefore, <emphasis>sonification</emphasis> (generation of data-dependent audio to present information) suits well for time-related tasks, as is the case of the body movement. Other attributes besides rhythm can also be associated to certain events or processes by listening. Pitch (i.e., the perceptual dimension of frequency), for example, is related to the perceived urgency of a warning and, the higher the pitch, the higher the perceived urgency [19].</para>
<para>Multiple types of sounds were explored by different authors as strategies to guide and provide feedback on walking patterns in people with PD, including, metronome and music. In all strategies employed, rhythm turns out to be a key aspect in influencing time-related tasks, as is the case of walking.</para>
<para>The concept of metronome is generally applied to a device that produces regular, metrical beats with adjustable number of beats per minute (BPM). It is typically used by musicians as a reference to help keeping a steady tempo and was also applied in the context of cueing in PD.</para>
<para>The metronome generates temporal expectations that can be intuitively associated to the cyclic movement of walking. In fact, it allows people with PD to predict when the next step should occur, which facilitates movement optimization and execution [17]. Therefore, it is required that an adequate rhythm is provided to the user, considering his/her normal walking cadence.</para>
<para>The metronome can pace both &#x02013; right and left &#x02013; footfalls, by producing a regular, repeated sound at an adjustable pace defined as the number of beats per minute (BPM). Several authors showed that the presentation of sounds with a rhythm that is lower than their natural walking rhythm can be used not only to influence rhythm but also to indirectly influence the magnitude of the movement through an increase in the length of the steps, while maintaining gait speed [9, 20]. A positive impact was also observed in other walking parameters, including the variability of walking [3, 9] and FOG episodes [2, 14&#x02013;16]. Rhythmic sounds could also enhance the performance of other tasks involving perceptual and motor timing [17].</para>
<para>More complex sounds, including music, have also shown to influence the organization of movement in time and space. Music, like movement, is multidimensional, as such it can be naturally linked to spatial, temporal and force elements of the movement. It can be used as an immediate entrainment stimuli acting during movement, or a facilitating stimulus for training to achieve more functional gait patterns. Music therapists are trained to adjust rhythm, dynamics, and pitch as needed specifically by each patient, according to their rehabilitation needs [21].</para>
<para>Wittwer, et al. in [22] showed that music produced a significant increase in gait velocity in healthy older adults, due to a significant increase in stride length. In contrast, when applied to a group of people with Huntington&#x02019;s disease, and contrarily to what would have been expected, music produced no results, and, in contrast, metronome performed better in this group. The authors suggested that participants&#x02019; cognitive deficits may have impaired their ability to discern the beat from the more complex music structure [22].</para>
<para>Besides auditory feedback, other types of external cueing can be applied, including visual and somatosensory cues. Visual cueing is traditionally employed using series of strips placed on the floor in transverse line for the patients to walk over. However, this type of strategy can only be applied in laboratory context, not being useful during the daily life. Portable solutions, such as goggles with light emitting diode (LED) or laser-guided walking canes have been developed, in which the same principles of projecting parallel lines on the floor are applied (see <link linkend="F7-1">Figure <xref linkend="F7-1" remap="7.1"/></link>). Some of these solutions can even present the stimuli on demand, for example, when a FOG episode occurs. However, some issues arise from the use of this kind of strategies in outdoor environments, especially in bright areas where the visual information may become less visible. Moreover, this kind of assistive devices may not be practical for real life usage conditions, due to its obtrusiveness [18, 23].</para>
<fig id="F7-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-1">Figure <xref linkend="F7-1" remap="7.1"/></link></label>
<caption><para>Examples of visual cueing strategies (extracted from [24]).</para></caption>
<graphic xlink:href="graphics/ch07_fig001.jpg"/>
</fig>
<para>In addition to these strategies, also rhythmic somatosensory cueing has been explored. Strategies such as electrical stimulation or rhythmic vibration have been studied by different researchers, showing also positive effects on gait [23]. Electrical stimulation, in particular, requires more complex setups that may not be practical for a daily usage [25].</para>
<para>In [23] it is shown that although all the three types of stimuli (visual, auditory, somatosensory) were effective in improving gait velocity, step length and cadence, auditory cueing was in fact the most effective cueing strategy applied. Moreover, it may provide the easiest setup, being more practical and realist for a daily everyday usage.</para>
</section>
<section class="lev1" id="sec7-3" label="7.3" xreflabel="7.3">
<title>State of the Art: Competitive Analysis</title>
<para>A systematic search was conducted on the World Wide Web in order to capture and analyse relevant information about existing studies, projects and commercial solutions, with a particular focus on solutions for auditory stimulation and feedback in PD.</para>
<para>Research included technology being developed and described in published and publicly available papers and conference proceedings, as well as commercial solutions that are already available in the market. Moreover, a patent search was conducted to find out innovative solutions for the management of PD. Search was limited to solutions targeting patients with movement disorders, in particular, patients with PD and technological approaches mostly based on auditory cueing aiming to reduce or overcome motor symptoms related to the disease.</para>
<para><link linkend="T7-1">Table <xref linkend="T7-1" remap="7.1"/></link> summarizes the results of said search for R&#x00026;D and market-ready products. For each solution, the following parameters were evaluated:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Current stage of development: R&#x00026;D or market-ready;</para></listitem>
<listitem>
<para>System Components: e.g. smartphone, headset, dedicated hardware, etc.;</para></listitem>
<listitem>
<para>Types of cueing: metronome, music, verbal cueing and possibly others (e.g. visual or sensory cueing);</para></listitem>
<listitem>
<para>Modalities and symptoms: identifies whether a system can or not provide cueing automatically in response to motor symptoms (i.e. the actuation mode); also identifies whether cueing can or not be manually activated under specific circumstances/requirements with the purpose of training (i.e. the training mode); provides a list of motor symptoms that are targeted by the system;</para></listitem>
<listitem>
<para>History Recording, in case the system is able to record the history of activations/deactivations;</para></listitem>
<listitem>
<para>Connection with a Disease Management System (DMS), in case the system is prepared to connect to a server, in which data are recorded to be then displayed and used by clinicians.</para></listitem>
</itemizedlist>
<table-wrap position="float" id="T7-1">
<label><link linkend="T7-1">Table <xref linkend="T7-1" remap="7.1"/></link></label>
<caption><para>Technology watch on actuators for auditory cueing in Parkinson&#x02019;s Disease</para></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="graphics/tab7-1.jpg"/>
</table-wrap>
<para>Not many non-pharmacological solutions for actuation in PD can currently be found in the market. The majority of the solutions found are still in R&#x00026;D stage. In particular, related to the auditory stimulation, only one commercial solution was found, the <emphasis role="underline">GAITAID Virtual Walker</emphasis>. This solution can provide not only auditory stimulation, but also visual stimulation and for that it requires the use of display glasses with built-in earphones, which are connected to a proprietary control unit that is responsible for creating images and sounds by responding to the user&#x02019;s movements. The system was made in the US, and the prices range from 1995 USD (&#x0223C;1840 ), for orders in US, to 2145 USD (&#x0223C;1980 ), for orders outside US and Canada. GAITAID, unlike the REMPARK solution, is not capable of detecting specific motor symptoms, neither actuating automatically upon the detection of the symptoms, being therefore more limited in this sense.</para>
<para>In the study develop by <emphasis role="underline">B&#x00E4;chlin</emphasis>, a system for the automatic detection of FOG episodes was developed. For that, they require the use of multiple sensors, which are placed on the waist, thigh and ankle. The system is controlled by a portable processing unit which is placed on the waist and is responsible for processing sensor data and triggering auditory cueing (metronome sound) as soon as a FOG episode is detected. It clearly demonstrates the positive and immediate effects of auditory stimulation in patients&#x02019; gait.</para>
<para>The <emphasis role="underline">iRACE</emphasis> application, developed for iOS, uses the sensors of the smartphone to detect steps and estimate steps length. The finger tapping test is also available in the application. The <emphasis role="underline">GaitAssist</emphasis>, which was developed in the FP7 European project <emphasis role="underline">CuPID</emphasis>, also uses the smartphone as a support for the execution of physical exercises for training, and enable the detection of FOG episodes through the analysis of the data coming out of two sensors which are placed in the ankles.</para>
<para><emphasis role="underline">CuePack</emphasis>, which was developed in the context of the European project <emphasis role="underline">RESCUE</emphasis>, enables the application of different types of stimulus, including auditory, visual and sensory stimulation. Its actuation capabilities are limited to a training context, since it is not able to detect motor symptoms.</para>
<para>According to <link linkend="T7-1">Table <xref linkend="T7-1" remap="7.1"/></link>, no cueing device is as complete as REMPARK ACS. While some solutions are not capable of detecting motor symptoms and actuating accordingly, others, are limited to the detection of FOG episodes. Also, to detect this type of episodes, both solutions require the use of multiple sensors, whereas REMPARK needs just one sensor unit to detect a larger amount of motor symptoms, including FOG episodes, bradykinesia and dyskinesia events.</para>
<para>Some of the presented solutions are based on the use of specific equipment for sounds generation and control, as is the case of <emphasis role="underline">GAITAID Virtual Walker</emphasis>, <emphasis role="underline">B&#x00E4;chlin</emphasis> and <emphasis role="underline">CuePack</emphasis>. In contrast, REMPARK, <emphasis role="underline">GaitAssist</emphasis> and <emphasis role="underline">iRACE</emphasis> are based on the use of a smartphone.</para>
<para>Moreover, REMPARK can connect to a DMS, enabling also clinicians to analyze their patients&#x02019; data. As expected, and since the majority of the systems are still in the R&#x00026;D stage, no references to the connection to a server are usually available in the considered systems.</para>
<para>It was noticed that, to actuate properly, the majority of the systems aforementioned, including REMPARK, require an initial configuration step, in which normal gait parameters for a specific patient with PD are identified and given as an input to the system. This step helps not only to decide when a gait pattern deviates from the normal, but also to establish the functional goals that need to be achieved after cueing is applied.</para>
<para>Regarding the type of sounds delivered to the patients, the majority of the solutions are based on the metronome, i.e. repetitive sounds played with a certain periodicity. REMPARK also offers the possibility of delivering verbal cueing (i.e. &#x0201C;one-two-one-two&#x0201D;). Additional solutions are also capable of providing other types of cueing. <emphasis role="underline">CuePack</emphasis>, for example, is able to provide three different types of cueing, including the metronome, visual cueing and sensory cueing. <emphasis role="underline">GAITAID Virtual Walker</emphasis> can provide both auditory and visual cueing, which can be used in combination or separately, according to the patient specificities. However, for this functionality, it requires the use of proprietary devices that need to be carried by the patient while walking.</para>
<para>Based on this analysis, and considering the limitations of the current solutions encountered on the literature, REMPARK seems to be the most integrated solution for detection, treatment and management of motor disorders in PD, being capable of actuating in real time, each time a motor symptom is detected and cueing is required. Moreover, it can be used either as a gait training device (at clinics or at home) or during the daily life, at home or outdoors, being capable of actuating automatically when a motor symptom is detected and cueing is deemed as required. As it uses mainly components that already exist in the market, such as the smartphone and a headset, and a single discrete sensor that needs to be worn in the belt, the solution itself may not be stigmatizing for its users, being therefore more attractive.</para>
<para>A more throughout analysis of the existing technology was conducted through the analysis of the patents produced in this area. The most relevant inventions are described in the following paragraphs:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>US 8409116 B2 (Granted, filing date 2010) presented a device and method for treating patients with movement disorders. The device includes a sensor for detecting an akinetic episode (e.g. a FOG episode) of the person and a receiver that automatically issues a single or multiples cues to aid in the restoration of the movement. The cue can be of any type, including verbal, auditory, physical or tactile. Moreover, they propose sending the information about FOG events wirelessly to a caregiver and/or an emergency contact [26].</para></listitem>
<listitem>
<para>EP 2346580 A2 (Application, filing date 2011) disclaims a method for the improvement of gait parameters comprising determining attributes of ideal spatial and temporal gait parameters of the subject, measuring the actual parameters and determining the rhythmic audio cue that may cause the subject to improve a gait parameter [27].</para></listitem>
<listitem>
<para>US 8961186 B2 (Granted, filing date 2012) presents an ambulation accessory that can also be used as a training device. The invention includes two balls that illuminate in an alternating fashion to provide a visual target to each leg. When the user reaches the ball with his foot, the system returns visual and auditory feedback indicating a successful step [28].</para></listitem>
<listitem>
<para>WO 2012177976 A2 (Application, filing date 2012) presents a method performed by one or more processing devices that includes generating a visual representation of an object in the environment, retrieving an auditory stimulus indicative of the location of a virtual target in the environment, determining the proximity of the object to the virtual target and adjusting the auditory attributes based on proximity [29].</para></listitem>
</itemizedlist>
<para>As can be perceived, some of these patents describe a system whose operating mode is basically the same adopted by the systems in <link linkend="T7-1">Table <xref linkend="T7-1" remap="7.1"/></link>. They include the possibility of detecting movement disorders, the ideal gait parameters and the cueing strategy/parameters required to overcome said disorder. All the systems described in the inventions offer the possibility of using auditory cueing as a feedback mechanism for gait. US 8409116 B2 presents a generic method that can use just one type of cueing or a combination of several types. EP 2346580 A2, on the other side, is focused on the use of audio cues comprising a tone and a beat. The last two commented patents (US 8961186 B2 and WO 2012177976 A2) are mainly focused on the use of visual cues combined with audio for feedback on gait. As can be understood, these systems lack practicability, as the delivery of visual stimulus while walking requires the use of additional equipment, e.g. display glasses. Systems based on the use of auditory cueing can be largely simpler and affordable, since they can benefit from the use of existing, commercial, equipment that a person may already have, as is the case of REMPARK ACS using standard headsets and a smartphone.</para>
</section>
<section class="lev1" id="sec7-4" label="7.4" xreflabel="7.4">
<title>REMPARK Auditory Cueing System (ACS)</title>
<para>The ACS was developed in the context of the project REMPARK according the specifications and characteristics described in <link linkend="ch03">Chapter <xref linkend="ch3" remap="3"/></link>. It uses an Android smartphone, which is connected via Bluetooth to a commercial headset. The smartphone is responsible for generating cueing sounds, controlling their rhythm and streaming them to the headset (<link linkend="F7-2">Figure <xref linkend="F7-2" remap="7.2"/></link>).</para>
<fig id="F7-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-2">Figure <xref linkend="F7-2" remap="7.2"/></link></label>
<caption><para>REMPARK Auditory Cueing System.</para></caption>
<graphic xlink:href="graphics/ch07_fig002.jpg"/>
</fig>
<para>The headset can be any commercial Bluetooth headset with, at least, Bluetooth version 2.1 and A2DP profile [30].</para>
<para>The ACS includes multiple types of sounds, which can be chosen through the smartphone interface. It includes metronome sounds, musical beats, clapping and verbal cueing (&#x0201C;One-two-one-two&#x0201D;). The patient may himself select the sound that he/she prefers the most and is more comfortable with.</para>
<para>Each sound, in reality, falls into the category of a metronome, considering that all sounds produce metrical beats with adjustable number of beats per minute (BPM). The rhythm of the sounds is provided in beats per minute for a direct connection with gait cadence or step rate, also defined as the number of steps per minute (SPM). Both footfalls, right and left, are paced by the system (<link linkend="F7-3">Figure <xref linkend="F7-3" remap="7.3"/></link>), and some of the available sounds are actually a combination of different timbres that aim at providing a different feedback for each step.</para>
<fig id="F7-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-3">Figure <xref linkend="F7-3" remap="7.3"/></link></label>
<caption><para>Cueing rhythm (beats per minute BPM) and cadence (steps per minute SPM).</para></caption>
<graphic xlink:href="graphics/ch07_fig003.jpg"/>
</fig>
<para>The ACS takes advantage of the existing modules that are integrated in the REMPARK solution, including the motor symptoms detection provided by the REMPARK sensor sub-system. The auditory cueing is activated by the system as soon as FOG or bradykinesia are detected by the movement sensor. Once a patient has continued walking without bradykinesia or has stopped walking, the cueing is discontinued. Nevertheless, each time auditory cues are activated, a pop-up window appears on the smartphone screen, for a quick interaction with the system, which enables the patient to easily stop the sounds, or manipulating sounds rhythm and volume (<link linkend="F7-4">Figure <xref linkend="F7-4" remap="7.4"/></link>).</para>
<fig id="F7-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-4">Figure <xref linkend="F7-4" remap="7.4"/></link></label>
<caption><para>Pop-Up window for basic control of ACS when it starts automatically.</para></caption>
<graphic xlink:href="graphics/ch07_fig004.jpg"/>
</fig>
<para>The rhythm and volume of cues are pre-configured through the smartphone. A clinician may introduce the target rhythm for the cueing sounds that will target patients&#x02019; needs the best as possible. The clinician may also define the maximum and minimum cueing rhythm that can be provided to the patient, so that rhythm may never compromise patients&#x02019; safety and the safe synchronization of steps with gait cueing, while still maintaining a good pattern of walk. The clinician may also help the patient define the minimum volume accepted by the system, so that it may never go below a level that is inaudible by the patient.</para>
<para>Voice instructions are also available in the system, to explain what to do, or how to proceed each time sounds start playing. Both temporal instructions (&#x0201C;Step in time to the beat&#x0201D;) and spatiotemporal instruction (&#x0201C;Take a big step in time to the beat&#x0201D;) can be delivered according to the type of symptoms detected. These instructions can be deactivated through the ACS settings application. Through this screen, the patient may also preview each sound available, as well as change the default actuator type of sound.</para>
<para>The ACS can also be activated manually by the patient, and therefore serve as a training device for gait. This will enable patients to listen to the sounds as part of a gait training task. The controller application can be opened from the REMPARK applications list (<link linkend="F7-5">Figure <xref linkend="F7-5" remap="7.5"/></link>).</para>
<fig id="F7-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-5">Figure <xref linkend="F7-5" remap="7.5"/></link></label>
<caption><para>Auditory Cueing System application.</para></caption>
<graphic xlink:href="graphics/ch07_fig005.jpg"/>
</fig>
<para>Moreover, the ACS takes advantage of the capability of recording the history of activations and deactivations, which can then be analyzed by clinicians through the disease management system (DMS) [30].</para>
</section>
<section class="lev1" id="sec7-5" label="7.5" xreflabel="7.5">
<title>Outcomes from Field Trials: Future Considerations</title>
<para>The ACS was developed as a module capable of providing auditory stimuli in real time, to help people with Parkinson&#x02019;s Disease improve speed and amplitude of walking. Before developing the final version of the system, which was then evaluated in the 3 days-long trials stage, a preliminary testing stage with a first prototype was required to get the first impressions on the feasibility of the system in stimulating gait, as well as evaluate system&#x02019;s usefulness and acceptance.</para>
<para>Preliminary tests were conducted in Spain with 12 people with PD. During the tests, patients were asked to walk, sometimes with cueing, other times without cueing, and their walking rhythm was measured against cueing rhythm. Motor symptoms were identified by observation by a trained medical doctor or therapist. Patients were asked to walk along predefined distances and walking circuits, but also to walk at will, being able to choose the trajectory they wanted to follow. Therefore, both indoor and outdoor conditions were captured (<link linkend="F7-6">Figure <xref linkend="F7-6" remap="7.6"/></link>).</para>
<fig id="F7-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-6">Figure <xref linkend="F7-6" remap="7.6"/></link></label>
<caption><para>Preliminary tests with PD patients for the ACS.</para></caption>
<graphic xlink:href="graphics/ch07_fig006.jpg"/>
</fig>
<para>Despite the reduced number of participants in this preliminary testing stage, experimental results suggested that better gait patterns could be stimulated when individuals follow rhythmic sounds whose rate is similar to their natural step rate. The fact that people tended to walk with better walking patterns and overcome gait problems when feedback rhythm was closer to their normal walking cadence supports this observation.</para>
<para>Additionally, people found the volume and quality of sounds adequate, even in outdoor conditions, where a louder environmental noise could be found. This is an important requirement for the system, since it is expected to work in real time, even in outdoor conditions during a person&#x02019;s daily routine. Actually, all participants would be willing to use the system during their everyday life, considering that it would help them in real time during their daily activities. A complete report of methods and results achieved in these preliminary tests can be found in reference [31].</para>
<para>After the final ACS prototype has been developed and integrated with the other REMPARK components, i.e. the REMPARK sensor and the DMS, the final trials period took place, as it is reported in <link linkend="ch09">Chapter <xref linkend="ch9" remap="9"/></link>. During the trials, 41 people with PD used the system continuously for three consecutive days and the ACS was put to the test under real life conditions.</para>
<para>After using the system continuously during three consecutive days, people reported some issues related to the size and comfort of the headset. In fact, the headset chosen for the trials was an existing commercial device that was chosen considering mainly its technical specification and price. However, for a final solution, it is also required to consider its aspect, weight, easiness to put and remove from the ear, ear fitting, sense of attachment and sound quality, and take into account also the individual preferences of its users.</para>
<para>In addition, some patients suggested the use of music instead of the metronome to act as cueing during their daily life, to be more enjoyable and not so monotonous. In fact, due to the requisite of maintaining a fixed rhythm, the metronome can become monotonous after a while, therefore challenging the acceptability and sustainability of the solution. Still, it can be the only viable cueing solution for some people, for example, people with cognitive deficits, as suggested by the authors in reference [22].</para>
<para>As a final conclusion, the REMPARK system appears to be usable and participants seem to be satisfied with the system. Improvements on the system will, for sure, take into account the valuable input provided by the people who participated in the trials.</para>
</section>
<section class="lev1" id="sec7-6" label="7.6" xreflabel="7.6">
<title>A Step Further in REMPARK: Automatic Drug Administration</title>
<para>As it has been already discussed in <link linkend="ch03">Chapter <xref linkend="ch3" remap="3"/></link>, one of the project goals was to technically validate the feasibility of using REMPARK system to create an automatic or semi-automatic feedback wireless control loop that would improve the treatment of PD patients, using some reaction solutions. For this purpose, a commercial apomorphine infusion pump was modified. The modifications consisted of incorporating the necessary electronic components so that it is able to communicate with the smartphone in order to receive commands related to the drug dosage to be administered. These commands come from the symptoms&#x02019; measurements performed by the developed REMPARK sensor. Additionally, the electronic system added to the pump should permit a manual user interaction through the smartphone.</para>
<para>REMPARK project proposal discarded, from the beginning, the organization of a specific pilot action using drug delivery systems control with real patients because this was out of the real possibilities of the project piloting activity. The main reason was the required timing for these type of pilots, where time scales are much more long than those for the rest of scheduled assessment pilots. The only activity, at this level, was to consider the effective possibility of a wireless control of these devices, preparing all the requirements and conditions from a technical and functional point of view.</para>
<para>Apomorphine has been widely used to treat Parkinson&#x02019;s Disease. One of its main usages is under Apo-go Pen format. Doses are small injections which patients can self-administer, with a limited amount of apomorphine. Its active principle provokes, compared to the levodopa effect, a very quick response (within few minutes), and the length of the effect is short, which makes this drug suitable for controlling the symptoms in real time.</para>
<para>At that level, REMPARK project proposed several objectives:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>to technically demonstrate that an automatic drug delivery system can be remotely controlled and activated by the REMPARK system when an unexpected OFF period is detected.</para></listitem>
<listitem>
<para>an automatic delivery of the rescue dose is technically possible.</para></listitem>
</itemizedlist>
<para>A subcutaneous infusion pump would be included in the system and would be ready for its automatic activation. This prototype will facilitate functional laboratory testing of the drug delivery pump for remote operation in simulated clinical conditions.</para>
<para>After analysing the existing options, the Microjet CronoPAR [37] subcutaneous pump manufactured by Can&#x00E8; s.r.l was identified as the unique option to be adopted. This commercially available pump provides the functional features associated with the infusion of apomorphine to Parkinson&#x02019;s Disease patients. In order to fulfil the project requirements, an electronic control unit was developed and integrated into the device. <link linkend="F7-7">Figure <xref linkend="F7-7" remap="7.7"/></link> shows this infusion pump model as it is commercially available.</para>
<fig id="F7-7" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-7">Figure <xref linkend="F7-7" remap="7.7"/></link></label>
<caption><para>Infusion pump to be adapted for a possible use with REMPARK system.</para></caption>
<graphic xlink:href="graphics/ch07_fig007.jpg"/>
</fig>
<para>In the original pump, a set of buttons enable the user to command the behaviour of the pump. A display shows the state of the device. As the device does not have a battery recharge system, the battery must be replaced and it may be accessed removing a side tap.</para>
<para>An automatic control requires the substitution of the manual interaction by an electronic interface, with the equivalent functionality and provided with a connection to the smartphone using a wireless communication channel. The strategy for this modification was to replace the PCB (Printed Circuit Board) integrated in the pump keypad by a much more complex PCB integrating the interaction with the pump, through the electronic control of the buttons, and the mentioned wireless connection.</para>
<para><link linkend="F7-8">Figure <xref linkend="F7-8" remap="7.8"/></link> shows the modified Microjet CronoPAR, where the controller has been replaced by a new electronic hardware (PCB). The PCB was designed to allow a similar aspect of the device, with the same functionality and its operative LCD display.</para>
<fig id="F7-8" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-8">Figure <xref linkend="F7-8" remap="7.8"/></link></label>
<caption><para>Modified pump.</para></caption>
<graphic xlink:href="graphics/ch07_fig008.jpg"/>
</fig>
<para>The main directive in the PCB design process was the achievement of a device with reasonable autonomy but keeping the original physical size, allowing the user to wear the subcutaneous pump without undue inconveniences. The components of the system were restricted to be compatible with an adjusted power consumption and practical size. <link linkend="F7-9">Figure <xref linkend="F7-9" remap="7.9"/></link> shows the general scheme of the PCB device. Internally, the device includes a microcontroller that handles the different sub-system parts. The microcontroller provides the system with the capacity of managing the subcutaneous pump and at the same time to establish a wireless communication.</para>
<fig id="F7-9" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-9">Figure <xref linkend="F7-9" remap="7.9"/></link></label>
<caption><para>PCB general scheme.</para></caption>
<graphic xlink:href="graphics/ch07_fig9.jpg"/>
</fig>
<para>The control board of the PCB is managed by a microcontroller, which is in charge of controlling the subcutaneous pump while managing the data received from the wireless module. The PCB replaces the original control board of the subcutaneous pump maintaining the same shape, but increasing its thickness. In order to control the pump behaviour, the control buttons have been replaced by control signals provided by the PCB. As a feedback, to confirm the proper operation of the pump, an electronic signal associated with internal acoustic information is provided.</para>
<para>The Microjet CronoPAR is supplied with a standard and commercially available 3 Volt type 123 A Lithium non-rechargeable battery with a capacity of 1400&#x02013;1500 mAh. As the operating voltage range of the PCB is 2.1 V to 3.6 V, it can be supplied with the battery of the original pump. This feature allows the PCB to work with all the available operating voltage ranges, ensuring that the system can work with any low battery situation.</para>
<para>The control and supervision functionalities of the modified pump are achieved with the execution of the microcontroller&#x02019;s embedded firmware. The system operation relies on a series of independent but coordinated processes that manage the behaviour of the subcutaneous pump, taking advantage of its functional capabilities. The PCB device takes control of the pump behaviour working as a wireless interface between the subcutaneous pump and the smartphone (<link linkend="F7-10">Figure <xref linkend="F7-10" remap="7.10"/></link>). The main state machine (firmware) is in charge of coordinating the commands received from the communication module, giving the necessary functionality to the system and synchronizing the remaining processes. Moreover, the subcutaneous pump provides multiple features (e.g., administration of the bolus dose). These features have been developed as a secondary software (state machine), which is managed by the main firmware software of the device.</para>
<fig id="F7-10" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-10">Figure <xref linkend="F7-10" remap="7.10"/></link></label>
<caption><para>System operation overview.</para></caption>
<graphic xlink:href="graphics/ch07_fig0010.jpg"/>
</fig>
<para>It is necessary to confirm that the control of the pump is correctly performed, and also, it is necessary to acknowledge and monitor the correct operation of the device. In consequence, an interface was provided giving the necessary information to the system. This information about the functioning of the pump is provided by means of an electronic signal, associated with an internal acoustic confirmation. Using this signal to complete the feedback loop, the entire system can be managed electronically. As a result, the PCB interface is connected to the subcutaneous pump through four signals: three output signals connected to the buttons of the pump, and one input connected to the beep signal. The connecting diagram between the subcutaneous pump and the PCB can be seen in <link linkend="F7-11">Figure <xref linkend="F7-11" remap="7.11"/></link>.</para>
<fig id="F7-11" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F7-11">Figure <xref linkend="F7-11" remap="7.11"/></link></label>
<caption><para>Connection diagram between the pump and the designed PCB.</para></caption>
<graphic xlink:href="graphics/ch07_fig0011.jpg"/>
</fig>
<para>In order to manage and control the pump, the input signals generated by the front buttons are now provided by the PCB. Then, by activating these signals, the PCB is able to perform all the required actions, for example administer bolus dose or program the infusion rate.</para>
<para>In normal operation regime, the ambulatory infusion pump manufactured by Can&#x00E8; s.r.l. offers two main operative modes: intermittent bolus or continuous apomorphine infusion at variable dose. When operating in a single shot mode the subcutaneous pump administrates a given quantity of drug only once. On the other hand, continuous apomorphine infusion consists on continuous pulses of infusion, where the rate of these pulses depends on the programmed infusion rate.</para>
<para>In REMPARK, the implemented firmware on the PCB is trying to replicate this operative in an electronic way, using a state-machine approach. Deployment of pump behaviour in state-machine based allows a good understanding of the logic process. In principle, the subcutaneous pump has two independent states; <emphasis>Pump Switched ON</emphasis> and <emphasis>Pump Switched OFF</emphasis>. Each state has the possibility to perform specific actions. For example, the pump must be switched off to program the bolus dose. On the other hand, switching on the pump allows to administer infusion, bolus dose and to program the flow rate.</para>
<para>The OFF state starts when the pump finishes an auto diagnostic routine. Here the bolus dose configuration may be managed. On the other hand, infusion state starts when the pump has been switched on. This state is in charge of managing the main actions that can be requested remotely and mainly the administration of the infusion and the bolus dose. The PCB interprets the command sent remotely and changes the state of the pump in consequence.</para>
<para>To ensure that actions are correctly performed, a feedback from the pump is obtained, as it was introduced. The pump confirms all its actions by emitting a brief sound signal. Then, taking this signal as an input, the PCB is able to read and analyse the action feedback. As a main characteristic, this sound signal has different behaviours depending on the action performed by the pump. For example, the length of the beep signal when the pump changes to infusion mode is different from that generated when it changes to bolus dose administration mode. Reading and processing this signal by the PCB allows the identification and confirmation of the action performed by the pump at any time.</para>
<para>As it has been already explained, the aim of REMPARK was not to include experience with patients around this implementation of an automatic control loop including the apomorphine pump, but just to demonstrate the technical viability and its feasibility.</para>
<para>The inclusion of a wirelessly controlled infusion pump in the REMPARK system would facilitate some future scenarios:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>If on-line symptoms recognition is done correctly, it opens the door to a better administration of the medication doses, since dosages would be automatically adapted to the immediate needs of patients.</para></listitem>
<listitem>
<para>Usually the practitioner has difficulties for adjusting a suitable dose for the pump&#x02019;s continuous mode, and also to control extra doses administered by the pump. REMPARK can help the professionals to properly assess the number of OFF hours that a given patient has experienced with the aim of judging the effect of the pump therapy through an objective information.</para></listitem>
<listitem>
<para>Usability from the patient&#x02019;s point of view. Some patients with Parkinson&#x02019;s have OFF phases so severe that they cannot even self-administrate extra doses. Patients with severe OFFs, which have no caregivers who can perform this task for them, often cannot choose the treatment with continuous infusion pumps. REMPARK could contribute to improve the quality of life of these patients.</para></listitem>
</itemizedlist>
</section>
<section class="lev1" id="sec7-7" label="7.7" xreflabel="7.7">
<title>Conclusion</title>
<para>Current chapter has presented the REMPARK activity on PD actuation as a possible improvement for a more effective management of the disease symptoms.</para>
<para>Auditory Cueing strategy is already a well-known solution for the improvement and facilitation of a better gait of people with Parkinson&#x02019;s when invalidating symptoms appear. REMPARK tries to improve this technique with some new characteristics and possibilities derived from an effective detection of symptoms on-line during the normal activities of the patients.</para>
<para>In a more speculative scenario, REMPARK has demonstrated the technical viability and the feasibility of an electronic control to be added to an infusion pump of apomorphine, allowing in the future, an automatic delivery of the drug depending on the patient specific needs.</para>
</section>
<section class="lev1" id="sec7-8">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>M. E. Morris, F. Huxham, J. McGinley, K. Dodd e R. Iansek, &#x0201C;The biomechanics and motor control of gait in Parkinson disease,&#x0201D; <emphasis>Clinical biomechanics,</emphasis> vol. 16, no. 6, pp. 459&#x02013;470, July 2001. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+E%2E+Morris%2C+F%2E+Huxham%2C+J%2E+McGinley%2C+K%2E+Dodd+e+R%2E+Iansek%2C+%22The+biomechanics+and+motor+control+of+gait+in+Parkinson+disease%2C%22+Clinical+biomechanics%2C+vol%2E+16%2C+no%2E+6%2C+pp%2E+459-470%2C+July+2001%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. B&#x00E4;chlin, M. Plotnik, D. Roggen, N. Giladi, J. M. Hausdorff e G. Tr&#x00F6;ster, &#x0201C;A wearable system to assist walking of Parkinson&#x02019;s disease patients,&#x0201D; <emphasis>Methods of information in medicine,</emphasis> vol. 49, no. 1, pp. 88&#x02013;95, January 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+B%E4chlin%2C+M%2E+Plotnik%2C+D%2E+Roggen%2C+N%2E+Giladi%2C+J%2E+M%2E+Hausdorff+e+G%2E+Tr%F6ster%2C+%22A+wearable+system+to+assist+walking+of+Parkinson%27s+disease+patients%2C%22+Methods+of+information+in+medicine%2C+vol%2E+49%2C+no%2E+1%2C+pp%2E+88-95%2C+January+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. M. Hausdorff, &#x0201C;Gait dynamics in Parkinson&#x02019;s disease: common and distinct behavior among stride length, gait variability, and fractal-like scaling,&#x0201D; <emphasis>Chaos (Woodbury, N.Y.),</emphasis> vol. 19, no. 2, pp. 1&#x02013;14, June 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+M%2E+Hausdorff%2C+%22Gait+dynamics+in+Parkinson%27s+disease%3A+common+and+distinct+behavior+among+stride+length%2C+gait+variability%2C+and+fractal-like+scaling%2C%22+Chaos+%28Woodbury%2C+N%2EY%2E%29%2C+vol%2E+19%2C+no%2E+2%2C+pp%2E+1-14%2C+June+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. F. del Olmo e J. Cudeiro, &#x0201C;Temporal variability of gait in Parkinson disease: effects of a rehabilitation programme based on rhythmic sound cues,&#x0201D; <emphasis>Parkinsonism &#x00026; related disorders,</emphasis> vol. 11, no. 1, pp. 25&#x02013;33, January 2005. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+F%2E+del+Olmo+e+J%2E+Cudeiro%2C+%22Temporal+variability+of+gait+in+Parkinson+disease%3A+effects+of+a+rehabilitation+programme+based+on+rhythmic+sound+cues%2C%22+Parkinsonism+%26+related+disorders%2C+vol%2E+11%2C+no%2E+1%2C+pp%2E+25-33%2C+January+2005%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>N. Giladi, H. Shabtai, E. Rozenberg e E. Shabtai, &#x0201C;Gait festination in Parkinson&#x02019;s disease,&#x0201D; <emphasis>Parkinsonism &#x00026; Related Disorders,</emphasis> vol. 7, pp. 135&#x02013;138, 2001. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=N%2E+Giladi%2C+H%2E+Shabtai%2C+E%2E+Rozenberg+e+E%2E+Shabtai%2C+%22Gait+festination+in+Parkinson%27s+disease%2C%22+Parkinsonism+%26+Related+Disorders%2C+vol%2E+7%2C+pp%2E+135-138%2C+2001%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. Rodger, W. Young e C. Craig, &#x0201C;Synthesis of Walking Sounds for Alleviating Gait Disturbances in Parkinson&#x02019;s Disease,&#x0201D; <emphasis>IEEE Transactions on Neural Systems and Rehabilitation Engineering,</emphasis> vol. 22, no. 3, pp. 543&#x02013;548, May 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+Rodger%2C+W%2E+Young+e+C%2E+Craig%2C+%22Synthesis+of+Walking+Sounds+for+Alleviating+Gait+Disturbances+in+Parkinson%27s+Disease%2C%22+IEEE+Transactions+on+Neural+Systems+and+Rehabilitation+Engineering%2C+vol%2E+22%2C+no%2E+3%2C+pp%2E+543-548%2C+May+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. P. Ford, L. A. Malone, I. Nyikos, R. Yelisetty e C. S. Bickel, &#x0201C;Gait Training With Progressive External Auditory Cueing in Persons With Parkinson&#x02019;s Disease,&#x0201D; <emphasis>Archieves of Physical Medicine and Rehabilitation,</emphasis> vol. 91, no. 8, pp. 1254&#x02013;1261, August 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+P%2E+Ford%2C+L%2E+A%2E+Malone%2C+I%2E+Nyikos%2C+R%2E+Yelisetty+e+C%2E+S%2E+Bickel%2C+%22Gait+Training+With+Progressive+External+Auditory+Cueing+in+Persons+With+Parkinson%27s+Disease%2C%22+Archieves+of+Physical+Medicine+and+Rehabilitation%2C+vol%2E+91%2C+no%2E+8%2C+pp%2E+1254-1261%2C+August+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. Picelli, M. Camin, M. Tinazzi, A. Vangelista, A. Cosentino, A. Fiaschi e N. Smania, &#x0201C;Three-dimensional motion analysis of the effects of auditory cueing on gait pattern in patients with Parkinson&#x02019;s disease: a preliminary investigation,&#x0201D; <emphasis>Neurological sciences,</emphasis> vol. 31, no. 4, pp. 423&#x02013;430, August 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+Picelli%2C+M%2E+Camin%2C+M%2E+Tinazzi%2C+A%2E+Vangelista%2C+A%2E+Cosentino%2C+A%2E+Fiaschi+e+N%2E+Smania%2C+%22Three-dimensional+motion+analysis+of+the+effects+of+auditory+cueing+on+gait+pattern+in+patients+with+Parkinson%27s+disease%3A+a+preliminary+investigation%2C%22+Neurological+sciences%2C+vol%2E+31%2C+no%2E+4%2C+pp%2E+423-430%2C+August+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>K. Baker, L. Rochester e A. Nieuwboer, &#x0201C;The effect of cues on gait variability &#x02013; reducing the attentional cost of walking in people with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Parkinsonism &#x00026; related disorders,</emphasis> vol. 14, no. 4, pp. 314&#x02013;320, January 2008. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=K%2E+Baker%2C+L%2E+Rochester+e+A%2E+Nieuwboer%2C+%22The+effect+of+cues+on+gait+variability+-+reducing+the+attentional+cost+of+walking+in+people+with+Parkinson%27s+disease%2C%22+Parkinsonism+%26+related+disorders%2C+vol%2E+14%2C+no%2E+4%2C+pp%2E+314-320%2C+January+2008%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. Suteerawattananon, G. S. Morris, B. R. Etnyre, J. Jankovic e E. J. Protas, &#x0201C;Effects of visual and auditory cues on gait in individuals with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Journal of the Neurological Sciences,</emphasis> vol. 219, no. 1&#x02013;2, pp. 63&#x02013;69, April 2004. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+Suteerawattananon%2C+G%2E+S%2E+Morris%2C+B%2E+R%2E+Etnyre%2C+J%2E+Jankovic+e+E%2E+J%2E+Protas%2C+%22Effects+of+visual+and+auditory+cues+on+gait+in+individuals+with+Parkinson%27s+disease%2C%22+Journal+of+the+Neurological+Sciences%2C+vol%2E+219%2C+no%2E+1-2%2C+pp%2E+63-69%2C+April+2004%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>W. Nanhoe-Mahabier, A. Delval, A. H. Snijders, V. Weerdesteyn, S. Overeem e B. R. Bloem, &#x0201C;The possible price of auditory cueing: Influence on obstacle avoidance in Parkinson&#x02019;s disease.,&#x0201D; <emphasis>Movement disorders,</emphasis> vol. 0, no. 0, pp. 1&#x02013;5, February 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=W%2E+Nanhoe-Mahabier%2C+A%2E+Delval%2C+A%2E+H%2E+Snijders%2C+V%2E+Weerdesteyn%2C+S%2E+Overeem+e+B%2E+R%2E+Bloem%2C+%22The+possible+price+of+auditory+cueing%3A+Influence+on+obstacle+avoidance+in+Parkinson%27s+disease%2E%2C%22+Movement+disorders%2C+vol%2E+0%2C+no%2E+0%2C+pp%2E+1-5%2C+February+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>S. Ledger, R. Galvin, D. Lynch e E. K. Stokes, &#x0201C;A randomised controlled trial evaluating the effect of an individual auditory cueing device on freezing and gait speed in people with Parkinson&#x02019;s disease,&#x0201D; <emphasis>BMC neurology,</emphasis> vol. 8, no. 46, January 2008. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=S%2E+Ledger%2C+R%2E+Galvin%2C+D%2E+Lynch+e+E%2E+K%2E+Stokes%2C+%22A+randomised+controlled+trial+evaluating+the+effect+of+an+individual+auditory+cueing+device+on+freezing+and+gait+speed+in+people+with+Parkinson%27s+disease%2C%22+BMC+neurology%2C+vol%2E+8%2C+no%2E+46%2C+January+2008%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>T. Howe, B. Lovgreen, F. Cody, V. Ashton e J. Oldham, &#x0201C;Auditory cues can modify the gait of persons with early-stage Parkinson&#x02019;s disease: a method for enhancing parkinsonian walking performance?,&#x0201D; <emphasis>Clinical Rehabilitation,</emphasis> vol. 17, no. 4, pp. 363&#x02013;367, July 2003. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=T%2E+Howe%2C+B%2E+Lovgreen%2C+F%2E+Cody%2C+V%2E+Ashton+e+J%2E+Oldham%2C+%22Auditory+cues+can+modify+the+gait+of+persons+with+early-stage+Parkinson%27s+disease%3A+a+method+for+enhancing+parkinsonian+walking+performance%B4%2C%22+Clinical+Rehabilitation%2C+vol%2E+17%2C+no%2E+4%2C+pp%2E+363-367%2C+July+2003%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. Spildooren, S. Vercruysse, P. Meyns, J. Vandenbossche, E. Heremans, K. Desloovere, W. Vandenberche e A. Nieuwboer, &#x0201C;Turning and Unilateral Cueing in Parkinson&#x02019;s Disease Patients with and without Freezing of Gait,&#x0201D; <emphasis>Neuroscience,</emphasis> vol. 207, pp. 298&#x02013;306, 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+Spildooren%2C+S%2E+Vercruysse%2C+P%2E+Meyns%2C+J%2E+Vandenbossche%2C+E%2E+Heremans%2C+K%2E+Desloovere%2C+W%2E+Vandenberche+e+A%2E+Nieuwboer%2C+%22Turning+and+Unilateral+Cueing+in+Parkinson%27s+Disease+Patients+with+and+without+Freezing+of+Gait%2C%22+Neuroscience%2C+vol%2E+207%2C+pp%2E+298-306%2C+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Z. Kadivar, D. Corcos, J. Foto e J. Hondzinski, &#x0201C;Effect of step training and rhythmic auditory stimulation on functional performance in Parkinson patients.,&#x0201D; <emphasis>Neurorehabilitation and Neural repair.,</emphasis> vol. 25, no. 2, pp. 626&#x02013;635, 2011. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Z%2E+Kadivar%2C+D%2E+Corcos%2C+J%2E+Foto+e+J%2E+Hondzinski%2C+%22Effect+of+step+training+and+rhythmic+auditory+stimulation+on+functional+performance+in+Parkinson+patients%2E%2C%22+Neurorehabilitation+and+Neural+repair%2E%2C+vol%2E+25%2C+no%2E+2%2C+pp%2E+626-635%2C+2011%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>R. Velik, &#x0201C;Effect of On-Demand Cueing on Freezing of Gait in Parkinson&#x02019;s Patients,&#x0201D; <emphasis>International Journal of Medical, Health, Pharmaceutical and Biomedical Engineering,</emphasis> vol. 6, no. 6, pp. 8&#x02013;13, 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=R%2E+Velik%2C+%22Effect+of+On-Demand+Cueing+on+Freezing+of+Gait+in+Parkinson%27s+Patients%2C%22+International+Journal+of+Medical%2C+Health%2C+Pharmaceutical+and+Biomedical+Engineering%2C+vol%2E+6%2C+no%2E+6%2C+pp%2E+8-13%2C+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>C.-E. Benoit, S. D. Bella, N. Farrugia, S. Mainka e S. Kotz, &#x0201C;Musically cued gait-training improves both perceptual and motor timing in Parkinson&#x02019;s Disease,&#x0201D; <emphasis>Frontiers in Human Neuroscience,</emphasis> vol. 8, July 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=C%2E-E%2E+Benoit%2C+S%2E+D%2E+Bella%2C+N%2E+Farrugia%2C+S%2E+Mainka+e+S%2E+Kotz%2C+%22Musically+cued+gait-training+improves+both+perceptual+and+motor+timing+in+Parkinson%27s+Disease%2C%22+Frontiers+in+Human+Neuroscience%2C+vol%2E+8%2C+July+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>R. Velik, U. Hoffmann, H. Zabaleta, J. F. M. Mass&#x00F3; e T. Keller, &#x0201C;The effect of visual cues on the number and duration of freezing episodes in Parkinson&#x02019;s patients,&#x0201D; <emphasis>Proceeding of the 34th Annual International Conference on Engineering in Medicine and Biology Society,</emphasis> 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=R%2E+Velik%2C+U%2E+Hoffmann%2C+H%2E+Zabaleta%2C+J%2E+F%2E+M%2E+Mass%F3+e+T%2E+Keller%2C+%22The+effect+of+visual+cues+on+the+number+and+duration+of+freezing+episodes+in+Parkinson%27s+patients%2C%22+Proceeding+of+the+34th+Annual+International+Conference+on+Engineering+in+Medicine+and+Biology+Society%2C+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. Forsberg, &#x0201C;A mobile application for improving running performance using interactive sonification,&#x0201D; Stockholm, Sweden, 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+Forsberg%2C+%22A+mobile+application+for+improving+running+performance+using+interactive+sonification%2C%22+Stockholm%2C+Sweden%2C+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>E. van Wegen, C. Goede, I. Lim, M. Rietberg, A. Nieuwboer, A. Willems, D. Jones, L. Rochester, V. Hetherington, H. Berendse, J. Zijlmans, E. Wolters e G. Kwakkel, &#x0201C;The effect of rhythmic somatosensory cueing on gait in patients with Parkinson&#x02019;s disease,&#x0201D; <emphasis>Journal of the Neurological Sciences,</emphasis> vol. 248, no. 1&#x02013;2, pp. 210&#x02013;214, October 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=E%2E+van+Wegen%2C+C%2E+Goede%2C+I%2E+Lim%2C+M%2E+Rietberg%2C+A%2E+Nieuwboer%2C+A%2E+Willems%2C+D%2E+Jones%2C+L%2E+Rochester%2C+V%2E+Hetherington%2C+H%2E+Berendse%2C+J%2E+Zijlmans%2C+E%2E+Wolters+e+G%2E+Kwakkel%2C+%22The+effect+of+rhythmic+somatosensory+cueing+on+gait+in+patients+with+Parkinson%27s+disease%2C%22+Journal+of+the+Neurological+Sciences%2C+vol%2E+248%2C+no%2E+1-2%2C+pp%2E+210-214%2C+October+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>R. F. Pfeiffer, Z. K. Wszolek e M. Ebadi, Parkinson&#x02019;s Disease, 2nd ed., T. &#x00026;. F. Group, Ed., CRC Press, 2013.</para></listitem>
<listitem>
<para>J. E. Wittwer, K. E. Webster e K. Hill, &#x0201C;Music and metronome cues produce different effects on gait spatiotemporal measures but not gait variability in healthy older adults,&#x0201D; <emphasis>Gait and Posture,</emphasis> vol. 37, no. 2, pp. 219&#x02013;222, February 2013. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+E%2E+Wittwer%2C+K%2E+E%2E+Webster+e+K%2E+Hill%2C+%22Music+and+metronome+cues+produce+different+effects+on+gait+spatiotemporal+measures+but+not+gait+variability+in+healthy+older+adults%2C%22+Gait+and+Posture%2C+vol%2E+37%2C+no%2E+2%2C+pp%2E+219-222%2C+February+2013%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>C. Pongmala, A. Suputtitada e M. Sriyuthsak, &#x0201C;The study of cueing devices by using visual, auditory and somatosensory stimuli for improving gait in Parkinson patients,&#x0201D; <emphasis>2010 International Conference on Bioinformatics and Biomedical Technology (ICBBT),</emphasis> pp. 185&#x02013;189, 2010. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=C%2E+Pongmala%2C+A%2E+Suputtitada+e+M%2E+Sriyuthsak%2C+%22The+study+of+cueing+devices+by+using+visual%2C+auditory+and+somatosensory+stimuli+for+improving+gait+in+Parkinson+patients%2C%22+2010+International+Conference+on+Bioinformatics+and+Biomedical+Technology+%28ICBBT%29%2C+pp%2E+185-189%2C+2010%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. Defranco, &#x0201C;Parkinson&#x02019;s Tips for Freezing of Gait from our Physical Therapist,&#x0201D; Center for Movement Disorders and Neurorestoration, 23 November 2011. [Online]. Available: http://movementdisorders.ufhea lth.org/2011/11/23/physical-therapy-tips-for-freezing-of-gait/. [Acedido em September 2016].</para></listitem>
<listitem>
<para>G. Lyons, T. Sinkjaer, J. Burridge e D. Wilcox, &#x0201C;A Review of Portable FES-Based Neural Orthoses for the Correction of Drop Foot,&#x0201D; <emphasis>IEEE Transactions on Neural Systems and Rehabilitation Engineering,</emphasis> vol. 10, no. 4, pp. 260&#x02013;279, 2002. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=G%2E+Lyons%2C+T%2E+Sinkjaer%2C+J%2E+Burridge+e+D%2E+Wilcox%2C+%22A+Review+of+Portable+FES-Based+Neural+Orthoses+for+the+Correction+of+Drop+Foot%2C%22+IEEE+Transactions+on+Neural+Systems+and+Rehabilitation+Engineering%2C+vol%2E+10%2C+no%2E+4%2C+pp%2E+260-279%2C+2002%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>E. Wang, L. Metman e E. Jovanov, &#x0201C;Method and device to manage freezing of gait in patients suffering from a movement disorder&#x0201D;. Patente US 8409116 B2, 2 Abr 2013. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=E%2E+Wang%2C+L%2E+Metman+e+E%2E+Jovanov%2C+%22Method+and+device+to+manage+freezing+of+gait+in+patients+suffering+from+a+movement+disorder%22%2E+Patente+US+8409116+B2%2C+2+Abr+2013%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. Whitall, S. Mccombe-Walker e M. Anjanappa, &#x0201C;Step trainer for enhanced performance using rhythmic cues&#x0201D;. Patente EP 2346580 A2, 27 Jul 2011. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+Whitall%2C+S%2E+Mccombe-Walker+e+M%2E+Anjanappa%2C+%22Step+trainer+for+enhanced+performance+using+rhythmic+cues%22%2E+Patente+EP+2346580+A2%2C+27+Jul+2011%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>P. LoSasso, &#x0201C;Accessory for a walker to improve gait performance&#x0201D;. Patente US 8961186 B2, 24 Fev 2015. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=P%2E+LoSasso%2C+%22Accessory+for+a+walker+to+improve+gait+performance%22%2E+Patente+US+8961186+B2%2C+24+Fev+2015%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>D. Polley e K. Hancock, &#x0201C;Auditory stimulus for auditory rehabilitation&#x0201D;. Patente WO 2012177976 A2, 27 Dez 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+Polley+e+K%2E+Hancock%2C+%22Auditory+stimulus+for+auditory+rehabilitation%22%2E+Patente+WO+2012177976+A2%2C+27+Dez+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>A. Sam&#x00E0;, C. P&#x00E9;rez-L&#x00F3;pez, D. Rodr&#x00ED;guez-Mart&#x00ED;n, J. M. Moreno-Ar&#x00F3;stegui, J. Rovira, C. Ahlrichs, R. Castro, J. Cevada, R. Gra&#x00E7;a, V. Guimar&#x00E3;es, B. Pina, T. Counihan, H. Lewy, R. Annicchiarico, &#x00C0;. Bay&#x00E9;s, A. Rodr&#x00ED;guez-Molinero e J. Cabestany, &#x0201C;A double closed loop to enhance the quality of life of Parkinson&#x02019;s Disease patients: REMPARK system,&#x0201D; <emphasis>Innovation in Medicine and Healthcare,</emphasis> pp. 115&#x02013;123, 2014.</para></listitem>
<listitem>
<para>V. Guimar&#x00E3;es, R. Castro, A. Barros, J. Cevada, &#x00C0;. Bay&#x00E9;s, S. Garc&#x00ED;a e B. Mestre, &#x0201C;Development of an Auditory Cueing System to Assist Gait in Patients with Parkinson&#x02019;s Disease,&#x0201D; <emphasis>Bioinformatics and Biomedical Engineering, Lecture Notes in Computer Science,</emphasis> vol. 9044, pp. 93&#x02013;104, 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;as_sdt=0,5&amp;q=V.+Guimaraes,+DE.+Castro,+A.+Barros,+J.+Cevada,+%3F.+Bay%3Fs,+S.+Garc%3Fa+e+B.+Mestre,+%22Development+of+an+Auditory+Cueing+System+to+Assist+Gait+in+Patients+with+Parkinson%27s+Disease,%22+Bioinformatics+and+Biomedical+Engineering,+Lecture+Notes+in+Computer+Science,+vo" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para><ulink url="http://medigait.com/">http://medigait.com/</ulink> [Accessed on April 15, 2015].</para></listitem>
<listitem>
<para>S. Zhu, R. Ellis, G. Schlaug, Y. Sien Ng e Y. Wang, &#x0201C;Validating an iOS-based Rhythmic Auditory Cueing Evaluation (iRACE) for Parkinson&#x02019;s Disease&#x0201D;, MM&#x02019;14. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=S%2E+Zhu%2C+R%2E+Ellis%2C+G%2E+Schlaug%2C+Y%2E+Sien+Ng+e+Y%2E+Wang%2C+%22Validating+an+iOS-based+Rhythmic+Auditory+Cueing+Evaluation+%28iRACE%29+for+Parkinson%27s+Disease%22%2C+MM%2714%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>S. Mazilu, U. Blanke, M. Hardegger, G. Tr&#x00F6;ster, E. Gazit e J. M. Hausdorffe, &#x0201C;GaitAssist: A Daily-Life Support and Training System for Parkinson&#x02019;s Disease Patients with Freezing of Gait&#x0201D;, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, pp. 2531&#x02013;2540, 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=S%2E+Mazilu%2C+U%2E+Blanke%2C+M%2E+Hardegger%2C+G%2E+Tr%F6ster%2C+E%2E+Gazit+e+J%2E+M%2E+Hausdorffe%2C+%22GaitAssist%3A+A+Daily-Life+Support+and+Training+System+for+Parkinson%27s+Disease+Patients+with+Freezing+of+Gait%22%2C+Proceedings+of+the+SIGCHI+Conference+on+Human+Factors+in+Computing+Systems%2C+pp%2E+2531-2540%2C+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para><ulink url="http://cupid-project.eu/project">http://cupid-project.eu/project</ulink> [Accessed on April 15, 2015].</para></listitem>
<listitem>
<para><ulink url="http://rescueprojects.org/">http://rescueprojects.org/</ulink> [Accessed on April 15, 2015].</para></listitem>
<listitem>
<para>CAN&#x00C8; S.p.A. Medical Technology. Microjet CRONO PAR Manuel d&#x02019;Instruction. MAN 01/F/04 PARII 09/09. Retrieved from <ulink url="http://www.canespa.it">http://www.canespa.it</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch08" label="8" xreflabel="8">
<title>Disease Management System (DMS)</title>
<para role="author"><emphasis role="strong">Hadas Lewy</emphasis></para>
<para>Maccabi Healthcare Services, Tel-Aviv, Israel</para>
<section class="lev1" id="sec8-1" label="8.1" xreflabel="8.1">
<title>Introduction</title>
<para>Parkinson&#x02019;s Disease is a chronic and progressive neurodegenerative disorder with a great number of motor and non-motor symptoms [2, 4, 5, 7]. The cardinal symptoms are bradykinesia, rigidity, tremor and postural instability [1, 3, 8]. However, a number of non-motor-related symptoms (e.g., sleep disturbances, depression, psychosis, autonomic and gastrointestinal dysfunction as well as dementia) may occur [3&#x02013;7].</para>
<para>The disease is a great burden as it has a negative incidence on the quality of life, due to a gradual loss of functionality and decreasing ability to take care of oneself. For these reasons, the caring process changes along disease progressions and involves many healthcare professionals. Usually, these professionals are located in different care services and organizations (hospitals and the community), and they cover a wide range of medical care including physicians, nurses, physiotherapists, nutritionists, occupational therapists and social workers. In addition, there is a need to support the family and reduce the informal caregiver burden by providing services, information and knowledge about the treatment.</para>
<para>To cope with the challenging care model of PD patients, the REMPARK project contributes to the development of a Personalized Health System (PHS) with detection, response and treatment capabilities for the remote management of the disease permitting, also, the integration of the generated data with the patient&#x02019;s EHR (Electronic Health Record) and the integration and support of a Disease Management System (DMS), that enable the medical team to provide integrated care and support to the patient and his family.</para>
<para>One of the main problems in most existing systems for disease management is that the data used for treatment is collected on the system overtime and is not updated by other systems that are used for treating the patient. For example, if the patient is treated by the neurologist for the PD and in parallel he is treated by the general physician in the community for other health conditions. Usually, no Integration between data is made and there is a lack of information about the overall condition of the patient. Furthermore, there is no communication between the healthcare professionals treating the patient.</para>
<para>This way of delivering care results in a fragmentation, slight duplication and lack of coordination. The DMS creates an integrated environment for data and knowledge sharing for all care providers without a need to access different organizational systems by users from different organizations and thus overcomes the privacy and security barriers. The DMS also includes clinical guidelines and a decision support tool for healthcare providers that allow the clinical team to obtain accurate and reliable information and to decide about the treatment that best suits the patient for improvement of the disease management.</para>
<para>This tool enables treating several conditions at the same time in a coordinated way; therefore, the organization can use several experts to treat a patient (e.g. psychiatrists, urologists or neurologists) and enable integrated care between different organizations (e.g. hospital community care and welfare) which provides flexibility and efficiency treating a patient with changing conditions, without breaching security constraints of the organization.</para>
<para>For the patient, there is a portal in which he is able to communicate with the professionals (doctor, nurse...) and obtain information about his condition and treatment plan. The DMS communicates with the patient&#x02019;s interface that can be reached by a home computer, a tablet or a Smartphone, it updates the data and collects inputs from the patients, such as self-reported questionnaires, for the evaluation and decision making by the healthcare professionals. These tools give useful information to the patients and empower them for better self-management.</para>
<para>The system also has an interface for healthcare organizations to enable management of the treating teams such as shifts and workload at the call centre, and reports for the management teams.</para>
<para>This chapter describes the use of the implementations of a DMS within the REMPARK system, its ability to communicate with REMPARK sensors, intelligent layer and actuators and reviews the advantages that the DMS brings to all users involved in the system from a clinical, personal (patient), organizational and healthcare points of view. At the end of the chapter, the conclusions from using the system and the vision for its contribution of the future treatment of PD patient are described, as well as for elderly people with co-morbidities in a changing era of care models moving from reactive to proactive treatment, empowering the patient and creating new services and relationship between the patient and the healthcare providers.</para>
</section>
<section class="lev1" id="sec8-2" label="8.2" xreflabel="8.2">
<title>Disease Management System Application</title>
<para>Providing integrated care and remotely treating large populations creates a challenge for the care providers at the clinical and organizational level. Although the data provided by the sensors and analytical tools are valuable and the REMPARK system paves the way for its clinical use in the future for the automatic control of continuous infusion pumps, automatic management of external cues to guide the gait or for comprehensive and reliable analysis of changes in motor state, still the use of this type of data in clinical practice is not implemented. Clinical guidelines for remote monitoring, standardization of care and risk management of the remote monitoring and care is still not well-established and requires development of supportive tools as well as methodological approaches.</para>
<para>The progression of the disease is individual and cannot be predicted, and the patient and their family need support at different levels and by multiple caregivers at different stages of the disease. Since the disease is usually related to elderly people, the associated symptoms may be mistakenly treated as geriatric symptoms and there is a need to diagnose the source of the symptom and provide the personalized treatment considering the overall condition of the patient. The services provided for comprehensive treatment are often provided by different organizations located in the hospital, community service and home care. Therefore, the treatment can be complex and involves several stakeholders.</para>
<para>For these reasons, healthcare system and the industry are interested in the implementation of technologies for remote care in healthcare. For healthcare system, the main challenge is to enable the use of these technologies by changing the model of care and sharing information. Implementation of these technologies requires collaboration of the healthcare professionals and patients not just in adoption but also in the process of development and implementation in new best practice and care pathways and open the way for sharing information from the patient (self-reported) and other sources (different organizations), capturing and analysing patient data from dispersed systems.</para>
<para>For the industry, the challenge is to provide solutions that will support healthcare systems considering constrains of standardization, privacy, reliability, security, existing models of care including healthcare professional workloads and workflows and adapt the solutions to the system [9]. With these challenges in mind, it was proposed and developed the REMPARK system composed of wearable sensors, analytical layer, decision support tool and a care platform (DMS) for professional care providers, patients and family.</para>
<para>The DMS system provides various functionalities that <emphasis role="strong">support the care</emphasis> by healthcare professionals and communicate with the patient. It is also adaptable to the <emphasis role="strong">organizational care pathways</emphasis> and <emphasis role="strong">workflows</emphasis> and flexible to different clinical guidelines that are used in different countries and/or can be developed overtime. It enables to treat the PD patient in a way that changes along the development of the disease and consider co-morbidities, motor and non-motor symptoms. In addition to the workflow and/process support, the system provides the organization tools for <emphasis role="strong">risk management</emphasis>, <emphasis role="strong">standardization</emphasis> and <emphasis role="strong">data reports</emphasis> that enable a better understanding, control and ways to manage the treating teams.</para>
<para>The care models are moving from <emphasis role="strong">reactive</emphasis> to <emphasis role="strong">proactive approach</emphasis>. The treatment of PD patient involves both approaches since it combines monitoring of motor symptoms, alerting and responding, as well as overall preventive assessment and on-going treatment in a proactive way. The REMPARK system receives data transmitted from the sensors. For each patient, there is a defined range of normal and abnormal values in each monitored parameter. Any deviation from normal event creates an alert on the system and consequently there is a reactive intervention. The <emphasis role="strong">alerts</emphasis> can be set not only for a single event but also for a set of events overtimes. For example, a fall requires immediate response therefore a single event will create an alert. However, for the neurologist it is important to know if the drug treatment is effective; therefore, parameters such as number of dyskinesia events or FoG events in the last week will be important and indicative for the treatment. In this sense, it is possible to set an alert whenever a set of accumulative events in a defined period occurs and to present it to the neurologist.</para>
<para>In addition, each patient has a <emphasis role="strong">personalized treatment plan</emphasis> defined by the doctor that is monitored by the nurse in the centre, who has a concrete list of <emphasis role="strong">tasks</emphasis> to handle. The tasks will be generated automatically from the patient&#x02019;s treatment plan or by the doctor/coordinator of the team. This way the patient is also being treated in a proactive way by the nurse or other care team members. The nurse can also see the condition of the patient in the last week at a glance or enter his record. The proactive treatment is driven by the treatment plan that is observed and followed by all care team members. This allows an <emphasis role="strong">integrated care</emphasis>, team discussion and coordination in providing comprehensive care. The platform has, also, the ability to communicate between care team through messaging tool or video call.</para>
<para>For each patient, participating in the REMPARK pilots, according to the patient&#x02019;s evaluation and clinical history, medications and definition of normal ranges for every measurement, the medical team can add and update the treatment plan according to changes in condition of the patient. A change in the treatment plan can be as a result of changes in the patient&#x02019;s health state or patient&#x02019;s environment. Some items create a task for a specific medical team member according to his profession while all team members can be updated in the status and given treatment.</para>
<para>The strength of the system also relies on the ability to obtain, analyse and <emphasis role="strong">integrate data from different sources</emphasis>: sensors, patient reported data and EHR. Wearable sensors provide data monitoring of clinical data about PD patients motor condition but also behavioral data such as activity levels, type of activities and social activity. The development of these technologies that monitor different data types to yield additional information about wide range of parameters and activities including behavioral, mental and clinical data that are transmitted in order to assist the treatment process, opens new opportunities for care providers but also requires integration of care models.</para>
<para>The data can be further analyzed for risk assessment of stratification for timely intervention. In these cases, data entered by the patient regarding his condition is pre-defined by the care provider and used as part of the treatment and for further assessment of the patient&#x02019;s condition [10, 11]. However, today the data collected for chronic conditions and specifically <emphasis role="strong">patient reported data</emphasis> in different care programs is partially used in care and are usually not treated by physicians as clinical data in the <emphasis role="strong">EHR</emphasis> as part of the clinical process. (see <link linkend="F8-1">Figure <xref linkend="F8-1" remap="8.1"/></link> for a shot view of a screen showing patients&#x02019; data. Consider that data are not real).</para>
<fig id="F8-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-1">Figure <xref linkend="F8-1" remap="8.1"/></link></label>
<caption><para>View of data on a patient from a list. (All appearing data are not real).</para></caption>
<graphic xlink:href="graphics/ch08_fig001.jpg"/>
</fig>
<para>The challenge of healthcare system will be to use these data providing additional information to that existing in the EHR. The REMPARK system provides a tool for implementation of this approach by using the integrated care platform to combine heterogeneous data from EHR, <emphasis role="strong">sensors</emphasis>, <emphasis role="strong">analytical tools</emphasis> and patients&#x02019; self-reported data for <emphasis role="strong">comprehensive care</emphasis> of multidisciplinary teams. Furthermore, the data are continuously updated from the different sources and do not require manual update enabling all stakeholders to continue using their organizational systems without duplication of work and bringing added value to the treatment process using intelligent tools on top of their existing system. The interaction between the patient and the healthcare professionals will be enabled through the DMS platform as a result of alerts and/or treatment plan, since the nurse will be able to call the patient or message him.</para>
<para>All correspondence is registered on the system for follow-up and <emphasis role="strong">risk management</emphasis>. One of the useful tools presented in REMPARK system is the <emphasis role="strong">clinical protocols</emphasis> tool. A clinical protocol is a document with the aim of guiding decisions and criteria regarding diagnosis, management and treatment of PD. It is a set of steps allowing the medical team to make decisions according to the collected information. It is actually a set of medical instructions for every situation according to the patient&#x02019;s medical state.</para>
<para>These protocols can be easily updated or changed from time to time by the care provider according to the medical considerations or according to organizational procedures. The protocols can guide the medical team how to treat the patient and co-morbidities. For this purpose, the clinical team of REMPARK project developed a set of clinical protocols based on the best practices for the treatment of PD patients. In addition, protocol for other chronic diseases or geriatric conditions exist in the system and enable the medical team to identify the clinical situation. The protocols are adapted to the user (e.g. healthcare organization) and can be generated for doctors, nurses or/and caregivers. By using the protocols the medical team will provide a standardized treatment that is in accordance with clinical guidelines (see <link linkend="F8-2">Figure <xref linkend="F8-2" remap="8.2"/></link>).</para>
<fig id="F8-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-2">Figure <xref linkend="F8-2" remap="8.2"/></link></label>
<caption><para>Protocol screen capture for apomorphine pump alert.</para></caption>
<graphic xlink:href="graphics/ch08_fig002.jpg"/>
</fig>
<para>The protocol is loaded automatically in case of treating a task or an alert. The clinical protocol automatically guides the medical team user to the next point or stage according to the data, until reaching the final decision or action. Using the clinical protocol the medical team will be able to send instructions to the auditory cueing system as described in the external interfaces or make a decision about any intervention or treatment using future tools that would be connected to the system.</para>
<para>In order to have an overall understanding about the patient&#x02019;s condition the neurologist interviews the patient about their symptoms, frequencies and daily condition. The patient is usually asked to fill a diary; however, the experience shows that these diaries are only partially filled in and the information provided to the neurologist is partial. One of the ways the REMPARK system overcomes this problem relies on the data obtained and analysed by the sensors and presented to the neurologist on the DMS platform. This tool is complemented under some conditions by the use of a questionnaire.</para>
<para>The DMS platform provides a tool of <emphasis role="strong">questionnaires</emphasis> that serves as &#x0201C;<emphasis role="strong">patient reported data sensors</emphasis>&#x0201D;. The questionnaires can be filled by the patient, relative or by a nurse calling the patient in cases the patient is unable to fill the questionnaire. In addition, some of these questionnaires can also be responded through the smartphone, which are also received by the DMS. In either case, the system presents the patient the questionnaire that has to be filled according to the treatment plan. For each questionnaire, there is a logic to calculate a score. The medical team and the patient are able to see all history of previously answered questionnaires.</para>
<para>The questionnaire tool is also combined with the sensors data and can ask the patient additional questions when the sensor data alerts. The information can be viewed along time to show a trend even if no alert was raised. This tool was designed to collect the patient&#x02019;s reported data and use it with clinical logic to create alerts and response by the medical team. It integrates the data with the clinical data in an innovative way that presents the physician the information they need and simplify the analysis of the patient&#x02019;s reported data for use in clinical practice. <link linkend="F8-3">Figure <xref linkend="F8-3" remap="8.3"/></link> shows, as an example, a part of the questionnaires section.</para>
<fig id="F8-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-3">Figure <xref linkend="F8-3" remap="8.3"/></link></label>
<caption><para>Questionnaire&#x02019;s section detail.</para></caption>
<graphic xlink:href="graphics/ch08_fig3.jpg"/>
</fig>
<para>As healthcare moves towards proactive treatment there is a need for changes in relationship between the care provider and the patient. The proactive concept that involve the patients in self-care requires <emphasis role="strong">patient empowerment</emphasis>. The patient becomes an active partner in care and makes his own decisions about his health and disease. In order to do so the patient has to be educated about his disease, aware of the clinical options and learn how to cope with the disease. Patients who participate in their care process, cope better with their disease, live healthier lifestyle, have higher quality of life and better clinical outcomes [9]. For these reasons, the REMPARK system adopted this approach and developed a web portal and smartphone interface for the patient.</para>
<para>Electronic correspondence between the patient and the medical team is bi-directional. The correspondence can be triggered from the patient (using the patient web site or the smartphone) or from the medical team or any DMS user. The patient interface is designed to enable the patient receiving all the information about his condition. They can view all sensor&#x02019;s data, questionnaires and correspondence and perform actions required for the treatment such as filling questionnaires and for correspondence with their carers (healthcare providers). The patient is able to add activities into the treatment plan. The patient&#x02019;s web interface is used, among the above, to communicate with the patient either by global message to every person registered to the REMPARK system or messaging a specific patient/medical team member. This way the message is personalized to a patient or can be addressed to a group of patients with the same clinical condition or need.</para>
<para>An emphasis was made on <emphasis role="strong">patient empowerment</emphasis> and <emphasis role="strong">education</emphasis>. Educational materials are sent to the patient according to their condition, need, and disease progression such as articles regarding PD, new treatments and medications or any links to external internet pages and support groups. <link linkend="F8-4">Figure <xref linkend="F8-4" remap="8.4"/></link> is showing how it looks the patient&#x02019;s interface presenting the personal treatment plan.</para>
<fig id="F8-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-4">Figure <xref linkend="F8-4" remap="8.4"/></link></label>
<caption><para>Treatment Plan. A patient&#x02019;s interface view.</para></caption>
<graphic xlink:href="graphics/ch08_fig4.jpg"/>
</fig>
<para>The REMPARK system provides additional organizational tools for management of the care team. The DMS includes a <emphasis role="strong">shift management</emphasis> module that manage the tasks and users that are at each shift. The shift manager can see the workload and type of activities done in the centre for efficient management of the care process. They can also receive reports about activities done on the system.</para>
<para>The above description of the REMPARK system provides an insight not only to the workflow application but also to the <emphasis role="strong">care approach of REMPARK project</emphasis> for PD patients. The system supports the care approach and enables the care provider to effectively manage the delivery of integrated care. The <emphasis role="strong">uniqueness of REMPARK system</emphasis> is that it includes a wide range of functionalities for delivering comprehensive customizable integrated care by multidisciplinary team, but it also enables the treating physician to maintain a supervision of the patient throughout the journey; from patient disease diagnosis, through treatment plan definition, customizing specific protocols.</para>
<para>Moving from reactive to proactive treatment, involving all care providers, requires a change in interaction and mode of delivery the care under the physician coordination. Here, the care is delivered under his supervision enabling to effectively leverage other providers to pursue a consistent treatment approach and objective. It establishes a way for patient&#x02019;s personalized treatment. The application interfaces with the EHR, and the physician receives on-going alerts, updates and patient&#x02019;s data. The care team operates as a supporting envelope to the physician, and maintain constant touch with the patients according to the treatment plan, protocols and alerts received from the system.</para>
</section>
<section class="lev1" id="sec8-3" label="8.3" xreflabel="8.3">
<title>DMS Functional Organization</title>
<para>For the already presented functionality, the DMS platform will communicate with the mobile gateway in both directions through the REMPARK server. This way, two types of information are distinguished:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Incoming data: contains the patient&#x02019;s parameters as they have been measured by the sensors or/and patient processed information from the Rule Engine. Furthermore, the DMS will get information from the Rule Engine through the REMPARK server too.</para></listitem>
<listitem>
<para>Outgoing data: contains updates for the patient&#x02019;s treatment according to the patient&#x02019;s pump or any other command from the auditory cueing system. These data are sent from the DMS.</para></listitem>
</itemizedlist>
<para>The system architecture allows that all the data are stored at the REMPARK server, so the interaction between the different parts of the system will be with the REMPARK server. <link linkend="F8-5">Figure <xref linkend="F8-5" remap="8.5"/></link> shows the main role that the REMPARK server has in the communications process. This is the only interaction point between the REMPARK&#x02019;s server to the Medical Application &#x02013; DMS system.</para>
<fig id="F8-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-5">Figure <xref linkend="F8-5" remap="8.5"/></link></label>
<caption><para>The server acting as a communication hub interfacing the DMA System.</para></caption>
<graphic xlink:href="graphics/ch08_fig005.jpg"/>
</fig>
<para>In general terms, there are two types of communications: telemonitoring of motor symptoms and another related to patient management issues. These flows were implemented by sending and receiving different services between the server and the DMS system. In case of the tele-monitoring of motor symptoms, the DMS system will receive measures and alerts immediately from the REMPARK server. On the other hand, regarding the patient&#x02019;s management communication, the DMS system will send events regarding the medication, questionnaires and clinical agenda of the patient.</para>
<fig id="F8-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F8-6">Figure <xref linkend="F8-6" remap="8.6"/></link></label>
<caption><para>The Web interface architecture.</para></caption>
<graphic xlink:href="graphics/ch08_fig006a.jpg"/>
</fig>
<para><link linkend="F8-6">Figure <xref linkend="F8-6" remap="8.6"/></link> presents the implemented architecture for the Internet interface, including a web server and a data base server (can be a physical or virtual server).</para>
</section>
<section class="lev1" id="sec8-4" label="8.4" xreflabel="8.4">
<title>Advantages Using the Disease Management System (DMS)</title>
<section class="lev2" id="sec8-4-1" label="8.4.1" xreflabel="8.4.1">
<title>Advantages for the Clinical Team</title>
<para>Nowadays, Healthcare delivery systems face problems such as the prevailing inequities in access to care, resulting from services with availability problems in different geographic areas, socioeconomic and cultural disparities. In addition, the system is usually fragmented and a comprehensive patient-centred care is almost impossible to be delivered with existing systems and care models. Therefore, even if services exist, it is very complicated for the clinician to provide the services to many patients that are not located in the geographical environment and even for these patients, there is a need of coordination between service provider&#x02019;s.</para>
<para>The main health dimensions are described in the SHARE document [14] and they can be listed as:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Physical health measured by self-reports on general health, functional limitations, ADLs, IADLs, diseases symptoms, and health behaviour</para></listitem>
<listitem>
<para>Healthcare use</para></listitem>
<listitem>
<para>Cognitive function test, literacy, numeracy, memory, verbal fluency</para></listitem>
<listitem>
<para>Mental health</para></listitem>
<listitem>
<para>Physical performance measures</para></listitem>
</itemizedlist>
<para>The inefficiencies, limited coordination and integration of complex healthcare systems further complicate the treatment and uneven adherence of patients to evidence-based medicine becomes a major barrier in treatment efficacy.</para>
<para>The care of PD patients is complex and requires a coordinated care team. It is possible to consider two approaches for delivering disease management programs: integrated and non-integrated care. Disease management programs based on the integrated care model with primary care have shown the most valuable and effective care and promising results. An integrated approach requires much deeper involvement from providers, and patients throughout the process and many health plans are starting to use in-house nurses with data analytics [12].</para>
<para>New models of integrated health management address member needs across the organization, offering value and transparency in all member interactions with the health plan. In order to provide such services there is a need in predictive modelling health risk assessment, utilization management and coordination of care. The care delivery model includes capturing and analysing patient data from dispersed systems, involving and engaging all stakeholders, especially primary care providers that are typically left out. An optimal identification and stratification of patient population is, also, derived from data integration and physician engagement challenges.</para>
<para>The REMPARK system supports the referred care approach and enables the clinical team to effectively manage the patient&#x02019;s disease. The advantage is that different healthcare professionals can use the same platform without changing their own system. The data are updated and the workflow is maintained. It serves for Information and knowledge sharing between all caregivers of the patient. The REMPARK system provides the care team a way to overcome the barriers of fragmented care service, overcome organizational and inter-organizational limitations and focus on patient&#x02019;s clinical needs for diagnosis to most advanced conditions, better management of care and replacement of some of the home visits by remote evaluations as well as better management of visit scheduling according to need instead of the periodic visits usually done.</para>
<para>At the PD management level, the system provides information that does not exist today enabling the neurologist to have better assessment of the patient&#x02019;s condition and treatment effectiveness with online information. The pilot studies done in REMPARK project provided clinical outcomes for the motor symptom detection. Further studies should be done for assessment of overall clinical outcomes of the new treatment approach on the PD patients. However, from previous experience with other chronic disease patients treated in Maccabi healthcare services, in Israel, using this approach, the following significant clinical outcomes can be found:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Significant improvements in the patient&#x02019;s well-being measured by Qol.</para></listitem>
<listitem>
<para>Patients maintained a healthy lifestyle: diet, physical activity...</para></listitem>
<listitem>
<para>The mental condition of these patients (reported depression) dropped from 24% before to 15% following the intervention using DMS.</para></listitem>
<listitem>
<para>Patients reported that they have better ability to cope with their disease.</para></listitem>
</itemizedlist>
<para>At the level of physicians there was a high satisfaction from the service which they found very helpful in the treatment process since the system supports Healthcare professionals in their routine work.</para>
</section>
<section class="lev2" id="sec8-4-2" label="8.4.2" xreflabel="8.4.2">
<title>Advantages for the Patients</title>
<para>Daily communication with caregivers, better understanding of the disease, education and awareness about the disease progression, symptoms and possible treatments are crucial for PD patients and their ability to cope with the disease. At early stages of the disease, there is a need to support the patient with educational materials and follow-ups, and at more advances stages there exists a difficulty of the patient to arrive to the clinic as often as needed, to adjust the medical treatment, provide additional treatments (physiotherapy and cognitive treatment, for instance) and perform a correct on-going assessment and intervention of the disease.</para>
<para>The REMPARK system monitors and provides care for PD patients considering their overall clinical condition including co-morbidities. The patients are treated by their doctor and do not have to move visiting different doctors and care providers for the treatment of different conditions. The care coordination is done within the program and provides them a clear treatment plan and one contact point. The system aims to enable the patients preserve/enhance of their physical and mental QoL, performance scores, compliance rates and satisfaction. It also enables to empower the patients and support them and their family in the care process.</para>
<para>In summary, the REMPARK system brings an innovative solution to the patients by involving them in the care process. They are actively participating in the assessment through the questionnaires and are able to view and follow their clinical condition. The neurologist can make a remote visit and assessment of the motor condition (administering the UPDRS scale, as demonstrated during the REMPARK project pilot in Israel) through video conference and save the need to go to the hospital, especially for patients that are living in rural areas or have motor symptoms and disabilities at advanced stages of the disease.</para>
<para>From the cumulated experiences with chronic disease patients adopting the DMS system approach at Maccabi in Tel-Aviv (Israel), the presented system clearly helps the patient in all the mentioned aspects. Patients seem less worried regarding their condition; feel they have the information for the treatment, for drug regimen and for self-management. It also helps to preserve/enhance their physical and mental QoL (as measured by PHQ9).</para>
<para>The treatment increases their performance scores and satisfaction, decrease reported depression and increase healthy behaviour. The effects were shown also on the whole treatment perception, self-management and treatment burden healthy lifestyle was assessed by the frequency of self-care activities of the patient.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Concerning the diet, physical activity and drug regime, there was a significant improvement due to the intervention (satisfaction with the service is very high and is rated 6 in a scale of 1&#x02013;7).</para></listitem>
<listitem>
<para>Use of a DMS based service results in a better empowerment of the patient and caregivers support of the care process. An increase of compliance and adherence to treatment is also detected.</para></listitem>
<listitem>
<para>Remote- UPDRS was performed in PD patients as part of the pilot.</para></listitem>
</itemizedlist>
</section>
<section class="lev2" id="sec8-4-3" label="8.4.3" xreflabel="8.4.3">
<title>Advantages for the Organization</title>
<para>It is very well-known that the prevalence of chronic diseases is increasing around the world, and 50&#x02013;80% of all global health spending is related to chronic diseases. Patients suffering from Parkinson&#x02019;s Disease are part of this population, since in most cases, PD patients suffer from more than one chronic disease.</para>
<para>The care of PD patients is complex and the correct treatment should be handled jointly by General Practitioners (GPs), and the specialized health service (hospitals or clinics): specialists (geriatrics and neurologist), general physicians, nurses, physiotherapists, nutritionists, occupational therapists, social workers, that may be affiliated to different organizations. Rehabilitation and self-management support should be handled in cooperation with GPs [13].</para>
<para>Disease management programs focus on patient monitoring and intervention. These shift healthcare expenses to less invasive and expensive care, thus, disease management programs are meant to strive to achieve two seemingly conflicting goals:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Improving patient outcomes</para></listitem>
<listitem>
<para>Optimizing resource utilization</para></listitem>
</itemizedlist>
<para>In parallel to the increase of the prevalence in chronic diseases, there is a decrease in number of healthcare professionals. Since the early 1980s there is a decrease in number of physicians per capita from &#x0223C;3 to &#x0223C;2 doctors per 1000 people in average in the OECD countries. The number of nurses per 1000 people decreased from 7.5 in the mid-1980s to 5.5 in 2004 in average in the OECD countries. This trend increases the workload on physicians and nurses as well as on other healthcare professionals which limit the system in providing all the services needed.</para>
<para>The healthcare system structure is fragmented and in order to treat PD and other chronic patients, it is needed to receive services from several stakeholders. There is a limited accessibility and availability and lack of treatment uniformity in different areas according to healthcare professionals and service availability. There is a continuous rise in national healthcare costs and as a result, the economic stress is rising.</para>
<para>Nowadays, the healthcare systems face huge challenges. At the level of the care process there is a need for capturing and analysing patient data from dispersed systems, involving and engaging all the related stakeholders, especially primary care providers that are typically left out. Optimal identification and stratification of patient population derives also from data integration and physician engagement challenges. Service should be equal to all patients regardless of their living area (rural or large cities) and involve care teams and case managers. At the organizational level, there is a need to establish the process/workflow, the clinical guidelines and protocols for remote treatment, risk management and cost control.</para>
<para>As it has been already explained, the integrated care workflow application considered in REMPARK includes built-in alerts, clinical protocols, guidelines and treatment plans. The application interfaces with remote monitoring devices and can be integrated with EHR and other medical systems. The advantage is that the system does not change the routine work of the healthcare professional and support them in their work and decisions, enabling knowledge sharing, online assessment, intervention and follow-up. Using this approach on PD patients, in REMPARK project, it was received a high level of satisfaction from both patients and doctors, however it was detected a real need to drive towards the implementation of the service and to study the success measurements as it has been already done in other chronic disease patients populations.</para>
<para>The system is composed of several modules that provide a number of tools and functionalities to the organization:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Risk management.</para></listitem>
<listitem>
<para>Control of large teams providing services 24H/7D.</para></listitem>
<listitem>
<para>Management of a large groups of patients that will enable scaling up to large population management.</para></listitem>
<listitem>
<para>Treating heterogeneous data coming from different monitoring device, including patient reporting data.</para></listitem>
<listitem>
<para>Ability to treat different conditions from well-being, clinical cognitive and mental conditions.</para></listitem>
<listitem>
<para>Keep more than one care organization in the loop by sharing data and knowledge.</para></listitem>
<listitem>
<para>The support of several care models/workflow and therefore the minimization of the number of systems that the organization has to use and implement.</para></listitem>
</itemizedlist>
</section>
</section>
<section class="lev1" id="sec8-5" label="8.5" xreflabel="8.5">
<title>Conclusions, Discussion and Vision</title>
<para>As the healthcare services changes and moves from hospitals to community care, there is a need to address the need of coordination between the services provided by specialists in the hospital, such as neurologists, and healthcare providers in the community and to create a system that will enable continuity of care, global coordination and integrated care. Furthermore, the treatment of actual complex patients includes also social care organizations, municipalities and sometimes private care providers, thus making their care quite complex, fragmented and with difficulties for sharing relevant information.</para>
<para>On the other hand, the interaction and relationship between patients and care providers is changing and is moving towards collaboration schemes and the active involvement of the patient in his care process, including self-management. This absolutely requires new tools and a different approach for patient empowerment, guidance and timely response by the care provider.</para>
<para>The REMPARK project developed and experienced a system that aims to address the challenges of the future model of care for the PD community. The different levels of sensors, data analytics, decision support tools, integrated care platform and actuators as well as tools for the patient, demonstrate the process and care pathway for treating PD patients and chronic patients at home.</para>
<para>The success of the system relies on its ability to adapt to different organizational and national systems as demonstrated in 3 pilot sites (Spain, Ireland and Italy) in which the main care of PD is provided by hospitals and in Israel in which the main treatment is provided in the community. The reliability of the system also at the level of data analysis provides a powerful tool when combined with clinical and organizational guidelines and thus pave the way to treat large populations with different and changing conditions in a personalized way.</para>
<para>The main barrier in implementing such systems is the need of integration with organizational systems, which is a slow and partial process. Therefore, the main challenge of healthcare system is to implement such systems at large scale and to use them as part of the existing workflows, sharing information with other organizations, patient and family and to develop methodologies for interactive treatment.</para>
<para>Healthcare organizations will use these technologies by changing the model of care, sharing information and advancing the research and development of systems that will bring additional information and knowledge to that already exist, in order to find the best way to use it in practice to improve care quality. This will also change the clinical practice and patient involvement in self-care and decision making.</para>
</section>
<section class="lev1" id="sec8-6">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Andlin-Sobocki P, Jnsson B, Wittchen HU, Olesen J (2005). Cost of disorders of the brain in Europe. Eur J Neurol 12:1&#x02013;27. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Andlin-Sobocki+P%2C+Jnsson+B%2C+Wittchen+HU%2C+Olesen+J+%282005%29%2E+Cost+of+disorders+of+the+brain+in+Europe%2E+Eur+J+Neurol+12%3A1-27%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Armstrong RA (2008). Visual signs and symptoms of Parkinson&#x02019;s disease. Clin Exp Optom 91(2):129&#x02013;138. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Armstrong+RA+%282008%29%2E+Visual+signs+and+symptoms+of+Parkinson%27s+disease%2E+Clin+Exp+Optom+91%282%29%3A129-138%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Davie CA (2008). A review of Parkinson&#x02019;s disease. Br Med Bull 86(1):109&#x02013;127. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Davie+CA+%282008%29%2E+A+review+of+Parkinson%27s+disease%2E+Br+Med+Bull+86%281%29%3A109-127%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Hou JGG, Lai EC (2007). Non-motor symptoms of Parkinson&#x02019;s disease. Int J Gerontol 1(2):53&#x02013;64. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Hou+JGG%2C+Lai+EC+%282007%29%2E+Non-motor+symptoms+of+Parkinson%27s+disease%2E+Int+J+Gerontol+1%282%29%3A53-64%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Jankovic J (2008). Parkinson&#x02019;s disease: clinical features and diagnosis. J Neurol Neurosurg Psychiatry 79(4):368&#x02013;376. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Jankovic+J+%282008%29%2E+Parkinson%27s+disease%3A+clinical+features+and+diagnosis%2E+J+Neurol+Neurosurg+Psychiatry+79%284%29%3A368-376%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Korczyn AD (2008). Parkinson&#x02019;s disease. In: E. in Chief: Kris Heggenhougen (ed) International encyclopedia of public health, Academic Press, Oxford, pp. 10&#x02013;17. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Korczyn+AD+%282008%29%2E+Parkinson%27s+disease%2E+In%3A+E%2E+in+Chief%3A+Kris+Heggenhougen+%28ed%29+International+encyclopedia+of+public+health%2C+Academic+Press%2C+Oxford%2C+pp%2E+10-17%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Samii A, Nutt JG, Ransom BR (2004). Parkinson&#x02019;s disease. Lancet 63(9423):1783&#x02013;1793.</para></listitem>
<listitem>
<para>Sian J, Gerlach M, Youdim MBH, Riederer P (1999). Parkinson&#x02019;s disease: a major hypokinetic basal ganglia disorder. J Neural Transm 106:443&#x02013;476. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Sian+J%2C+Gerlach+M%2C+Youdim+MBH%2C+Riederer+P+%281999%29%2E+Parkinson%27s+disease%3A+a+major+hypokinetic+basal+ganglia+disorder%2E+J+Neural+Transm+106%3A443-476%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Hadas Lewy. Future challenges for implementation in healthcare services. Healthcare Technology Letters. Special issue: Wearable Healthcare Technology, Vol. 2 Issue 1, pp. 2&#x02013;5, 2015. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Hadas+Lewy%2E+Future+challenges+for+implementation+in+healthcare+services%2E+Healthcare+Technology+Letters%2E+Special+issue%3A+Wearable+Healthcare+Technology%2C+Vol%2E+2+Issue+1%2C+pp%2E+2-5%2C+2015%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Lewy H. Kaufman G. The Maccabi multidisciplinary center for disease management in &#x0201C;Recipes for sustainable healthcare&#x0201D; sponsored by abbvie, Philips and EUPHA. Brussels, Biblioteque Solvay Brussels, May 2013.</para></listitem>
<listitem>
<para>Yee K., Yeung A., Robertson T., et al.: &#x02018;A networked system for selfmanagement of drug therapy and wellness&#x02019;. Wireless Health &#x02018;10 October 2010, San Diego, CA, USA. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Yee+K%2E%2C+Yeung+A%2E%2C+Robertson+T%2E%2C+et+al%2E%3A+%27A+networked+system+for+selfmanagement+of+drug+therapy+and+wellness%27%2E+Wireless+Health+%2710+October+2010%2C+San+Diego%2C+CA%2C+USA%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Matheson, M., et al.: &#x02018;Realizing the promise of Disease Management &#x02013; Payer Trends and Opportunities in the United States&#x02019;, The Boston Consulting group, 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Matheson%2C+M%2E%2C+et+al%2E%3A+%27Realizing+the+promise+of+Disease+Management+-+Payer+Trends+and+Opportunities+in+the+United+States%27%2C+The+Boston+Consulting+group%2C+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Joseph F. Coughlin et al.: &#x02018;Old Age, New Technology, and Future Innovations in Disease Management and Home Health Care&#x02019;, Home Health Care Management &#x00026; Practice, Vol. 18, 3, 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Joseph+F%2E+Coughlin+et+al%2E%3A+%27Old+Age%2C+New+Technology%2C+and+Future+Innovations+in+Disease+Management+and+Home+Health+Care%27%2C+Home+Health+Care+Management+%26+Practice%2C+Vol%2E+18%2C+3%2C+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>The Survey of Health, Ageing and Retirement in Europe &#x02013; http://www. share-project.org/ <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=The+Survey+of+Health%2C+Ageing+and+Retirement+in+Europe+-+http%3A%2F%2Fwww%2E+share-project%2Eorg%2F" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch09" label="9" xreflabel="9">
<title>REMPARK System Assessment: Main Results</title>
<para role="author"><emphasis role="strong">Albert Sama<superscript><emphasis role="strong">1</emphasis></superscript>, J. Manuel Moreno<superscript><emphasis role="strong">1</emphasis></superscript>, Carlos P&#x00E9;rez<superscript><emphasis role="strong">1</emphasis></superscript>, Joan Cabestany<superscript><emphasis role="strong">1</emphasis></superscript>, Angels Bay&#x00E9;s<superscript><emphasis role="strong">2</emphasis></superscript> and Jordi Rovira<superscript><emphasis role="strong">3</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<para><superscript>2</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<para><superscript>3</superscript>Telef&#x00F3;nica I+D, Spain</para>
<section class="lev1" id="sec9-1" label="9.1" xreflabel="9.1">
<title>Introduction</title>
<para>In the previous chapters, the REMPARK system has been presented and discussed, along with its usefulness. According to the initial project specifications and some important conclusions obtained from the work carried out during the project, the main characteristics and requirements of the integrating parts and REMPARK sub-systems were initially defined and refined afterwards.</para>
<para>The present chapter will first describe the final system and, then, its overall final assessment. This way, first, a description of the communication flows established in the REMPARK platform (type of information, dataflow and security issues) is given. Secondly, an overview of the final necessary platform, ready to be used in the piloting part of the project is provided.</para>
<para>The assessment process was done through a pilot in which the patients tested the system in ambulatory conditions and during their daily living activities. More than 40 PD patients participated from four countries (Spain, Italy, Israel and Ireland).</para>
</section>
<section class="lev1" id="sec9-2" label="9.2" xreflabel="9.2">
<title>Description of Main Communication Flows</title>
<para>As it has been described in previous chapters, the effectivity of REMPARK system is based on a couple of interaction loops that define specific communication data flows. This way, communication between the different sub-systems of REMPARK is a crucial aspect and the correctness and security of the information flows must be guaranteed. In order to understand and specify the characteristics of the communication flows, it must be considered that the REMPARK system has two differentiated functional parts:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The first one is related to the <emphasis role="strong">monitoring of PD motor symptoms</emphasis>, including: movement sensors, actuator, smartphone, the REMPARK server, the Rule Engine, the Disease Management System (DMS) and a patient&#x02019;s web interface.</para></listitem>
<listitem>
<para>The second functional part is related to the <emphasis role="strong">monitoring of non-motor PD symptoms</emphasis>. This monitoring strategy is mainly based on the use of questionnaires and also includes a simple agenda system to interact with the patient. This part of the system requires the smartphone, the REMPARK server and the DMS to exchange information.</para></listitem>
</itemizedlist>
<para>Thus, two different information flows are distinguished in the REMPARK system. This differentiation will be used to specify the system according to either 1) the communication flow due to the monitoring of motor symptoms and the application of the actuation action or 2) the communication flow due to non-motor symptoms.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The monitoring process of the motor symptoms is mainly done in the immediate loop, around the patient. The mobile phone is acting as the gateway for the communication of the related sub-systems with the REMPARK server and the different channels and data type, according to the definition presented in the next section, are shown in the <link linkend="F9-1">Figure <xref linkend="F9-1" remap="9.1"/></link>:</para></listitem>
<listitem>
<para>The non-motor symptoms mode embraces the communication flows related to patient management issues, e.g. agenda, treatment, questionnaires, etc. <link linkend="F9-2">Figure <xref linkend="F9-2" remap="9.2"/></link> presents the REMPARK system parts participating in non-motor symptoms monitoring and their communication flow.</para></listitem>
</itemizedlist>
<fig id="F9-1" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-1">Figure <xref linkend="F9-1" remap="9.1"/></link></label>
<caption><para>Communication flow of motor symptoms detection and actuation in REMPARK system.</para></caption>
<graphic xlink:href="graphics/ch09_fig1.jpg"/>
</fig>
<fig id="F9-2" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-2">Figure <xref linkend="F9-2" remap="9.2"/></link></label>
<caption><para>Communication flow of non-motor symptoms management and actuation in REMPARK system.</para></caption>
<graphic xlink:href="graphics/ch09_fig2.jpg"/>
</fig>
<section class="lev2" id="sec9-2-1" label="9.2.1" xreflabel="9.2.1">
<title>Type of Transmitted Information</title>
<para>This section details the general specifications of the different information types sent and received through the communication channels indicated in Figures 9.1 and 9.2. Four different types of information are considered: (I) Alarms, (II) Data sent within the closed loop of the REMPARK monitor- ing system, (III) Configuration parameters in the smartphone and, finally, (IV) Agendas and questionnaires:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Alarm specifications</emphasis></para>
<para>An alarm is defined as an event detected by the REMPARK system that must be urgently notified to an end-user. For instance, a fall-detection event is the only alarm provided by the REMPARK wearable system. Other alarms can be defined within the DMS as a combination of one or more rules applied to the stored information; for instance, a value from a questionnaire lower than a specific threshold.</para>
<para>In the communication flow, as a general rule, alarms within the REMPARK system will be handled as states. This means, for instance, that when the sensor sends a data packet it will also send the state of all the alarms, a value 1 meaning an activated alarm and a value 0 meaning a deactivated alarm. There should be 3 stages for clinical alarms: red, yellow and green. Therefore, when a low battery level is detected its corresponding alarm will be set to 1, and its value will not become 0 until an optimum charging level is detected.</para></listitem>
<listitem>
<para><emphasis role="strong">Data sharing between the REMPARK wearable system and the DMS</emphasis> The sensor sends data every minute to the smartphone. The smartphone will store the data sent by the movement sensor during a specified time frame, which usually consists in few hours. Once this time frame is reached, the smartphone establishes a connection with the REMPARK server to upload all the data stored since the last connection. The connection between the smartphone and the server will take place every 1&#x02013;3 hours, except when the data sent by the sensor contains an activated alarm or when an alarm is generated at the smartphone. In this case, an immediate connection with the server is established.</para></listitem>
<listitem>
<para><emphasis role="strong">Configurable parameters</emphasis></para>
<para>All configurable parameters must be stored in the REMPARK server. These parameters are used by the machine learning algorithms and the ACS cueing system, which enable their personalisation to each patient. They are defined in the DMS and their values are transmitted to the smartphone, in which they are applied to the sensor&#x02019;s output provided every minute. These parameters are, for instance, the patient&#x02019;s walking rhythm, the threshold used to detect bradykinesia or the freezing index level necessary to consider an episode of FOG.</para></listitem>
<listitem>
<para><emphasis role="strong">Questionnaires and agendas</emphasis></para>
<para>The data associated with the monitoring of non-motor symptoms can be grouped in three broad categories: the request for a specific questionnaire, the generation of an event in the agenda and the completion of a questionnaire. All the questionnaires, including the TAP tests, are stored locally in the smartphone and in the DMS. The request for a specific questionnaire consists in asking for a specific questionnaire number and a date and time. The results of the questionnaires are sent in an encoded REMPARK format. As an option, the questionnaires could be filled in 3 ways:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Using the smartphone</para></listitem>
<listitem>
<para>Through the Patient&#x02019;s web application</para></listitem>
<listitem>
<para>By the nurse asking the patient and completing, directly, through the DMS platform</para></listitem>
</orderedlist>
<para>The data from the questionnaires will be sent to the REMPARK server from the smartphone or the DMS respectively, they will be analysed by the Rule Engine and alerts will be then sent to the DMS. The smartphone will send all data filled by the patient and will be presented to the patient also on the Web application. An agenda event is generated by the DMS and sent to the smartphone through the REMPARK server. Even if the event is stored in the server for record purposes, this information will not be accessible by the rest of the subsystems (smartphone or DMS) once the event is transferred to the smartphone. All the data related to the questionnaires and the agendas must be stored in the REMPARK server.</para></listitem>
</itemizedlist>
</section>
<section class="lev2" id="sec9-2-2" label="9.2.2" xreflabel="9.2.2">
<title>Security Aspects</title>
<para>Security aspects related to the communication are very important in the application of the REMPARK system. The system can be split into two different domains (the BAN and the platform/server), and different considerations should be made possible. In the BAN, security issues are related to the Bluetooth communication between the different sub-systems. In the platform, security aspects come in the communication between the smartphone and the server and the rest of the entities of that domain, the Rule Engine and the DMS. The most relevant security aspects are summarized as follows:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">BAN:</emphasis> All the different devices forming the BAN, i.e. the sensor, the smartphone and the cueing system, exchange data using Bluetooth 2.1. Traditionally, using Bluetooth devices was associated to use pin codes for each device in order to establish communication between devices. This method required a manual intervention and security is not very high. REMPARK uses Bluetooth v2.1, which uses SSP. This security approach uses public key cryptography, which gives a lot of advantages. It just works without manual intervention; however, a device may prompt the user to confirm the pairing process. During the pairing time, if the devices have a screen, numeric comparison is used, which informs the user that a device is trying to connect. The number shown in the screen must be the same as the one in the device. From Bluetooth v2.1 encryption is required and the encryption key is regularly refreshed.</para></listitem>
<listitem>
<para><emphasis role="strong">Platform/server:</emphasis> The server is interfaced by three different elements, the Rule Engine, the DMS and the smartphone. Communication with the server fulfils the European Data Protection Directive (Directive 95/46/EC), which embraces the different national laws for data protection.</para></listitem>
</itemizedlist>
</section>
<section class="lev2" id="sec9-2-3" label="9.2.3" xreflabel="9.2.3">
<title>Final Deployment and Implementation of the REMPARK Platform</title>
<para>With the already presented specifications and characteristics, the REMPARK platform was implemented for its use during the last piloting phase of the project. According to the pilot specification, the system was conceived to be implemented following a distributed approach, and this is how it was tested during an early pre-pilot phase. Many efforts were devoted to ensure the synchronisation, data transmission, processing and representation of the information considering different scenarios like a sudden lack of communication, for instance.</para>
<para>After this early phase, the integration of the Rule Engine into the REMPARK server was decided, obtaining in this way a more efficient management of the communication bandwidth and a mitigation of transmission delays.</para>
<para>The REMPARK system worked steady, secure and with good performance to carry out the scheduled pilots. The <link linkend="F9-3">Figure <xref linkend="F9-3" remap="9.3"/></link> shows the <emphasis role="strong">final REMPARK functional view</emphasis> (it was deployed in June 2014 as starting point for the pilots).</para>
<fig id="F9-3" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-3">Figure <xref linkend="F9-3" remap="9.3"/></link></label>
<caption><para>Final REMPARK platform (ready for pilots) functional view.</para></caption>
<graphic xlink:href="graphics/ch09_fig003.jpg"/>
</fig>
<para>In the figure, the Rule Engine is already presented as a part integrated in the REMPARK server and directly accessing to the information generated by the patient&#x02019;s sensor (measures, alerts). All this information is transmitted by patient&#x02019;s smartphone in a secure way using a Transport Layer Security (TLS) channel.</para>
<para>The Rule Engine, then, analyses this information and creates new post-processed measures, which are stored and forwarded to the DMS system in a secure way using a TLS channel. Eventually, the DMS shows all the gathered information to the clinical professionals as well as providing a decision support system that follows the defined clinical protocols. Furthermore, clinical professionals can set up treatments and appointments that are forwarded to patients&#x02019; mobile phone.</para>
<para>In order to guarantee the execution of the pilot, it was decided to implement four different and equivalent environments. As REMPARK pilot experience must be distributed among four different countries (Spain, Ireland, Italy and Israel), it was entailed the deployment of four different servers, one isolated server per pilot site and the same replica for the DMS system.</para>
<para>In order to guarantee patient&#x02019;s data privacy, pseudonyms and ID&#x02019;s instead of personal information were transmitted. Moreover, to maximise the security of the pilots, external calls to each environment were forwarded through a proxy to an isolated Telef&#x00F3;nica&#x02019;s private network which can only be accessed from inside (Telef&#x00F3;nica was the responsible partner for the REMPARK platform and communications). The <link linkend="F9-4">Figure <xref linkend="F9-4" remap="9.4"/></link> shows how it looks like this set up.</para>
<fig id="F9-4" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-4">Figure <xref linkend="F9-4" remap="9.4"/></link></label>
<caption><para>REMPARK server in isolated network.</para></caption>
<graphic xlink:href="graphics/ch09_fig004.jpg"/>
</fig>
<fig id="F9-5" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-5">Figure <xref linkend="F9-5" remap="9.5"/></link></label>
<caption><para>Final REMPARK system deployment and used for the pilots.</para></caption>
<graphic xlink:href="graphics/ch09_fig005a.jpg"/>
</fig>
<para>In total, four environments were set up assuring this level of security. Furthermore, any external communication with the server, either from patient&#x02019;s mobile phone or the DMS system goes through a TLS channel and each message includes specific credentials according to the type of user/system sending the message (i.e. patient, DMS). Moreover, other security mechanisms have been implemented to assure that there are warning alerts in cases where there are communication problems between the different devices (i.e. alert when the smartphone loses communication with the platform, alert if sensor or actuator connections are lost, presence of a fall detection). <link linkend="F9-5">Figure <xref linkend="F9-5" remap="9.5"/></link> shows the final set-up implemented and used for REMPARK&#x02019;s pilots. The secure connections between the REMPARK server and other external sub-systems, like the DMS and the smartphones used by the patients are indicated. As a proof of concept, the DMS was integrated with the information systems used by Maccabi in Israel through HL7 protocol.</para>
</section>
</section>
<section class="lev1" id="sec9-3" label="9.3" xreflabel="9.3">
<title>Pilot for the REMPARK System Assessment: Description</title>
<para>This section introduces the details and the execution of the distributed pilot, executed in REMPARK. The main objective of this pilot was the global assessment of the system in terms of ON and OFF detection. As a previous activity, before starting the main pilot, an early pre-pilot was organized with very few volunteers in order to test the stability and the validity of the overall system.</para>
<para>In this section, the experimental protocol is described first, followed by some conclusions after the early trial (pre-pilot experience). Finally, the analysis of the REMPARK system during the pilots is fully provided, with the main conclusions regarding the obtained results.</para>
<section class="lev2" id="sec9-3-1" label="9.3.1" xreflabel="9.3.1">
<title>Definition of the Pilots&#x02019; Objectives and Eligibility Criteria</title>
<para>The objectives of the pilot activity were divided into primary and secondary. The complete list to be covered is following:</para>
<para><emphasis role="strong">Primary objectives</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To study the performance and reliability of the REMPARK system under real conditions on a significant group of patients.</para></listitem>
<listitem>
<para>To study the validity of the ON/OFF motor phase detection by the system on a significant group of patients.</para></listitem>
</itemizedlist>
<para><emphasis role="strong">Secondary objectives</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>To study the functionality of cognitive tests administered through the smartphone in detecting ON/OFF states on a pilot group of patients.</para></listitem>
<listitem>
<para>To check the operation of an auditory cueing system, activated by the output of an algorithm, in improving the gait on a pilot group of patients.</para></listitem>
<listitem>
<para>To assess both usability and user&#x02019;s satisfaction referring to the REMPARK system under real daily living conditions on a pilot group of patients.</para></listitem>
<listitem>
<para>To study the validity of the fall detection algorithm of the REMPARK&#x02019;s system on a pilot group of patients.</para></listitem>
<listitem>
<para>To verify the safety of the REMPARK in individuals with Parkinson&#x02019;s disease on a pilot group of patients.</para></listitem>
</itemizedlist>
<para><emphasis role="strong">Population and eligibility criteria</emphasis></para>
<para>The reference population is that formed by a pilot group of patients with moderate to severe Parkinson&#x02019;s Disease, presenting ON/OFF phases, FOG or dyskinesia (Hoehn and Yahr greater than 2 in ON phases and lower than 5 in OFF phases). Candidates found to be eligible to participate in the study immediately were provided with the Patient Information Sheet and the Informed Consent Form. The Principal Investigator or a co-investigator met the subjects and explained the study purpose, procedures, possible risks and benefits and subject responsibilities to the potential participants. The subjects had the opportunity to evaluate these documents in detail and were allowed to ask the investigators any question regarding the study. The subject&#x02019;s willingness and ability to meet the follow-up requirements were determined.</para>
<para>Patients fulfilling the following criteria were candidates to be included in the study:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Clinical diagnosis of Idiopathic Parkinson&#x02019;s Disease according to the UK Parkinson&#x02019;s Disease Society Brain Bank [1].</para></listitem>
<listitem>
<para>Disease in moderate-severe phase, with a Hoehn and Yahr greater than 2 in ON phases and lower than 5 in OFF phases, or with a scale greater or equal to 2.5 (in ON state) with motor fluctuations comprising bradykinesia, FOG and/or dyskinesia [2].</para></listitem>
<listitem>
<para>Able to walk unaided in OFF state.</para></listitem>
<listitem>
<para>Age between 50 and 80 years.</para></listitem>
<listitem>
<para>Sufficient literacy capacity to answer questionnaires.</para></listitem>
<listitem>
<para>Willing to participate in the study (in writing-sign informed consent) and wanting to co-operate in all its parts, accepting the performance regulations and procedures provided by the researchers. The patients&#x02019; family members and responsible doctors should fulfil, also, this inclusion criteria.</para></listitem>
</itemizedlist>
<para>Patients fulfilling the following criteria were excluded from the study:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Other health problems that hamper physical activity and gait: rheumatologic, neuromuscular, respiratory, cardiologic problems other neurological disorders- (Post stroke, Polio), mental disorders, significant pain.</para></listitem>
<listitem>
<para>Alcohol and/or drug abuse.</para></listitem>
<listitem>
<para>Being treated with duodopa or apomorphine pump, or deep brain stimulator.</para></listitem>
<listitem>
<para>Patients who are participating in another clinical trial.</para></listitem>
<listitem>
<para>Dementia according to clinical criteria -DSM-IV-TR [3].</para></listitem>
<listitem>
<para>Unable to fully understand the potential risks and benefits of the study and give informed consent.</para></listitem>
<listitem>
<para>Unable to recognize the ON and OFF fluctuations, after proper training.</para></listitem>
<listitem>
<para>Subjects who are unable or unwilling to cooperate with study procedures (for example- unwilling to carry the sensors during the study hours).</para></listitem>
</itemizedlist>
<para>All participants in the pilot presented motor fluctuations, according with the inclusion criteria, and at least 25% of the total of the sample had FOG problems. Family members and responsible doctors of the participants were included in the study and they were allowed to consult patient&#x02019;s health data through the web information system.</para>
</section>
<section class="lev2" id="sec9-3-2" label="9.3.2" xreflabel="9.3.2">
<title>Design of the Study</title>
<para>The REMPARK pilot was designed as a longitudinal pilot study in which each participant was using the REMPARK system under real conditions (ambulatory conditions) during 4 consecutive days. An additional pre-trial day (day 0) is necessary for customizing the system to the user, and a day 1, to train the user in the system&#x02019;s use. This pre-trial day was scheduled at least 1 week prior to the trial start. The organization of the study design is shown in <link linkend="F9-6">Figure <xref linkend="F9-6" remap="9.6"/></link>.</para>
<fig id="F9-6" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-6">Figure <xref linkend="F9-6" remap="9.6"/></link></label>
<caption><para>Timing of the methodological study design.</para></caption>
<graphic xlink:href="graphics/ch09_figN006.jpg"/>
</fig>
<para>In the pre-trial day (day 0), the thresholds for the bradykinesia detection algorithm, the FOG detection algorithm and the TAP test parameters were adjusted for each individual participant. For doing so, three short specific experiments were conducted: walk in OFF, walk in ON, FOG provocation test and TAP test. During the trial days (day 1&#x02013;day 4), patients were wearing and using the REMPARK system under real conditions. The system was recording motor and non-motor symptoms, which were also video recorded by standard means (video cameras or smartphones).</para>
<para>The pilot study started after getting the approval of the corresponding Ethics Committees and the competent authorities in the four countries (i.e., in Spain the Spanish Agency for Drugs and Medical Devices, AEMPS gave the corresponding permission). The following data and records from each participant were obtained and integrated into the pilot database:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Personal identification data:</emphasis> name, address, phone number.</para></listitem>
<listitem>
<para><emphasis role="strong">Socio-demographic variables:</emphasis> date of birth, gender, educational level, cohabitation.</para></listitem>
<listitem>
<para><emphasis role="strong">Clinical assessment questionnaires:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Parkinson&#x02019;s diagnosis:</emphasis> according Brain Bank criteria by Hughes et al. [1].</para></listitem>
<listitem>
<para><emphasis role="strong">Parkinson&#x02019;s severity:</emphasis> measured by Hoehn and Yahr scale [2].</para></listitem>
<listitem>
<para><emphasis role="strong">Questionnaire assessment of motor fluctuations, FOGs, and dyskinesia.</emphasis></para></listitem>
<listitem>
<para><emphasis role="strong">Basal health status:</emphasis> list of chronic conditions, list of current medications.</para></listitem>
<listitem>
<para><emphasis role="strong">ON/OFF current phase:</emphasis> The current motor phase was established by using three different instruments. 1) Patient&#x02019;s report: patients who were previously trained for recognizing their ON/OFF phases 2) report whether they are in ON or OFF phase every 60 minutes, or 3) when they detect a change.</para></listitem>
<listitem>
<para><emphasis role="strong">Unified Parkinson&#x02019;s Disease Rating Scale (UPDRS)</emphasis> [4], which was administered by a trained researcher to participants several times during the pilot.</para></listitem>
<listitem>
<para><emphasis role="strong">Video recording</emphasis> and posterior analysis by an expert was used for confirming the motor phase of the patient.</para></listitem>
<listitem>
<para><emphasis role="strong">TAP-test:</emphasis> This test was designed to objectively assess changes in movement, such as slowing and rigidity which are effects commonly related to the OFF state. In this test the subject is requested to repeatedly press a button on the touch screen of the smartphone representing a white arrow in order to fill up a vessel as soon as possible according to ten predefined levels (each target level is marked by a green bar). The ten levels represent the number of button presses needed for the level to be fulfilled. The subject has to press the button by using his forefinger of the dominant hand (i.e., right hand).</para></listitem>
<listitem>
<para><emphasis role="strong">Cognitive status:</emphasis> Assessed by Folstein Mini-Mental [5] and applying the criteria of DSM-IV TR dementia.</para></listitem>
<listitem>
<para><emphasis role="strong">Freezing of Gait (FOG) episodes and severity</emphasis>, measured by two different standard methods:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Video recording and subsequent analysis by a trained observer, was used for identifying the section of the sensor signal&#x02019;s corresponding to FOG episodes.</para></listitem>
<listitem>
<para>Freezing of Gait Questionnaire (FOG-Q) [6]: This instrument was used for establishing the basal (over the last 4 days week) severity of freezing of gait in the participants, and also its severity during the 4 days of the REMPARK&#x02019;s system use.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><emphasis role="strong">Gait quality:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Video recorded timed Up &#x00026; Go test [7]: This instrument is a timed test of standing and walking. It is a gait-speed test used to assess a person&#x02019;s mobility and requires both static and dynamic balance.</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><emphasis role="strong">Non-motor symptoms:</emphasis></para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Non-Motor Symptom Questionnaire: NMSQuest [8].</para></listitem>
</itemizedlist>
</listitem>
<listitem>
<para><emphasis role="strong">Usability:</emphasis> The usability instruments were used to assess separately the usability of each device, and also the whole system.</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>System Usability Scale (SUS) [9].</para></listitem>
<listitem>
<para>Quebec User Evaluation of Satisfaction with Assistive Technologies (QUEST) [10].</para></listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<para>The REMPARK system for these pilots included all the already described sub-systems:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Sensor sub-system (located in the waist). &#x003BC;SD cards were used on day 0 to collect the raw data from the sensor in order to perform the user particularization. The remaining days, the sensor shared the results of the algorithms with the smartphone once per minute.</para></listitem>
<listitem>
<para>Smartphone: The smartphone used in the experiments is the Samsung Galaxy Nexus. The specific software running in the smartphone was developed within the framework of the REMPARK project.</para></listitem>
<listitem>
<para>Headset for auditory cueing: The headset chosen for the REMPARK experiments was the Samsung HM3500 Bluetooth earphone.</para></listitem>
<listitem>
<para>REMPARK Platform (according the description in precedent text).</para></listitem>
<listitem>
<para>Web Server &#x02013; Disease Management System (application for managing the patient&#x02019;s health by the medical staff).</para></listitem>
</itemizedlist>
</section>
<section class="lev2" id="sec9-3-3" label="9.3.3" xreflabel="9.3.3">
<title>Pre-Pilot Conclusions</title>
<para>As it has been mentioned, a preliminary pre-pilot activity was scheduled with the participation of a limited number of patients, and with the objective of checking the stability of the overall REMPARK system to be used. It was also intended to evaluate its performance in terms of correct detection of the motor state of few PD patients in ambulatory conditions.</para>
<para>During the pre-pilot, regarding the system stability, it must be noted that the data gathered by the REMPARK sensor were correctly sent through the different communication layers so that no information loss due to communication errors were detected. Although some packet losses were observed during the experiment, they were due to the fact that the user didn&#x02019;t remember to have the smartphone always in coverage range of the sensor. In this respect, it was concluded that, during the user training session, emphasis to keep both devices as close as possible during the whole duration of the experiments had to be done.</para>
<para>It was also found with these pre-pilot tests that the performance of the REMPARK system when detecting the motor state of a patient is in line with the original specifications, even if the gold standard available to validate the results is not always accurate enough. The existing issue is the fact that <emphasis role="underline">the only available gold standard is the self-reporting of the patients using a diary</emphasis>. <link linkend="F9-7">Figure <xref linkend="F9-7" remap="9.7"/></link> presents the diary filled by one of the participants in the pre-pilot experience, during the first day of experimentation (day 1). It can be observed that the patient, as it is commonly done in motor states self-reporting, writes down the motor state for each hour of the day.</para>
<fig id="F9-7" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-7">Figure <xref linkend="F9-7" remap="9.7"/></link></label>
<caption><para>Motor states section of the diary filled by one patient during the first day of experimentation. Third row corresponds to the &#x02018;intermediate state&#x02019;.</para></caption>
<graphic xlink:href="graphics/ch09_fig007.jpg"/>
</fig>
<para>Reporting the motor state in this manner presents the following two issues:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>The <emphasis role="underline">time in which the motor state is reported has been shown to be inaccurate in some cases</emphasis>. More specifically, it is unclear when exactly changes among motor states occur. In contrast, the information obtained by REMPARK system is known with seconds&#x02019; accuracy.</para></listitem>
<listitem>
<para><emphasis role="underline">Some PD patients are not able to recognize their motor state</emphasis>. This risk could be mitigated in the recruitment phase, since neurologists only should select those patients able to recognize ON and OFF states.</para></listitem>
</itemizedlist>
<para>In order to evaluate the ability of the REMPARK system for the detection of ON and OFF motor states, a set of three main performance measures are used: specificity, sensitivity and correlation with a gold standard. These measures can be severely affected by the two inaccuracy issues presented above:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Concerning specificity and sensitivity measurements: These measurements may be strongly affected by the described issues, since the REMPARK system provides an estimation of the motor state once every 10 minutes. First, given a patient who constantly switches among different motor states, a big difference between the time assumed in self-reporting and the time provided by the REMPARK system could lead to very low specificity and sensitivity values. Second, if the patient does not correctly recognize the motor state, a similar effect would be obtained.</para></listitem>
<listitem>
<para>Concerning the correlation between REMPARK system output and patient diary (used as gold-standard), it must be pointed out that these measurements would be affected similarly to the specificity and sensitivity ones.</para></listitem>
</itemizedlist>
<para>Two possible options appear when comparing the self-reported motor state of a patient and the REMPARK system output:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>It is possible to consider the correct REMPARK system output as the output that is closest to the time of the self-reported motor state by the patient. Results for this option were presented as &#x02018;<emphasis>exact time</emphasis>&#x02019;.</para></listitem>
<listitem>
<para>It is possible to consider the correct REMPARK system output as the mode (most frequent value) among the outputs obtained within the one-hour period that corresponds to the self-reported motor state. Results for this option were presented as &#x02018;<emphasis>mode</emphasis>&#x02019;.</para></listitem>
</itemizedlist>
<para>Finally, it should be noted that patients can report to be in ON, OFF or intermediate state (see <link linkend="F9-7">Figure <xref linkend="F9-7" remap="9.7"/></link>). However, REMPARK system only provides ON and OFF predictions. In consequence, those periods in which intermediate state was reported will not be included in the performance analysis.</para>
<para><link linkend="T9-1">Table <xref linkend="T9-1" remap="9.1"/></link> shows results for two patients, who participated in the pre-pilot. No valid conclusions can be extracted from this pre-pilot phase, but the identification of the discussed issues and the technical validation of the system. In the results of the first patient, it can be observed that only 8 hours were analysed, given that most of the reported states correspond to the &#x02018;intermediate state&#x02019;.</para>
<table-wrap position="float" id="T9-1">
<label><link linkend="T9-1">Table <xref linkend="T9-1" remap="9.1"/></link></label>
<caption><para>Pre-pilot results on motor state detection</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="center">Patient</td>
<td valign="bottom" align="center">REMPARK System Output Selection</td>
<td valign="bottom" align="center">Specificity</td>
<td valign="bottom" align="center">Sensitivity</td>
<td valign="bottom" align="center">VPP</td>
<td valign="bottom" align="center">VPN</td>
<td valign="bottom" align="center">Correlation</td>
<td valign="bottom" align="center">Number of Hours Analysed</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="center">1</td>
<td valign="top" align="center">Mode</td>
<td valign="top" align="center">0.6</td>
<td valign="top" align="center">0.3</td>
<td valign="top" align="center">0.33</td>
<td valign="top" align="center">0.6</td>
<td valign="top" align="center">&#x02013;0.07</td>
<td valign="top" align="center">8</td>
</tr>
<tr>
<td valign="top" align="center"></td>
<td valign="top" align="center">Exact time</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">8</td>
</tr>
<tr>
<td valign="top" align="center">2</td>
<td valign="top" align="center">Mode</td>
<td valign="top" align="center">0.91</td>
<td valign="top" align="center">0.71</td>
<td valign="top" align="center">0.71</td>
<td valign="top" align="center">0.90</td>
<td valign="top" align="center">0.62</td>
<td valign="top" align="center">29</td>
</tr>
<tr>
<td valign="top" align="center"></td>
<td valign="top" align="center">Exact time</td>
<td valign="top" align="center">0.73</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">0.54</td>
<td valign="top" align="center">0.7</td>
<td valign="top" align="center">29</td>
</tr></tbody>
</table>
</table-wrap>
</section>
</section>
<section class="lev1" id="sec9-4" label="9.4" xreflabel="9.4">
<title>REMPARK Pilots&#x02019; Execution and Obtained Results</title>
<para>Pilots with REMPARK system were conducted in accordance with the protocol presented above. It must be remembered that the main objectives of the study were to analyse the performance and reliability of the REMPARK system under real conditions, and to study the validity of the ON/OFF detection by the system. A list of secondary objectives was also focused (see Section 9.3.1).</para>
<para>The recruitment was carried out following a convenience sampling among patients assisted in the different centres participating in the study, following the methodology described in the above Section 9.3.1. Fifty-four (54) patients were initially contacted, 44 of them met inclusion criteria and agreed to participate. Three of the included patient did not complete the study days. One of them discontinued participation voluntarily. Two patients were removed from the study by the researchers, the first of them due to lack of adherence to the study protocol, the second patient was removed due to a health condition, which required hospitalization, apparently not related to study devices or procedures. Finally, 41 patients completed all study days and evaluations.</para>
<para><link linkend="T9-2">Table <xref linkend="T9-2" remap="9.2"/></link> shows recruitment and follow-up data by participant entity.</para>
<table-wrap position="float" id="T9-2">
<label><link linkend="T9-2">Table <xref linkend="T9-2" remap="9.2"/></link></label>
<caption><para>Recruitment and follow-up data by participant entity</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">Medical Partner</td>
<td valign="bottom" align="center">Contacted Patients</td>
<td valign="bottom" align="center">Included Patients</td>
<td valign="bottom" align="center">Lost-Dropout Patients</td>
<td valign="bottom" align="center">Completed Protocol</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">NUI Galway (Ireland)</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">6</td>
</tr>
<tr>
<td valign="top" align="left">TEKNON (Spain)</td>
<td valign="top" align="center">18</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">15</td>
</tr>
<tr>
<td valign="top" align="left">FSL (Italy)</td>
<td valign="top" align="center">16</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">10</td>
</tr>
<tr>
<td valign="top" align="left">MACCABI (Israel)</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">10</td>
</tr>
<tr>
<td valign="top" align="left">Total</td>
<td valign="top" align="center">54</td>
<td valign="top" align="center">44</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">41</td></tr></tbody>
</table>
</table-wrap>
<para>Concerning the socio-demographic and health data of the participants, twenty-eight participant patients were men (68.3%) and 13 were women (31,7%). The average age of participants was 71.3 years (SD 7.3; range 56&#x02013;84).</para>
<para>All the participants had been diagnosed of Parkinson&#x02019;s Disease according to the UK Parkinson&#x02019;s Disease Society Brain Bank [1]. The average time from diagnosis was 11.3 years (range 2&#x02013;26). As per inclusion criteria, all participants had a Hoehn and Yahr scale equal or greater than 2.5 [2], being median stage of the sample 3 (range 2.5&#x02013;4). The motor section of the Unified Parkinson&#x02019;s Disease Rating Scale (UPDRS) was in average 28.2 (SD 1.7) [3], when the patients were in OFF phase and 12.2 (SD 1.5) when the patients were in ON phase. The median of the Freezing of Gait (FOG) questionnaire of all participants was 13 (IQR 6) [4], this scale explores gait disturbances of the patients and ranges from 0 through 24, being the higher scores related to worse gait disturbances.</para>
<para>Participants with dementia and acute medical conditions were not included in the study. Mini-Mental State Examination (MMSE) [5] results of the participants are shown in <link linkend="T9-3">Table <xref linkend="T9-3" remap="9.3"/></link>, along with other medical chronic conditions of participants.</para>
<table-wrap position="float" id="T9-3">
<label><link linkend="T9-3">Table <xref linkend="T9-3" remap="9.3"/></link></label>
<caption><para>Mental and chronic disease condition of the participants</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">Condition</td>
<td valign="top" align="center">Number of Participants (n)</td>
<td valign="top" align="center">%</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">High blood pressure</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">36,6</td>
</tr>
<tr>
<td valign="top" align="left">Heart conditions</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">7,3</td>
</tr>
<tr>
<td valign="top" align="left">Arthritis, osteoarthritis or rheumatic conditions</td>
<td valign="top" align="center">11</td>
<td valign="top" align="center">26,8</td>
</tr>
<tr>
<td valign="top" align="left">Back ache</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">31,7</td>
</tr>
<tr>
<td valign="top" align="left">Asthma or COPD</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2,4</td>
</tr>
<tr>
<td valign="top" align="left">Diabetes</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">24,4</td>
</tr>
<tr>
<td valign="top" align="left">Urinary incontinence</td>
<td valign="top" align="center">14</td>
<td valign="top" align="center">35</td>
</tr>
<tr>
<td valign="top" align="left">High cholesterol</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">29,3</td>
</tr>
<tr>
<td valign="top" align="left">Depression</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">22,5</td>
</tr>
<tr>
<td valign="top" align="left">Anxiety disorder</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">7,3</td>
</tr>
<tr>
<td valign="top" align="left">Stroke, cerebral embolism, cerebral infarct or cerebral bleeding in the past</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
</tr>
<tr>
<td valign="top" align="left">Cancer (malignant tumours)</td>
<td valign="top" align="center">5</td>
<td valign="top" align="center">12,2</td>
</tr>
<tr>
<td valign="top" align="left">Osteoporosis</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">5</td>
</tr>
<tr>
<td valign="top" align="left">Thyroid disease</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2,4</td>
</tr>
<tr>
<td valign="top" align="left">Cognition (MMSE)</td>
<td valign="top" align="center">29 (Median)</td>
<td valign="top" align="center">5 (IQR)</td></tr>
</tbody>
</table>
</table-wrap>
<section class="lev2" id="sec9-4-1" label="9.4.1" xreflabel="9.4.1">
<title>Performance of the System</title>
<para>The assessment of the system performance was done considering and analysing the data received and stored in the REMPARK server.</para>
<para>One of the main problems that was detected in the system and that was widely repeated in many users is related to the communication structure of the BAN and the usage received from patients. REMPARK wearable system is composed of a smartphone, a wireless headset and the waist-worn movement sensor. Bluetooth is employed among them to communicate. More concretely, the movement sensor and smartphone communicate once per minute (every 60 seconds). In consequence, given the short-range reached by this type of communication, whenever patients placed the sensor and smartphone at a certain distance (e.g. in different rooms) communication could be lost. Some measures would not be received by the smartphone which, then, would not be received by the server. These periods of lost information were mainly addressed and analysed as an objective measurement of the system performance.</para>
<para>In order to distinguish them from those in which the sensor is turned off, it was used the first packet after the communication between the smartphone and the sensor is established, which contains specific values that make this situation recognisable.</para>
<para>The performance analysis process of the REMPARK system was organized according the following procedure. First, presenting a summary of the most relevant data sent and stored in the server during the pilots, distinguishing them according to the different sources and types of information. Then, data received in each day of the pilot were analysed in order to evaluate the performance of the system communications. In ideal conditions, in every minute during which the patient wore the system, the corresponding set of samples should be stored in the server.</para>
<para><link linkend="T9-4">Table <xref linkend="T9-4" remap="9.4"/></link> shows just a summary example of the kind of data stored in the REMPARK server. This table includes the source of the information (in this example, only data corresponding to the sensor and the smartphone are shown), a description of the variable (between parentheses, the internal code assigned to the variable in the database is appearing) and the amount of data samples for each variable stored in the server.</para>
<table-wrap position="float" id="T9-4">
<label><link linkend="T9-4">Table <xref linkend="T9-4" remap="9.4"/></link></label>
<caption><para>Example of data stored in the REMPARK server</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">Information Source</td>
<td valign="bottom" align="left">Information Variable</td>
<td valign="bottom" align="center">Quantity</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Movement sensor</td>
<td valign="top" align="left">BRADYKINESIA &#x02013; NUM STEPS (106)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">BRADYKINESIA &#x02013; BRADY MEAN (107)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">BRADYKINESIA &#x02013; BRADY STD (108)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">DYSKINESIA &#x02013; DISK PROBABILITY (110)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">DYSKINESIA &#x02013; DISK CONFIDENCE (111)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">FOG &#x02013; MAX_FI (112)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">ACTIVITY &#x02013; SMA (901)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">ACTIVITY &#x02013; CADENCE (902)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left">Smartphone</td>
<td valign="top" align="left">BRADYKINESIA (201)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">FREEZING OF GAIT (202)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">DYSKINESIA (203)</td>
<td valign="top" align="center">56955</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">TAP RESPONSE TIME MEAN (204)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;99</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">TAP RESPONSE TIME STD (205)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;99</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">LAST TAP RESPONSE TIME MEAN (206)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;99</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">LAST TAP RESPONSE TIME STD (207)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;99</td>
</tr>
<tr>
<td valign="top" align="left"></td>
<td valign="top" align="left">TAP TEST RESULT DECISION (208)</td>
<td valign="top" align="center">&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;&#x00A0;99</td></tr>
</tbody>
</table>
</table-wrap>
<para>Along the complete pilot execution, a total of 949 hours of raw data were stored in the system. This assumes that an average of 6.6 hours of raw data per user per day were collected. It is noted that this average number of monitoring hours is obtained on a minute basis, that is, the number of values in which the movement sensor sent information, meaning that missing values are not included.</para>
<para>In order to estimate the amount of missed data, it must be considered that if the sensor did not communicate with the smartphone during a given period of usage, missing packets are reflected with time intervals higher than 60 seconds. More concretely, it is considered that some packets have been missed when two consecutive movement-sensor measurements were received by the smartphone with more than 100 seconds of difference.</para>
<para>It was observed that some packets were lost in most patients (only in 5 patients there were not any missed packets). Moreover, it was calculated that the average number of missed packets was only of 6 minutes. Finally, the error rate was considered in terms of missed packets vs. total number of measurements received. According to this, <emphasis role="underline">it was observed that less than 4% of the packets were missed among all patients</emphasis>.</para>
<para>These missed short periods are not relevant since motor symptoms algorithms, require sensor measurements on a time interval of 60 minutes, allowing to have missing values in the analysed period, which means that these short-time missed packets do not influence the information provided to clinicians.</para>
<para>Given these considerations, <link linkend="T9-5">Table <xref linkend="T9-5" remap="9.5"/></link> provides the performance analysis of REMPARK system related to a very few patients participating in the pilot (shown patients are randomly selected from the complete set and must be considered only as an illustrative example).</para>
<table-wrap position="float" id="T9-5">
<label><link linkend="T9-5">Table <xref linkend="T9-5" remap="9.5"/></link></label>
<caption><para>Performance analysis of the REMPARK system (some examples)</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="center">Patient Number</td>
<td valign="bottom" align="center">ID</td>
<td valign="bottom" align="center">Number of Time Intervals of Missing Packets</td>
<td valign="bottom" align="center">Average Number of Missing Packets Per Time Interval</td>
<td valign="bottom" align="center">Number of Time Intervals > 10 min.</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="center">1</td>
<td valign="top" align="center">TEKNON 1</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2,67</td>
<td valign="top" align="center">0</td>
</tr>
<tr>
<td valign="top" align="center">2</td>
<td valign="top" align="center">TEKNON 2</td>
<td valign="top" align="center">18</td>
<td valign="top" align="center">10,55</td>
<td valign="top" align="center">6</td>
</tr>
<tr>
<td valign="top" align="center">16</td>
<td valign="top" align="center">MACC 1</td>
<td valign="top" align="center">37</td>
<td valign="top" align="center">19,74</td>
<td valign="top" align="center">8</td>
</tr>
<tr>
<td valign="top" align="center">24</td>
<td valign="top" align="center">FSL 1</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">3,28</td>
<td valign="top" align="center">0</td>
</tr>
<tr>
<td valign="top" align="center">25</td>
<td valign="top" align="center">FSL 2</td>
<td valign="top" align="center">11</td>
<td valign="top" align="center">7,64</td>
<td valign="top" align="center">2</td>
</tr>
<tr>
<td valign="top" align="center">34</td>
<td valign="top" align="center">NUIG 1</td>
<td valign="top" align="center">21</td>
<td valign="top" align="center">20,11</td>
<td valign="top" align="center">10</td>
</tr>
<tr>
<td valign="top" align="center">Total pilot average</td>
<td valign="top" align="center">&#x02013;</td>
<td valign="top" align="center">8,64</td>
<td valign="top" align="center">6,70</td>
<td valign="top" align="center">2,16</td>
</tr></tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec9-4-2" label="9.4.2" xreflabel="9.4.2">
<title>Validity of the ON-OFF Detection Algorithm</title>
<para>REMPARK system would be very useful enabling neurologists to adjust the medication regime based on detailed information of ON/OFF states fluctuations, which is provided in real-time by the wearable sensor sub-system (a waist-worn inertial sensor), with the concurrency of a smartphone. Final adjustment is then performed with the help of the specifically designed Disease Management System (DMS), which is a server-based service that allows neurologists, patients and caregivers to follow the disease evolution and communicate among them. This section presents the validation of the main objective of the REMPARK: the monitoring of ON/OFF motor fluctuations. The presented validation consists in the evaluation of the REMPARK system in detecting motor states in PD patients, who used the system over 4 consecutive days, as part of the described pilot.</para>
<section class="lev3" id="sec9-4-2-1" label="9.4.2.1" xreflabel="9.4.2.1">
<title>The methodology</title>
<para>The system assesses, in real-time, objective ON/OFF motor states based on the inertial signals given by the waist-worn device, treated with different machine learning algorithms that provide the presence or absence of specific symptoms, from which PD motor states are then determined. In the following part, the ON/OFF detection methodology is described.</para>
<para>Accelerometer measurements obtained by the waist-sensor are analysed with two different algorithms: a bradykinetic-gait detector [11] and a dyskinesia (choreic-dyskinesia) detector [12]. The bradykinetic-gait detector is based on the patients&#x02019; strides analyses, only after identifying that the patient is walking. Each stride is characterized by a measure of its fluidity: high fluidity measurements correspond to non-bradykinetic gait and vice-versa. On the other hand, the dyskinesia algorithm has two main outcomes: first, a probability value that represents the chances of having obtained the signals from a patient suffering dyskinesia and, second, a confidence value that represents the degree of certainty on such probability. The outputs of both algorithms on a period of T minutes are then processed.</para>
<para>The inferred motor state is ON when bradykinesia is not present in gait or when dyskinesia output is present. This is due to, on the one hand, a lack of symptomatic gait in ON states and, on the other hand, because of peak-dose dyskinesia detection, also is associated to ON states. OFF state is determined as the detection of bradykinesia and the absence of dyskinesia. Finally, the intermediate state is defined by an intermediate detection of the bradykinesia algorithm and lack of dyskinesia. A not evaluated (NE) state is provided in case of not detecting dyskinesia and if the patient did not walk in the period under analysis.</para>
<para>A final refinement is performed to the sequence of ON-OFF detections obtained from the evaluation of 10 consecutive 1-minute periods. Those periods determined as not NE are changed according to the following rules:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>If a NE period is found between two periods whose states are equal (either ON or OFF), that period is set to be the same state as adjacent periods.</para></listitem>
<listitem>
<para>If adjacent periods of an empty period correspond to different motor states, an intermediate state is then inserted.</para></listitem>
</itemizedlist>
</section>
<section class="lev3" id="sec9-4-2-2" label="9.4.2.2" xreflabel="9.4.2.2">
<title>Validation of the ON-OFF diaries: available data</title>
<para>As it was introduced in above Section 9.3.3, the only possible and available gold-standard for the validation of the ON and OFF states detection algorithms are the patients&#x02019; diaries with the self-reported states and all the inherent and already described inaccuracies. In order to stablish a methodology, two strategies were followed to ensure the validity of the gold-standard:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>First, the validity of motor state diaries was evaluated based on clinicians&#x02019; expertise through UPDRS. In each scale that clinicians administered, it was annotated the state in which the patient perceived to be. As it has been described in many works devoted to study the factors involved in UPDRS, scores obtained in OFF state are higher than the scores obtained in ON states [13]. Thus, the validity of the gold-standard has been evaluated based on an objective measure consisting in the correlation between UPDRS scores and motor states provided by patients at the moment of administration. Motor state is represented with 2 = OFF, 1 = Intermediate and 0 = ON, so positive correlations are expected. It is noted that, in some cases, negative correlations have been obtained. In order to also avoid those situations in which there is not any relation between UPDRS and the annotated motor state (i.e. nearly-zero correlation), patients whose correlation was lower than 0.20 were not included in the study since their ON/OFF diaries were considered not reliable enough to be used as gold-standard.</para></listitem>
<listitem>
<para>A second aspect taken into account is the timeframe during which annotations are valid. More concretely, in order to consider a motor state annotation to be valid, this motor state has to appear two consecutive times in the diary, being the time interval of 1 hour between both annotations its corresponding valid timeframe. In case the motor state changes between two consecutive annotations, both annotations are excluded from the analysis since the time in which the motor state changed cannot be established. Although this strategy reduces the number of annotations used from patients, it ensures that the annotations employed to validate the system are temporally reliable. Results obtained when this procedure is applied are presented under the name <emphasis>Strict diary.</emphasis> On the other hand, when this procedure is not applied, results obtained are reported as <emphasis>Original diary.</emphasis></para></listitem>
</itemizedlist>
<para>The complete validation of the ON/OFF detection algorithm requires the usage of the data stored in REMPARK server during the pilots, the ON/OFF diaries filled in by patients and the CRF&#x02019;s administered by clinicians. Finally used and useful data for these purposes were obtained from a total of 36 patients, after two drop-outs and the exclusion of 5 diaries due to incoherencies (15 patients administered by Teknon in Spain, 10 patients from Italy administered by FSL, 8 patients from Israel under the supervision of Maccabi and 3 patients from Ireland administered by NUIG).</para>
</section>
<section class="lev3" id="sec9-4-2-3" label="9.4.2.3" xreflabel="9.4.2.3">
<title>Results of the ON/OFF state detection</title>
<para>Among the initial 36 patients, data from 3 of them were removed due to a low correlation between UPDRS scores and the movement state reported by the patient (correlations were &#x02013;0.62, 0.06 and 0.2, respectively), as discussed in the previous section.</para>
<para><link linkend="T9-6">Table <xref linkend="T9-6" remap="9.6"/></link> presents the average results of REMPARK system in detecting motor states in the 33 patients under real-life conditions, being the system adjusted without using data from artificially induced OFF states. The average specificity and sensitivity achieved by the system in recognizing ON/OFF motor states is 89% and 98%, respectively. These values dramatically decrease when the described time ensuring is removed: specificity is 82% and sensitivity falls to 57%.</para>
<table-wrap position="float" id="T9-6">
<label><link linkend="T9-6">Table <xref linkend="T9-6" remap="9.6"/></link></label>
<caption><para>Average results according to the Original diary method and time-ensured method (Strict)</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">Validation Method</td>
<td valign="bottom" align="center">Average Specificity Per Patient</td>
<td valign="bottom" align="center">Average Sensitivity Per Patient</td>
<td valign="bottom" align="center">Average Number of Validated Hours Per Patient</td>
<td valign="bottom" align="center">Average Number of ON/OFF Monitoring Hours Per Patient</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Original diary</td>
<td valign="top" align="center">82%</td>
<td valign="top" align="center">57%</td>
<td valign="top" align="center">9.73</td>
<td valign="top" align="center">81.25</td>
</tr>
<tr>
<td valign="top" align="left">Strict diary</td>
<td valign="top" align="center">89%</td>
<td valign="top" align="center">98%</td>
<td valign="top" align="center">6.42</td>
<td valign="top" align="center">81.25</td>
</tr>
</tbody>
</table>
</table-wrap>
<para>In overall, the system generates an average of 35.3 hourly-based motor state detections per patient over the 4 days (11.8 hours in ON, 4.9 hours in OFF and 18.6 hours in an intermediate state). Thus, in average, for each of the four days, almost 9 hours of monitoring per day have been provided by the system.</para>
<para>Performance obtained by the system provides excellent results (sensitivity of 98% and specificity of 89%). Although the minimum sensitivity achieved is 75%, some specificity values are presented in the range of 50&#x02013;70%. The lowest values are obtained due to a very low number of validated estimations for some of the participating patients. It must be noted that <emphasis role="underline">in some cases validation was not possible due to a lack of annotations</emphasis>, which is noted with NE in both Specificity and Sensitivity (main reason was because patients did not fill in the diary).</para>
<para>Regarding the method used to set the thresholds of the bradykinetic-gait measurement algorithm, the distribution-based approach reveals to suitably set the algorithm parameters, according to the excellent results obtained. <emphasis role="underline">The novelty of this approach relies on the fact that the approach does not require any OFF-induced data</emphasis>. In contrast, other works such as [14] employ OFF-induced states, obtained by skipping medication intakes, to train machine learning algorithms. Following the method described here, patients would not be required to skip medication intakes to adjust the algorithms. Moreover, patients do not have to follow any specific set of scripted activities as in [14], either at home or in a lab, to particularize the detection method.</para>
<para>One of the main limitations of the system is that, in order to estimate the motor state, it requires the patient either to walk or to present choreic-dyskinesia. However, this is compensated by a reasonable high number of monitored hours with enough number of correct detections and a correct selection done for the kind of patients recruited (H&#x00026;Y greater than 2 and lower than 5 in OFF state). On the other hand, one of the main advantages of the motor states detection offered by REMPARK system is in the fact that the evaluation method only requires patients to wear a single sensor.</para>
</section>
</section>
<section class="lev2" id="sec9-4-3" label="9.4.3" xreflabel="9.4.3">
<title>Non-Motor Symptoms Descriptive Analysis</title>
<para>The REMPARK system was designed for the administration of questionnaires to the participants in the pilots [15], through the mobile phone interface. One of these questionnaires was a patient-based 30-points, used to determine the non-motor symptoms experienced by the patient during the past month. It had thirty items answered by the patient with a dichotomous answer: yes or no.</para>
<para>The following two questions were added to enquiry other non-motor symptoms:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para>Difficulty to speak.</para></listitem>
<listitem>
<para>Have you had unusually strong urges that are hard to control? Do you feel driven to do or think about something and find it hard to stop (Such gambling, cleaning, use the computer, obsessing about food or sex)?</para></listitem>
</itemizedlist>
<para>In addition to the standard dichotomous answers (yes or no), the REMPARK system was given the option of rating each symptom by using an analogical 10-points scale (0&#x02013;10).</para>
<para>All the 41 patients answered the non-motor symptoms questionnaire (NMSQ). Among them, 63.4% presented mild non-motor symptoms, 36.6% presented moderated non-motor symptoms and no patient had a result within the &#x0201C;severe&#x0201D; range of the questionnaire. The median of the questionnaire answers was 8 (over the 30 points) and IQR was 9.0.</para>
<para><link linkend="T9-7">Table <xref linkend="T9-7" remap="9.7"/></link> shows a random selection of answers (five of them) with the most frequent positive answer. In addition, the two new introduced questions are also shown.</para>
<table-wrap position="float" id="T9-7">
<label><link linkend="T9-7">Table <xref linkend="T9-7" remap="9.7"/></link></label>
<caption><para>Non-motor symptoms selected answers sorted by frequency</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">Question Number</td>
<td valign="bottom" align="left">Question Text</td>
<td valign="bottom" align="center">Positive (n)</td>
<td valign="bottom" align="center">Positive (%)</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">8</td>
<td valign="top" align="left">A sense of urgency to pass urine makes you rush to the toilet</td>
<td valign="top" align="center">27</td>
<td valign="top" align="center">69,5</td>
</tr>
<tr>
<td valign="top" align="left">9</td>
<td valign="top" align="left">Getting up regularly at night to pass urine</td>
<td valign="top" align="center">27</td>
<td valign="top" align="center">69,5</td>
</tr>
<tr>
<td valign="top" align="left">5</td>
<td valign="top" align="left">Constipation (less than 3 bowel movements a week) or having to strain to pass a stool (faeces)</td>
<td valign="top" align="center">17</td>
<td valign="top" align="center">41,5</td>
</tr>
<tr>
<td valign="top" align="left">12</td>
<td valign="top" align="left">Problems remembering things that have happened recently or forgetting to do things</td>
<td valign="top" align="center">17</td>
<td valign="top" align="center">41,5</td>
</tr>
<tr>
<td valign="top" align="left">15</td>
<td valign="top" align="left">Difficulty concentrating or staying focused</td>
<td valign="top" align="center">17</td>
<td valign="top" align="center">41,5</td>
</tr>
<tr>
<td valign="top" align="left">Added</td>
<td valign="top" align="left">Difficult to speech</td>
<td valign="top" align="center">26</td>
<td valign="top" align="center">63,4</td>
</tr>
<tr>
<td valign="top" align="left">Added</td>
<td valign="top" align="left">Have you had unusually strong urges that are hard to control? Do you feel driven to do or think about something and find it hard to stop (Such gambling, cleaning, use the computer, obsessing about food or sex)?</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4,9</td>
</tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev2" id="sec9-4-4" label="9.4.4" xreflabel="9.4.4">
<title>Efficacy and Effectiveness of the Cueing System</title>
<para>The efficacy of the cueing system to improve walk was tested by comparing the timed UP and GO test [16] with and without the cueing system activated, according the protocol of the study established in REMPARK.</para>
<para>The average time performing the timed UP &#x00026; GO (TUG) test with the cueing system activated was 25.8 seconds, and without the cueing system was 25.7 seconds. Thus, no significant or clinical difference was found.</para>
<para>Several sub-analyses selecting participants were performed with severe gait problems according their FOG questionnaire. Some improvement in the average time in completing the timed UP and GO test was found then, but it was still no significant from a statistical point of view. Results of these sub-analyses are shown in <link linkend="T9-8">Table <xref linkend="T9-8" remap="9.8"/></link>.</para>
<table-wrap position="float" id="T9-8">
<label><link linkend="T9-8">Table <xref linkend="T9-8" remap="9.8"/></link></label>
<caption><para>Results of the cueing systems for participants with severe gait problems</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left">FOG Questionnaire Filter&#x0002A;</td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">TUG with Cueing: Average Seconds</td>
<td valign="bottom" align="center">TUG without Cueing: Average Seconds</td>
<td valign="bottom" align="center">Mean Differences (seconds)</td>
<td valign="bottom" align="center">Comment</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Questions<?lb?>4 > 2</td>
<td valign="bottom" align="center">11</td>
<td valign="bottom" align="center">24,7</td>
<td valign="bottom" align="center">27,0</td>
<td valign="bottom" align="center">&#x02013;2,4</td>
<td valign="bottom" align="center">Ns</td>
</tr>
<tr>
<td valign="top" align="left">Questions<?lb?>5 &#x00026; 6 > 2</td>
<td valign="bottom" align="center">9</td>
<td valign="bottom" align="center">26,9</td>
<td valign="bottom" align="center">29,5</td>
<td valign="bottom" align="center">&#x02013;2,5</td>
<td valign="bottom" align="center">Ns</td>
</tr>
<tr>
<td valign="top" align="left">Questions<?lb?>4 or 5 or 6 > 2</td>
<td valign="bottom" align="center">16</td>
<td valign="bottom" align="center">24,5</td>
<td valign="bottom" align="center">26,0</td>
<td valign="bottom" align="center">&#x02013;1,5</td>
<td valign="bottom" align="center">Ns</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<para>&#x0002A;FOG questionnaire question 4 > 2: longest FOG episodes lasting > 10 seconds</para>
<para>&#x0002A;FOG questionnaire question 5 > 2: starting hesitation episodes lasting > 10 seconds</para>
<para>&#x0002A;FOG questionnaire question 6 > 2: turning hesitation episodes lasting > 10 seconds</para>
<para>Ns: no significant.</para>
</table-wrap-foot>
</table-wrap>
<para>The effectiveness of the ACS cueing system to improve walking problems was tested by comparing the results of two administered FOG questionnaires (before and after the REMPARK system testing). At the beginning of the pilots, participants answered the FOG questionnaire [6], which measures walking related problems (higher values in the results of this questionnaire means more severe gait problems), regarding the last 4&#x02013;5 days. After the pilot experiments, the participants answered again the same questionnaire, regarding the pilot days.</para>
<para>The mean of the FOG questionnaire before using the REMPARK system was 12.8 and after the use of REMPARK system was 12.3, not being the difference clinical or statistically significant. The results did not significantly change in the sub-group of patients with worse walking problems. Thus, <emphasis role="underline">we cannot conclude with the data obtained in the study that the cueing system of the REMPARK system helped the patients to reduce their walking problems in real conditions</emphasis>.</para>
</section>
</section>
<section class="lev1" id="sec9-5" label="9.5" xreflabel="9.5">
<title>Health-Safety of the REMPARK System</title>
<para>In all health interventions, there is a risk that intervention entailing unexpected negative effects that counteract the possible benefits from it. It is important to notice that, according to the operative definition, and adverse event is &#x0201C;<emphasis>any untoward medical occurrence, unintended disease or injury, or untoward clinical signs (including abnormal laboratory findings) in subjects, users or other persons, whether or not related to the investigational medical device</emphasis>&#x0201D;.</para>
<para>During the experimental time, 7 participants presented health &#x0201C;adverse events&#x0201D;, one of them had a &#x0201C;serious adverse event&#x0201D; consisting in condition deterioration that led to hospitalization. The most frequent adverse events were limbs pain (three cases) and depressive symptoms (3 cases); cervical pain was also reported (1 case). All adverse events, including the serious adverse event, were considered as &#x0201C;<emphasis>unrelated to the investigational device</emphasis>&#x0201D;.</para>
<para>In conclusion, <emphasis role="underline">we can&#x02019;t identify special health-risk associated with the use of the REMPARK system in this pilot</emphasis>, although the study timeline and the lack of comparison group makes difficult to detect any health-risk associated with the use of the system. Further studies on safety are warranted.</para>
</section>
<section class="lev1" id="sec9-6" label="9.6" xreflabel="9.6">
<title>Usability and User Satisfaction of the REMPARK System</title>
<para>The usability and user satisfaction with the system were measured by using two standard instruments: the System Usability Scale (SUS) [17] and the Assistive Device sub-scale of the Quebec User Evaluation of Satisfaction with Assistive Technologies (QUEST) [18].</para>
<para>The SUS is a 10 items Likert scale in which the respondent indicates the degree of agreement or disagreement with the statement on a 5-point scale (<link linkend="F9-8">Figure <xref linkend="F9-8" remap="9.8"/></link>). To calculate the SUS score, first the score contributions from each item are summed. Each item&#x02019;s score contribution ranges from 0 to 4. For items 1, 3, 5, 7 and 9 the score contribution is the scale position minus 1. For items 2, 4, 6, 8 and 10, the contribution is 5 minus the scale position. Finally, the sum of the scores is multiplied by 2.5 to obtain the overall value of SUS. SUS scores have a range of 0 to 100.</para>
<fig id="F9-8" position="float" xmlns:xlink="http://www.w3.org/1999/xlink">
<label><link linkend="F9-8">Figure <xref linkend="F9-8" remap="9.8"/></link></label>
<caption><para>System Usability Scale.</para></caption>
<graphic xlink:href="graphics/ch09_fig008.jpg"/>
</fig>
<para>Results over 50 are considered acceptable, and over 68&#x02013;70 are considered good [19, 20]. The median SUS score of the REMPARK system in the pilots was 70 (IQR 25).</para>
<para>The results can be considered good, according with standard interpretations of the scale. However, the results must be interpreted with caution, as the researchers administered themselves the SUS to the participants, who knew that the answers were not anonymous. This could have biased the results, because participants could have tried to please the researchers, offering a more positive vision of the usability than they would have given under anonymous circumstances.</para>
<para>Concerning the evaluation of user satisfaction, a subset of the QUEST questionnaire was used. The QUEST scale as it is described in [18] contains a number of items related to device characteristics and several questions related to the service characteristics. All the answers must be done according the following scale:</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>not satisfied at all</para></listitem>
<listitem>
<para>not very satisfied</para></listitem>
<listitem>
<para>more or less satisfied</para></listitem>
<listitem>
<para>quite satisfied</para></listitem>
<listitem>
<para>very satisfied</para></listitem>
</orderedlist>
<para>For evaluating REMPARK system, the 6 following items of the device subscale were used, together with a general question (number 7):</para>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>The dimensions (size, height, length, width) of your assistive device?</para></listitem>
<listitem>
<para>The weight of your assistive device?</para></listitem>
<listitem>
<para>The ease in adjusting (fixing, fastening) the parts of your assistive device?</para></listitem>
<listitem>
<para>How safe and secure your assistive device is?</para></listitem>
<listitem>
<para>The ease in using your assistive device?</para></listitem>
<listitem>
<para>The comfort of your assistive device?</para></listitem>
<listitem>
<para>What is your overall satisfaction with the assistive device?</para></listitem>
</orderedlist>
<para>Obtained results are shown in <link linkend="T9-9">Table <xref linkend="T9-9" remap="9.9"/></link>. The results can be considered good, being comfort the worst rated item and safety the best rated item. Overall satisfaction is good, being not satisfied 5% of the participants, and quite satisfied or very satisfied 75% of the users.</para>
<table-wrap position="float" id="T9-9">
<label><link linkend="T9-9">Table <xref linkend="T9-9" remap="9.9"/></link></label>
<caption><para>Results for the QUEST questionnaire</para></caption>
<table cellspacing="5" cellpadding="5" frame="hsides" rules="groups">
<thead>
<tr>
<td valign="bottom" align="left"></td>
<td valign="bottom" align="center" colspan="2">Not Satisfied At All<emphasis role="cline"/></td>
<td valign="bottom" align="center" colspan="2">Not Very Satisfied<emphasis role="cline"/></td>
<td valign="bottom" align="center" colspan="2">More or Less Satisfied<emphasis role="cline"/></td>
<td valign="bottom" align="center" colspan="2">Quite Satisfied<emphasis role="cline"/></td>
<td valign="bottom" align="center" colspan="2">Very Satisfied<emphasis role="cline"/></td></tr>
<tr>
<td valign="bottom" align="left"></td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">%</td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">%</td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">%</td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">%</td>
<td valign="bottom" align="center">n</td>
<td valign="bottom" align="center">%</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" align="left">Dimensions</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">7,3</td>
<td valign="top" align="center">10</td>
<td valign="top" align="center">24,4</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">32</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">36,6</td>
</tr>
<tr>
<td valign="top" align="left">Weight</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4,9</td>
<td valign="top" align="center">6</td>
<td valign="top" align="center">14,6</td>
<td valign="top" align="center">14</td>
<td valign="top" align="center">34</td>
<td valign="top" align="center">19</td>
<td valign="top" align="center">46,3</td>
</tr>
<tr>
<td valign="top" align="left">Ease in adjusting</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2,4</td>
<td valign="top" align="center">1</td>
<td valign="top" align="center">2,4</td>
<td valign="top" align="center">15</td>
<td valign="top" align="center">36,6</td>
<td valign="top" align="center">11</td>
<td valign="top" align="center">27</td>
<td valign="top" align="center">13</td>
<td valign="top" align="center">31,7</td>
</tr>
<tr>
<td valign="top" align="left">Safe</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">17,1</td>
<td valign="top" align="center">22</td>
<td valign="top" align="center">54</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">29,3</td>
</tr>
<tr>
<td valign="top" align="left">Ease in using</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4,9</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">19,5</td>
<td valign="top" align="center">22</td>
<td valign="top" align="center">54</td>
<td valign="top" align="center">9</td>
<td valign="top" align="center">22</td>
</tr>
<tr>
<td valign="top" align="left">Comfort</td>
<td valign="top" align="center">3</td>
<td valign="top" align="center">7,3</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4,9</td>
<td valign="top" align="center">11</td>
<td valign="top" align="center">26,3</td>
<td valign="top" align="center">18</td>
<td valign="top" align="center">44</td>
<td valign="top" align="center">7</td>
<td valign="top" align="center">17,1</td>
</tr>
<tr>
<td valign="top" align="left">Overall satisfaction</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">0</td>
<td valign="top" align="center">2</td>
<td valign="top" align="center">4,9</td>
<td valign="top" align="center">8</td>
<td valign="top" align="center">19,5</td>
<td valign="top" align="center">19</td>
<td valign="top" align="center">46</td>
<td valign="top" align="center">12</td>
<td valign="top" align="center">29,3</td>
</tr>
</tbody>
</table>
</table-wrap>
</section>
<section class="lev1" id="sec9-7" label="9.7" xreflabel="9.7">
<title>Summary and Conclusions</title>
<para>Forty-one (41) Parkinson Disease patients, under real conditions, participated in the test of the REMPARK system. Overall results show that the system has a good performance and reliability, with few data loss (4% of data), which does not impact the main information provided by the system, as it comes from several data slots, grouped and presented in 60 minutes&#x02019; periods.</para>
<para>The validity of the REMPARK system to detect motor fluctuations is very good. When all possible errors of the gold-standard timeline (the diary completed by the user) are excluded, by using the so called &#x0201C;<emphasis>strict method</emphasis>&#x0201D;, the sensitivity reaches 89% and specificity reaches 98%. These seems very good results, given the fact that they have been achieved in real life conditions, which are very demanding; in real life, there are many situations which could cause false positive or false negative detections. We consider this an important outcome, as it opens the door to a possible clinical use of the REMPARK system in the future.</para>
<para>The study has also demonstrated how difficult it is for patient to fill their diaries. In this respect, the REMPARK system constitutes a promising candidate to evaluate the correlation between the medication intake and the motor state in real life conditions. This can also constitute an invaluable help as a quantitative assessment instrument in clinical trials.</para>
<para>Additionally, during the REMPARK pilots, users could answer non-motor symptoms questionnaires using the mobile-phone interface. We did not measure the validity of this way of administration of questionnaires, but we really didn&#x02019;t expect a decrease in validity of the questionnaires when administered in this electronically way. This, again, suggested that the REMPARK system could be successfully used by clinicians, to remotely gather non-motor symptoms information from their patients.</para>
<para>Although the usefulness of the cueing system to improve gait in PD patients have been previously demonstrated by other groups, we failed to show any benefit of the REMPARK system in improving gait, during this specific pilot. No benefit was noticed when performing the timed Up and Go test under controlled conditions (efficacy), though a tendency to improvement was shown in the subgroup of patients with severe gait problems. These results did not reach statistical significance, possibly due to the small sample size, which pose problems of statistical power. In addition, the FOG questionnaire did not improve after using the system during the testing days (effectiveness). We think these results are inconclusive, as they were secondary outcomes of the pilot, which was not specifically designed to address these issues. If REMPARK system can improve gait problems or not, should be tested in longer experiments, specifically designed for measuring the effectiveness of the ACS sub-system.</para>
<para>The REMPARK system appeared to be safe, as no health adverse events were noticed, which could be related to the system. However, this result has to be interpreted with caution, as the small sample size and short observation period, pose again problems of power to detected adverse events. Safety of the system should be tested in additional research studies.</para>
<para>Finally, REMPARK system appears to be usable and participants seem to be satisfied with the system. Although this is a very encouraging conclusion, a possible bias in the usability results has to be taken into account, as the participants&#x02019; answers were not anonymous and the researchers where not blind to their answers.</para>
<para>Overall, we consider that the REMPARK system piloting was successful, demonstrating good performance and validity to detect motor fluctuations, and good usability characteristics. The system is prepared for further testing in its way to commercialization and medical use.</para>
</section>
<section class="lev1" id="sec9-8">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>A. J. Hughes, S. E. Daniel, L. Kilford, and a J. Lees, &#x0201C;Accuracy of clinical diagnosis of idiopathic Parkinson&#x02019;s disease: a clinico-pathological study of 100 cases.,&#x0201D; J. Neurol. Neurosurg. Psychiatry, vol. 55, no. 3, pp. 181&#x02013;184, Mar. 1992. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=A%2E+J%2E+Hughes%2C+S%2E+E%2E+Daniel%2C+L%2E+Kilford%2C+and+a+J%2E+Lees%2C+%22Accuracy+of+clinical+diagnosis+of+idiopathic+Parkinson%27s+disease%3A+a+clinico-pathological+study+of+100+cases%2E%2C%22+J%2E+Neurol%2E+Neurosurg%2E+Psychiatry%2C+vol%2E+55%2C+no%2E+3%2C+pp%2E+181-184%2C+Mar%2E+1992%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>M. M. Hoehn and M. D. Yahr, &#x0201C;Parkinsonism: onset, progression, and mortality. 1967.,&#x0201D; Neurology, vol. 57, no. 10 Suppl 3, pp. S11&#x02013;26, Nov. 2001. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+M%2E+Hoehn+and+M%2E+D%2E+Yahr%2C+%22Parkinsonism%3A+onset%2C+progression%2C+and+mortality%2E+1967%2E%2C%22+Neurology%2C+vol%2E+57%2C+no%2E+10+Suppl+3%2C+pp%2E+S11-26%2C+Nov%2E+2001%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>American Psychiatric Association. (2000). Diagnostic and statistical manual of mental disorders (4th ed., text rev.). Washington, DC: Author.</para></listitem>
<listitem>
<para>T. P. Fahn Stanley, Jenner Peter, Marsden C. David, Recent developments in Parkinson&#x02019;s disease. Florham Park, NJ: Macmillan, 1987, pp. 153&#x02013;163.</para></listitem>
<listitem>
<para>M. F. Folstein, S. E. Folstein, and P. R. McHugh, &#x0201C;Mini-mental state,&#x0201D; J. Psychiatr. Res., vol. 12, no. 3, pp. 189&#x02013;198, Nov. 1975. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=M%2E+F%2E+Folstein%2C+S%2E+E%2E+Folstein%2C+and+P%2E+R%2E+McHugh%2C+%22Mini-mental+state%2C%22+J%2E+Psychiatr%2E+Res%2E%2C+vol%2E+12%2C+no%2E+3%2C+pp%2E+189-198%2C+Nov%2E+1975%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>N. Giladi, J. Tal, T. Azulay, O. Rascol, D. J. Brooks, E. Melamed, W. Oertel, W. H. Poewe, F. Stocchi, and E. Tolosa, &#x0201C;Validation of the freezing of gait questionnaire in patients with Parkinson&#x02019;s disease.,&#x0201D; Mov. Disord., vol. 24, pp. 655&#x02013;661, 2009. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=N%2E+Giladi%2C+J%2E+Tal%2C+T%2E+Azulay%2C+O%2E+Rascol%2C+D%2E+J%2E+Brooks%2C+E%2E+Melamed%2C+W%2E+Oertel%2C+W%2E+H%2E+Poewe%2C+F%2E+Stocchi%2C+and+E%2E+Tolosa%2C+%22Validation+of+the+freezing+of+gait+questionnaire+in+patients+with+Parkinson%27s+disease%2E%2C%22+Mov%2E+Disord%2E%2C+vol%2E+24%2C+pp%2E+655-661%2C+2009%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>D. Podsiadlo and S. Richardson, &#x0201C;The timed &#x02018;Up &#x00026; Go&#x02019;: a test of basic functional mobility for frail elderly persons.,&#x0201D; J. Am. Geriatr. Soc., vol. 39, pp. 142&#x02013;148, 1991. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+Podsiadlo+and+S%2E+Richardson%2C+%22The+timed+%27Up+%26+Go%27%3A+a+test+of+basic+functional+mobility+for+frail+elderly+persons%2E%2C%22+J%2E+Am%2E+Geriatr%2E+Soc%2E%2C+vol%2E+39%2C+pp%2E+142-148%2C+1991%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>K. R. Chaudhuri, P. Martinez-Martin, A. H. V. Schapira, F. Stocchi, K. Sethi, P. Odin, R. G. Brown, W. Koller, P. Barone, G. MacPhee, L. Kelly, M. Rabey, D. MacMahon, S. Thomas, W. Ondo, D. Rye, A. Forbes, S. Tluk, V. Dhawan, A. Bowron, A. J. Williams, and C. W. Olanow, &#x0201C;International multicenter pilot study of the first comprehensive self-completed nonmotor symptoms questionnaire for Parkinson&#x02019;s disease: the NMSQuest study.,&#x0201D; Mov. Disord., vol. 21, no. 7, pp. 916&#x02013;23, Jul. 2006. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=K%2E+R%2E+Chaudhuri%2C+P%2E+Martinez-Martin%2C+A%2E+H%2E+V%2E+Schapira%2C+F%2E+Stocchi%2C+K%2E+Sethi%2C+P%2E+Odin%2C+R%2E+G%2E+Brown%2C+W%2E+Koller%2C+P%2E+Barone%2C+G%2E+MacPhee%2C+L%2E+Kelly%2C+M%2E+Rabey%2C+D%2E+MacMahon%2C+S%2E+Thomas%2C+W%2E+Ondo%2C+D%2E+Rye%2C+A%2E+Forbes%2C+S%2E+Tluk%2C+V%2E+Dhawan%2C+A%2E+Bowron%2C+A%2E+J%2E+Williams%2C+and+C%2E+W%2E+Olanow%2C+%22International+multicenter+pilot+study+of+the+first+comprehensive+self-completed+nonmotor+symptoms+questionnaire+for+Parkinson%27s+disease%3A+the+NMSQuest+study%2E%2C%22+Mov%2E+Disord%2E%2C+vol%2E+21%2C+no%2E+7%2C+pp%2E+916-23%2C+Jul%2E+2006%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. Brooke, &#x0201C;SUS &#x02013; A quick and dirty usability scale,&#x0201D; in Usability Evaluation in Industry, 1996, pp. 189&#x02013;194. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+Brooke%2C+%22SUS+-+A+quick+and+dirty+usability+scale%2C%22+in+Usability+Evaluation+in+Industry%2C+1996%2C+pp%2E+189-194%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Demers L., Weiss-Lambrou R., Ska B. Development of the Quebec User Evaluation of Satisfaction with assistive Technology (QUEST). Assist Technol. 1996; 8(1):3&#x02013;13. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Demers+L%2E%2C+Weiss-Lambrou+R%2E%2C+Ska+B%2E+Development+of+the+Quebec+User+Evaluation+of+Satisfaction+with+assistive+Technology+%28QUEST%29%2E+Assist+Technol%2E+1996%3B+8%281%29%3A3-13%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Rodr&#x00ED;guez-Molinero, A., Sam&#x00E0;, A., P&#x00E9;rez-Mart&#x00ED;nez, D. A., L&#x00F3;pez, C. P., et al. Validation of a Portable Device for Mapping Motor and Gait Disturbances in Parkinson&#x02019;s Disease. JMIR mHealth and uHealth, 3(1), e9, 2015. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Rodr%EDguez-Molinero%2C+A%2E%2C+Sam%E0%2C+A%2E%2C+P%E9rez-Mart%EDnez%2C+D%2E+A%2E%2C+L%F3pez%2C+C%2E+P%2E%2C+et+al%2E+Validation+of+a+Portable+Device+for+Mapping+Motor+and+Gait+Disturbances+in+Parkinson%27s+Disease%2E+JMIR+mHealth+and+uHealth%2C+3%281%29%2C+e9%2C+2015%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Sam&#x00E0;, A., P&#x00E9;rez-L&#x00F3;pez, C., Romagosa, J., Rodr&#x00ED;guez-Mart&#x00ED;n, D., Catal&#x00E0;, A., Cabestany, J., P&#x00E9;rez-Mart&#x00ED;nez, D.A., &#x00026; Rodr&#x00ED;guez-Molinero, A. Dyskinesia and motor state detection in Parkinson&#x02019;s Disease patients with a single movement sensor. In Engineering in Medicine and Biology Society (EMBC), 2012 Annual International Conference of the IEEE (pp. 1194&#x02013;1197). IEEE. August 2012, San Diego (CA, USA).</para></listitem>
<listitem>
<para>Vassar, S. D., Bordelon, Y. M., Hays, R. D., Diaz, N., Rausch, R., Mao, C., &#x00026; Vickrey, B. G. Confirmatory factor analysis of the motor unified Parkinson&#x02019;s disease rating scale. Parkinson&#x02019;s Disease, 2012. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Vassar%2C+S%2E+D%2E%2C+Bordelon%2C+Y%2E+M%2E%2C+Hays%2C+R%2E+D%2E%2C+Diaz%2C+N%2E%2C+Rausch%2C+R%2E%2C+Mao%2C+C%2E%2C+%26+Vickrey%2C+B%2E+G%2E+Confirmatory+factor+analysis+of+the+motor+unified+Parkinson%27s+disease+rating+scale%2E+Parkinson%27s+Disease%2C+2012%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Tzallas, A. T., Tsipouras, M. G., Rigas, G., Tsalikakis, D. G., Karvounis, E. C., Chondrogiorgi, M., Psomadellis F., Cancela J., Pastorino M., Arredondo Waldmeyer M. T., Konitsiotis S. and Fotiadis, D. I. PERFORM: A System for Monitoring, Assessment and Management of Patients with Parkinson&#x02019;s Disease. Sensors, 14(11), 21329&#x02013;21357, 2014. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Tzallas%2C+A%2E+T%2E%2C+Tsipouras%2C+M%2E+G%2E%2C+Rigas%2C+G%2E%2C+Tsalikakis%2C+D%2E+G%2E%2C+Karvounis%2C+E%2E+C%2E%2C+Chondrogiorgi%2C+M%2E%2C+Psomadellis+F%2E%2C+Cancela+J%2E%2C+Pastorino+M%2E%2C+Arredondo+Waldmeyer+M%2E+T%2E%2C+Konitsiotis+S%2E+and+Fotiadis%2C+D%2E+I%2E+PERFORM%3A+A+System+for+Monitoring%2C+Assessment+and+Management+of+Patients+with+Parkinson%27s+Disease%2E+Sensors%2C+14%2811%29%2C+21329-21357%2C+2014%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Romenets S. R., Wolfson C., Galatas C., Pelletier A., Altman R., Wadup L., Postuma R. B. Validation of the non-motor symptoms questionnaire (NMS-Quest). Parkinsonism RelatDisord. 2012 Jan; 18(1): 54&#x02013;8. doi: 10.1016/j.parkreldis.2011.08.013. Epub 2011 Sep 14. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Romenets+S%2E+R%2E%2C+Wolfson+C%2E%2C+Galatas+C%2E%2C+Pelletier+A%2E%2C+Altman+R%2E%2C+Wadup+L%2E%2C+Postuma+R%2E+B%2E+Validation+of+the+non-motor+symptoms+questionnaire+%28NMS-Quest%29%2E+Parkinsonism+RelatDisord%2E+2012+Jan%3B+18%281%29%3A+54-8%2E+doi%3A+10%2E1016%2Fj%2Eparkreldis%2E2011%2E08%2E013%2E+Epub+2011+Sep+14%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>D. Podsiadlo and S. Richardson, &#x0201C;The timed &#x02018;Up &#x00026; Go&#x02019;: a test of basic functional mobility for frail elderly persons.,&#x0201D; J. Am. Geriatr. Soc., vol. 39, pp. 142&#x02013;148, 1991. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=D%2E+Podsiadlo+and+S%2E+Richardson%2C+%22The+timed+%27Up+%26+Go%27%3A+a+test+of+basic+functional+mobility+for+frail+elderly+persons%2E%2C%22+J%2E+Am%2E+Geriatr%2E+Soc%2E%2C+vol%2E+39%2C+pp%2E+142-148%2C+1991%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>J. Brooke, &#x0201C;SUS &#x02013; A quick and dirty usability scale,&#x0201D; in Usability Evaluation in Industry, 1996, pp. 189&#x02013;194. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=J%2E+Brooke%2C+%22SUS+-+A+quick+and+dirty+usability+scale%2C%22+in+Usability+Evaluation+in+Industry%2C+1996%2C+pp%2E+189-194%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Demers L., Weiss-Lambrou R., Ska B. Development of the Quebec User Evaluation of Satisfaction with assistive Technology (QUEST). Assist Technol. 1996; 8(1):3&#x02013;13. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Demers+L%2E%2C+Weiss-Lambrou+R%2E%2C+Ska+B%2E+Development+of+the+Quebec+User+Evaluation+of+Satisfaction+with+assistive+Technology+%28QUEST%29%2E+Assist+Technol%2E+1996%3B+8%281%29%3A3-13%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Bangor A., Kortum P., Miller J. Determining What Individual SUS Scores Mean: Adding an Adjective Rating Scale. Journal of Usability Studies, 4(3) pp. 114&#x02013;123. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Bangor+A%2E%2C+Kortum+P%2E%2C+Miller+J%2E+Determining+What+Individual+SUS+Scores+Mean%3A+Adding+an+Adjective+Rating+Scale%2E+Journal+of+Usability+Studies%2C+4%283%29+pp%2E+114-123%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>System Usability Scale (SUS): http://www.usability.gov/how-to-and-tools/methods/system-usability-scale.html Accessed May 27th 2015. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=System+Usability+Scale+%28SUS%29%3A+http%3A%2F%2Fwww%2Eusability%2Egov%2Fhow-to-and-tools%2Fmethods%2Fsystem-usability-scale%2Ehtml+Accessed+May+27th+2015%2E" target="_blank">Google Scholar</ulink></para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="chapter" id="ch10" label="10" xreflabel="10">
<title>Epilogue and Some Conclusions</title>
<para role="author"><emphasis role="strong">Roberta Annicchiarico<superscript><emphasis role="strong">1</emphasis></superscript>, Angels Bay&#x00E9;s<superscript><emphasis role="strong">2</emphasis></superscript> and Joan Cabestany<superscript><emphasis role="strong">3</emphasis></superscript></emphasis></para>
<para><superscript>1</superscript>IRCCS Fondazione Santa Lucia (FSL), Rome, Italy</para>
<para><superscript>2</superscript>Centro M&#x00E9;dico Teknon &#x2013; Grupo Hospitalario Quir&#x00F3;n, Parkinson Unit, Barcelona, Spain</para>
<para><superscript>3</superscript>Universitat Polit&#x00E8;cnica de Catalunya &#x2013; UPC, CETpD &#x2013; Technical Research Centre for Dependency Care and Autonomous Living, Vilanova i la Geltr&#x00FA; (Barcelona), Spain</para>
<section class="lev1" id="sec10-1" label="10.1" xreflabel="10.1">
<title>Summary of PD Symptoms and the Influence on QoL</title>
<para>As it was extensively presented along Chapters 1 and 2, Parkinson&#x02019;s Disease (PD) is a major, chronic, non-communicable disease and the second most frequent neurodegenerative disorder worldwide. There is currently no cure for PD, but treatments are available to help relieve the symptoms and maintain individual&#x02019;s Quality of Life (QoL) at least for the first years.</para>
<para>It has been already debated the impact on the QoL of the Parkinson&#x02019;s Disease due to an enormous number of motor and non-motor symptoms: bradykinesia, rigidity, tremor, postural instability, reduced gait speed, freezing of gait, sleep disturbances, depression, psychosis, autonomic and gastrointestinal dysfunction as well as dementia. As already explained, the majority of patients will develop an increasing number of more complex symptoms over time.</para>
<para>The treatment in the early stages of the disease, focused on the use of levodopa in pills, is very effective. Nevertheless, different problems related with the treatment may start to appear depending on the advance of the disease. Thus, it might be the case of motor complications: motor fluctuations such as the wearing-off phenomenon, involuntary movements known as dyskinesia, abnormal cramps and postures of the extremities and trunk known as dystonia, and a variety of complex fluctuations in other motor and non-motor functions. In these cases, the correct adjustment of the therapy is crucial for avoiding to decrease the QoL of the patient. The motor symptoms are especially responsible of falls and gait impairments and negatively impact on QoL by reducing the ability to perform many activities of daily living. They are the major causes of institutionalisation and to lose the capability to live independently. Daily tasks at home: self-care, food preparation, hygiene, become difficult, as do many activities outside the home (shopping, visiting friends/family, leisure activities &#x02026;).</para>
<para>The global management of this disease has to be based on a simultaneous treatment and consideration of different symptoms that usually are treated in different by different specialists. Unfortunately, many times no integration between data is made and there is a lack of information about the overall condition of the patient and, furthermore, there is not enough communication between the healthcare professionals treating the patient.</para>
<para>REMPARK system, discussed along the present document is a good example of the recent advances in technologies for people with neurological diseases, focused on the development and validation of tools, techniques and overall solutions for the effective management of PD. The system exhibits the combination of two technologies that promise to radically change the daily management of PD: the so-called wearables technology (WT) and the machine-learning based algorithmic approach. These technologies can provide objective, high frequency, sensitive and continuous data on motor and non-motor phenomena in PD. Thanks to the technology, it is possible to solve one on the major existing problem: the data acquisition over a continuous time period. An important aspect of a WT system is that it allows remote monitoring of symptoms with its obvious potential advantage for patients and health economics.</para>
</section>
<section class="lev1" id="sec10-2" label="10.2" xreflabel="10.2">
<title>Existing Barriers of PD Management</title>
<para>In order to preserve their quality of life and allow them to live independently for longer while experiencing their burdens, PD patients fully resort on tailored treatments that can address the symptoms as they appear or prevent/delay the onset of other symptoms and co-morbidities. Emerging systems, like REMPARK, try to improve the efficacy of disease management and treatments in the current clinical practice that presents the following major obstacles:</para>
<itemizedlist mark="bullet" spacing="normal">
<listitem>
<para><emphasis role="strong">Barrier 1: Lack of accuracy and completeness when reporting about own symptoms.</emphasis> Due to the cognitive impairments, distress or the evasive nature of some of the symptoms caused by PD, the patients often find difficulties or lack sufficient ability to provide reliable/consistent clinically relevant information about the symptoms they experience in order to optimise the treatment. In particular, often the patients are not aware of the onset of dyskinesia and sometimes it is even difficult for them to distinguish between ON/OFF periods. However, these are key information items for the doctor to adjust the treatments.</para></listitem>
<listitem>
<para><emphasis role="strong">Barrier 2: Missing information about the PD symptoms and signs of disease progression at clinical level.</emphasis> The current available means to report and monitor the symptoms are modest as compared to the huge challenge posed by the variety of PD symptoms and their fluctuations. The patient&#x02019;s visits and self-reporting may not throw reliable or complete evidence for the physician to cope with the entire picture and overall phenomena surrounding their patient&#x02019;s day-to-day. Most of the evidence used builds on reporting provided by the same patients and they often lack the ability to undertake this task.</para></listitem>
<listitem>
<para><emphasis role="strong">Barrier 3: Compromised self-care and adherence to treatments.</emphasis> Treatment regimens (medications, times, doses) and adherence to treatment are crucial for a correct PD management and the QoL of the patients. PD patients resort to prescribed regimes, but this seemingly simple commitment may represent a non-trivial feat, since patients must add on top of the overall burden the challenge of self-care, which is often difficult to achieve due to the many impairments and distresses linked to the disease. Cognitive deficits such as attention, communication, memory, and executive functions; depression and impulsive behaviours play a key role in the common lack of adherence and self-efficacy in co-management of the disease.</para></listitem>
<listitem>
<para><emphasis role="strong">Barrier 4: Symptoms recognition in time to better administrate the medication dose.</emphasis> Another related barrier is the capability of the professional to properly assess the number of OFF hours the patient has experienced to judge, based on that information, the therapeutic effect of the administered therapy, since it is based on daily or patient recall. Thus, the practitioner has difficulties for adjusting the continuous dose and control the administration of extra doses, mainly when an infusion pump therapy is used.</para></listitem>
<listitem>
<para><emphasis role="strong">Barrier 5: Usability from the patient&#x02019;s point of view.</emphasis> Some patients with Parkinson&#x02019;s have OFF phases so severe that they cannot even self-administrate extra doses. Patients with severe OFFs, which have no caregivers who can perform this task for them, often cannot choose the treatment with continuous infusion pumps.</para></listitem>
</itemizedlist>
</section>
<section class="lev1" id="sec10-3" label="10.3" xreflabel="10.3">
<title>The Role of the REMPARK System in the Context</title>
<para>REMPARK system was proposed and has been developed as a personal health system for the remote and autonomous management of PD. It is composed of wearable sensors for the detection and measurement of motor symptoms, a high level analytical layer and decision support tool, and a care platform (DMS) for professional care providers, patients and family. It enables the real-time, continuous and quantitative identification of the patient&#x02019;s motor symptoms in ambulatory conditions. The novelty and added value of REMPARK relies on using just one inertial sensor located and fixed to the patient&#x02019;s waist and a mobile interface to constantly read and send to the remote server a wealth of key relevant motor symptoms related to PD.</para>
<para>After symptoms&#x02019; identification, the system is also able to provide some degree of actuation, like gait guidance mainly with an auditory cueing system, automatic fall detection and alarms, and assistance for self-management during daily life activities. Further development of the system should also include an automatic control of an infusion pump for a more accurate dosage or a delivery of an extra dose, when necessary.</para>
<para>The remote computing platform underneath REMPARK provides automatic data storage, processing, analysis and visualization tool so that other relevant actors, doctors and caregivers, can be included in the loop and can provide the best-informed, evidence-based and personalized action for therapy and healthcare management. In particular, REMPARK can be used to extract indicators of the disease evolution and open the possibility of a better adjust of the medication and treatments.</para>
<para>One of the main advantages of REMPARK is its alignment with the actual evolution of the care models, that are moving from reactive to proactive approach. The strength of the system relies on the ability to obtain, analyse and integrate data from different sources: sensors, patient reported data and healthcare professionals.</para>
<para>The system is able to receive the data transmitted from the sensors. For each individual patient, it is possible to define a range of normal values, permitting to stablish some levels of alarms according the thresholds defined by the professionals. Any deviation from normal event creates an alert on the system and consequently there is a reactive intervention. The DMS includes a shift management module that manages the tasks and users that are at each shift. The shift manager can see the workload and type of activities done in the centre for efficient management of the care process.</para>
<para>The REMPARK system is an interesting solution that includes a wide range of functionalities for delivering comprehensive and customizable integrated care by a multidisciplinary team, but it also enables the treating physician to maintain a supervision of the patient throughout the journey; from patient disease diagnosis, through treatment plan definition, customizing specific protocols. One of the main problem in most existing systems for disease management is that the patient&#x02019;s data used for treatment is collected on the system overtime and is not updated by other systems that are used for treating the patient. This problem is particularly relevant when the patients are affected by a multimorbidity.</para>
<para>Multimorbidity is commonly defined as the presence of two or more chronic medical conditions in an individual and it can present several challenges in care particularly with higher numbers of coexisting conditions and related polypharmacy. For this reason the patient is treated by the neurologist for the PD and in parallel he is treated by the general physician in the community for other health conditions. Typically, a completeintegration between data doesn&#x02019;t exist and there is a lack of information about the overall condition of the patient. Furthermore, the communication between the healthcare professionals treating the patient is quite limited. This way of delivering care results in a fragmentation, some duplication and lacks of coordination.</para>
<para>REMPARK, offers an integrated environment for data and knowledge sharing for all care providers and also it provides clinical guidelines and a decision support tool for healthcare providers helping in management of patient&#x02019;s disease. This tool enables treating several conditions at the same time in a coordinated way avoiding the interaction among drugs and the negative impact on the patients compliance.</para>
<para>Another additional value is the available integrated platform, allowing the stablishement of improved communication channels among patients and professionals (doctor, nurse, etc.)</para>
<para>Some advantages for the patients are the increase of their treatment performance scores, the improvement of the patients&#x02019; empowerment and a good degree of satisfaction.</para>
</section>
<section class="lev1" id="sec10-4" label="10.4" xreflabel="10.4">
<title>Limitations of the REMPARK System</title>
<para>The characteristics and advantages of REMPARK system would contribute, for sure, to the mitigation of the barriers analysed in the Section 10.2. It is obvious that some limitations exist, and because a main part of REMPARK is the sensor (a wearable device) for the detection and measurement of the motor symptoms related with PD, part of the inherent limitations are in line with those of different wearable products developed for their use in e-Health domains.</para>
<para>There is a need to improve the cost-to-benefit ratio of WT strategies and their effectiveness for chronic disease and rehabilitation therapy management. Innovative research is still needed to continue developing the best combination of wellness, special needs and technologies in order to assist and maintain the preferred QoL for individuals with chronic disabilities and older adults.</para>
<para>A further limitation is the need of a refinement of the technology to correctly measure and monitoring non-motor symptomatology of the disease. Patient priorities and sources of disability often arise from non-motor deficits, such as: depression, anxiety, fatigue, orthostatic hypotension, sleep disturbance. There is a need for developing unobtrusive systems to monitor non-motor end points in the home environments and community settings. As it has been presented along the chapters, REMPARK was designed as a complete system, where in a limited way, the consideration of the non-motor symptoms was already included and worked-on. Further versions of REMPARK system must, for sure, consider and emphasize these aspects.</para>
<para>Usability of the REMPARK system was a challenge from the beginning of the project and quite good results are reported in <link linkend="ch09">Chapter <xref linkend="ch9" remap="9"/></link>. A problem that the consortium was working-on and tried to solve is the PD patient&#x02019;s adapted smartphone interface. The special adapted interface (see <link linkend="ch06">Chapter <xref linkend="ch6" remap="6"/></link>) is a good point for the usability and acceptability of the system.</para>
<para>After the REMPARK project finalization, relevant experiences would be used for an improved version of the different parts of the system, but always some common issues related with the acceptability of wearables in general would be encountered.</para>
<para>Systems are often not as user friendly or compelling to adopt as they should be. Currently, patient and care giver engagement with wearable and mobile technology is modest, as shown by recent studies.</para>
<para>A lack of motivation to use wearables and monitoring systems should not be underestimated, particularly in the absence of meaningful feedback provided to their users. Preliminary evidence suggests that patient empowerment and their inclusion as active players in the development of research activities may favourably impact on compliance. As a preliminary conclusion, it could be stablished that additional research is needed to determine the characteristics and the feasibility of wearable systems for long-term monitoring of motor and non-motor symptoms that would be acceptable to patients.</para>
</section>
<section class="lev1" id="sec10-5" label="10.5" xreflabel="10.5">
<title>Clinical Applicability of the REMPARK System</title>
<para>The power and usefulness of the devices and systems based on ICT technologies are still under-recognized by a part of the physicians and professionals participating in the treatment and management of the PD patients. Its potential, considered as an aid to the patients, is also under-exploited.</para>
<para>In the case of REMPARK, the system is based on non-obtrusive elements worn by the patient: the waist inertial sensor, a smartphone and an auditory cueing system. The elements seamlessly communicate with each other and with the server platforms providing further service and capabilities. REMPARK is an interoperable standalone solution that can be easily integrated in Hospital Management Systems and external eHealth services operated by third parties.</para>
<para>The REMPARK system core is a sensor device placed on the patient&#x02019;s waist that it is able, as it has been already explained, to identify and quantify the main motor symptoms of PD (bradykinesia, dyskinesia and FOG) in real time. This sensor also recognizes and registers the patient&#x02019;s motor fluctuations (ON and OFF motor states) in ambulatory conditions in a very reliable and automatic way while patients are performing their normal activities. Finally, the device wirelessly transmits this information to a server.</para>
<para>Furthermore, the use of these devices with the described characteristics would enable the doctors to accurately personalize medication intakes and, thus, improve the patient&#x02019;s response to the treatment. A system with the REMPARK characteristics would result an invaluable tool in the diagnosis and management of PD. A correct detection of the symptoms would help to, on one hand, enhance the effectiveness of the oral medication through a better regimen adjustment; on the other hand, to automatically control the administration of an extra dose when the patients are using infusion pumps (apomorphine or duodopa). These new approaches are aimed at significantly improve the QoL of patients and, it will allow a deeper understanding of the personalized evolution of the disease.</para>
<para>An additional benefit is represented by the contribution of the system to the real and effective implementation of a multidisciplinary care. In fact, clinical experience suggests that optimal management requires a multidisciplinary approach, with multifactorial health plans tailored to the needs of each individual patient. In case of PD patients, the multidisciplinary team includes physiotherapists, occupational and speech-language therapists, dieticians and social workers.</para>
<para>The use of systems highly based on ICT technology, like REMPARK, contributes to alleviate and facilitate the organization of the multidisciplinary approach improving communication between the different health professionals, the patients and the caregiver.</para>
<para>Another area that would benefit from a tool, like the sensor developed in REMPARK is the clinical and epidemiological research. This kind of studies are expensive and highly laborious. Sometimes, they suffer economic limitations that can affect the methodological rigor of the studies carried out. In general, the studies based on movement disorders are especially complicated, on the one hand by the lack of well-established markers to establish a clear diagnosis and, on the other hand, by the lack of uniformity in diagnostic criteria.</para>
<para>Finally, it must be pointed out that REMPARK system technological innovation can be an interesting challenge for companies developing business based on the commercialization of new e-health home based services for PD patients. Such tools would provide the unique opportunity to objectively monitor and control the treatment efficacy of any given therapy on an individual basis, which would sustainably change traditional health care methods.</para>
</section>
<section class="lev1" id="sec10-6" label="10.6" xreflabel="10.6">
<title>As a Concluding Remark</title>
<para>We can conclude that REMPARK system is a big step to a new approach to a new approach of the PD treatment where the technology contribution is helping to provide a different and complimentary view of the symptoms of the disease by offering clinicians a complete map and evolution.</para>
<para>The provided information will not only be useful from a diagnosis but rather would contribute to a better and more effective management of the disease.</para>
<para>This kind of systems, when completely developed, will be relevant because the possible supervision and measurement of the evolution of the symptoms and the appearance of new ones. This will permit a rapid action when necessary, facilitating among others the establishment of preventive polices according patients&#x02019; individual needs.</para>
</section>
<section class="lev1" id="sec10-7">
<title>References</title>
<orderedlist numeration="arabic" continuation="restarts" spacing="normal">
<listitem>
<para>Chang P. Wray L. Lin Y. Social Relationships, Leisure Activity, and Health in Older Adults, Health Psychology, American Psychological Association, 2014, Vol. 33, No. 6, 516&#x02013;523. <ulink url="https://scholar.google.com/scholar?hl=en&amp;q=Chang+P%2E+Wray+L%2E+Lin+Y%2E+Social+Relationships%2C+Leisure+Activity%2C+and+Health+in+Older+Adults%2C+Health+Psychology%2C+American+Psychological+Association%2C+2014%2C+Vol%2E+33%2C+No%2E+6%2C+516-523%2E" target="_blank">Google Scholar</ulink></para></listitem>
<listitem>
<para>Wallace E. et al., Managing patients with multimorbidity in primary care. BMJ 2015;350:h176.</para></listitem>
</orderedlist>
</section>
</chapter>
<chapter class="nosec" id="ch11">
<title>About the Editors</title>
<para><emphasis role="strong">Joan Cabestany</emphasis> holds a Telecommunications Engineer degree (1976) from the Universitat Polit&#x00E8;cnica de Catalunya (UPC) in Barcelona, Spain. He got his PhD (1982) from the same University, where he is working as a Full-time Professor in the Department of Electronic Engineering.</para>
<para>He has been involved in research and innovation activities as a part of his career. He is the responsible member of the AHA (&#x0201C;Advanced Hardware Architectures&#x0201D;) research group at UPC, with expertise on reconfigurable hardware, electronic system design, advanced hardware architectures, microelectronics, and VLSI design. One of the main topics of interest has been the practical application of the Artificial Intelligence to the functional improvement of electronic systems.</para>
<para>He is a member of the CETpD Research Center staff structure at UPC since 2005. The activities of CETpD are focused on technological developments applied to the improvement and help people with chronic diseases, like Parkinson Disease and different conditions related with aging.</para>
<para>On behalf of UPC, Prof. Cabestany has been responsible for several EU-funded projects. Among them, the REMPARK project on PD management and the FATE project for the accurate detection of falls in aging people are the two projects, where Prof. Cabestany has been acting as coordinator. He is the co-author for more than 100 research papers and communications to Conferences. Prof. Cabestany is a co-founder of the Sense4Care Company (www.sense4care.com), a Spin-off of the UPC commercializing relevant innovative research results.</para> 
<para><emphasis role="strong">Angels Bay&#x00E9;s Rusi&#x00F1;ol</emphasis> MD is a Doctor in Medicine and Neurology specialist. Her career and research activity has been focused on the study and treatment of Movement Disorders like Parkinson&#x02019;s Disease (PD) and Tourette syndrome, and on dementias, like Alzheimer&#x02019;s disease.</para>
<para>She has been the director of the Unit for Movement Disorders and Parkinson of TEKNON Medical Center in Barcelona (Spain) during the last 20 years.</para>
<para>Her main research areas are related to the implementation of complete treatment, complementary therapies, psycho-education, and to try to improve the quality of life of patients suffering from movement disorders. During the last 5 years, she has been cooperating with an engineering team at Universitat Polit&#x00E8;cnica de Catalunya, in Barcelona, for the development and implementation of technological solutions for the support and management of PD.</para>
<para>She has participated in 39 research projects, with special mention of the EU funded EDUPARK and REMPARK ones. She has authored more than 60 publications, including 6 books, many conferences, communications, and training courses.</para>
</chapter>
</book>
