Geneva, Switzerland, 26-27 April 2012

Introduction to session 7 - “Advancing e-health standards: Roles and responsibilities of stakeholders”

Marco Carugi ITU-T SG13 vice-Chair, Q3/13 Rapporteur and

FG M2M Service Layer vice-Chair ZTE Corporation

Marco.Carugi@zte.com.cn

Joint ITU-WHO Workshop on e-Health Standards and Interoperability

(Geneva, Switzerland, 26-27 April 2012)

Information update on ITU-T Focus Group on M2M Service Layer

Established in January 2012First meeting: 17-18 April 2012, ITU, GenevaNext meeting: 26-28 June 2012, Beijing, hosted by CCSA/CATR, teleconference facilities availableTo study requirements and specifications for a common Machine-to-Machine (M2M) Service Layer

Cost-efficient platformAcross vertical marketsMulti-vendor environment

Initial focus of the Focus Group: E-HealthWorking structure

WG1 Use cases and service modelsWG2 Requirements and architectural framework of the M2M Service LayerWG3 API and protocols (it will start later)

NOTE : Machine-to-Machine (M2M) communications are considered to be a key enabler of applications and services across a broad range of vertical domains (e.g., health-care, logistics, transport, utilities, smart home etc.)

Information update (continued): work programmes - 1

WG1 Use cases and service models (E-Health) definitions, terminology, taxonomies Use cases (templates ? which services (categories) ?)Ecosystem including business roles and key actors Service Models

WG2 Requirements and architectural framework of the M2M Service Layer

Common understanding on M2M reference model and M2M Service LayerRequirements of the M2M Service Layer

common to different application domainsspecific to E-Health

M2M Service Layer architectural framework: M2M Service Layer capabilities and functional components, reference points

Information update (continued): work programmes - 2

WG3 API and protocolsFramework of APIs and protocols for M2MAPIs and protocols for specific M2M interfaces

High reusability of existing specifications is assumedNeed to identify specific interfaces - E-Health focus

Other planned deliverablesCollection of E-Health relevant activities from SDOsGap analysis (which level of analysis)Action plan for future development of ITU-T standards

An usual recommendation from a closing FG [the produced deliverables, potential work items

recommended for future work]

FG M2M will coordinate with other standardization efforts within and outside ITU-T FG M2M aims at including vertical market stakeholders that are not part of traditional ITU-T membership and collaborating with M2M communities worldwide (incl. research, academia)

WHO and Continua Health Alliance present at 1st meeting, invitations planned to other SDOs

Input welcome: Focus Group is open to any individual from a country which is a member of ITU and willing to contribute

Please see the FG terms of Reference and additional information at

www.itu.int/en/ITU-T/focusgroups/m2m/

Information update (continued): coordination aspects

Some messages concerning E-Health technical standardization and interoperability I have

captured from workshop’s talks - 1Fragmentation of standards, pilots, (techno-based) systemsMultiple stakeholders, multiple/lack of policies, uncertain regulatory models, country and regional levels (but also market driven, borderless)Some existing standards could do much already but often not well known/known only to some (education, implementation practices) A number of non-technical barriers to standards adoption and complianceCoordination of information, Collaboration and harmonization among SDOs is neededShared vision: mission/expectations of E-Health in 5 yearsGlobal and collaborative standards roadmap based on common understanding of the work scope, priorities (services, technical areas, system interfaces), which standards already exist, which gaps and missing areasStandards should be accessible to all and free of charge

Some messages concerning E-Health technical standardization and interoperability I have

captured from workshop’s talks - 2

Interoperability, Compatibility, Scalability, PortabilityQoS, Security and Privacy, still allowing the required information exchangeImpact on standards of legal and regulatory frameworks (e.g. digital signage, authentication)Impact on standards of economic aspects (e.g. service models and stakeholders, new business models) Synergy between E-Health development and other ICT efforts: digital agenda; cloud, grid, M2M and social/Web 2.0 technology penetration in networks; smart mobile devices; global e-service frameworks - but also consider E-Health specifics (cloud quality label)Exploit commonalities across different vertical application domains operated on the same network infrastructure (e.g. E-Health, ITS, smart home etc.)

Some messages concerning E-Health technical standardization and interoperability I have

captured from workshop’s talks - 3

Flexible approaches in standards development (e.g. profiles, templates, incremental interoperability, cross-border targets)“Semantically annotated Web Services” as promising interim approach for interoperabilityApplication adaptation to environmental technical constraints (e.g. to mobile device capabilities) Technical platforms are a good supporting tool to show/validate usage of standards (implementation practices)Interoperability events are also very usefulGlobal dialogue towards E-Health standards and interoperability should continue under coordination of WHO and ITU involving all relevant stakeholders

Session 7 “Advancing e-health standards: Roles and responsibilities of stakeholders”

This session is to capture your inputs for development of the next steps of the expected collaborative effort

Which (categories of) stakeholders ?

Users (patients, communities, health institutions, governments etc.)Medical staff (doctors, experts, hospitals etc.)Partners (e.g. application developers)Vendors and operators of device, network and service infrastructureStandards Development Organizations

Policy makers, regulatorsDonors (and coordination among them)Others ?

Which Roles and Responsibilities ?Priorities, technical requirements, identified issues ?

Session 7 chair’s personal inputs on technical aspects

Identification of (categories of) stakeholdersTheir roles and responsibilities in E-Health value chainShared technical ground and work scope: which services and use cases, service models, environment assumptions, terminology and taxonomies, global architecture framework ?Priorities, technical requirements and identified issues from each stakeholder (category)SDOs’ landscape positioning, E-Health standards status Gap analysis of these (technical) standardsGlobal and shared E-Health standards roadmap (items and priorities, stakeholders’ roles and responsibilities)Collaboration in progressing the roadmapValidation of the progress (e.g. interoperability events etc.)