The TeleSCoPE Project Methodology and results

Size: px

Start display at page:

Download "The TeleSCoPE Project Methodology and results"

Rudolph Christopher Butler
8 years ago
Views:

1 The TeleSCoPE Project Methodology and results Paraciani N. et al.* La telemedicina: verso uno standard europeo 1

2 Project Overview TeleSCoPE: Telehealth Services Code of Practice for Europe Funded by EC, Health Programme Involved 13 partners in 7 member States Latest version of the Code published in September 2014 (available at Italian translation to be published in

States Latest version of the Code published in September 2014 (available at www.

3 Aims and Goals Development of a comprehensive European Code of Practice for telehealth services Providing a quality benchmark and a framework for service evaluation/certification, based on the Code Changing health management Building trust among European citizens to promote ehealth adoption 3

service evaluation/certification, based on the Code Changing health

4 Methodology TeleSCoPE definition of Telehealth Telehealth is the means by which technologies and related services that are concerned with health and wellbeing are accessed by people or provided for them at a distance User centred approach - Choice and control to patients/service users - Ensuring proper personal data management and user privacy - Stress on services configuration and use 4

for them at a distance User centred approach - Choice and control to patients/service users -

5 Methodology Telehealth Service Domains Health and motivational coaching Activity, behavioural and lifestyle monitoring Gait, seizure and falls monitoring Point of care testing, and support for diagnoses/decision making Vital signs monitoring mhealth Prompting for medication or therapy adherence Rehabilitation and (re)ablement Responding to events Tele-consultation 5

testing, and support for diagnoses/decision making Vital signs monitoring mhealth Prompting

6 Methodology Steps followed for Code development 1. Gathering of the evidence base 2. Development of Draft Code 3. Consultation on and validation of Draft Code 4. Updating/amending the Code based on 3 5. Final feedback gathering on updated version of the Code 6. Publishing the Code 6

Consultation on and validation of Draft Code 4.

7 Code Structure 54 clauses 7 appendices (including Glossary) 5 of which offer further guidance Accreditation requires conformity with all applicable clauses: minimum 46 (and 47 within 12 months of service commencement) 7

Accreditation requires conformity with all applicable

8 Code Structure 8

9 Code Contents Sections of the Code: A. General Considerations B. Ethical Principles C. Governance and Financial Issues D. Personal Information Management E. Staff and Staff Management F. Contact with Users and Carers G. Interpretation of and Responses to Information H. Communications Networks J. Hardware and Technological Considerations 9

Personal Information Management E. Staff and Staff Management F.

10 Code Consultation and Validation CONSULTATION: ACCEPTABILITY and SUITABILITY of the Draft Code s clauses evaluated by 42 stakeholders, including: Telehealth service providers (41%) User/Carers organizations (14%) Government/Regulatory bodies (14%) Others (Research, Academia) (31%) VALIDATION: Draft Code validated by 15 services in 4 EU countries: Belgium Hungary Italy United Kingdom (4 services) (4 services) (4 services) (3 services) 10

Government/Regulatory bodies (14%) Others (Research, Academia) (31%) VALIDATION: Draft Code validated by 15

11 Results of Consultation 11

12 Results of Consultation 12

13 Results of Validation Number of services by category Service category Number of services Telemonitoring and support / consultation 6 Monitoring for activity and wandering 3 Responding to events (incl. social alarms) 6 Telecare 1 13

support / consultation 6 Monitoring for activity and

14 Results of Validation Positive acceptance of the Draft Code overall. Weak points: 1) redundant requirements/wording 2) possibility of different interpretations depending on member state 3) further specifications needed for future development 14

15 Conclusions Current final version of the Code produced by taking into account: 1) External feedback from stakeholders (consultation) 2) Internal feedback from project partners 3) Validation process with telehealth services 4) Other suggestions/comments collected by other means (workshops, conferences, individual meetings etc.) 15

project partners 3) Validation process with telehealth services 4) Other

16 Thank you for your attention! Nicolò Paraciani CNR - Istituto per le Tecnologie della Costruzione paraciani@itc.cnr.it 16

17 * Maiuri F. 1, Di Pasquale D. 1, Biocca L. 1, Padula M. 1, Lapiello C. 1, Tabozzi S. A. 2 1 ITC-CNR, 2 IBFM-CNR 17

Telehealth Services Meeting changing needs? - Achievements and Challenges

Seminar 2016 University of East Anglia, Norwich Telehealth Services Meeting changing needs? - Achievements and Challenges Dr Malcolm J Fisk malcolm.fisk@dmu.ac.uk Telehealth What do we mean by telehealth?