Journal Information
Vol. 34. Issue. 2.March 2014
Pages 0-272
Vol. 34. Issue. 2.March 2014
Pages 0-272
DOI: 10.3265/Nefrologia.pre2014.Jan.12115
Full text access
Methodological approach to designing a telecare system for pre-dialysis and peritoneal dialysis patients
Aproximación metodológica al diseño de un sistema de teleasistencia para pacientes en prediálisis y diálisis peritoneal
Jorge Calvillo Arbizua, Jorge Calvillo-Arbizub, Laura María Roa Romeroc, Laura M. Roa-Romerob, José A. Milán Martínd, José A. Milán-Martíne, Nuria Aresté Fosalbaf, Nuria Aresté-Fosalbag, Fernando Tornero Molinah, Fernando Tornero-Molinai, Manuel Macía Herasj, Manuel Macía-Herask, Nicanor Vega Díazl, Nicanor Vega-Díazm
a Grupo de Ingenier??a Biom??dica, Universidad de Sevilla, Sevilla, Spain,
b Grupo de Ingenier??a Biom??dica; CIBER-BBN, Universidad de Sevilla,
c Grupo de Ingenier??a Biom??dica, Universidad de Sevilla; CIBER-BBN, Sevilla, Spain,
d Nefrolog??a, Hospital Universitario Virgen Macarena. Grupo de Ingenier??a Biom??dica, Universidad de Sevilla; CIBER-BBN, Sevilla, Spain,
e Grupo de Ingenier??a Biom??dica; CIBER-BBN. Universidad de Sevilla, Servicio de Nefrolog??a. Hospital Universitario Virgen Macarena, Sevilla,
f Nefrologia, Servicio de Nefrolog??a, Hospital Universitario Virgen Macarena, Sevilla, Spain,
g Servicio de Nefrolog??a, Hospital Universitario Virgen Macarena, Sevilla,
h Nefrolog??a, Hospital Sureste de Madrid, Madrid, Spain,
i Servicio de Nefrolog??a, Hospital Sureste de Madrid,
j Nefrologia, Hospital Universitario Ntra. Sra. de Candelaria, Santa Cruz de Tenerife, Islas Canarias, Spain,
k Servicio de Nefrologia, Hospital Universitario Nuestra Se??ora de Candelaria, Santa Cruz de Tenerife,
l Nefrologia, Hospital Universitario Dr. Negr??n, Las Palmas de Gran Canaria Islas Canarias, Spain,
m Servicio de Nefrolog??a, Hospital Universitario Doctor Negr??n, Las Palmas de Gran Canaria
Article information
Full Text
Download PDF
Figures (3)
Show moreShow less

Antecedentes: Un importante obstáculo que dificulta el despliegue de soluciones tecnológicas en sanidad es el rechazo que encuentran los sistemas desarrollados por los usuarios que tienen que utilizarlos (ya sean profesionales sanitarios o pacientes), que consideran que no se adaptan a sus necesidades reales. Objetivos: (1) Diseñar una arquitectura tecnológica para la asistencia remota de pacientes nefrológicos aplicando una metodología que prime la implicación de los usuarios (profesionales y pacientes) en todo el diseño y desarrollo; (2) ilustrar cómo las necesidades de los usuarios pueden ser recogidas y respondidas mediante la tecnología, aumentando el nivel de aceptación de los sistemas finales. Métodos: Para obtener las principales necesidades que existen actualmente en Nefrología se implicó a un conjunto de servicios españoles de la especialidad. Se realizó una recogida de necesidades mediante entrevistas semiestructuradas al equipo médico y cuestionarios a profesionales y pacientes. Resultados: Se extrajeron un conjunto de requisitos tanto de profesionales como de pacientes y, paralelamente, el grupo de ingenieros biomédicos identificó requisitos de la asistencia remota de pacientes desde un punto de vista tecnológico. Todos estos requisitos han dado pie al diseño de una arquitectura modular para la asistencia remota de pacientes en diálisis peritoneal y prediálisis. Conclusiones: Este trabajo ilustra cómo es posible implicar a los usuarios en todo el proceso de diseño y desarrollo de un sistema. Fruto de este trabajo es el diseño de una arquitectura modular adaptable para asistencia remota de pacientes nefrológicos respondiendo a las preferencias y necesidades de los usuarios pacientes y profesionales consultados.

Palabras clave:
Diseño de sistemas
Palabras clave:

Background: A major obstacle that hinders the implementation of technological solutions in healthcare is the rejection of developed systems by users (healthcare professionals and patients), who consider that they do not adapt to their real needs. Objectives: (1) To design technological architecture for the telecare of nephrological patients by applying a methodology that prioritises the involvement of users (professionals and patients) throughout the design and development process; (2) to show how users’ needs can be determined and addressed by means of technology, increasing the acceptance level of the final systems. Methods: In order to determine the main current needs in Nephrology, a group of Spanish Nephrology Services was involved. Needs were recorded through semi-structured interviews with the medical team and questionnaires for professionals and patients. Results: A set of requirements were garnered from professionals and patients. In parallel, the group of biomedical engineers identified requirements for patient telecare from a technological perspective. All of these requirements drove the design of modular architecture for the telecare of peritoneal dialysis and pre-dialysis patients. Conclusions: This work shows how it is possible to involve users in the whole process of design and development of a system. The result of this work is the design of adaptable modular architecture for the telecare of nephrological patients and it addresses the preferences and needs of patient and professional users consulted.

System design
Full Text



The application of information and communications technology (ICT) in the healthcare domain has revolutionised all areas and specialties of care. In Nephrology, the application of ICT may provide care with advanced capabilities, such as the remote monitoring of haemodialysis patients, the monitoring of dialysis sessions for the early detection of problems and the transfer of data and messages from the home to the healthcare organisation or the development of artificial kidneys.1-4 These advances have not yet been implemented in healthcare practice mainly because there are various obstacles that hinder the effective application of ICT. One of them is the rejection of the systems by those who have to use them (whether they be healthcare professionals or patients), who consider that they are not adapted to their real needs.1,5,6

Apart from the advanced capabilities involved in applying ICT, another benefit that is often discussed is the improvement in healthcare process efficiency and the reduction of associated costs.7,8 An example supporting telemedicine for peritoneal dialysis patients is9 that this technique involves saving expenses on medical transport and obtains a positive response from patients. Given the ageing population, the resulting growing demand for healthcare services and the current economic climate, this type of technique that optimises resources and improves the cost-efficiency relationship of healthcare becomes indispensable. This is particularly urgent in Nephrology, given that renal replacement therapy has high costs and is very demanding from an organisational point of view.10,11

As a result, the effective application of ICT in healthcare, although it can be beneficial on various levels (organisational, care, etc.), has many complex requirements from very diverse disciplines (technology, healthcare, resource management, etc.). Some of these are:

  • Sustainability must be one of the keys of the developments, prioritising solutions with a high cost-efficiency rate. That is, we must try to apply the most suitable (not the latest) technology with respect to the particular needs of the problem.12,13
  • In a setting as fragmented as healthcare, the systems must be integrated and cooperate with each other with the aim of reducing the impact of isolated systems. Interoperability is a necessary requirement for the advancement of healthcare information systems with advanced capabilities.14
  • The continuity of care should be promoted through administrative, regional and time barriers. Healthcare practice is increasingly distributed and shared between separate organisations. The continuity of care, closely related to aspects of technical and organisational interoperability, is a key requirement for strengthening the quality of healthcare services.15
  • Given the highly sensitive nature of the information managed in this setting (mainly administrative and health data), the protection of systems and confidentiality of communications are indispensable requirements for any application of ICT in healthcare.16
  • Lastly, from the clinical point of view, a key aspect in the development of ICT solutions must be the involvement of users in the whole design process and as evaluators of developments. User (whether they be healthcare professionals or patients) contributions are often avoided in the design and development of the systems, resulting in technological applications with major rejections by users because they are not adapted to the daily practice methods or they have limited usability.17

The complexity involved in covering and satisfying such a wide and heterogeneous spectrum of requirements (those previously described are only some examples) is one of the main obstacles for the development of efficient and complete solutions. The application of ICT in healthcare following a methodological approach will be key to coping with this complexity and will also allow the implementation of new healthcare settings, cost reduction and an improvement in healthcare processes.

Taking into account the current situation of the Spanish healthcare system, a project called e-Nefro18 has been developed in which a methodology that applies ICT to healthcare is put into practice and it prioritises the involvement of its users in all the stages of its design and development. The methodology is explained in section 2, as well as the key aspects on which it is based. Section 3 briefly describes the aim of this initiative, it explains the requirements provided by users and experts and it presents an initial approach to the system design. Section 4 summarises the conclusions.




The domain of ICT system design and development methodologies has grown exponentially in the last few decades and there are currently many methodological approaches with different aims (development of software and/or hardware, for example), means of operation (in cascade, iterative, etc.) or key aspects (usability, user experience, sustainability, etc.).19

One of the factors that most affects the success of ICT applications in healthcare is the imperfect understanding between the parties involved in the design, development and use of the systems, particularly whenever the users’ requirements are established. All information systems need to be user-centred in terms of design. This is applied with greater emphasis in the healthcare domain and mainly whenever the systems are directly involved in patient care, since the latter may be users of the system (aside from professional users). Recognising the final users as key participants to be involved in all stages of system design and development may contribute to the latter having greater opportunities of success once it is implemented and in use.

User involvement and the consideration of their needs in the design and development processes are widely recognised aspects, but it is still not very clear how they can be used in practice.20 There are many different work philosophies that try to involve users in the design processes, such as user-centred design,21 participatory design,22 design for all (which strengthens the inclusion of all types of users)23 or human-centred design (which is addressed in regulation ISO 9241-210).24 The benefits of proposals focussed on the user and applied to the healthcare domain include: greater patient safety, better healthcare results and greater user satisfaction.25,26

Resulting from the analysis of general purpose methodologies, a method of applying ICT in the healthcare domain has been set out (Figure 1). This methodological approach takes into account design principles considered as good practices in the applicable regulations.24 These are:

  • Understanding the users, tasks and settings. Faced with any design it is necessary to be sure of the profiles of those who are going to use the system. As such, not only must different types of users be taken into account (patients, healthcare professionals, carers, etc.), but rather the degree of digital and health literacy of each user must also be considered. The system, therefore, must be adapted to the needs, uses and preferences of each user with their specific characteristics.
  • The involvement of the user in the design and development: this provides a valuable source of knowledge about the context of use and how users prefer to work with the system being developed.
  • Design and development cycle based on incremental iterations. At the end of each cycle, a completely functional and validated prototype will be obtained, although not with all the capabilities of the final system intended to be developed. The first phase of each cycle is an incremental revision in which the scope of the prototype to be developed in this cycle is defined and the objectives developed thus far are analysed. This phase has two aims: it allows the following cycle to be planned, specifying exactly what parts of the system are going to be developed and, furthermore, it is a phase in which the process is evaluated and its efficiency improved, since errors in previous cycles are identified and corrected.
  • Continuous user-centred evaluation. The final stage of developing a system often involves its evaluation and this is when faults and errors appear that are difficult to rectify at such an advanced stage. As such, the evaluation must be carried out from the start of the project as an integral part of it. The system also becomes more robust as it acquires knowledge and experience of potential failures and how to resolve them, which allows for special attention and anticipation of adequate alternatives when the fault has implications for patient care.
  • As illustrated in Figure 1, our methodological proposal begins with a collection of user requirements (taking into account the wide heterogeneity of potential users) and of the technological requirements defined by the team of developers. An initial design of the system is thereby carried out for the first iteration and it is developed and validated with the users. This cycle continues and functionality is added to the system until the complete solution is achieved.

    Below, we describe the application of this methodology to the e-Nefro project, whose objective is the design and development of a telecare system for pre-dialysis and peritoneal dialysis patients.




    The e-Nefro project (Adaptable modular architecture for the comprehensive telecare of kidney patients)18 is a multicentre effort between the Universidad de Sevilla and various national hospitals, whose objective is to establish architecture that is applicable and adaptable to the telecare of pre-dialysis and peritoneal dialysis patients. It is being carried out using the methodology presented in the previous section, with users having an active role in the design and development of the end solution. With the aim of involving them in the development of the systems to be applied, the first step was to determine the main current needs in a group of Spanish Nephrology services from the experiences and perspective of nephrologists and the patients themselves. This garnering of needs and requirements was carried out in three stages:

  • Semi-structured interviews with the medical team: an understanding was gained of the reality of healthcare for pre-dialysis and peritoneal dialysis patients in Spain and the potential needs and interests of the medical team were studied.
  • Questionnaires for professionals (nephrologists and nurses) and patients (on pre-dialysis and peritoneal dialysis): these were conducted with the aim of learning their experiences in the different services and understanding what are, from their different points of view, the healthcare needs and current technologies. This form of consultation allowed a varied collection of information (direct contact between the design team and users was not necessary), thus allowing different geographically separated national services to be covered, with the idea of obtaining multicentre information and reducing the possible bias of local experiences. The Nephrology services involved were those belonging to: Hospital Sureste de Madrid, Hospital Universitario Doctor Negrín de Gran Canaria, Hospital Universitario Nuestra Señora de Candelaria de Tenerife and Hospital Universitario Virgen Macarena de Sevilla. Figure 2 displays the sets of questions of which the questionnaires consisted.
  • In parallel to the above consultations, we carried out a review of the literature in order to add other information published in this field to the results obtained.1-3,7,12
  • Furthermore, the development team, composed mainly of experts in biomedical engineering, established the main technological requirements that the system and its support infrastructure would have to meet. These requirements are displayed in section 3.2.


    3.1. Technology-independent aspects: the users’ point of view


    The interviews and questionnaires allowed two sets of requirements to be extracted: those from professional users and those identified by the patient users. This section briefly reports the most significant results of this needs collection task.

    Firstly, the healthcare professionals interviewed and surveyed thought that, by using technology, the efficiency of their care work could be improved, although they identified various obstacles and weak points that hinder this improvement process. The requirements that they proposed and that could be resolved by technology include:

  • The ability to access complete and reliable registries of patient users, as well as patient user data updated in real time at any time. One of the fundamental challenges that technology must resolve (according to 92% of professionals interviewed) is the coherent integration of all the information related to each patient, regardless of its nature (diagnostic tests, medication, past healthcare episodes, surgery report, etc.), in order that a professional may have all this information and may make ubiquitous use of it at any time.
  • Receiving critical events in real time and avoiding being inundated with non-critical alarms/interventions (this aspect would require each professional to configure the alarms that they wish to receive and their priority level). Professionals advocate the use of text messaging as a channel of communication with patients (61.5%), as well as for receiving alarms or abnormal events that require a quick response (53.77%). E-mail is, likewise, interesting for healthcare professionals, as long as the matter is not urgent (61.5%). Both this and the foregoing requirement are closely related to the strong component of mobility in healthcare, which requires professionals to move about the healthcare organisation, hindering their availability for traditional telephone communication.
  • The possibility of accessing useful information (with a flexible visualisation of the latter in accordance with the needs and preferences of each professional user) to assess the progression of patients. Another element considered to be interesting for patient telecare is the direct communication between patient and doctor, with the possibility of carrying out a consultation via videoconference and transferring data remotely without the need for travel or consultations in person (indicated by 83% of professionals surveyed).
  • From the questionnaires to patient users, we have deduced that the design and development of a telecare system for pre-dialysis and peritoneal dialysis patients must take into account:

  • The ability to automatically monitor and transfer healthcare and environmental conditions, as well as automatically or by request of the user, the capability to inform medical staff about emergency situations, resulting in a request for intervention or a consultation with the doctor. Although 92% of those surveyed consider the frequency of consultations in person to be adequate (generally every two months), most patients stress the importance of a communication channel during the consultation period in order that the doctor may be aware of the patient’s progression (71%) and in order to communicate alarms or abnormal events (85%).
  • The possibility of easily communicating with healthcare professionals and carers flexibly in accordance with the needs and preferences of each patient user. The frequency with which the doctor receives information from the patient may depend to a great extent on the willingness of the latter (for example, the frequency with which they evaluate their physiological parameters and fill in forms via the website). The results show that the patients’ willingness to send this information explicitly is low (half of those surveyed would agree to send data once a month, while only 35% would be prepared to so once a week). We conclude that a crucial design parameter is automation of the physiological variable collection process and the sending of data to the healthcare organisation in a manner that is transparent to the user.
  • The possibility of receiving useful information on the treatment of their illness and visualising the progression of their health data, indicated as desirable by 92% of users surveyed. It is interesting to highlight that patients, even when they wish to receive information concerning their health and the treatment of their illness, express the willingness to do so only when there is something interesting and not with a set frequency (as expressed in 72% of cases). This translates into the need for each patient to specify what they consider to be of interest and not of interest, and thus establish a personalised information system adapted to the specific preferences of each patient. In spite of this, it should always be the professionals who ultimately decide on the frequency with which the patients must be informed (or re-trained) in the treatment of their illness, thereby compensating the lack of willingness of those who show unreliability.

    3.2. Technology-dependent aspects


    In parallel to the study of the needs of professionals and patients, the group of biomedical engineers carried out an analysis from the technological point of view of patient telecare. The decentralised setting of healthcare that is determined by the remote monitoring of pre-dialysis and peritoneal dialysis patients in their home imposes a set of technological requirements on the solutions to develop. The most important are listed below:

  • Remote access: the components will be distributed geographically and the infrastructure must facilitate this communication.
  • Concurrency and asynchrony: the components must be able to be executed in parallel and there must not be dependence between some components and others in communication activities (for example, a patient may send data from their home without the need for their doctor to be simultaneously connected in the hospital to receive the data).
  • Availability: communication channels must be available at all times in order not to interrupt the components’ provision of service.
  • Heterogeneity: the system or system’s components may be built on different technologies and the latter may even change over time. The infrastructure must facilitate communication between heterogeneous components through the provision of technical, syntactic and semantic interoperability.
  • Transparency of complexity for the final user: patient and professional users must not be involved in the complexity inherent in the communications of the different systems.
  • Reliability in the distribution of messages: the infrastructure must ensure basic reliability in the distribution and submission of messages. There may be mechanisms for prioritising messages (for example, data for alarms) that are based on their reliability requirements.
  • Scalability of devices, services and users: the system must be designed ensuring that an increase in the number of components in a system or in systems or users can be assumed without a loss in the quality of service of communications.
  • Confidentiality (of transfer), safety (protection of the user’s information from non-authorised persons) and privacy (right of the user to control the dissemination of their personal information).
  • Sustainable cost/benefit relationship: the last design requirement is the need to develop a system that is economically and environmentally sustainable.

    3.3. Design of technological architecture for the telecare of pre-dialysis and peritoneal dialysis patients


    Given the technological and user requirements, the architecture that has to be designed is very complex. The use of middleware, providing elements and capabilities that allow most requirements of the distributed systems to be resolved makes it possible to simplify this complexity. One of the most widespread design paradigms of distributed systems, service-oriented architecture (SOA),27 establishes an architectural model that seeks system agility, efficiency and productivity, as well as services as its key component. The main characteristic of SOA is that it is independent of the underlying implementation technology. Applying this paradigm facilitates the satisfaction of functional requirements related to the operation, distribution and heterogeneity of the systems. The system is configured as services that, by their own definition, are autonomous and physically independent units (requirements of concurrency and asynchrony). Furthermore, use of the publication and discovery of services paradigm on which SOA is based satisfies distribution, scalability and heterogeneity requirements. On this middleware (which will consist of implementing SOA technology such as web services technologies28), services specific to the application domain will be developed, that is home telecare for pre-dialysis and peritoneal dialysis patients.

    To build flexible architecture that can be adapted to different settings and that is able to evolve over time, the most appropriate approach would be to follow a modular design in which the architecture is broken down into cooperating and independent systems, each centred on specific functionality with the possibility of replacing or adding modules without the need to modify the whole architecture. Figure 3 displays a diagram of this architecture that comprises an infrastructure of communications (falling primarily under middleware) and a set of systems, each centred on specific aspects of the complete architecture. Each subsystem is in turn composed of modules or services that encompass specific functionalities. An infrastructure system (IS) is defined and includes the basic functionality of communication between the patient’s home and the hospital (telecare module), between hospitals (interhospital module) and of data protection and privacy control (safety module). The IS provides the basic technological components that support the communication of data between systems (sending variable measurements from home to the hospital, transfer of patient histories between hospitals, etc.), as well as different means of communication between individuals (messaging, videoconferences, etc.).

    The access setting system (ASS) groups the whole functionality related to the specialised, patient user and healthcare professional interfaces. These modules allow access to architecture services to be personalised according to user preferences, their limitations and their authorised permits. The ASS will cover management and compliance with the preferences that each user has for accessing platform services. Some of these preferences could be: the frequency of receiving new information, the group of alert events that they wish to receive or the interface parameters in line with potential functional limitations for users (font size, use of screen reader software, auditory limitation, etc.).

    The aim of the monitoring system (MS) is to provide architecture with the capability of sending, receiving and consulting data between the patient’s home and the healthcare organisations, using the MS mechanisms both for communication and for safety. Furthermore, included in this system are all the specific pre-dialysis and peritoneal dialysis patient healthcare services. The remote configuration of devices and access to data obtained would also be carried out using this system. It would include, on one hand, the devices that automatically collect the user’s physiological variables and send them to the hospital, and on the other, the information systems that allow the patient (and specialised) user, through computers or mobile devices, to be aware of the activities determined by the professionals in their care plan. The professionals could also be aware of the incidents that occur to their patients, exchange messages with them and adapt the care plan of each, allowing continuous monitoring of the therapy, through various devices (mobiles, tablets or computers).

    Lastly, the service provider system (SPS) complements the architecture with a set of general purpose services added within the healthcare setting. These services contribute added value to the system and may be provided by one or several providers. In this system, we may find services designed for data processing, alarm management (notifying the relevant users in accordance with the protocol defined for each one) and knowledge generating tools (clinical decision support systems, simulation via mathematical models, etc.)


    We see how the modules, although independent and separate, are closely linked to one another. As such, for example, whenever a user accesses the system, they consult the corresponding ASS module to recover how they wish to access the information and how the latter should be presented. The safety module would have to be consulted previously in order that the user may authorise access to the system and indicate what functionality is available for it. In accordance with the service that the user will employ, MS or SPS modules will be used.

    Once the system is designed, the next step will consist of an iterative and incremental process of development in which involvement of the final users will be constant, and there will be a guarantee of acceptance once the system is developed. We should state that the aspects of usability of the devices and systems developed are envisaged in subsequent stages of the methodology and they will be addressed in the project when design has begun on the final user interfaces and devices.




    One of the main keys for the acceptance of systems by final users (professionals and patients) is using their specific needs as a basis and involving them in the whole design and development process. This methodological requirement has been put into practice in the e-Nefro project, whose objective is to establish architecture that is applicable and adaptable to telecare of pre-dialysis and peritoneal dialysis patients. For the study of needs, we conducted a set of interviews and questionnaires for professionals and patients, whose results have been presented in this study.

    We determined various requirements from the results. Patients wish to: automatically monitor and transfer their health conditions between consultations, but without having to participate actively or be in contact with their doctors and mainly in order to notify medical staff about emergency situations and receive information on the treatment of the illness in accordance with their preferences. Healthcare professionals identified the following needs: the ability to access complete and reliable patient user registries, as well as patient user data updated in real time at any time, receive critical events in real time and avoid being inundated with non-critical interventions/alarms and the possibility of accessing useful information (with a flexible visualisation of the latter in accordance with the needs and preferences of each professional user) in order to evaluate patient progression.

    These user needs, in combination with technological requirements identified by the developers, have led to the design of modular architecture adaptable to the different existing settings and to the preferences of patient and professional users. Specific telecare services will be developed for pre-dialysis and peritoneal dialysis users, although its flexibility will allow it to be re-used in any other specialty and clinical setting.


    Conflicts of interest


    The authors declare that they have no conflicts of interest related to the contents of this article.

    Figure 1. Methodology for applying the healthcare information and communications technologies is incremental and user-centred.

    Figure 2. Diagrams of the questionnaires used for healthcare professionals and patients.

    Figure 3. Modular architecture for the telecare of pre-dialysis and peritoneal dialysis patients.

    Kaldoudi E, Vargemezis V. Renal telemedicine and telehealth - Where do we stand? IFMBE Proc 2010;29:920-3.
    G??mez-Martino JR, Su??rez MA, Gallego SD, Gonz??lez PM, Covars?? AR, Castellano IC, et al. Telemedicina aplicada a la nefrolog??a: otra forma de consulta. Nefrologia 2008;4:407-12.
    Musso C, Aguilera J, Otero C, Vilas M, Luna D, de Quir??s FG. Informatic nephrology. Int Urol Nephrol 2013;45:1033-8. [Pubmed]
    Ronco C, Davenport A, Gura V. The future of the artificial kidney: moving towards wearable and miniaturized devices. Nefrologia 2011;31:9-16. [Pubmed]
    Mair FS, May C, O'Donnell C, Finch T, Sullivan F, Murray E. Factors that promote or inhibit the implementation of e-health systems: an explanatory systematic review. Bull World Health Organ 2012;90(5):357-64. [Pubmed]
    May CR, Finch TL, Cornford J, Exley C, Gately C, Kirk S, et al. Integrating telecare for chronic disease management in the community: what needs to be done? BMC Health Serv Res 2011;11:131. [Pubmed]
    Mark DA, Fitzmaurice GJ, Haughey KA, O'Donnell ME, Harty JC. Assessment of the quality of care and financial impact of a virtual renal clinic compared with the traditional outpatient service model. Int J Clin Pract 2011;65(10):1100-7. [Pubmed]
    Kumar G, Falk DM, Bonello RS, Kahn JM, Perencevich E, Cram P. The costs of critical care telemedicine programs: a systematic review and analysis. Chest 2013;143(1):19-29. [Pubmed]
    Gallar P, Guti??rrez M, Ortega O, Rodr??guez I, Oliet A, Herrero JC, et al. Utilidad de la Telemedicina en el seguimiento de los pacientes en di??lisis peritoneal. Nefrologia 2006;26(3):365-71. [Pubmed]
    Arrieta J. Evaluaci??n econ??mica del tratamiento sustitutivo renal (hemodi??lisis, di??lisis peritoneal y trasplante) en Espa??a. Nefrologia 2010;1(Supl Ext 1):37-47.
    Parra Moncasi E, Arenas Jim??nez MD, Alonso M, Mart??nez MF, G??men Pardo A, Rebollo P, et al. Estudio multic??ntrico de costes en hemodi??lisis. Nefrologia 2011;31(3):299-307. [Pubmed]
    Connor A, Mortimer F, Tomson C. Clinical transformation: the key to green nephrology. Nephron Clin Pract 2010;116(3):c200-5.
    Connor A, O'Donoghue D. Sustainability: the seventh dimension of quality in health care. Hemodial Int 2012;16(1):2-5. [Pubmed]
    de la Torre I, Gonz??lez S, L??pez-Coronado M. Analysis of the EHR systems in Spanish Primary Public Health System: the lack of interoperability. J Med Syst 2012;36(5):3273-81. [Pubmed]
    EN 13940 ?? Health informatics ?? System of concepts to support continuity of care, 2007.
    ISO 27799 - Health informatics - Information security management in health using ISO/IEC 27002, 2008.
    Blackburn SJ, Cudd PA. A discussion of systematic user requirements gathering from a population who require assistive technology. Technol Disabil 2012;24(3):193-204.
    PI11/00111 - Arquitectura modular adaptable para la teleasistencia integral de paciente renales (e-Nefro). FIS, Instituto de Salud Carlos II. 2012-2014.
    Wikipedia. Metodolog??as de desarrollo de software. Availabe at: (accessed 25 April 2013).
    Martin JL, Barnett J. Integrating the results of user research into medical device development: insights from a case study. BMC Med Inform Decis Mak 2012;12:74. [Pubmed]
    Usability Professionals?? Association. User-centered design. Available at: (accessed 25 April 2013).
    CPSR. Participatory Design. Available at: (accessed 25 April 2013).
    Emiliani PL, Stephanidis C. Universal access to ambient intelligence environments: opportunities and challenges for people with disabilities. IBM Syst J 2005;44(3):605-19.
    ISO 9241 - Ergonomics of human-system interaction -- Part 210: Human-centred design for interactive systems, 2010.
    Gosbee J. Human factors engineering and patient safety. Qual Saf Health Care 2002;11(4):352-4. [Pubmed]
    Martin JL, Clark DJ, Morgan SP, Crowe JA, Murphy E. A user-centred approach to requirements elicitation in medical device development: a case study from an industry perspective. Appl Ergon 2012;43(1):184-90. [Pubmed]
    Erl T. SOA: principles of service design. 5.?? ed. Upper Saddle River New Jersey: Prentice Hall; 2009.
    Booth D, Haas H, McCabe F, Newcomer E, Champion M, Ferris C, et al. Web Services Architecture. W3C recommendation. 2004.
    Nefrología (English Edition)

    Subscribe to our newsletter

    Article options
    es en

    ¿Es usted profesional sanitario apto para prescribir o dispensar medicamentos?

    Are you a health professional able to prescribe or dispense drugs?

    es en
    Política de cookies Cookies policy
    Utilizamos cookies propias y de terceros para mejorar nuestros servicios y mostrarle publicidad relacionada con sus preferencias mediante el análisis de sus hábitos de navegación. Si continua navegando, consideramos que acepta su uso. Puede cambiar la configuración u obtener más información aquí. To improve our services and products, we use "cookies" (own or third parties authorized) to show advertising related to client preferences through the analyses of navigation customer behavior. Continuing navigation will be considered as acceptance of this use. You can change the settings or obtain more information by clicking here.