Evidence map›Paper›PMID 27147515›Full record

ArticleJournal of medical systems2016

Security Recommendations for mHealth Apps: Elaboration of a Developer's Guide.

Enrique Pérez Morera, Isabel de la Torre Díez, Begoña Garcia-Zapirain, Miguel López-Coronado, Jon Arambarri

Abstract read
PubMed Publisher
In one paragraph

Article in Journal of medical systems, 2016. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 22 papers.

0numbers the graph read from it
0cells of the map it votes in
22citing papers in PubMed
–field-weighted citation impact
1 · What the graph read from it

What it found

Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.

The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.

2 · The registry

The trial behind it

Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.

Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.

3 · Its place in the literature

Who cites it

22 citing papers in PubMed.

  1. Trial
  2. Article
  3. Article
  4. Article
  5. Article
  6. Article
  7. Article
  8. Article
  9. Evaluation of Android and Apple Store Depression Applications Based on Mobile Application Rating Scale.International journal of environmental research and public health · 2021
    Review
  10. Article
  11. Article
  12. Article
  13. Article
  14. Article
  15. Article
  16. Article
  17. Article
  18. Article
  19. Review
  20. Article
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

5 authors.

Enrique Pérez MoreraDepartment of Signal Theory and Communications, and Telematics Engineering, University of Valladolid, Paseo de Belén, 15, 47011, Valladolid, Spain.
Isabel de la Torre DíezDepartment of Signal Theory and Communications, and Telematics Engineering, University of Valladolid, Paseo de Belén, 15, 47011, Valladolid, Spain. isator@tel.uva.es.
Begoña Garcia-ZapirainUniversity of Deusto, Avenida de las Universidades 24, 48007, Bilbao, Spain.
Miguel López-CoronadoDepartment of Signal Theory and Communications, and Telematics Engineering, University of Valladolid, Paseo de Belén, 15, 47011, Valladolid, Spain.
Jon ArambarriVirtualWare Labs Foundation, C/ Usausuaga, 7, 48970, Basauri, Vizcaya, Spain.

Funding

No grant is acknowledged in the PubMed record.

6 · The paper itself

Abstract

Being the third fastest-growing app category behind games and utilities, mHealth apps are changing the healthcare model, as medicine today involves the data they compile and analyse, information known as Big Data. However, the majority of apps are lacking in security when gathering and dealing with the information, which becomes a serious problem. This article presents a guide regarding security solution, intended to be of great use for developers of mHealth apps. In August 2015 current mobile health apps were sought out in virtual stores such as Android Google Play, Apple iTunes App Store etc., in order to classify them in terms of usefulness. After this search, the most widespread weaknesses in the field of security in the development of these mobile apps were examined, based on sources such as the "OWASP Mobile Security Project, the initiative recently launched by the Office of Civil Rights (OCR), and other articles of scientific interest. An informative, elemental guide has been created for the development of mHealth apps. It includes information about elements of security and its implementation on different levels for all types of mobile health apps based on the data that each app manipulates, the associated calculated risk as a result of the likelihood of occurrence and the threat level resulting from its vulnerabilities - high level (apps for monitoring, diagnosis, treatment and care) from 6 ≤ 9, medium level (calculator, localizer and alarm) from 3 ≤ 6 and low level (informative and educational apps) from 0 ≤ 3. The guide aims to guarantee and facilitate security measures in the development of mobile health applications by programmers unconnected to the ITC and professional health areas.

Indexed as

Computer SecurityTelemedicineSoftware DesignAppsDevelopers’ guidemHealthSecurity

Identifiers

What OpenQuestion holds

Textmetadata
Read underepoch 390

Registered trials

None linked

Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.