A Data Encryption Solution for Mobile Health Apps in Cooperation Environments
Identifieur interne : 000479 ( Pmc/Corpus ); précédent : 000478; suivant : 000480A Data Encryption Solution for Mobile Health Apps in Cooperation Environments
Auteurs :Source :
- Journal of Medical Internet Research [ 1439-4456 ] ; 2013.
Abstract
Mobile Health (mHealth) proposes health care delivering anytime and anywhere. It aims to answer several emerging problems in health services, including the increasing number of chronic diseases, high costs on national health services, and the need to provide direct access to health services, regardless of time and place. mHealth systems include the use of mobile devices and apps that interact with patients and caretakers. However, mobile devices present several constraints, such as processor, energy, and storage resource limitations. The constant mobility and often-required Internet connectivity also exposes and compromises the privacy and confidentiality of health information.
This paper presents a proposal, construction, performance evaluation, and validation of a data encryption solution for mobile health apps (DE4MHA), considering a novel and early-proposed cooperation strategy. The goal was to present a robust solution based on encryption algorithms that guarantee the best confidentiality, integrity, and authenticity of users health information. In this paper, we presented, explained, evaluated the performance, and discussed the cooperation mechanisms and the proposed encryption solution for mHealth apps.
First, we designed and deployed the DE4MHA. Then two studies were performed: (1) study and comparison of symmetric and asymmetric encryption/decryption algorithms in an mHealth app under a cooperation environment, and (2) performance evaluation of the DE4MHA. Its performance was evaluated through a prototype using an mHealth app for obesity prevention and cares, called SapoFit. We then conducted an evaluation study of the mHealth app with cooperation mechanisms and the DE4MHA using real users and a real cooperation scenario. In 5 days, 5 different groups of 7 students selected randomly agreed to use and experiment the SapoFit app using the 7 devices available for trials.
There were 35 users of SapoFit that participated in this study. The performance evaluation of the app was done using 7 real mobile devices in 5 different days. The results showed that confidentiality and protection of the users’ health information was guaranteed and SapoFit users were able to use the mHealth app with satisfactory quality. Results also showed that the app with the DE4MHA presented nearly the same results as the app without the DE4MHA. The performance evaluation results considered the probability that a request was successfully answered as a function of the number of uncooperative nodes in the network. The service delivery probability decreased with the increase of uncooperative mobile nodes. Using DE4MHA, it was observed that performance presented a slightly worse result. The service average was also slightly worse but practically insignificantly different than with DE4MHA, being considered negligible.
This paper proposed a data encryption solution for mobile health apps, called DE4MHA. The data encryption algorithm DE4MHA with cooperation mechanisms in mobile health allow users to safely obtain health information with the data being carried securely. These security mechanisms did not deteriorate the overall network performance and the app, maintaining similar performance levels as without the encryption. More importantly, it offers a robust and reliable increase of privacy, confidentiality, integrity, and authenticity of their health information. Although it was experimented on a specific mHealth app, SapoFit, both DE4MHA and the cooperation strategy can be deployed in other mHealth apps.
Url:
DOI: 10.2196/jmir.2498
PubMed: 23624056
PubMed Central: 3636327
Links to Exploration step
PMC:3636327Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">A Data Encryption Solution for Mobile Health Apps in Cooperation Environments</title>
</titleStmt>
<publicationStmt><idno type="wicri:source">PMC</idno>
<idno type="pmid">23624056</idno>
<idno type="pmc">3636327</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3636327</idno>
<idno type="RBID">PMC:3636327</idno>
<idno type="doi">10.2196/jmir.2498</idno>
<date when="2013">2013</date>
<idno type="wicri:Area/Pmc/Corpus">000479</idno>
<idno type="wicri:explorRef" wicri:stream="Pmc" wicri:step="Corpus" wicri:corpus="PMC">000479</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">A Data Encryption Solution for Mobile Health Apps in Cooperation Environments</title>
</analytic>
<series><title level="j">Journal of Medical Internet Research</title>
<idno type="ISSN">1439-4456</idno>
<idno type="eISSN">1438-8871</idno>
<imprint><date when="2013">2013</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass></textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en"><sec sec-type="background"><title>Background</title>
<p>Mobile Health (mHealth) proposes health care delivering anytime and anywhere. It aims to answer several emerging problems in health services, including the increasing number of chronic diseases, high costs on national health services, and the need to provide direct access to health services, regardless of time and place. mHealth systems include the use of mobile devices and apps that interact with patients and caretakers. However, mobile devices present several constraints, such as processor, energy, and storage resource limitations. The constant mobility and often-required Internet connectivity also exposes and compromises the privacy and confidentiality of health information.</p>
</sec>
<sec sec-type="objective"><title>Objective</title>
<p>This paper presents a proposal, construction, performance evaluation, and validation of a data encryption solution for mobile health apps (DE4MHA), considering a novel and early-proposed cooperation strategy. The goal was to present a robust solution based on encryption algorithms that guarantee the best confidentiality, integrity, and authenticity of users health information. In this paper, we presented, explained, evaluated the performance, and discussed the cooperation mechanisms and the proposed encryption solution for mHealth apps.</p>
</sec>
<sec sec-type="methods"><title>Methods</title>
<p>First, we designed and deployed the DE4MHA. Then two studies were performed: (1) study and comparison of symmetric and asymmetric encryption/decryption algorithms in an mHealth app under a cooperation environment, and (2) performance evaluation of the DE4MHA. Its performance was evaluated through a prototype using an mHealth app for obesity prevention and cares, called SapoFit. We then conducted an evaluation study of the mHealth app with cooperation mechanisms and the DE4MHA using real users and a real cooperation scenario. In 5 days, 5 different groups of 7 students selected randomly agreed to use and experiment the SapoFit app using the 7 devices available for trials.</p>
</sec>
<sec sec-type="results"><title>Results</title>
<p>There were 35 users of SapoFit that participated in this study. The performance evaluation of the app was done using 7 real mobile devices in 5 different days. The results showed that confidentiality and protection of the users’ health information was guaranteed and SapoFit users were able to use the mHealth app with satisfactory quality. Results also showed that the app with the DE4MHA presented nearly the same results as the app without the DE4MHA. The performance evaluation results considered the probability that a request was successfully answered as a function of the number of uncooperative nodes in the network. The service delivery probability decreased with the increase of uncooperative mobile nodes. Using DE4MHA, it was observed that performance presented a slightly worse result. The service average was also slightly worse but practically insignificantly different than with DE4MHA, being considered negligible.</p>
</sec>
<sec sec-type="conclusions"><title>Conclusions</title>
<p>This paper proposed a data encryption solution for mobile health apps, called DE4MHA. The data encryption algorithm DE4MHA with cooperation mechanisms in mobile health allow users to safely obtain health information with the data being carried securely. These security mechanisms did not deteriorate the overall network performance and the app, maintaining similar performance levels as without the encryption. More importantly, it offers a robust and reliable increase of privacy, confidentiality, integrity, and authenticity of their health information. Although it was experimented on a specific mHealth app, SapoFit, both DE4MHA and the cooperation strategy can be deployed in other mHealth apps.</p>
</sec>
</div>
</front>
<back><div1 type="bibliography"><listBibl><biblStruct><analytic><author><name sortKey="Le Moullee, B" uniqKey="Le Moullee B">B Le Moullee</name>
</author>
<author><name sortKey="Ray, P" uniqKey="Ray P">P Ray</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Akter, S" uniqKey="Akter S">S Akter</name>
</author>
<author><name sortKey="D Ambra, J" uniqKey="D Ambra J">J D'Ambra</name>
</author>
<author><name sortKey="Ray, P" uniqKey="Ray P">P Ray</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Subramoniam, S" uniqKey="Subramoniam S">S Subramoniam</name>
</author>
<author><name sortKey="Sadi, S" uniqKey="Sadi S">S Sadi</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Akter, S" uniqKey="Akter S">S Akter</name>
</author>
<author><name sortKey="Ray, P" uniqKey="Ray P">P Ray</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Tachakra, S" uniqKey="Tachakra S">S Tachakra</name>
</author>
<author><name sortKey="Wang, Xh" uniqKey="Wang X">XH Wang</name>
</author>
<author><name sortKey="Istepanian, Rs" uniqKey="Istepanian R">RS Istepanian</name>
</author>
<author><name sortKey="Song, Yh" uniqKey="Song Y">YH Song</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Laxminarayan, S" uniqKey="Laxminarayan S">S Laxminarayan</name>
</author>
<author><name sortKey="Istepanian, Rs" uniqKey="Istepanian R">RS Istepanian</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Istepanian, Rsh" uniqKey="Istepanian R">RSH Istepanian</name>
</author>
<author><name sortKey="Lacal, Jc" uniqKey="Lacal J">JC Lacal</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Istepanian, Rsh" uniqKey="Istepanian R">RSH Istepanian</name>
</author>
<author><name sortKey="Laxminarayan, S" uniqKey="Laxminarayan S">S Laxminarayan</name>
</author>
<author><name sortKey="Pattichis, Cs" uniqKey="Pattichis C">CS Pattichis</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Pare, G" uniqKey="Pare G">G Paré</name>
</author>
<author><name sortKey="Moqadem, K" uniqKey="Moqadem K">K Moqadem</name>
</author>
<author><name sortKey="Pineau, G" uniqKey="Pineau G">G Pineau</name>
</author>
<author><name sortKey="St Hilaire, C" uniqKey="St Hilaire C">C St-Hilaire</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Fayn, J" uniqKey="Fayn J">J Fayn</name>
</author>
<author><name sortKey="Rubel, P" uniqKey="Rubel P">P Rubel</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Lin, Ct" uniqKey="Lin C">CT Lin</name>
</author>
<author><name sortKey="Chang, Kc" uniqKey="Chang K">KC Chang</name>
</author>
<author><name sortKey="Lin, Cl" uniqKey="Lin C">CL Lin</name>
</author>
<author><name sortKey="Chiang, Cc" uniqKey="Chiang C">CC Chiang</name>
</author>
<author><name sortKey="Lu, Sw" uniqKey="Lu S">SW Lu</name>
</author>
<author><name sortKey="Chang, Ss" uniqKey="Chang S">SS Chang</name>
</author>
<author><name sortKey="Lin, Bs" uniqKey="Lin B">BS Lin</name>
</author>
<author><name sortKey="Liang, Hy" uniqKey="Liang H">HY Liang</name>
</author>
<author><name sortKey="Chen, Rj" uniqKey="Chen R">RJ Chen</name>
</author>
<author><name sortKey="Lee, Yt" uniqKey="Lee Y">YT Lee</name>
</author>
<author><name sortKey="Ko, Lw" uniqKey="Ko L">LW Ko</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Kollmann, A" uniqKey="Kollmann A">A Kollmann</name>
</author>
<author><name sortKey="Riedl, M" uniqKey="Riedl M">M Riedl</name>
</author>
<author><name sortKey="Kastner, P" uniqKey="Kastner P">P Kastner</name>
</author>
<author><name sortKey="Schreier, G" uniqKey="Schreier G">G Schreier</name>
</author>
<author><name sortKey="Ludvik, B" uniqKey="Ludvik B">B Ludvik</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Mougiakakou, Sg" uniqKey="Mougiakakou S">SG Mougiakakou</name>
</author>
<author><name sortKey="Bartsocas, Cs" uniqKey="Bartsocas C">CS Bartsocas</name>
</author>
<author><name sortKey="Bozas, E" uniqKey="Bozas E">E Bozas</name>
</author>
<author><name sortKey="Chaniotakis, N" uniqKey="Chaniotakis N">N Chaniotakis</name>
</author>
<author><name sortKey="Iliopoulou, D" uniqKey="Iliopoulou D">D Iliopoulou</name>
</author>
<author><name sortKey="Kouris, I" uniqKey="Kouris I">I Kouris</name>
</author>
<author><name sortKey="Pavlopoulos, S" uniqKey="Pavlopoulos S">S Pavlopoulos</name>
</author>
<author><name sortKey="Prountzou, A" uniqKey="Prountzou A">A Prountzou</name>
</author>
<author><name sortKey="Skevofilakas, M" uniqKey="Skevofilakas M">M Skevofilakas</name>
</author>
<author><name sortKey="Tsoukalis, A" uniqKey="Tsoukalis A">A Tsoukalis</name>
</author>
<author><name sortKey="Varotsis, K" uniqKey="Varotsis K">K Varotsis</name>
</author>
<author><name sortKey="Vazeou, A" uniqKey="Vazeou A">A Vazeou</name>
</author>
<author><name sortKey="Zarkogianni, K" uniqKey="Zarkogianni K">K Zarkogianni</name>
</author>
<author><name sortKey="Nikita, Ks" uniqKey="Nikita K">KS Nikita</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Jara, Aj" uniqKey="Jara A">AJ Jara</name>
</author>
<author><name sortKey="Zamora, Ma" uniqKey="Zamora M">MA Zamora</name>
</author>
<author><name sortKey="Skarmeta, Afg" uniqKey="Skarmeta A">AFG Skarmeta</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Zhu, F" uniqKey="Zhu F">F Zhu</name>
</author>
<author><name sortKey="Bosch, M" uniqKey="Bosch M">M Bosch</name>
</author>
<author><name sortKey="Woo, I" uniqKey="Woo I">I Woo</name>
</author>
<author><name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
<author><name sortKey="Boushey, Cj" uniqKey="Boushey C">CJ Boushey</name>
</author>
<author><name sortKey="Ebert, Ds" uniqKey="Ebert D">DS Ebert</name>
</author>
<author><name sortKey="Delp, Ej" uniqKey="Delp E">EJ Delp</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Pollak, J" uniqKey="Pollak J">J Pollak</name>
</author>
<author><name sortKey="Gay, G" uniqKey="Gay G">G Gay</name>
</author>
<author><name sortKey="Byrne, S" uniqKey="Byrne S">S Byrne</name>
</author>
<author><name sortKey="Wagner, E" uniqKey="Wagner E">E Wagner</name>
</author>
<author><name sortKey="Retelny, D" uniqKey="Retelny D">D Retelny</name>
</author>
<author><name sortKey="Humphreys, L" uniqKey="Humphreys L">L Humphreys</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Patrick, K" uniqKey="Patrick K">K Patrick</name>
</author>
<author><name sortKey="Raab, F" uniqKey="Raab F">F Raab</name>
</author>
<author><name sortKey="Adams, Ma" uniqKey="Adams M">MA Adams</name>
</author>
<author><name sortKey="Dillon, L" uniqKey="Dillon L">L Dillon</name>
</author>
<author><name sortKey="Zabinski, M" uniqKey="Zabinski M">M Zabinski</name>
</author>
<author><name sortKey="Rock, Cl" uniqKey="Rock C">CL Rock</name>
</author>
<author><name sortKey="Griswold, Wg" uniqKey="Griswold W">WG Griswold</name>
</author>
<author><name sortKey="Norman, Gj" uniqKey="Norman G">GJ Norman</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Watson, A" uniqKey="Watson A">A Watson</name>
</author>
<author><name sortKey="Bickmore, T" uniqKey="Bickmore T">T Bickmore</name>
</author>
<author><name sortKey="Cange, A" uniqKey="Cange A">A Cange</name>
</author>
<author><name sortKey="Kulshreshtha, A" uniqKey="Kulshreshtha A">A Kulshreshtha</name>
</author>
<author><name sortKey="Kvedar, J" uniqKey="Kvedar J">J Kvedar</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Whittaker, R" uniqKey="Whittaker R">R Whittaker</name>
</author>
<author><name sortKey="Dorey, E" uniqKey="Dorey E">E Dorey</name>
</author>
<author><name sortKey="Bramley, D" uniqKey="Bramley D">D Bramley</name>
</author>
<author><name sortKey="Bullen, C" uniqKey="Bullen C">C Bullen</name>
</author>
<author><name sortKey="Denny, S" uniqKey="Denny S">S Denny</name>
</author>
<author><name sortKey="Elley, Cr" uniqKey="Elley C">CR Elley</name>
</author>
<author><name sortKey="Maddison, R" uniqKey="Maddison R">R Maddison</name>
</author>
<author><name sortKey="Mcrobbie, H" uniqKey="Mcrobbie H">H McRobbie</name>
</author>
<author><name sortKey="Parag, V" uniqKey="Parag V">V Parag</name>
</author>
<author><name sortKey="Rodgers, A" uniqKey="Rodgers A">A Rodgers</name>
</author>
<author><name sortKey="Salmon, P" uniqKey="Salmon P">P Salmon</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Deglise, C" uniqKey="Deglise C">C Déglise</name>
</author>
<author><name sortKey="Suggs, Ls" uniqKey="Suggs L">LS Suggs</name>
</author>
<author><name sortKey="Odermatt, P" uniqKey="Odermatt P">P Odermatt</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Silva, Bmc" uniqKey="Silva B">BMC Silva</name>
</author>
<author><name sortKey="Lopes, Imc" uniqKey="Lopes I">IMC Lopes</name>
</author>
<author><name sortKey="Machado, Tmf" uniqKey="Machado T">TMF Machado</name>
</author>
<author><name sortKey="Zhou, L" uniqKey="Zhou L">L Zhou</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Silva, Bmc" uniqKey="Silva B">BMC Silva</name>
</author>
<author><name sortKey="Lopes, Imc" uniqKey="Lopes I">IMC Lopes</name>
</author>
<author><name sortKey="Rodrigues, Jjpc" uniqKey="Rodrigues J">JJPC Rodrigues</name>
</author>
<author><name sortKey="Ray, P" uniqKey="Ray P">P Ray</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Rodrigues, Jj" uniqKey="Rodrigues J">JJ Rodrigues</name>
</author>
<author><name sortKey="Lopes, Im" uniqKey="Lopes I">IM Lopes</name>
</author>
<author><name sortKey="Silva, Bm" uniqKey="Silva B">BM Silva</name>
</author>
<author><name sortKey="De La Torre, I" uniqKey="De La Torre I">I de la Torre</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Jonsson, J" uniqKey="Jonsson J">J Jonsson</name>
</author>
<author><name sortKey="Kaliski, B" uniqKey="Kaliski B">B Kaliski</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Raeburn, K" uniqKey="Raeburn K">K Raeburn</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Housley, R" uniqKey="Housley R">R Housley</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Jaganathan, K" uniqKey="Jaganathan K">K Jaganathan</name>
</author>
<author><name sortKey="Zhu, L" uniqKey="Zhu L">L Zhu</name>
</author>
<author><name sortKey="Brezak, J" uniqKey="Brezak J">J Brezak</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Shirey, R" uniqKey="Shirey R">R Shirey</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Rescorla, E" uniqKey="Rescorla E">E Rescorla</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Mcgrew, D" uniqKey="Mcgrew D">D McGrew</name>
</author>
<author><name sortKey="Igoe, M" uniqKey="Igoe M">M Igoe</name>
</author>
<author><name sortKey="Salter, M" uniqKey="Salter M">M Salter</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Raychaudhuri, K" uniqKey="Raychaudhuri K">K Raychaudhuri</name>
</author>
<author><name sortKey="Ray, P" uniqKey="Ray P">P Ray</name>
</author>
</analytic>
</biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="research-article"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">J Med Internet Res</journal-id>
<journal-id journal-id-type="iso-abbrev">J. Med. Internet Res</journal-id>
<journal-id journal-id-type="publisher-id">JMIR</journal-id>
<journal-title-group><journal-title>Journal of Medical Internet Research</journal-title>
</journal-title-group>
<issn pub-type="ppub">1439-4456</issn>
<issn pub-type="epub">1438-8871</issn>
<publisher><publisher-name>Gunther Eysenbach</publisher-name>
<publisher-loc>JMIR Publications Inc., Toronto, Canada</publisher-loc>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="pmid">23624056</article-id>
<article-id pub-id-type="pmc">3636327</article-id>
<article-id pub-id-type="publisher-id">v15i4e66</article-id>
<article-id pub-id-type="doi">10.2196/jmir.2498</article-id>
<article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject>
</subj-group>
</article-categories>
<title-group><article-title>A Data Encryption Solution for Mobile Health Apps in Cooperation Environments</article-title>
</title-group>
<contrib-group><contrib contrib-type="editor"><name><surname>Eysenbach</surname>
<given-names>Gunther</given-names>
</name>
</contrib>
<contrib contrib-type="editor"><name><surname>Jara</surname>
<given-names>Antonio</given-names>
</name>
</contrib>
<contrib contrib-type="editor"><name><surname>Koch</surname>
<given-names>Sabine</given-names>
</name>
</contrib>
<contrib contrib-type="editor"><name><surname>Ray</surname>
<given-names>Pradeep</given-names>
</name>
</contrib>
</contrib-group>
<contrib-group><contrib contrib-type="reviewer"><name><surname>Zeadally</surname>
<given-names>Sherali</given-names>
</name>
</contrib>
<contrib contrib-type="reviewer"><name><surname>Verikoukis</surname>
<given-names>Christos</given-names>
</name>
</contrib>
<contrib contrib-type="reviewer"><name><surname>Vinel</surname>
<given-names>Alexey</given-names>
</name>
</contrib>
<contrib contrib-type="reviewer"><name><surname>Lorenz</surname>
<given-names>Pascal</given-names>
</name>
</contrib>
<contrib contrib-type="reviewer"><name><surname>Jara</surname>
<given-names>Antonio</given-names>
</name>
</contrib>
</contrib-group>
<contrib-group><contrib id="contrib1" contrib-type="author"><name><surname>Silva</surname>
<given-names>Bruno M</given-names>
</name>
<degrees>BSC, MSc</degrees>
<xref ref-type="aff" rid="aff1">1</xref>
</contrib>
<contrib id="contrib2" contrib-type="author" corresp="yes"><name><surname>Rodrigues</surname>
<given-names>Joel JPC</given-names>
</name>
<degrees>BSC, MSc, PhD</degrees>
<xref ref-type="aff" rid="aff1">1</xref>
<address><institution>Instituto de Telecomunicações, University of Beira Interior</institution>
<addr-line>Rua Marques D'Avila e Bolama</addr-line>
<addr-line>Covilhã, 6201-001</addr-line>
<country>Portugal</country>
<phone>351 275242081</phone>
<fax>351 275319891</fax>
<email>joeljr@ieee.org</email>
</address>
</contrib>
<contrib id="contrib3" contrib-type="author"><name><surname>Canelo</surname>
<given-names>Fábio</given-names>
</name>
<degrees>BSC, Msc Candidate</degrees>
<xref ref-type="aff" rid="aff1">1</xref>
</contrib>
<contrib id="contrib4" contrib-type="author"><name><surname>Lopes</surname>
<given-names>Ivo C</given-names>
</name>
<degrees>BSC, MSc</degrees>
<xref ref-type="aff" rid="aff1">1</xref>
</contrib>
<contrib id="contrib5" contrib-type="author"><name><surname>Zhou</surname>
<given-names>Liang</given-names>
</name>
<degrees>BSC, MSc, PhD</degrees>
<xref ref-type="aff" rid="aff2">2</xref>
</contrib>
</contrib-group>
<aff id="aff1" rid="aff1"><sup>1</sup>
<institution>Instituto de Telecomunicações, University of Beira Interior</institution>
<addr-line>Covilhã</addr-line>
<country>Portugal</country>
</aff>
<aff id="aff2" rid="aff2"><sup>2</sup>
<institution>Nanjing University of Posts and Telecommunications</institution>
<addr-line>Nanjing</addr-line>
<country>China</country>
</aff>
<author-notes><corresp>Corresponding Author: Joel JPC Rodrigues <email>joeljr@ieee.org</email>
</corresp>
</author-notes>
<pub-date pub-type="collection"><month>4</month>
<year>2013</year>
</pub-date>
<pub-date pub-type="epub"><day>25</day>
<month>4</month>
<year>2013</year>
</pub-date>
<volume>15</volume>
<issue>4</issue>
<elocation-id>e66</elocation-id>
<history><date date-type="received"><day>15</day>
<month>12</month>
<year>2012</year>
</date>
<date date-type="rev-request"><day>10</day>
<month>1</month>
<year>2013</year>
</date>
<date date-type="rev-recd"><day>22</day>
<month>1</month>
<year>2013</year>
</date>
<date date-type="accepted"><day>09</day>
<month>2</month>
<year>2013</year>
</date>
</history>
<permissions><copyright-statement>©Bruno M Silva, Joel JPC Rodrigues, Fábio Canelo, Ivo C Lopes, Liang Zhou. Originally published in the Journal of Medical Internet Research (http://www.jmir.org), 25.04.2013. </copyright-statement>
<copyright-year>2013</copyright-year>
<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/2.0/"><license-p><pmc-comment>CREATIVE COMMONS</pmc-comment>
This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0/">http://creativecommons.org/licenses/by/2.0/</ext-link>
), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in the Journal of Medical Internet Research, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/,">http://www.jmir.org/,</ext-link>
as well as this copyright and license information must be included.</license-p>
</license>
</permissions>
<self-uri xlink:type="simple" xlink:href="http://www.jmir.org/2013/4/e66/"></self-uri>
<abstract><sec sec-type="background"><title>Background</title>
<p>Mobile Health (mHealth) proposes health care delivering anytime and anywhere. It aims to answer several emerging problems in health services, including the increasing number of chronic diseases, high costs on national health services, and the need to provide direct access to health services, regardless of time and place. mHealth systems include the use of mobile devices and apps that interact with patients and caretakers. However, mobile devices present several constraints, such as processor, energy, and storage resource limitations. The constant mobility and often-required Internet connectivity also exposes and compromises the privacy and confidentiality of health information.</p>
</sec>
<sec sec-type="objective"><title>Objective</title>
<p>This paper presents a proposal, construction, performance evaluation, and validation of a data encryption solution for mobile health apps (DE4MHA), considering a novel and early-proposed cooperation strategy. The goal was to present a robust solution based on encryption algorithms that guarantee the best confidentiality, integrity, and authenticity of users health information. In this paper, we presented, explained, evaluated the performance, and discussed the cooperation mechanisms and the proposed encryption solution for mHealth apps.</p>
</sec>
<sec sec-type="methods"><title>Methods</title>
<p>First, we designed and deployed the DE4MHA. Then two studies were performed: (1) study and comparison of symmetric and asymmetric encryption/decryption algorithms in an mHealth app under a cooperation environment, and (2) performance evaluation of the DE4MHA. Its performance was evaluated through a prototype using an mHealth app for obesity prevention and cares, called SapoFit. We then conducted an evaluation study of the mHealth app with cooperation mechanisms and the DE4MHA using real users and a real cooperation scenario. In 5 days, 5 different groups of 7 students selected randomly agreed to use and experiment the SapoFit app using the 7 devices available for trials.</p>
</sec>
<sec sec-type="results"><title>Results</title>
<p>There were 35 users of SapoFit that participated in this study. The performance evaluation of the app was done using 7 real mobile devices in 5 different days. The results showed that confidentiality and protection of the users’ health information was guaranteed and SapoFit users were able to use the mHealth app with satisfactory quality. Results also showed that the app with the DE4MHA presented nearly the same results as the app without the DE4MHA. The performance evaluation results considered the probability that a request was successfully answered as a function of the number of uncooperative nodes in the network. The service delivery probability decreased with the increase of uncooperative mobile nodes. Using DE4MHA, it was observed that performance presented a slightly worse result. The service average was also slightly worse but practically insignificantly different than with DE4MHA, being considered negligible.</p>
</sec>
<sec sec-type="conclusions"><title>Conclusions</title>
<p>This paper proposed a data encryption solution for mobile health apps, called DE4MHA. The data encryption algorithm DE4MHA with cooperation mechanisms in mobile health allow users to safely obtain health information with the data being carried securely. These security mechanisms did not deteriorate the overall network performance and the app, maintaining similar performance levels as without the encryption. More importantly, it offers a robust and reliable increase of privacy, confidentiality, integrity, and authenticity of their health information. Although it was experimented on a specific mHealth app, SapoFit, both DE4MHA and the cooperation strategy can be deployed in other mHealth apps.</p>
</sec>
</abstract>
<kwd-group><kwd>mobile health</kwd>
<kwd>mHealth</kwd>
<kwd>mobile computing</kwd>
<kwd>eHealth</kwd>
<kwd>cooperation</kwd>
<kwd>encryption</kwd>
<kwd>security</kwd>
</kwd-group>
</article-meta>
</front>
<body><sec><title>Introduction</title>
<p>In the last decade, health telematics, also known as electronic health (eHealth), have offered patients major improvements in their lives by providing more accessible and affordable health care solutions [<xref ref-type="bibr" rid="ref1">1</xref>
,<xref ref-type="bibr" rid="ref2">2</xref>
]. This is particularly true for patients that live in remote rural areas, travel constantly, are physically incapacitated, elderly, or chronically ill. Telemedicine assumes the use of medical information, also known as electronic health records (EHRs), exchanged via electronic communications improving the patients’ health status [<xref ref-type="bibr" rid="ref3">3</xref>
]. The rapid evolution of information and communication technology (ICT) infrastructures enables and provides rapid access to patient data. The Web 2.0 concept and the emerging Web 3.0 offer opportunities to health care professionals never seen before [<xref ref-type="bibr" rid="ref4">4</xref>
,<xref ref-type="bibr" rid="ref5">5</xref>
]. Now, physicians can perform many tasks through these modern technologies, such as (1) sharing medical videos, photos, and presentations (via YouTube, Flickr, and Slideshare, respectively), (2) use blogs to post medical cases and images, (3) share hospital management information, (4) use social networking to share medical ideas and tasks, and (5) use RSS feeds to keep track of alerts on specific medical interests.</p>
<p>With the advent of mobile communications using smart mobile devices that support 3G and 4G mobile networks for data transport, mobile computing has been the main attraction of research and business communities, thus offering innumerous opportunities to create efficient mobile health solutions. Mobile health (mHealth) is the new edge on health care innovations. It delivers health care anywhere and anytime, surpassing geographical, temporal, and even organizational barriers [<xref ref-type="bibr" rid="ref6">6</xref>
,<xref ref-type="bibr" rid="ref7">7</xref>
]. Laxminarayan and Istepanian defined mobile health for the first time in 2000, as “unwired e-med<italic>”</italic>
[<xref ref-type="bibr" rid="ref8">8</xref>
]<italic>.</italic>
In 2003, the term “mHealth” was defined as the <italic>”</italic>
emerging mobile communications and network technologies for health care systems<italic>”</italic>
[<xref ref-type="bibr" rid="ref9">9</xref>
]. Laxminarayan et al, in 2006, presented a comprehensive study on the impact of mobility on the existing eHealth commercial telemedical systems. They also presented other relevant computing and information technologies that will influence and offer the basis for the next generation of mHealth services [<xref ref-type="bibr" rid="ref10">10</xref>
]. Furthermore, this study served as the basis for future studies on mHealth technologies and services [<xref ref-type="bibr" rid="ref11">11</xref>
]<italic>.</italic>
Several research topics related to health have gathered important findings and contributions using mHealth, such as cardiology [<xref ref-type="bibr" rid="ref12">12</xref>
,<xref ref-type="bibr" rid="ref13">13</xref>
], diabetes [<xref ref-type="bibr" rid="ref14">14</xref>
-<xref ref-type="bibr" rid="ref16">16</xref>
], obesity [<xref ref-type="bibr" rid="ref17">17</xref>
-<xref ref-type="bibr" rid="ref20">20</xref>
], and smoking cessation [<xref ref-type="bibr" rid="ref21">21</xref>
]. More specifically, mHealth apps were applied to health monitoring, disease prevention and detection, basic diagnosis, and in more advanced services. mHealth services are also becoming popular in developing countries where health care facilities are frequently remote and inaccessible [<xref ref-type="bibr" rid="ref2">2</xref>
,<xref ref-type="bibr" rid="ref22">22</xref>
].</p>
<p>Mobile devices and wireless communications present several challenging characteristics and constraints, such as battery and storage capacity, broadcasting constraints, signal interferences, disconnections, noises, limited bandwidths, and network delays. In this sense, cooperation-based approaches are presented as a solution to solve such limitations, focusing on increasing network connectivity, communication rates, and reliability.</p>
<p>In this paper, we present a data encryption solution for mHealth apps (DE4MHA) in cooperative environments guaranteeing data confidentiality, integrity, and authenticity. This novel and early-proposed cooperation strategy [<xref ref-type="bibr" rid="ref23">23</xref>
] for mHealth apps focuses on forwarding and retrieving data to and from nodes that have no direct connection to an mHealth service. In this way, devices without Internet connectivity can use mHealth apps without problems. This cooperation approach presents a reputation-based strategy where a Web service manages the access control and the cooperation among nodes along with their reputation. It considers the following three main components: a <italic>node control message,</italic>
a <italic>requester control message,</italic>
and a <italic>cooperative Web service</italic>
(CWS). Both control messages are used to manage a local cooperation between two or more nodes. The CWS includes a reputation table for all the nodes and decides which nodes can have access to the requested services. The cooperation strategy and the DE4MHA was deployed and evaluated in an mHealth app for obesity prevention and control, called SapoFit [<xref ref-type="bibr" rid="ref24">24</xref>
-<xref ref-type="bibr" rid="ref26">26</xref>
]. To the best of our knowledge, there are no cooperative solutions thus far for mHealth services and apps considering this network scenario with constant network disconnection. DE4MHA uses symmetric and asymmetric encryption and decryption techniques. We used the Rivest, Shamir, Adleman (RSA) algorithm [<xref ref-type="bibr" rid="ref27">27</xref>
] for asymmetric encryption/decryption to ensure key exchange confidentiality, and the Advanced Encryption Standard (AES) [<xref ref-type="bibr" rid="ref28">28</xref>
] algorithm for symmetric encryption/decryption for data confidentiality. To ensure data integrity, we have created a message digest that creates a hash of transmitted data. For data authenticity, we used a digital signature. We encrypted the hash message with the RSA private key. To secure the communication with the SapoFit Web service (WS), we used the Hypertext Transfer Protocol Secure (HTTPS) protocol.</p>
<p>In this paper we report two studies that were performed to design and construct the DE4MHA algorithms: (1) a direct evaluation and comparison of several encryption algorithms, and (2) a series of trials evolving 35 people and 7 different mobile devices with SapoFit. The first study revealed what algorithms performed best in an mHealth app in cooperation environments. Overall, this study evaluated the performance of the DE4MHA over the cooperation mechanisms for mHealth apps. The second study revealed that real users experimenting on the SapoFit app trusted DE4MHA. More relevant, this study concluded that the performance of the app used was not affected by the inclusion of DE4MHA.</p>
</sec>
<sec sec-type="methods"><title>Methods</title>
<sec><title>Overview</title>
<p>This study used an existing mHealth app, called SapoFit, to deploy, evaluate, and validate the proposed solution. This app uses a cooperation strategy that addresses two related limitations to mHealth apps with service-oriented architectures, namely the network infrastructure and Internet connectivity dependency. It follows a reputation-based approach as an incentive method for cooperation, which includes a Web service to manage all the network cooperation. It is responsible for verifying the cooperation status of neighbor nodes and to provide relay nodes the required data in order to perform a full data request.</p>
</sec>
<sec><title>Cooperation Strategy for mHealth Apps</title>
<p>The cooperation strategy for mHealth apps with service oriented architectures (SOAs) is based on the following two mobile modules and one remote module, respectively: (1) the <italic>node control message,</italic>
(2) the <italic>requester control message</italic>
, and (3) the <italic>CWS</italic>
.</p>
<p>The mobile <italic>nodes control messages</italic>
aim to provide an awareness of the relay node status, that is, if the node is willing to cooperate and in what conditions. It contains the established node unique identifier, the battery state, the Internet connectivity status, and the cooperation status (ie, if it is cooperative or not).</p>
<p>The <italic>requester control message</italic>
is sent by the initial requester node first (the mobile device with mHealth app requesting health data), and it comprises the following five main components: (1) the requester ID, the node unique identifier, (2) the service request, that is, what the node is specifically requesting (eg, the login token or its health profile), (3) the neighbors list, (4) the reputation list, and (5) the achieved cooperation time (ACT).</p>
<p>The <italic>CWS</italic>
is responsible for performing a fair access control to data. Thus, according to the received reputation information, the Web service holds the final reputation list in order to decide if a requester node should have access to the mHealth app Web service or not. The reputation list contains all registered network nodes with their identifier and their corresponding reputation value.</p>
<p><xref ref-type="fig" rid="figure1">Figure 1</xref>
presents a user scenario of the mHealth cooperation approach. <italic>User A</italic>
has network connectivity and cooperates. <italic>User B</italic>
has network connectivity and does not cooperate. The status value is according to the battery status. Then, the status value will suffer a negative impact according to the battery status. <italic>Users C</italic>
and <italic>D</italic>
do not have network connectivity. <italic>User C</italic>
queries <italic>User A</italic>
for cooperation and receives a positive response and all the requested data. <italic>User D</italic>
queries <italic>User B</italic>
for cooperation and receives a negative response. Then, <italic>User D</italic>
requests data from <italic>User C</italic>
that answers this request, getting positive status by cooperating.</p>
</sec>
<sec><title>SapoFit App</title>
<p>SapoFit is a weight control mobile app that allows users to keep track of weight in a healthier and more practical way. SapoFit allows users to control their weight, body mass index (BMI), basal metabolic rate (BMR), sports activity, and the possibility to follow food plans based on their needed calories. In this mHealth app, all the users must be registered in a Web service. <xref ref-type="fig" rid="figure2">Figure 2</xref>
presents screenshots of three main activities of the SapoFit app: <italic>Login, Plans,</italic>
and <italic>User Profile.</italic>
</p>
<p>Cooperating nodes have a better reputation, and have priority over selfish nodes to access the mHealth app services.</p>
</sec>
<sec><title>Data Encryption Algorithm for Mobile Health Apps (DE4MHA)</title>
<p>The process begins with a mobile node (a person using SapoFit) trying to access the SapoFit Web Service that contains the user profile, weight measures, fitness, and diet indications.</p>
<p>A SapoFit user (mobile requester node) without network connectivity and therefore without access to the SapoFit WS obtains the required health information through cooperation. Another SapoFit user with network connectivity (mobile requested node) will forward the requested health information from the SapoFit Web service. Both the requested and requester nodes will create a pair of RSA keys and send public keys to both the requested and requester node through Bluetooth. After the public key exchange, the requested node creates an AES session key.</p>
<p>The next step is the creation of the digest message and its encryption using the private key. The Message Digest 5 (MD5) algorithm was used to create a 128-bit hash. For data authenticity, we used a digital signature. A digital signature is created for the message containing requested health information. This digital signature allows any node to verify that the message is the original one. By decrypting the digital signature with the public key, the original digest message is obtained. The receiver node then creates a new hash of the received message and compares it to the decrypted digest message to guarantee authenticity. The digital signature is then added to the message. When the message containing the session key is received, if its integrity and authenticity is verified, the requester node then sends an acknowledgement (<italic>ack</italic>
) to the requested node. This method guaranties safe communication between nodes; if the integrity and authenticity is not verified, the communication between nodes is ended.</p>
<p>A mobile node with network connectivity will access the cooperative WS to obtain the required health information. To secure all communication with the WS the Secure Socket Layer (SSL) over the HTTP (also known as HTTPS) is used. Therefore, it grants confidentiality, integrity, and authenticity of all retrieved health data from the Web service.</p>
<p>Two studies were performed: (1) a study evaluating which symmetric and asymmetric algorithm present the best performance in SapoFit in cooperation environment, and (2) a series of trials involving 35 people and 7 different mobile devices with SapoFit. This study evaluated the performance of the DE4MHA over the cooperation mechanisms.</p>
<fig id="figure1" position="float"><label>Figure 1</label>
<caption><p>Illustration of the interaction for an mHealth app with the proposed cooperation approach for 4 users.</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig1"></graphic>
</fig>
<fig id="figure2" position="float"><label>Figure 2</label>
<caption><p>Screenshots of the three main activities of SapoFit app: Login, Plans, and User Profile.</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig2"></graphic>
</fig>
</sec>
<sec><title>Study 1: Study of Cryptography Algorithms in an mHealth App Under a Cooperation Environment</title>
<sec><title>Symmetric Algorithm</title>
<p>In order to choose the best suited symmetric encryption algorithm for the SapoFit app, performance experiments were conducted using 4 different encryption algorithms, namely AES, Triple Data Encryption Standard (3DES) [<xref ref-type="bibr" rid="ref29">29</xref>
], Rivest Cypher 4 (RC4) [<xref ref-type="bibr" rid="ref30">30</xref>
], and Blowfish [<xref ref-type="bibr" rid="ref31">31</xref>
], using the data size encryption as a performance metric.</p>
</sec>
<sec><title>Asymmetric Algorithm</title>
<p>Two options were considered in selecting an asymmetric algorithm to exchange session keys between mobile nodes. We tested RSA, which enables encrypting the session key before sending it, and Diffie-Hellman [<xref ref-type="bibr" rid="ref32">32</xref>
], which allows users to first share a secret, then generating a session key based on the shared secret. For our network scenario, these were the most suitable algorithms. Other encryption algorithms were considered in this study, such as the Elliptic Curve Cryptography (ECC) algorithm [<xref ref-type="bibr" rid="ref33">33</xref>
].</p>
</sec>
</sec>
<sec><title>Study 2: Performance evaluation of the DE4MHA</title>
<sec><title>Performance Evaluation</title>
<p>The performance evaluation study was carried out using 7 real mobile devices, which were used 7 times in 5 different days with a total of 35 different users who successfully tested the app. <xref ref-type="fig" rid="figure3">Figure 3</xref>
presents the 7 different mobile devices with different hardware and software used with the SapoFit mHealth app.</p>
<p>Cooperative nodes without network connection cooperated with each other through Bluetooth. The communication with the CWS was obtained through the Wi-Fi or Edge/3.5G/4G modules of the device. The CWS was developed with the help of Java Server Pages (JSP) technology, using the Representational State Transfer (REST) architecture. To serve the WS, the Apache Tomcat Web Server was used.</p>
<p>Non-cooperative cases were controlled and measured to a maximum of 4 to guarantee the minimum service performance in order to guarantee cooperation among nodes. Through cooperation, all the devices could use the mHealth app. However, uncooperative nodes directly affect the service delivery probability, service average delay, and the overall network performance. Performance metrics considered in this study were the service delivery probability (as percentages) and the average service delay (in seconds). We present a comparison of the performance of the mHealth app with and without the DE4MHA.</p>
</sec>
<sec><title>User Trials Evaluation of DE4MHA in Cooperative Environments</title>
<p>User trials were conducted within the University informatics department using 7 devices available for trials. Within 5 days, 5 different groups of 7 students selected randomly agreed to use and experiment the SapoFit app using the 7 devices available for trials. Users were constantly moving far away from each other. This mobility was necessary to test the network scenario, forcing network delays and disconnections. The cooperative strategy and the DE4MHA was ubiquitous to its user. Throughout the trials, users only experienced and used the obesity prevention services that SapoFit offered without any constraints or perception of any cooperation mechanism or encryption algorithm that was embedded in the mHealth app.</p>
<p>While conducting the experiments, almost every users asked if their information was being kept secure or not, clearly showing that they did not wanted their health information to be available or disclosed to unauthorized people, revealing privacy concerns. Another frequently raised question was the need to share Internet connectivity to other users.</p>
<p>We explained and justified that sharing and cooperating with other users was essential to obtain a better reputation to gain cooperation privileges over other nodes with worse reputation. Furthermore we demonstrated to them that SapoFit was not intrusive with other users’ personal data on the mobile device and only requested for SapoFit services.</p>
<p>After the experiments, the users completed a survey evaluating their experience. The questions are listed in <xref ref-type="boxed-text" rid="box1">Textbox 1</xref>
and the results in <xref ref-type="fig" rid="figure4">Figure 4</xref>
.</p>
<fig id="figure3" position="float"><label>Figure 3</label>
<caption><p>Mobile devices used for trials with the SapoFit mHealth app.</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig3"></graphic>
</fig>
<boxed-text id="box1" position="float"><caption><title>Survey questions.</title>
</caption>
<list list-type="simple"><list-item><p>Without network connectivity, do the user always gets the required information?</p>
</list-item>
<list-item><p>Without network connectivity, does the required information get delivered in a comfortable time?</p>
</list-item>
<list-item><p>Understanding the implemented cooperation strategy and its benefits, are you willing to cooperate and share the device/network resources with other users?</p>
</list-item>
<list-item><p>With the encryption strategy applied to SapoFit, do you trust that your personal health information is secure?</p>
</list-item>
<list-item><p>Was the mobile device affected by app cooperation and encryption mechanisms (eg, broadband, battery, etc)?</p>
</list-item>
</list>
</boxed-text>
<fig id="figure4" position="float"><label>Figure 4</label>
<caption><p>Results of the survey evaluating the main questions about the performance of the mHealth app with the proposed cooperation strategy and encryption solution.</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig4"></graphic>
</fig>
</sec>
</sec>
</sec>
<sec sec-type="results"><title>Results</title>
<sec><title>Symmetric Algorithm</title>
<p>As seen in <xref ref-type="fig" rid="figure5">Figure 5</xref>
, results showed that when the amount of data that needed to be encrypted increased, the encryption time (in seconds) also increased, as expected. When comparing small amounts of data, all 4 algorithms presented similar results. However, the AES algorithm presented better results, as there was a slower overall increase in encryption time in response to increased amount of data. The encryption time of the other three experimented algorithms grew exponentially when encryption data size exceeded 1000 kilobytes. The 3DES algorithm presented the worst encryption rate, encrypting 10,000KB of data in, on average, 14.3 seconds, presenting an average time of 4.58 seconds for multiple data size inputs (SD 6.17). With the same amount of data, the AES encryption time was only 0.0045 seconds, resulting in an average of 0.0035 seconds for the given data set (SD 0.00061 seconds). Decryption gave similar results (<xref ref-type="fig" rid="figure5">Figure 5</xref>
). The average AES algorithm decryption time was 0.0038 seconds for 10,000KB of data and 0.0025 seconds on average for the working data-set (SD 0.001 seconds). Overall, the AES algorithm with a 128 bits key encryption was the most efficient algorithm for these network scenarios, when handling with both small and large amounts of data.</p>
</sec>
<sec><title>Asymmetric Algorithm</title>
<p>Two options were considered for an asymmetric algorithm in order to exchange session keys between mobile nodes—the RSA and the Diffie-Hellman algorithms. The RSA encrypts the session key first before it gets sent, and Diffie-Hellman allows users to first share a secret, then generates a session key based on the shared secret.</p>
<p>Several experiments were performed with both algorithms with RSA presenting better encryption times than Diffie-Hellman, due to the high amount of computation needed by Diffie-Hellman and the low processing capacity of mobile devices.</p>
<fig id="figure5" position="float"><label>Figure 5</label>
<caption><p>Comparison of encryption and decryption of symmetric algorithms (AES, 3DES, RC4, and Blowfish).</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig5"></graphic>
</fig>
</sec>
<sec><title>DE4MHA Performance Evaluation Results</title>
<p>In the presented scenario, all the devices had Bluetooth class 2 modules, but only 3 devices had Internet connectivity. Users without Internet connectivity had to use the integrated cooperation mechanisms in order to obtain the requested health information. When the number of uncooperative nodes increased, the service delivery probability decreased. The average service delay was also affected in the same mannor, as expected. Increased number of uncooperative nodes increased the average service delay.</p>
<p><xref ref-type="fig" rid="figure6">Figure 6</xref>
shows the results of the service delivery probability and the average service delay as a function of the number of uncooperative mobile nodes with and without the DE4MHA. The probability that a request was successfully answered as a function of uncooperative nodes in the network decreased with the increase of uncooperative mobile nodes. Taking into account both approaches, with and without DE4MHA, it was observed that DE4MHA presented a slightly worse result. The average service delay also grew when the number of uncooperative mobile nodes increased, as expected. The results of the DE4MHA were also slightly worse but practically insignificant. As can be observed, with 4 uncooperative nodes, the service average delay, with and without DE4MHA, was about 30.78 and 29.77 seconds, respectively.</p>
<fig id="figure6" position="float"><label>Figure 6</label>
<caption><p>Service delivery probability and average service delay as a function of the number of uncooperative mobile nodes with and without the DE4MHA.</p>
</caption>
<graphic xlink:href="jmir_v15i4e66_fig6"></graphic>
</fig>
</sec>
</sec>
<sec sec-type="discussion"><title>Discussion</title>
<sec><title>Findings</title>
<p>Our main goal was to propose and construct a security encryption/decryption based solution in a cooperative environment for mHealth apps. We aimed to ensure data confidentiality, integrity, and authenticity. Privacy is a top priority issue in mHealth services and apps that deal with user sensitive information. On mHealth apps, several security issues must be considered, such as personal information management, secondary use of personal information, improper use of personal information, and errors with stored personal information. Therefore, cryptographic mechanisms can be seen as a solution to guarantied data confidentiality and protection [<xref ref-type="bibr" rid="ref34">34</xref>
].</p>
<p>In a mobility and cooperative environment with constant health data being forwarded and retrieved, studying and developing security mechanisms become crucial. Several experiments were conducted, involving 35 different users, to check if they could distinguish the app running with and without the DE4MHA embedded. Through the trials, we concluded that users could not tell which app had the DE4MHA embedded mainly because the time response taken to obtain the user health information was nearly the same as without DE4MHA. The DE4MHA was implemented in a ubiquitous manner so users were able to keep using the app without noticing changes or presence of any cryptography mechanisms.</p>
</sec>
<sec><title>Limitations</title>
<p>There were several limitations to the study. The main limitation was applying security on mobile devices due to the low processor capacity compared with personal computers (PCs), though tremendous improvements in this area have been made, with a few mobile devices capable of competing with traditional PCs. This improvement allowed us to test several security algorithms to address the issues of confidentiality (AES, RC4, 3DES, and Blowfish), integrity (MD5 and SHA1), and authenticity (RSA with MD5 and DSA with SHA1) in order to verify which combination had a better performance in a mobile environment.</p>
<p>During the experiments, some users without Internet connectivity who wanted to obtain health information were in constantly moving further away from other users. Although the cooperation mechanism was embedded, users that were beyond the range of 10 meters (the maximum range for Bluetooth class 2 modules) could not obtain the desired health information. Another limitation, though not related to security, was with regard to the number of uncooperative nodes (mobile nodes that may not want to cooperate or they may not have cooperation mechanisms embedded), compromising service response probability.</p>
</sec>
<sec><title>Conclusion</title>
<p>This paper proposed a data encryption solution for mobile health apps, called DE4MHA. The data encryption algorithm DE4MHA with cooperation mechanisms in mobile health allow users to safely obtain health information with the data being carried securely. These security mechanisms did not deteriorate the overall network performance and the app, maintaining similar performance levels as without the encryption. More importantly, it offers a robust and reliable increase of privacy, confidentiality, integrity, and authenticity of their health information. Although it was experimented on a specific mHealth app, SapoFit, both DE4MHA and the cooperation strategy can be deployed in other mHealth apps.</p>
</sec>
</sec>
</body>
<back><ack><p>This study was partially supported by Instituto de Telecomunicacões, Next Generation Networks and Applications Group (NetGNA) Portugal, National Funding from the FCT—Fundacão para a Ciência e a Tecnologia through the PEst-OE/EEI/LA0008/2011 Project, National Natural Science Foundation of China (Grant No. 61201165 and No. 61271240), and the AAL4ALL (Ambient Assisted Living for All), project co-funded by COMPETE under FEDER via QREN Programme.</p>
</ack>
<fn-group><fn fn-type="conflict"><p>Conflicts of Interest: None declared.</p>
</fn>
</fn-group>
<glossary><title>Abbreviations</title>
<def-list><def-item><term id="abb1">3DES</term>
<def><p>Triple Data Encryption Standard</p>
</def>
</def-item>
<def-item><term id="abb2">ACT</term>
<def><p>achieved cooperation time</p>
</def>
</def-item>
<def-item><term id="abb3">AES</term>
<def><p>Advanced Encryption Standard</p>
</def>
</def-item>
<def-item><term id="abb4">BMI</term>
<def><p>body mass index</p>
</def>
</def-item>
<def-item><term id="abb5">BMR</term>
<def><p>basal metabolic rate</p>
</def>
</def-item>
<def-item><term id="abb6">CWS</term>
<def><p>cooperative Web service</p>
</def>
</def-item>
<def-item><term id="abb7">DE4MHA</term>
<def><p>data encryption solution for mobile health apps</p>
</def>
</def-item>
<def-item><term id="abb8">EHR</term>
<def><p>electronic health record</p>
</def>
</def-item>
<def-item><term id="abb9">HTTPS</term>
<def><p>Hypertext Transfer Protocol Secure</p>
</def>
</def-item>
<def-item><term id="abb10">ICT</term>
<def><p>information and communication technologies</p>
</def>
</def-item>
<def-item><term id="abb11">JSP</term>
<def><p>Java Server Pages</p>
</def>
</def-item>
<def-item><term id="abb12">RC4</term>
<def><p>Rivest Cipher 4</p>
</def>
</def-item>
<def-item><term id="abb13">REST</term>
<def><p>Representational State Transfer</p>
</def>
</def-item>
<def-item><term id="abb14">RSA</term>
<def><p>Rivest, Shamir, Adleman</p>
</def>
</def-item>
<def-item><term id="abb15">SOAs</term>
<def><p>service oriented architectures</p>
</def>
</def-item>
<def-item><term id="abb16">SSL</term>
<def><p>Secure Socket Layer</p>
</def>
</def-item>
<def-item><term id="abb17">WS</term>
<def><p>Web service</p>
</def>
</def-item>
</def-list>
</glossary>
<ref-list><ref id="ref1"><label>1</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Le Moullee</surname>
<given-names>B</given-names>
</name>
<name><surname>Ray</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Issues in E-Health Cost Impact Assessment</article-title>
<source>IFMBE Proceedings</source>
<year>2009</year>
<conf-name>World Congress on Medical Physics and Biomedical Engineering</conf-name>
<conf-date>September 9-12, 2009</conf-date>
<conf-loc>Munich, Germany</conf-loc>
<fpage>223</fpage>
<lpage>226</lpage>
<pub-id pub-id-type="doi">10.1007/978-3-642-03893-8_63</pub-id>
</element-citation>
</ref>
<ref id="ref2"><label>2</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Akter</surname>
<given-names>S</given-names>
</name>
<name><surname>D'Ambra</surname>
<given-names>J</given-names>
</name>
<name><surname>Ray</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>User Perceived Service Quality of mHealth Services in Developing Countries</article-title>
<year>2010</year>
<month>6</month>
<day>09</day>
<conf-name>European Conference on Information Systems</conf-name>
<conf-date>June 6-9, 2010</conf-date>
<conf-loc>Pretoria, South Africa</conf-loc>
</element-citation>
</ref>
<ref id="ref3"><label>3</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><collab>United Nations Foundation</collab>
<collab>Vodafone Group Foundation</collab>
<collab>Telemedicine Society of India</collab>
</person-group>
<source>mHealth and Mobile Telemedicine - an Overview</source>
<year>2008</year>
<month>8</month>
<day>01</day>
<date-in-citation>2013-03-06</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://ehealth-connection.org/content/mhealth-and-mobile-telemedicine-an-overview">http://ehealth-connection.org/content/mhealth-and-mobile-telemedicine-an-overview</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6EvqsNn7K"></ext-link>
</element-citation>
</ref>
<ref id="ref4"><label>4</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Subramoniam</surname>
<given-names>S</given-names>
</name>
<name><surname>Sadi</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Healthcare 2.0</article-title>
<source>IT Professional</source>
<year>2010</year>
<volume>12</volume>
<issue>6</issue>
<fpage>46</fpage>
<lpage>51</lpage>
<pub-id pub-id-type="doi">10.1109/MITP.2010.66</pub-id>
</element-citation>
</ref>
<ref id="ref5"><label>5</label>
<element-citation publication-type="webpage"><source>epSOS – the European eHealth Project</source>
<date-in-citation>2013-02-28</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.epsos.eu/">http://www.epsos.eu/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6E0ipZcb2"></ext-link>
</element-citation>
</ref>
<ref id="ref6"><label>6</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Akter</surname>
<given-names>S</given-names>
</name>
<name><surname>Ray</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>mHealth - an Ultimate Platform to Serve the Unserved</article-title>
<source>Yearb Med Inform</source>
<year>2010</year>
<fpage>94</fpage>
<lpage>100</lpage>
<pub-id pub-id-type="medline">20938579</pub-id>
<pmc-comment>me10010094 </pmc-comment>
<pub-id pub-id-type="pmid">20938579</pub-id>
</element-citation>
</ref>
<ref id="ref7"><label>7</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Tachakra</surname>
<given-names>S</given-names>
</name>
<name><surname>Wang</surname>
<given-names>XH</given-names>
</name>
<name><surname>Istepanian</surname>
<given-names>RS</given-names>
</name>
<name><surname>Song</surname>
<given-names>YH</given-names>
</name>
</person-group>
<article-title>Mobile e-health: the unwired evolution of telemedicine</article-title>
<source>Telemed J E Health</source>
<year>2003</year>
<volume>9</volume>
<issue>3</issue>
<fpage>247</fpage>
<lpage>57</lpage>
<pub-id pub-id-type="doi">10.1089/153056203322502632</pub-id>
<pub-id pub-id-type="medline">14611692</pub-id>
<pub-id pub-id-type="pmid">14611692</pub-id>
</element-citation>
</ref>
<ref id="ref8"><label>8</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Laxminarayan</surname>
<given-names>S</given-names>
</name>
<name><surname>Istepanian</surname>
<given-names>RS</given-names>
</name>
</person-group>
<article-title>UNWIRED E-MED: the next generation of wireless and internet telemedicine systems</article-title>
<source>IEEE Trans Inf Technol Biomed</source>
<year>2000</year>
<month>9</month>
<volume>4</volume>
<issue>3</issue>
<fpage>189</fpage>
<lpage>194</lpage>
<pub-id pub-id-type="medline">11026588</pub-id>
<pub-id pub-id-type="pmid">11026588</pub-id>
</element-citation>
</ref>
<ref id="ref9"><label>9</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Istepanian</surname>
<given-names>RSH</given-names>
</name>
<name><surname>Lacal</surname>
<given-names>JC</given-names>
</name>
</person-group>
<article-title>Emerging mobile communication technologies for health: some imperative notes on m-health</article-title>
<year>2003</year>
<conf-name>25th Annual International Conference of the IEEE Engineering in Medicine and Biology Society</conf-name>
<conf-date>September 17-21</conf-date>
<conf-loc>Cancun, Mexico</conf-loc>
<publisher-name>IEEE</publisher-name>
<fpage>1414</fpage>
<lpage>1416</lpage>
<pub-id pub-id-type="doi">10.1109/IEMBS.2003.1279581</pub-id>
</element-citation>
</ref>
<ref id="ref10"><label>10</label>
<element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Istepanian</surname>
<given-names>RSH</given-names>
</name>
<name><surname>Laxminarayan</surname>
<given-names>S</given-names>
</name>
<name><surname>Pattichis</surname>
<given-names>CS</given-names>
</name>
</person-group>
<article-title>M-Health: Emerging Mobile Health Systems</article-title>
<source>M-health: emerging mobile health systems</source>
<year>2006</year>
<publisher-loc>New York, NY</publisher-loc>
<publisher-name>Springer</publisher-name>
</element-citation>
</ref>
<ref id="ref11"><label>11</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Paré</surname>
<given-names>G</given-names>
</name>
<name><surname>Moqadem</surname>
<given-names>K</given-names>
</name>
<name><surname>Pineau</surname>
<given-names>G</given-names>
</name>
<name><surname>St-Hilaire</surname>
<given-names>C</given-names>
</name>
</person-group>
<article-title>Clinical effects of home telemonitoring in the context of diabetes, asthma, heart failure and hypertension: a systematic review</article-title>
<source>J Med Internet Res</source>
<year>2010</year>
<month>6</month>
<volume>12</volume>
<issue>2</issue>
<fpage>e21</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2010/2/e21/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.1357</pub-id>
<pub-id pub-id-type="medline">20554500</pub-id>
<pmc-comment>v12i2e21 </pmc-comment>
<pmc-comment>PMC2956232 </pmc-comment>
<pub-id pub-id-type="pmid">20554500</pub-id>
</element-citation>
</ref>
<ref id="ref12"><label>12</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Fayn</surname>
<given-names>J</given-names>
</name>
<name><surname>Rubel</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Toward a personal health society in cardiology</article-title>
<source>IEEE Trans Inf Technol Biomed</source>
<year>2010</year>
<month>3</month>
<volume>14</volume>
<issue>2</issue>
<fpage>401</fpage>
<lpage>409</lpage>
<pub-id pub-id-type="doi">10.1109/TITB.2009.2037616</pub-id>
<pub-id pub-id-type="medline">20007033</pub-id>
<pub-id pub-id-type="pmid">20007033</pub-id>
</element-citation>
</ref>
<ref id="ref13"><label>13</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Lin</surname>
<given-names>CT</given-names>
</name>
<name><surname>Chang</surname>
<given-names>KC</given-names>
</name>
<name><surname>Lin</surname>
<given-names>CL</given-names>
</name>
<name><surname>Chiang</surname>
<given-names>CC</given-names>
</name>
<name><surname>Lu</surname>
<given-names>SW</given-names>
</name>
<name><surname>Chang</surname>
<given-names>SS</given-names>
</name>
<name><surname>Lin</surname>
<given-names>BS</given-names>
</name>
<name><surname>Liang</surname>
<given-names>HY</given-names>
</name>
<name><surname>Chen</surname>
<given-names>RJ</given-names>
</name>
<name><surname>Lee</surname>
<given-names>YT</given-names>
</name>
<name><surname>Ko</surname>
<given-names>LW</given-names>
</name>
</person-group>
<article-title>An intelligent telecardiology system using a wearable and wireless ECG to detect atrial fibrillation</article-title>
<source>IEEE Trans Inf Technol Biomed</source>
<year>2010</year>
<month>5</month>
<volume>14</volume>
<issue>3</issue>
<fpage>726</fpage>
<lpage>733</lpage>
<pub-id pub-id-type="doi">10.1109/TITB.2010.2047401</pub-id>
<pub-id pub-id-type="medline">20371411</pub-id>
<pub-id pub-id-type="pmid">20371411</pub-id>
</element-citation>
</ref>
<ref id="ref14"><label>14</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kollmann</surname>
<given-names>A</given-names>
</name>
<name><surname>Riedl</surname>
<given-names>M</given-names>
</name>
<name><surname>Kastner</surname>
<given-names>P</given-names>
</name>
<name><surname>Schreier</surname>
<given-names>G</given-names>
</name>
<name><surname>Ludvik</surname>
<given-names>B</given-names>
</name>
</person-group>
<article-title>Feasibility of a mobile phone-based data service for functional insulin treatment of type 1 diabetes mellitus patients</article-title>
<source>J Med Internet Res</source>
<year>2007</year>
<month>12</month>
<volume>9</volume>
<issue>5</issue>
<fpage>e36</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2007/5/e36/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.9.5.e36</pub-id>
<pub-id pub-id-type="medline">18166525</pub-id>
<pmc-comment>v9i5e36 </pmc-comment>
<pmc-comment>PMC2270419 </pmc-comment>
<pub-id pub-id-type="pmid">18166525</pub-id>
</element-citation>
</ref>
<ref id="ref15"><label>15</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mougiakakou</surname>
<given-names>SG</given-names>
</name>
<name><surname>Bartsocas</surname>
<given-names>CS</given-names>
</name>
<name><surname>Bozas</surname>
<given-names>E</given-names>
</name>
<name><surname>Chaniotakis</surname>
<given-names>N</given-names>
</name>
<name><surname>Iliopoulou</surname>
<given-names>D</given-names>
</name>
<name><surname>Kouris</surname>
<given-names>I</given-names>
</name>
<name><surname>Pavlopoulos</surname>
<given-names>S</given-names>
</name>
<name><surname>Prountzou</surname>
<given-names>A</given-names>
</name>
<name><surname>Skevofilakas</surname>
<given-names>M</given-names>
</name>
<name><surname>Tsoukalis</surname>
<given-names>A</given-names>
</name>
<name><surname>Varotsis</surname>
<given-names>K</given-names>
</name>
<name><surname>Vazeou</surname>
<given-names>A</given-names>
</name>
<name><surname>Zarkogianni</surname>
<given-names>K</given-names>
</name>
<name><surname>Nikita</surname>
<given-names>KS</given-names>
</name>
</person-group>
<article-title>SMARTDIAB: a communication and information technology approach for the intelligent monitoring, management and follow-up of type 1 diabetes patients</article-title>
<source>IEEE Trans Inf Technol Biomed</source>
<year>2010</year>
<month>5</month>
<volume>14</volume>
<issue>3</issue>
<fpage>622</fpage>
<lpage>33</lpage>
<pub-id pub-id-type="doi">10.1109/TITB.2009.2039711</pub-id>
<pub-id pub-id-type="medline">20123578</pub-id>
<pub-id pub-id-type="pmid">20123578</pub-id>
</element-citation>
</ref>
<ref id="ref16"><label>16</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Jara</surname>
<given-names>AJ</given-names>
</name>
<name><surname>Zamora</surname>
<given-names>MA</given-names>
</name>
<name><surname>Skarmeta</surname>
<given-names>AFG</given-names>
</name>
</person-group>
<article-title>An internet of things–based personal device for diabetes therapy management in ambient assisted living (AAL)</article-title>
<source>Pers Ubiquit Comput</source>
<year>2011</year>
<month>1</month>
<day>2011</day>
<volume>15</volume>
<issue>4</issue>
<fpage>431</fpage>
<lpage>440</lpage>
<pub-id pub-id-type="doi">10.1007/s00779-010-0353-1</pub-id>
</element-citation>
</ref>
<ref id="ref17"><label>17</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Zhu</surname>
<given-names>F</given-names>
</name>
<name><surname>Bosch</surname>
<given-names>M</given-names>
</name>
<name><surname>Woo</surname>
<given-names>I</given-names>
</name>
<name><surname>Kim</surname>
<given-names>S</given-names>
</name>
<name><surname>Boushey</surname>
<given-names>CJ</given-names>
</name>
<name><surname>Ebert</surname>
<given-names>DS</given-names>
</name>
<name><surname>Delp</surname>
<given-names>EJ</given-names>
</name>
</person-group>
<article-title>The Use of Mobile Devices in Aiding Dietary Assessment and Evaluation</article-title>
<source>IEEE J Sel Top Signal Process</source>
<year>2010</year>
<month>8</month>
<volume>4</volume>
<issue>4</issue>
<fpage>756</fpage>
<lpage>766</lpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://europepmc.org/abstract/MED/20862266"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.1109/JSTSP.2010.2051471</pub-id>
<pub-id pub-id-type="medline">20862266</pub-id>
<pmc-comment>PMC2941896 </pmc-comment>
<pub-id pub-id-type="pmid">20862266</pub-id>
</element-citation>
</ref>
<ref id="ref18"><label>18</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Pollak</surname>
<given-names>J</given-names>
</name>
<name><surname>Gay</surname>
<given-names>G</given-names>
</name>
<name><surname>Byrne</surname>
<given-names>S</given-names>
</name>
<name><surname>Wagner</surname>
<given-names>E</given-names>
</name>
<name><surname>Retelny</surname>
<given-names>D</given-names>
</name>
<name><surname>Humphreys</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>It's Time to Eat! Using Mobile Games to Promote Healthy Eating</article-title>
<source>IEEE Pervasive Comput</source>
<year>2010</year>
<month>7</month>
<day>2010</day>
<volume>9</volume>
<issue>3</issue>
<fpage>21</fpage>
<lpage>27</lpage>
<pub-id pub-id-type="doi">10.1109/MPRV.2010.41</pub-id>
</element-citation>
</ref>
<ref id="ref19"><label>19</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Patrick</surname>
<given-names>K</given-names>
</name>
<name><surname>Raab</surname>
<given-names>F</given-names>
</name>
<name><surname>Adams</surname>
<given-names>MA</given-names>
</name>
<name><surname>Dillon</surname>
<given-names>L</given-names>
</name>
<name><surname>Zabinski</surname>
<given-names>M</given-names>
</name>
<name><surname>Rock</surname>
<given-names>CL</given-names>
</name>
<name><surname>Griswold</surname>
<given-names>WG</given-names>
</name>
<name><surname>Norman</surname>
<given-names>GJ</given-names>
</name>
</person-group>
<article-title>A text message-based intervention for weight loss: randomized controlled trial</article-title>
<source>J Med Internet Res</source>
<year>2009</year>
<volume>11</volume>
<issue>1</issue>
<fpage>e1</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2009/1/e1/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.1100</pub-id>
<pub-id pub-id-type="medline">19141433</pub-id>
<pmc-comment>v11i1e1 </pmc-comment>
<pmc-comment>PMC2729073 </pmc-comment>
<pub-id pub-id-type="pmid">19141433</pub-id>
</element-citation>
</ref>
<ref id="ref20"><label>20</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Watson</surname>
<given-names>A</given-names>
</name>
<name><surname>Bickmore</surname>
<given-names>T</given-names>
</name>
<name><surname>Cange</surname>
<given-names>A</given-names>
</name>
<name><surname>Kulshreshtha</surname>
<given-names>A</given-names>
</name>
<name><surname>Kvedar</surname>
<given-names>J</given-names>
</name>
</person-group>
<article-title>An internet-based virtual coach to promote physical activity adherence in overweight adults: randomized controlled trial</article-title>
<source>J Med Internet Res</source>
<year>2012</year>
<volume>14</volume>
<issue>1</issue>
<fpage>e1</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2012/1/e1/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.1629</pub-id>
<pub-id pub-id-type="medline">22281837</pub-id>
<pmc-comment>v14i1e1 </pmc-comment>
<pmc-comment>PMC3374543 </pmc-comment>
<pub-id pub-id-type="pmid">22281837</pub-id>
</element-citation>
</ref>
<ref id="ref21"><label>21</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Whittaker</surname>
<given-names>R</given-names>
</name>
<name><surname>Dorey</surname>
<given-names>E</given-names>
</name>
<name><surname>Bramley</surname>
<given-names>D</given-names>
</name>
<name><surname>Bullen</surname>
<given-names>C</given-names>
</name>
<name><surname>Denny</surname>
<given-names>S</given-names>
</name>
<name><surname>Elley</surname>
<given-names>CR</given-names>
</name>
<name><surname>Maddison</surname>
<given-names>R</given-names>
</name>
<name><surname>McRobbie</surname>
<given-names>H</given-names>
</name>
<name><surname>Parag</surname>
<given-names>V</given-names>
</name>
<name><surname>Rodgers</surname>
<given-names>A</given-names>
</name>
<name><surname>Salmon</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>A theory-based video messaging mobile phone intervention for smoking cessation: randomized controlled trial</article-title>
<source>J Med Internet Res</source>
<year>2011</year>
<volume>13</volume>
<issue>1</issue>
<fpage>e10</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2011/1/e10/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.1553</pub-id>
<pub-id pub-id-type="medline">21371991</pub-id>
<pmc-comment>v13i1e10 </pmc-comment>
<pmc-comment>PMC3221331 </pmc-comment>
<pub-id pub-id-type="pmid">21371991</pub-id>
</element-citation>
</ref>
<ref id="ref22"><label>22</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Déglise</surname>
<given-names>C</given-names>
</name>
<name><surname>Suggs</surname>
<given-names>LS</given-names>
</name>
<name><surname>Odermatt</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Short message service (SMS) applications for disease prevention in developing countries</article-title>
<source>J Med Internet Res</source>
<year>2012</year>
<volume>14</volume>
<issue>1</issue>
<fpage>e3</fpage>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.jmir.org/2012/1/e3/"></ext-link>
</comment>
<pub-id pub-id-type="doi">10.2196/jmir.1823</pub-id>
<pub-id pub-id-type="medline">22262730</pub-id>
<pmc-comment>v14i1e3 </pmc-comment>
<pub-id pub-id-type="pmid">22262730</pub-id>
</element-citation>
</ref>
<ref id="ref23"><label>23</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Silva</surname>
<given-names>BMC</given-names>
</name>
<collab>Rodrigues JJPC</collab>
<name><surname>Lopes</surname>
<given-names>IMC</given-names>
</name>
<name><surname>Machado</surname>
<given-names>TMF</given-names>
</name>
<name><surname>Zhou</surname>
<given-names>L</given-names>
</name>
</person-group>
<article-title>A Novel Cooperation Strategy for Mobile Health Applications</article-title>
<source>IEEE Journal on Selected Areas in Communications Special Issue on Emerging Technologies in Communications - eHealth, IEEE Communications Society</source>
<year>2013</year>
<fpage>1</fpage>
<lpage>9</lpage>
<comment>(forthcoming)</comment>
</element-citation>
</ref>
<ref id="ref24"><label>24</label>
<element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Silva</surname>
<given-names>BMC</given-names>
</name>
<name><surname>Lopes</surname>
<given-names>IMC</given-names>
</name>
<name><surname>Rodrigues</surname>
<given-names>JJPC</given-names>
</name>
<name><surname>Ray</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>SapoFitness: A mobile health application for dietary evaluation</article-title>
<year>2011</year>
<conf-name>13th IEEE International Conference on e-Health Networking Applications and Services (IEEE HEALTHCOM 2011)</conf-name>
<conf-date>June 13-15, 2011</conf-date>
<conf-loc>Columbia, MO, USA</conf-loc>
<publisher-name>IEEE</publisher-name>
<fpage>13</fpage>
<lpage>20</lpage>
<pub-id pub-id-type="doi">10.1109/HEALTH.2011.6026782</pub-id>
</element-citation>
</ref>
<ref id="ref25"><label>25</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Rodrigues</surname>
<given-names>JJ</given-names>
</name>
<name><surname>Lopes</surname>
<given-names>IM</given-names>
</name>
<name><surname>Silva</surname>
<given-names>BM</given-names>
</name>
<name><surname>de la Torre</surname>
<given-names>I</given-names>
</name>
</person-group>
<article-title>A new mobile ubiquitous computing application to control obesity: SapoFit</article-title>
<source>Inform Health Soc Care</source>
<year>2013</year>
<month>1</month>
<volume>38</volume>
<issue>1</issue>
<fpage>37</fpage>
<lpage>53</lpage>
<pub-id pub-id-type="doi">10.3109/17538157.2012.674586</pub-id>
<pub-id pub-id-type="medline">22657250</pub-id>
<pub-id pub-id-type="pmid">22657250</pub-id>
</element-citation>
</ref>
<ref id="ref26"><label>26</label>
<element-citation publication-type="webpage"><source>SapoFit</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="https://itunes.apple.com/pt/app/sapo-fit/id438487775?mt=8">https://itunes.apple.com/pt/app/sapo-fit/id438487775?mt=8</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw2BHsOA"></ext-link>
</element-citation>
</ref>
<ref id="ref27"><label>27</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Jonsson</surname>
<given-names>J</given-names>
</name>
<name><surname>Kaliski</surname>
<given-names>B</given-names>
</name>
</person-group>
<source>Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw66XuiI"></ext-link>
</element-citation>
</ref>
<ref id="ref28"><label>28</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Raeburn</surname>
<given-names>K</given-names>
</name>
</person-group>
<source>Advanced Encryption Standard (AES) Encryption for Kerberos 5</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw4IKbXi"></ext-link>
</element-citation>
</ref>
<ref id="ref29"><label>29</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Housley</surname>
<given-names>R</given-names>
</name>
</person-group>
<source>Triple-DES and RC2 Key Wrapping</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw4ZXBdH"></ext-link>
</element-citation>
</ref>
<ref id="ref30"><label>30</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Jaganathan</surname>
<given-names>K</given-names>
</name>
<name><surname>Zhu</surname>
<given-names>L</given-names>
</name>
<name><surname>Brezak</surname>
<given-names>J</given-names>
</name>
</person-group>
<source>The RC4-HMAC Kerberos Encryption Types</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw5Lwx1B"></ext-link>
</element-citation>
</ref>
<ref id="ref31"><label>31</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Shirey</surname>
<given-names>R</given-names>
</name>
</person-group>
<source>Internet Security Glossary, Version 2</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw5pWnxS"></ext-link>
</element-citation>
</ref>
<ref id="ref32"><label>32</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>Rescorla</surname>
<given-names>E</given-names>
</name>
</person-group>
<source>Diffie-Hellman Key Agreement Method</source>
<date-in-citation>2013-02-15</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/">http://www.rfc-editor.org/</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6Cw6I1jk5"></ext-link>
</element-citation>
</ref>
<ref id="ref33"><label>33</label>
<element-citation publication-type="webpage"><person-group person-group-type="author"><name><surname>McGrew</surname>
<given-names>D</given-names>
</name>
<name><surname>Igoe</surname>
<given-names>M</given-names>
</name>
<name><surname>Salter</surname>
<given-names>M</given-names>
</name>
</person-group>
<source>Fundamental Elliptic Curve Cryptography Algorithms</source>
<date-in-citation>2013-02-28</date-in-citation>
<comment><ext-link ext-link-type="uri" xlink:href="http://www.rfc-editor.org/rfc/rfc6090.txt">http://www.rfc-editor.org/rfc/rfc6090.txt</ext-link>
</comment>
<ext-link ext-link-type="webcite" xlink:href="6E0ktAxqb"></ext-link>
</element-citation>
</ref>
<ref id="ref34"><label>34</label>
<element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Raychaudhuri</surname>
<given-names>K</given-names>
</name>
<name><surname>Ray</surname>
<given-names>P</given-names>
</name>
</person-group>
<article-title>Privacy Challenges in the Use of eHealth Systems for Public Health Management</article-title>
<source>International Journal of e-Health and Medical Communications, IGI-Global</source>
<year>2010</year>
<volume>1</volume>
<issue>2</issue>
<fpage>12</fpage>
<lpage>23</lpage>
<pub-id pub-id-type="doi">10.4018/jehmc.2010040102</pub-id>
</element-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/TelematiV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000479 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000479 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= TelematiV1 |flux= Pmc |étape= Corpus |type= RBID |clé= PMC:3636327 |texte= A Data Encryption Solution for Mobile Health Apps in Cooperation Environments }}
Pour générer des pages wiki
HfdIndexSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/RBID.i -Sk "pubmed:23624056" \ | HfdSelect -Kh $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd \ | NlmPubMed2Wicri -a TelematiV1
![]() | This area was generated with Dilib version V0.6.31. | ![]() |