вторник, 31 января 2017 г.
Ежедневная рассылка от 31 января
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Отказаться от получения данной рассылки: нажмите здесь или отправьте это письмо | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
понедельник, 30 января 2017 г.
Недоставленное сообщение
Return-Path: <ali.ali-an@yandex.by>
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward14o.cmail.yandex.net (Yandex) with ESMTP id 9921B21E32
for <bugmenot@asdasd.ru>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<bugmenot@asdasd.ru>: connect to mail.avias.ru[109.206.181.71]:25: Connection
refused
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward14o.cmail.yandex.net (Yandex) with ESMTP id 9921B21E32
for <bugmenot@asdasd.ru>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<bugmenot@asdasd.ru>: connect to mail.avias.ru[109.206.181.71]:25: Connection
refused
Ежедневная рассылка от 30 января
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Отказаться от получения данной рассылки: нажмите здесь или отправьте это письмо | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
воскресенье, 29 января 2017 г.
Ежедневная рассылка от 29 января
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Отказаться от получения данной рассылки: нажмите здесь или отправьте это письмо | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
суббота, 28 января 2017 г.
Ежедневная рассылка от 28 января
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Отказаться от получения данной рассылки: нажмите здесь или отправьте это письмо | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
пятница, 27 января 2017 г.
Недоставленное сообщение
Return-Path: <ali.ali-an@yandex.by>
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward10p.cmail.yandex.net (Yandex) with ESMTP id D08D921FED
for <raybpayne@gmail.com>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<raybpayne@gmail.com>: host gmail-smtp-in.l.google.com[64.233.162.27] said:
550-5.1.1 The email account that you tried to reach does not exist. Please
try 550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/?p=NoSuchUser v29si3403862ljd.8 - gsmtp (in
reply to RCPT TO command)
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward10p.cmail.yandex.net (Yandex) with ESMTP id D08D921FED
for <raybpayne@gmail.com>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<raybpayne@gmail.com>: host gmail-smtp-in.l.google.com[64.233.162.27] said:
550-5.1.1 The email account that you tried to reach does not exist. Please
try 550-5.1.1 double-checking the recipient's email address for typos or
550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/?p=NoSuchUser v29si3403862ljd.8 - gsmtp (in
reply to RCPT TO command)
Недоставленное сообщение
Return-Path: <ali.ali-an@yandex.by>
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward6p.cmail.yandex.net (Yandex) with ESMTP id DE2C3224E9
for <virginiahhart@gmail.com>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<virginiahhart@gmail.com>: host
gmail-smtp-in.l.google.com[2a00:1450:4010:c02::1b] said: 550-5.1.1 The
email account that you tried to reach does not exist. Please try 550-5.1.1
double-checking the recipient's email address for typos or 550-5.1.1
unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/?p=NoSuchUser c13si3380228lfk.381 - gsmtp
(in reply to RCPT TO command)
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward6p.cmail.yandex.net (Yandex) with ESMTP id DE2C3224E9
for <virginiahhart@gmail.com>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<virginiahhart@gmail.com>: host
gmail-smtp-in.l.google.com[2a00:1450:4010:c02::1b] said: 550-5.1.1 The
email account that you tried to reach does not exist. Please try 550-5.1.1
double-checking the recipient's email address for typos or 550-5.1.1
unnecessary spaces. Learn more at 550 5.1.1
https://support.google.com/mail/?p=NoSuchUser c13si3380228lfk.381 - gsmtp
(in reply to RCPT TO command)
Re: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
для подтверждения регистрации универсального аккаунта на новом ресурсе перейдите по ссылке http://interport2000.blogspot.ru/
Недоставленное сообщение
Return-Path: <ali.ali-an@yandex.by>
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward12j.cmail.yandex.net (Yandex) with ESMTP id 821C9212F6
for <zhorazhorashvili@mail.ru>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<zhorazhorashvili@mail.ru>: host mxs.mail.ru[94.100.180.150] said: 550 Message
was not accepted -- invalid mailbox. Local mailbox
zhorazhorashvili@mail.ru is unavailable: account is disabled (in reply to
end of DATA command)
Received: from mxfront8m.mail.yandex.net (mxfront8m.mail.yandex.net [IPv6:2a02:6b8:0:2519::107])
by forward12j.cmail.yandex.net (Yandex) with ESMTP id 821C9212F6
for <zhorazhorashvili@mail.ru>; Fri, 27 Jan 2017 22:09:20 +0300 (MSK)
Received: from mxfront8m.mail.yandex.net ([127.0.0.1])
by mxfront8m.mail.yandex.net with LMTP id MSxkcSHR
for <ali.ali-an@yandex.by>; Fri, 27 Jan 2017 22:09:19 +0300
Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238])
by mxfront8m.mail.yandex.net (nwsmtp/Yandex) with ESMTPS id uu7WboBf2X-9Hea9O8r;
Fri, 27 Jan 2017 22:09:17 +0300
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(Client certificate not present)
Authentication-Results: mxfront8m.mail.yandex.net; spf=softfail (mxfront8m.mail.yandex.net: transitioning domain of snscommunication.com does not designate 74.91.85.238 as permitted sender) smtp.mail=andy.silva@snscommunication.com; dkim=pass header.i=@smtp.com
X-MSFBL: 906w5JEHr+94DaoJSXyOwM1nr4koVpxd4T7hVYKf6lA=|eyJyIjoiYWxpLmFsaS1
hbkB5YW5kZXguYnkiLCJiIjoiNzRfOTFfODVfMjM4IiwiZyI6IlNuc3RlbGVjb21
fZGVkaWNhdGVkX3Bvb2wifQ==
Received: from [192.168.80.32] ([192.168.80.32:42856] helo=rs-ord-mta03-2.smtp.com)
by rs-ord-mta03-4.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP
id EF/7B-06020-CDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple;
q=dns/txt; i=@smtp.com; t=1485544156;
h=From:Subject:To:Date:MIME-Version:Content-Type;
bh=ykfX9RIF3y0Afabd5WLrzjmC83KsN1WBq2gXs1ed6WQ=;
b=hfx/PK27V1qNXY0pwjVzpDXOHlgo1T6IzLVDVTQslVJm5Cx93NNwpACv7us/pNZ0
CNJW1EQzuARJpm2nqmRIEZzlQ4zHmDROn5dRMKb2CPoJgkx5X9r5WlsLVTQ12KkS
ku7f1J2wUq+QgGF3dMXBKEp9uEqINyU2d/XH1DVXxRw=;
Received: from [70.79.69.78] ([70.79.69.78:41360] helo=S01061c1b689e28c7.vc.shawcable.net)
by rs-ord-mta03-2.smtp.com (envelope-from <andy.silva@snscommunication.com>)
(ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA
id 70/61-27267-BDA9B885; Fri, 27 Jan 2017 19:09:16 +0000
MIME-Version: 1.0
From: "Andy Silva" <andy.silva@snscommunication.com>
Reply-To: andy.silva@snscommunication.com
To: ali.ali-an@yandex.by
Subject: mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_6A5D_6A6E2C43.26982647"
X-Mailer: Smart_Send_2_0_138
Date: Fri, 27 Jan 2017 11:09:07 -0800
Message-ID: <1212410495072425513595@Ankur>
X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation.
X-SMTPCOM-Tracking-Number: 0ee4afc8-7063-4fb8-a773-ecceeadecea3
X-SMTPCOM-Sender-ID: 6008902
Feedback-ID: 6008902:SMTPCOM
X-Yandex-Forward: 4d5f734b4dc5e0eef1298172b29bef18
**********
Это письмо отправлено почтовым сервером yandex.ru.
К сожалению, мы вынуждены сообщить Вам о том, что Ваше письмо не может
быть отправлено одному или нескольким адресатам. Причины указаны ниже.
Пожалуйста, не отвечайте на это сообщение.
**********
This is the mail system at host yandex.ru.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
Please, do not reply to this message.
<zhorazhorashvili@mail.ru>: host mxs.mail.ru[94.100.180.150] said: 550 Message
was not accepted -- invalid mailbox. Local mailbox
zhorazhorashvili@mail.ru is unavailable: account is disabled (in reply to
end of DATA command)
mHealth (Mobile Healthcare) Ecosystem: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report)
| mHealth (Mobile Healthcare) Ecosystem: 2017 – 2030 – Opportunities, Challenges, Strategies & Forecasts (Report) |
Hello
Let me offer you the latest SNS Research report to you and your team, "mHealth (Mobile Healthcare) Ecosystem: 2017 – 2030 – Opportunities, Challenges, Strategies & Forecasts" Below is the report highlight and if you like I can send you sample pages for your details inside.
Driven by the thriving ecosystem, SNS Research estimates that the mHealth market will account for over $23 Billion in 2017 alone. Despite barriers relating to regulation, patient acceptance and privacy concerns, SNS Research estimates further growth at a CAGR of more than 35% over the next three years.
Report Information:
Release Date: Nov 2016
Number of Pages: 424
Number of Tables and Figures: 106
Key Questions Answered:
- What are the key market drivers and challenges for mHealth?
- What are the key applications of mHealth?
- How is the mHealth value chain structured and how will it evolve overtime?
- How big is the mHealth opportunity, and how much revenue will it generate in 2020?
- What will be the installed base of IoT connections for mHealth applications in 2020?
- How many mHealth centric wearable devices will be shipped in 2020?
- Which regions, countries and submarkets will see the highest percentage of growth?
- Who are the key market players and what are their strategies?
- What level of cost savings can mHealth facilitate for healthcare service providers in each region?
- What are the key applications of LTE and 5G networks in the mHealth market?
- What considerations should be taken into account to devise a successful mHealth strategy for a hospital?
- What strategies should mobile operators, enabling technology providers, mHealth device OEMs, healthcare service providers, pharmaceutical companies and application developers adopt to capitalize on the mHealth opportunity?
Key Findings:
The report has the following key findings:
- Driven by the thriving ecosystem, SNS Research estimates that the mHealth market will account for over $23 Billion in 2017 alone. Despite barriers relating to regulation, patient acceptance and privacy concerns, SNS Research estimates further growth at a CAGR of more than 35% over the next three years.
- While the use of mHealth devices and apps is already widespread in clinical trials, pharmaceutical giants are now setting their sights on connected drug delivery platforms that will automatically detect and log patients' medication use to improve adherence.
- SNS Research estimates that mHealth centric wearable devices will account for over 60 Million unit shipments by the end of 2017. In order to gain valuable insights from the data generated by these devices, healthcare service providers and other stakeholders are increasingly investing in Big Data and analytics technology.
- mHealth has the potential to dramatically reduce the costs of healthcare operations, while improving the quality of healthcare. SNS Research estimates that by the end of 2017, mHealth could represent up to $370 Billion in annual healthcare cost savings worldwide.
The report covers the following topics:
- The scope and implementation of mHealth across the globe
- mHealth technology
- Market drivers and key benefits of mHealth
- Challenges and inhibitors to the mHealth ecosystem
- mHealth standardization and regulatory initiatives
- mHealth opportunities, use cases and applications
- mHealth deployment case studies
- Value chain analysis of the mHealth ecosystem and the recognition of key players in each segment of the value chain
mHealth industry roadmap: 2017 – 2030 - Key trends in the mHealth ecosystem; mHealth regulation, security, adoption of cloud based mHealth services, alliances for ecosystem fortification, and the impact of LTE/5G deployments
- The role of IoT and wearable technology in the mHealth ecosystem
- Profiles and strategies of over 230 leading ecosystem players
- Strategic recommendations for mobile operators, enabling technology providers, mHealth device OEMs, application developers, healthcare service providers and pharmaceutical companies
- In-depth analysis for 5 individual submarkets and their associated mHealth application use cases:
- Pharmaceutical Applications
- Medical Information & Healthcare Management
- Healthcare & Fitness
- Remote Consultation/Diagnostic Services
- IoT, Wearable Technology, Sensor & Monitoring Applications
-
- Historical revenue figures and forecasts till 2030
Forecast Segmentation:
Market forecasts and historical revenue figures are provided for each of the following 5 submarkets and their 23 use case categories:
- Pharmaceutical Applications
- Safety Data Collection
- Consumer Education
- Medical Education
- Post–Market Monitoring
- Drug Authentication
- Social Media
- Patient Compliance & Retention: Clinical Trials
-
- Information & Healthcare Management
- Electronic Health/Medical Records & Tracking Tools
- Diagnostic Tools & Medical Reference
- Continuing Medical Education
- Awareness Through Alerts
- Logistical & Payment Support
-
- Healthcare & Fitness
- Medical Compliance
- Fitness & Nutrition Apps
- Clinical Decision Support Systems
- Prescribable Mobile Apps
-
- Remote Consultation/Diagnostic Services
- Mobile Video Consultations, Collaboration & Surgery
- Non-Video Consultations & Collaboration
- Remote Collaboration in Emergency Situations
-
- IoT, Wearable Technology, Sensor & Monitoring Applications
- Health and Wellness Monitoring
- Disease Surveillance/Remote Monitoring
- Diagnostic Tools
- Technical Logistics
-
- Revenue is also split by ecosystem player:
- Ecosystem Player Segmentation
- Mobile Operators & Connectivity Providers
- Mobile & mHealth Device OEMs
- Content & Application Providers
- Healthcare Service Providers
- Pharmaceutical Industry
-
-
The following regional and country markets are also covered:
- Regional Markets
- Asia Pacific
- Eastern Europe
- Latin & Central America
- Middle East & Africa
- North America
- Western Europe
-
- Country Markets
Argentina, Australia, Brazil, Canada, China, Czech Republic, Denmark, Finland, France, Germany, India, Indonesia, Israel, Italy, Japan, Malaysia, Mexico, Norway, Pakistan, Philippines, Poland, Qatar, Russia, Saudi Arabia, Singapore, South Africa, South Korea, Spain, Sweden, Taiwan, Thailand, UAE, UK, USA
Additional forecasts are provided for the following:
- IoT connections for mHealth applications
- mHealth centric wearable device shipments
- Mobile video calling users
- Annual throughput of mobile network data traffic
- Smartphone, feature phone, tablet, desktop PC and notebook shipments
- Mobile network subscriptions by region
- Cost saving potential of mHealth by region
- Big Data & analytics technology investments in the healthcare sector
Report Pricing:
Single User License: USD 2,500
Company Wide License: USD 3,500
Ordering Process:
Please provide the following information:
- Report Title -
- Report License - (Single User/Company Wide)
- Name -
- Email -
- Job Title -
- Company -
- Invoice Address -
Please contact me if you have any questions, or wish to purchase a copy. Table of contents and List of figures mentioned in report are given below for more inside.
I look forward to hearing from you.
Kind Regards
Andy Silva
Marketing Executive
_________________________________________________________________________
Table of Contents (page number):
1 Chapter 1: Introduction 21
1.1 Executive Summary 21
1.2 Topics Covered 23
1.3 Forecast Segmentation 25
1.4 Key Questions Answered 28
1.5 Key Findings 30
1.6 Methodology 31
1.7 Target Audience 32
1.8 Companies & Organizations Mentioned 33
1.1 Executive Summary 21
1.2 Topics Covered 23
1.3 Forecast Segmentation 25
1.4 Key Questions Answered 28
1.5 Key Findings 30
1.6 Methodology 31
1.7 Target Audience 32
1.8 Companies & Organizations Mentioned 33
2 Chapter 2: An Overview of mHealth 35
2.1 What is mHealth? 35
2.2 The Evolution from eHealth to mHealth 35
2.3 Telemedicine 36
2.4 Health Informatics 36
2.5 The mHealth Business Case 37
2.6 Key Market Drivers 37
2.6.1 Increasing Penetration of Smartphones, Tablets & Wearables 37
2.6.2 Proliferation of Mobile Broadband Networks 40
2.6.3 The Rise of Chronic Diseases 41
2.6.4 Growing Adoption of mHealth Apps: Reduction in Lead Time 41
2.6.5 Government & Regulatory Initiatives 41
2.6.6 Physicians at Forefront of Mobility Adoption 42
2.6.7 The Cost Saving Potential of mHealth 42
2.6.8 Increasing Adoption of Open Source Software 43
2.6.9 The Role of Developed Economies 44
2.6.10 The Role of Emerging Economies 44
2.7 Barriers to Growth 45
2.7.1 Security/Privacy Concerns & Absence of Legal Guidelines 45
2.7.2 Regulation & Efficacy of Applications 45
2.7.3 Operational Maintenance & Control 45
2.7.4 Human Behavior: Disbelief Among Patients 46
2.7.5 Lack of Clear mHealth Strategies 46
2.7.6 Funding Challenges 46
2.8 Key Enabling Technologies for mHealth 47
2.8.1 Smartphones & Tablets 47
2.8.2 Mobile Apps 47
2.8.3 Mobile Broadband: The LTE & 5G Era 47
2.8.4 Wearable Devices & Sensor Technologies 48
2.8.5 IoT & M2M Connectivity 49
2.8.6 Mobile Video Calling & Multimedia Capabilities 53
2.9 mHealth Use Case Categories 54
2.9.1 Pharmaceutical Applications 55
2.9.2 Medical Information & Healthcare Management 55
2.9.3 Healthcare & Fitness 56
2.9.4 Remote Consultation/Diagnostic Services 56
2.9.5 IoT, Wearable Technology, Sensor & Monitoring Applications 57
2.1 What is mHealth? 35
2.2 The Evolution from eHealth to mHealth 35
2.3 Telemedicine 36
2.4 Health Informatics 36
2.5 The mHealth Business Case 37
2.6 Key Market Drivers 37
2.6.1 Increasing Penetration of Smartphones, Tablets & Wearables 37
2.6.2 Proliferation of Mobile Broadband Networks 40
2.6.3 The Rise of Chronic Diseases 41
2.6.4 Growing Adoption of mHealth Apps: Reduction in Lead Time 41
2.6.5 Government & Regulatory Initiatives 41
2.6.6 Physicians at Forefront of Mobility Adoption 42
2.6.7 The Cost Saving Potential of mHealth 42
2.6.8 Increasing Adoption of Open Source Software 43
2.6.9 The Role of Developed Economies 44
2.6.10 The Role of Emerging Economies 44
2.7 Barriers to Growth 45
2.7.1 Security/Privacy Concerns & Absence of Legal Guidelines 45
2.7.2 Regulation & Efficacy of Applications 45
2.7.3 Operational Maintenance & Control 45
2.7.4 Human Behavior: Disbelief Among Patients 46
2.7.5 Lack of Clear mHealth Strategies 46
2.7.6 Funding Challenges 46
2.8 Key Enabling Technologies for mHealth 47
2.8.1 Smartphones & Tablets 47
2.8.2 Mobile Apps 47
2.8.3 Mobile Broadband: The LTE & 5G Era 47
2.8.4 Wearable Devices & Sensor Technologies 48
2.8.5 IoT & M2M Connectivity 49
2.8.6 Mobile Video Calling & Multimedia Capabilities 53
2.9 mHealth Use Case Categories 54
2.9.1 Pharmaceutical Applications 55
2.9.2 Medical Information & Healthcare Management 55
2.9.3 Healthcare & Fitness 56
2.9.4 Remote Consultation/Diagnostic Services 56
2.9.5 IoT, Wearable Technology, Sensor & Monitoring Applications 57
3 Chapter 3: mHealth Value Chain and Industry Roadmap 58
3.1 The mHealth Value Chain 58
3.1.1 Enabling Technology Providers and mHealth Device OEMs 59
3.1.2 Mobile Operators 59
3.1.3 Healthcare Professionals & Providers 60
3.1.4 Insurers and Government Health Systems 60
3.1.5 The Pharmaceutical Industry 60
3.1.6 Application Developers & Integrators 61
3.1.7 Patients 61
3.2 The mHealth Industry Roadmap: 2017 – 2030 62
3.2.1 2017 – 2020: Commercialization of Consumer Centric mHealth Apps & Devices 62
3.2.2 2020 – 2025: Growing Adoption of Connected Drug Delivery & Prescribable Medical Apps 63
3.2.3 2025 – 2030: The Era of mHealth Analytics 63
3.1 The mHealth Value Chain 58
3.1.1 Enabling Technology Providers and mHealth Device OEMs 59
3.1.2 Mobile Operators 59
3.1.3 Healthcare Professionals & Providers 60
3.1.4 Insurers and Government Health Systems 60
3.1.5 The Pharmaceutical Industry 60
3.1.6 Application Developers & Integrators 61
3.1.7 Patients 61
3.2 The mHealth Industry Roadmap: 2017 – 2030 62
3.2.1 2017 – 2020: Commercialization of Consumer Centric mHealth Apps & Devices 62
3.2.2 2020 – 2025: Growing Adoption of Connected Drug Delivery & Prescribable Medical Apps 63
3.2.3 2025 – 2030: The Era of mHealth Analytics 63
4 Chapter 4: mHealth Use Cases 64
4.1 Pharmaceutical Applications 64
4.1.1 Safety Data Collection 64
4.1.2 Consumer Education 64
4.1.3 Medical Education 64
4.1.4 Post-Market Monitoring 65
4.1.5 Drug Authentication 65
4.1.6 Social Media 65
4.1.7 Patient Compliance & Retention: Clinical Trials 66
4.2 Medical Information & Healthcare Management 66
4.2.1 EHRs (Electronic Health Records) & Tracking Tools 66
4.2.2 Diagnostic Tools & Medical Reference 66
4.2.3 Continuing Medical Education 67
4.2.4 Awareness through Alerts 67
4.2.5 Logistical & Payment Support 67
4.3 Healthcare & Fitness 68
4.3.1 Medical Compliance 68
4.3.2 Fitness & Nutrition Apps 68
4.3.3 Clinical Decision Support Systems 69
4.3.4 Prescribable Mobile Apps 69
4.4 Remote Consultation & Diagnostics Services 69
4.4.1 Mobile Video Consultations, Collaboration & Surgery 69
4.4.2 Non-Video Consultations & Collaboration 70
4.4.3 Remote Collaboration in Emergency Situations 70
4.5 IoT, Wearable Technology, Sensor & Monitoring Applications 70
4.5.1 Health & Wellness Monitoring 70
4.5.2 Disease Surveillance/Remote Monitoring 71
4.5.3 Diagnostic Tools 71
4.5.4 Technical Logistics 71
4.1 Pharmaceutical Applications 64
4.1.1 Safety Data Collection 64
4.1.2 Consumer Education 64
4.1.3 Medical Education 64
4.1.4 Post-Market Monitoring 65
4.1.5 Drug Authentication 65
4.1.6 Social Media 65
4.1.7 Patient Compliance & Retention: Clinical Trials 66
4.2 Medical Information & Healthcare Management 66
4.2.1 EHRs (Electronic Health Records) & Tracking Tools 66
4.2.2 Diagnostic Tools & Medical Reference 66
4.2.3 Continuing Medical Education 67
4.2.4 Awareness through Alerts 67
4.2.5 Logistical & Payment Support 67
4.3 Healthcare & Fitness 68
4.3.1 Medical Compliance 68
4.3.2 Fitness & Nutrition Apps 68
4.3.3 Clinical Decision Support Systems 69
4.3.4 Prescribable Mobile Apps 69
4.4 Remote Consultation & Diagnostics Services 69
4.4.1 Mobile Video Consultations, Collaboration & Surgery 69
4.4.2 Non-Video Consultations & Collaboration 70
4.4.3 Remote Collaboration in Emergency Situations 70
4.5 IoT, Wearable Technology, Sensor & Monitoring Applications 70
4.5.1 Health & Wellness Monitoring 70
4.5.2 Disease Surveillance/Remote Monitoring 71
4.5.3 Diagnostic Tools 71
4.5.4 Technical Logistics 71
5 Chapter 5: mHealth Case Studies 72
5.1 Apollo Hospitals Group: Enabling mHealth for the Masses 72
5.2 Appirio: Cutting Health Insurance Costs with Wearable Activity Trackers 73
5.3 AT&T: Connected Healthcare Monitoring for the Elderly 74
5.4 London Air Ambulance: Saving Lives with mHealth Apps and 4G Connectivity 75
5.5 Novartis: Connected Drug Delivery for COPD (Chronic Obstructive Pulmonary Disease) 76
5.6 Orange Healthcare: Fighting Counterfeit Drugs with Text Messaging 77
5.7 Praekelt Foundation: Raising HIV/AIDS Awareness with mHealth 78
5.8 Qualcomm Life: Extending Healthcare Beyond Hospital Walls 79
5.9 Roche: Enhancing Clinical Trials with mHealth Apps 80
5.10 WellDoc: Managing Chronic Diseases with mHealth Apps 81
5.1 Apollo Hospitals Group: Enabling mHealth for the Masses 72
5.2 Appirio: Cutting Health Insurance Costs with Wearable Activity Trackers 73
5.3 AT&T: Connected Healthcare Monitoring for the Elderly 74
5.4 London Air Ambulance: Saving Lives with mHealth Apps and 4G Connectivity 75
5.5 Novartis: Connected Drug Delivery for COPD (Chronic Obstructive Pulmonary Disease) 76
5.6 Orange Healthcare: Fighting Counterfeit Drugs with Text Messaging 77
5.7 Praekelt Foundation: Raising HIV/AIDS Awareness with mHealth 78
5.8 Qualcomm Life: Extending Healthcare Beyond Hospital Walls 79
5.9 Roche: Enhancing Clinical Trials with mHealth Apps 80
5.10 WellDoc: Managing Chronic Diseases with mHealth Apps 81
6 Chapter 6: mHealth Solution Provider Profiles 83
6.1 270 Vision 83
6.2 3L Labs 85
6.3 3M 86
6.4 4DForce 88
6.5 4iii Innovations 89
6.6 Abbott Laboratories 90
6.7 Accenture 91
6.8 AdhereTech 92
6.9 Adherium 93
6.10 Adidas 94
6.11 Aerotel Medical Systems 96
6.12 Aetna 97
6.13 Agfa Healthcare 98
6.14 AiRISTA 99
6.15 AirStrip Technologies 100
6.16 Alego Health 102
6.17 AliveCor 103
6.18 AllScripts Healthcare 104
6.19 AMD Global Telemedicine 105
6.20 Amiigo 106
6.21 Apple 107
6.22 ASICS Corporation 109
6.23 AstraZeneca 110
6.24 AT&T 112
6.25 Athenahealth 114
6.26 Atlas Wearables 115
6.27 Augmendix 116
6.28 BettrLife 117
6.29 Big Cloud Analytics 118
6.30 Biosensics 119
6.31 BioTelemetry Technology 121
6.32 Biotricity 122
6.33 BlackBerry 123
6.34 Boehringer Ingelheim 124
6.35 Boston Scientific Corporation 125
6.36 Breakthrough Technologies 126
6.37 BSX Athletics 127
6.38 BTS Bioengineering 128
6.39 Cambridge Consultants 129
6.40 CardioComm Solutions 130
6.41 CardioNet 131
6.42 Carre Technologies 132
6.43 Catapult Sports 134
6.44 CEEK VR 136
6.45 CellTrust Corporation 137
6.46 CenTrak 138
6.47 Cerner Corporation 139
6.48 Chetu 140
6.49 CirrusMD 141
6.50 Cisco Systems 142
6.51 Cityzen Sciences 143
6.52 Codoon 144
6.53 Cohero Health 145
6.54 Companion Medical 146
6.55 Comtech Telecommunications Corporation 147
6.56 Conversa Health 148
6.57 CRF Health 149
6.58 CTC (Cambridge Temperature Concepts) 150
6.59 Cupris Health 151
6.60 Cyberdyne 152
6.61 Cypress Semiconductor Corporation 153
6.62 Diversinet 154
6.63 DocbookMD 156
6.64 dorsaVi 157
6.65 Dreamtrap Commercials 158
6.66 DT (Deutsche Telekom) 159
6.67 Ducere Technologies 160
6.68 EB Sport Group 161
6.69 eClinicalWorks 162
6.70 EE 163
6.71 Ekso Bionics 164
6.72 EMN (European Medical Network) 165
6.73 Emotiv Systems 166
6.74 Epic Systems Corporation 167
6.75 Epion Health 168
6.76 Ericsson 169
6.77 Evena Medical 170
6.78 Extension Healthcare 171
6.79 Fatigue Science 172
6.80 Finis 173
6.81 Fitbit 174
6.82 Flyfit 176
6.83 FRUCT MD 177
6.84 Fujitsu 178
6.85 Gait Up 179
6.86 Garmin 180
6.87 GE Healthcare 181
6.88 Gemalto 182
6.89 Genesis Health Technologies 183
6.90 Ginger.io 184
6.91 Google 185
6.92 GOQii 187
6.93 Grameen Foundation 188
6.94 GSK (GlaxoSmithKline) 189
6.95 Guandong Biolight Meditech 191
6.96 HealBe 192
6.97 Honeywell Life Care Solutions 193
6.98 Hövding 194
6.99 HPE (Hewlett Packard Enterprise) 195
6.100 Huawei 196
6.101 Human API 197
6.102 i4C Innovations 198
6.103 IBM Corporation 199
6.104 ICEdot 200
6.105 Ideal Life 201
6.106 iHealth Labs 202
6.107 Imec 203
6.108 ImPACT Applications 204
6.109 Imprivata 205
6.110 Instabeat 207
6.111 Integron Corporation 208
6.112 Intel Corporation 209
6.113 InteraXon 210
6.114 Intermountain Healthcare 211
6.115 InTouch Health 212
6.116 InvenSense 213
6.117 Invision Heart 214
6.118 IQMax 215
6.119 iRhythm Technologies 217
6.120 Jawbone 218
6.121 Jaybird 220
6.122 Johnson & Johnson 221
6.123 KDDI Corporation 222
6.124 Ki Performance 223
6.125 KORE Wireless Group 224
6.126 Kreyos 225
6.127 Lark Technologies 226
6.128 Lenovo 227
6.129 LG Electronics 228
6.130 LMD (Leman Micro Devices) 229
6.131 Lumo BodyTech 230
6.132 Magellan (MiTAC Digital Corporation) 231
6.133 McKinsey & Company 232
6.134 MDLIVE 233
6.135 Medecin Direct 234
6.136 Medella Health 235
6.137 Medisafe 236
6.138 MedM 237
6.139 MedSignals/VitalSignals 238
6.140 Medtronic 239
6.141 MedWeb 241
6.142 Melon 242
6.143 mHealthAlert 243
6.144 Microsoft 244
6.145 Mio Global 246
6.146 Misfit 247
6.147 Moov 249
6.148 Moticon 250
6.149 Motion Fitness 251
6.150 mQure 252
6.151 Myontec 253
6.152 Neurometrix 254
6.153 NeuroPro 255
6.154 Nike 256
6.155 No Isolation 258
6.156 Nokia 259
6.157 Nonin Medical 260
6.158 Notch Interfaces 261
6.159 Novartis 262
6.160 Novo Nordisk 264
6.161 NTT DoCoMo 265
6.162 Nuubo 267
6.163 NXP Semiconductors 268
6.164 NZN Labs 269
6.165 Omron Corporation 270
6.166 OMsignal 271
6.167 OPKO Health 272
6.168 Optalert 273
6.169 Orange 274
6.170 Orpyx Medical Technologies 275
6.171 O–Synce 276
6.172 Owlet Baby Care 277
6.173 Panasonic Corporation 278
6.174 Pharmica Consulting 279
6.175 Phyode 280
6.176 Polar Electro 281
6.177 Pragmasystems 282
6.178 Preventice 283
6.179 Propeller Health 284
6.180 Proteus Digital Health 285
6.181 PUSH 286
6.182 Qardio 287
6.183 Qloudlab 288
6.184 Qualcomm Life 289
6.185 Reflexion Health 291
6.186 Rest Devices 292
6.187 Roche Holding (F. Hoffmann-La Roche) 293
6.188 Royal Philips 295
6.189 RSL Steeper Group 296
6.190 S3 Group 297
6.191 Samsung Group 298
6.192 Sanofi 300
6.193 Santech 301
6.194 SAP 302
6.195 SCOTTY Group 303
6.196 Sensible Baby 304
6.197 Senso Solutions 305
6.198 Sentimoto 306
6.199 Seraphim Sense 307
6.200 Siemens Healthcare 308
6.201 SK Telecom 309
6.202 SmartCap Technologies 310
6.203 Snaptracs 311
6.204 SoftBank Corporation 312
6.205 SoftServe 314
6.206 Somaxis 315
6.207 Sonitus Medical 316
6.208 Sony Corporation 317
6.209 Sotera Wireless 318
6.210 Stanley Healthcare 319
6.211 STMicroelectronics 320
6.212 Swisscom 321
6.213 Tactio Health Group 322
6.214 Telcare 323
6.215 Tele2 324
6.216 Telecom Italia 325
6.217 Telenor 326
6.218 Teva Pharmaceutical Industries 327
6.219 TI (Texas Instruments) 328
6.220 Toshiba Corporation 329
6.221 Tricella 330
6.222 Tunstall Group 331
6.223 U-blox 332
6.224 Valencell 333
6.225 Validic (Motivation Science) 334
6.226 Vancive Medical Technologies 335
6.227 Verizon Communications 336
6.228 Vitaphone 337
6.229 Vodafone Group 338
6.230 Voxiva 339
6.231 Wearable Intelligence 340
6.232 WellDoc 341
6.233 Wellograph 342
6.234 Xiaomi 343
6.235 Xplore Technologies 344
6.236 Xsensio 345
6.237 Zinc Software 346
6.238 Zoll Medical Corporation 347
6.1 270 Vision 83
6.2 3L Labs 85
6.3 3M 86
6.4 4DForce 88
6.5 4iii Innovations 89
6.6 Abbott Laboratories 90
6.7 Accenture 91
6.8 AdhereTech 92
6.9 Adherium 93
6.10 Adidas 94
6.11 Aerotel Medical Systems 96
6.12 Aetna 97
6.13 Agfa Healthcare 98
6.14 AiRISTA 99
6.15 AirStrip Technologies 100
6.16 Alego Health 102
6.17 AliveCor 103
6.18 AllScripts Healthcare 104
6.19 AMD Global Telemedicine 105
6.20 Amiigo 106
6.21 Apple 107
6.22 ASICS Corporation 109
6.23 AstraZeneca 110
6.24 AT&T 112
6.25 Athenahealth 114
6.26 Atlas Wearables 115
6.27 Augmendix 116
6.28 BettrLife 117
6.29 Big Cloud Analytics 118
6.30 Biosensics 119
6.31 BioTelemetry Technology 121
6.32 Biotricity 122
6.33 BlackBerry 123
6.34 Boehringer Ingelheim 124
6.35 Boston Scientific Corporation 125
6.36 Breakthrough Technologies 126
6.37 BSX Athletics 127
6.38 BTS Bioengineering 128
6.39 Cambridge Consultants 129
6.40 CardioComm Solutions 130
6.41 CardioNet 131
6.42 Carre Technologies 132
6.43 Catapult Sports 134
6.44 CEEK VR 136
6.45 CellTrust Corporation 137
6.46 CenTrak 138
6.47 Cerner Corporation 139
6.48 Chetu 140
6.49 CirrusMD 141
6.50 Cisco Systems 142
6.51 Cityzen Sciences 143
6.52 Codoon 144
6.53 Cohero Health 145
6.54 Companion Medical 146
6.55 Comtech Telecommunications Corporation 147
6.56 Conversa Health 148
6.57 CRF Health 149
6.58 CTC (Cambridge Temperature Concepts) 150
6.59 Cupris Health 151
6.60 Cyberdyne 152
6.61 Cypress Semiconductor Corporation 153
6.62 Diversinet 154
6.63 DocbookMD 156
6.64 dorsaVi 157
6.65 Dreamtrap Commercials 158
6.66 DT (Deutsche Telekom) 159
6.67 Ducere Technologies 160
6.68 EB Sport Group 161
6.69 eClinicalWorks 162
6.70 EE 163
6.71 Ekso Bionics 164
6.72 EMN (European Medical Network) 165
6.73 Emotiv Systems 166
6.74 Epic Systems Corporation 167
6.75 Epion Health 168
6.76 Ericsson 169
6.77 Evena Medical 170
6.78 Extension Healthcare 171
6.79 Fatigue Science 172
6.80 Finis 173
6.81 Fitbit 174
6.82 Flyfit 176
6.83 FRUCT MD 177
6.84 Fujitsu 178
6.85 Gait Up 179
6.86 Garmin 180
6.87 GE Healthcare 181
6.88 Gemalto 182
6.89 Genesis Health Technologies 183
6.90 Ginger.io 184
6.91 Google 185
6.92 GOQii 187
6.93 Grameen Foundation 188
6.94 GSK (GlaxoSmithKline) 189
6.95 Guandong Biolight Meditech 191
6.96 HealBe 192
6.97 Honeywell Life Care Solutions 193
6.98 Hövding 194
6.99 HPE (Hewlett Packard Enterprise) 195
6.100 Huawei 196
6.101 Human API 197
6.102 i4C Innovations 198
6.103 IBM Corporation 199
6.104 ICEdot 200
6.105 Ideal Life 201
6.106 iHealth Labs 202
6.107 Imec 203
6.108 ImPACT Applications 204
6.109 Imprivata 205
6.110 Instabeat 207
6.111 Integron Corporation 208
6.112 Intel Corporation 209
6.113 InteraXon 210
6.114 Intermountain Healthcare 211
6.115 InTouch Health 212
6.116 InvenSense 213
6.117 Invision Heart 214
6.118 IQMax 215
6.119 iRhythm Technologies 217
6.120 Jawbone 218
6.121 Jaybird 220
6.122 Johnson & Johnson 221
6.123 KDDI Corporation 222
6.124 Ki Performance 223
6.125 KORE Wireless Group 224
6.126 Kreyos 225
6.127 Lark Technologies 226
6.128 Lenovo 227
6.129 LG Electronics 228
6.130 LMD (Leman Micro Devices) 229
6.131 Lumo BodyTech 230
6.132 Magellan (MiTAC Digital Corporation) 231
6.133 McKinsey & Company 232
6.134 MDLIVE 233
6.135 Medecin Direct 234
6.136 Medella Health 235
6.137 Medisafe 236
6.138 MedM 237
6.139 MedSignals/VitalSignals 238
6.140 Medtronic 239
6.141 MedWeb 241
6.142 Melon 242
6.143 mHealthAlert 243
6.144 Microsoft 244
6.145 Mio Global 246
6.146 Misfit 247
6.147 Moov 249
6.148 Moticon 250
6.149 Motion Fitness 251
6.150 mQure 252
6.151 Myontec 253
6.152 Neurometrix 254
6.153 NeuroPro 255
6.154 Nike 256
6.155 No Isolation 258
6.156 Nokia 259
6.157 Nonin Medical 260
6.158 Notch Interfaces 261
6.159 Novartis 262
6.160 Novo Nordisk 264
6.161 NTT DoCoMo 265
6.162 Nuubo 267
6.163 NXP Semiconductors 268
6.164 NZN Labs 269
6.165 Omron Corporation 270
6.166 OMsignal 271
6.167 OPKO Health 272
6.168 Optalert 273
6.169 Orange 274
6.170 Orpyx Medical Technologies 275
6.171 O–Synce 276
6.172 Owlet Baby Care 277
6.173 Panasonic Corporation 278
6.174 Pharmica Consulting 279
6.175 Phyode 280
6.176 Polar Electro 281
6.177 Pragmasystems 282
6.178 Preventice 283
6.179 Propeller Health 284
6.180 Proteus Digital Health 285
6.181 PUSH 286
6.182 Qardio 287
6.183 Qloudlab 288
6.184 Qualcomm Life 289
6.185 Reflexion Health 291
6.186 Rest Devices 292
6.187 Roche Holding (F. Hoffmann-La Roche) 293
6.188 Royal Philips 295
6.189 RSL Steeper Group 296
6.190 S3 Group 297
6.191 Samsung Group 298
6.192 Sanofi 300
6.193 Santech 301
6.194 SAP 302
6.195 SCOTTY Group 303
6.196 Sensible Baby 304
6.197 Senso Solutions 305
6.198 Sentimoto 306
6.199 Seraphim Sense 307
6.200 Siemens Healthcare 308
6.201 SK Telecom 309
6.202 SmartCap Technologies 310
6.203 Snaptracs 311
6.204 SoftBank Corporation 312
6.205 SoftServe 314
6.206 Somaxis 315
6.207 Sonitus Medical 316
6.208 Sony Corporation 317
6.209 Sotera Wireless 318
6.210 Stanley Healthcare 319
6.211 STMicroelectronics 320
6.212 Swisscom 321
6.213 Tactio Health Group 322
6.214 Telcare 323
6.215 Tele2 324
6.216 Telecom Italia 325
6.217 Telenor 326
6.218 Teva Pharmaceutical Industries 327
6.219 TI (Texas Instruments) 328
6.220 Toshiba Corporation 329
6.221 Tricella 330
6.222 Tunstall Group 331
6.223 U-blox 332
6.224 Valencell 333
6.225 Validic (Motivation Science) 334
6.226 Vancive Medical Technologies 335
6.227 Verizon Communications 336
6.228 Vitaphone 337
6.229 Vodafone Group 338
6.230 Voxiva 339
6.231 Wearable Intelligence 340
6.232 WellDoc 341
6.233 Wellograph 342
6.234 Xiaomi 343
6.235 Xplore Technologies 344
6.236 Xsensio 345
6.237 Zinc Software 346
6.238 Zoll Medical Corporation 347
7 Chapter 7: Standardization, Regulation & Development Initiatives 348
7.1 Standardization Bodies & Alliances 348
7.1.1 ECHAlliance (European Connected Health Alliance) 348
7.1.2 Global Digital Health Network 349
7.1.3 GSMA's Mobile for Development mHealth Program 349
7.1.4 HIMSS (Healthcare Information and Management Systems Society) 350
7.1.5 HL7 (Health Level Seven International) 351
7.1.6 IEEE (Institute of Electrical and Electronics Engineers) 351
7.1.7 ISO (International Organization for Standardization) 352
7.1.8 ITU (International Telecommunications Union) 352
7.1.9 JHU-GmI (Johns Hopkins University Global mHealth Initiative) 353
7.1.10 PCHA (Personal Connected Health Alliance) 353
7.1.11 United Nations Foundation 354
7.1.12 WHO (World Health Organization) 355
7.1.13 WLSA (Wireless–Life Services Alliance) 355
7.2 Key Standards & Legislation 357
7.2.1 ISO/IEEE 11073 PHD (Personal Health Device) Standards 357
7.2.2 HL7's PHMR (Personal Health Monitoring Report) 358
7.2.3 Continua Design Guidelines 358
7.2.4 ITU's E-Health Standards 359
7.2.5 HIPAA (Health Insurance Portability and Accountability Act) 359
7.2.6 HITECH (Heath Information Technology for Economic and Clinical Health) 360
7.1 Standardization Bodies & Alliances 348
7.1.1 ECHAlliance (European Connected Health Alliance) 348
7.1.2 Global Digital Health Network 349
7.1.3 GSMA's Mobile for Development mHealth Program 349
7.1.4 HIMSS (Healthcare Information and Management Systems Society) 350
7.1.5 HL7 (Health Level Seven International) 351
7.1.6 IEEE (Institute of Electrical and Electronics Engineers) 351
7.1.7 ISO (International Organization for Standardization) 352
7.1.8 ITU (International Telecommunications Union) 352
7.1.9 JHU-GmI (Johns Hopkins University Global mHealth Initiative) 353
7.1.10 PCHA (Personal Connected Health Alliance) 353
7.1.11 United Nations Foundation 354
7.1.12 WHO (World Health Organization) 355
7.1.13 WLSA (Wireless–Life Services Alliance) 355
7.2 Key Standards & Legislation 357
7.2.1 ISO/IEEE 11073 PHD (Personal Health Device) Standards 357
7.2.2 HL7's PHMR (Personal Health Monitoring Report) 358
7.2.3 Continua Design Guidelines 358
7.2.4 ITU's E-Health Standards 359
7.2.5 HIPAA (Health Insurance Portability and Accountability Act) 359
7.2.6 HITECH (Heath Information Technology for Economic and Clinical Health) 360
8 Chapter 8: Market Analysis & Forecasts 362
8.1 Global Outlook of mHealth Revenue: 2017 – 2030 362
8.2 Submarket Segmentation 363
8.3 Pharmaceutical Applications Submarket Revenue: 2017 – 2030 364
8.3.1 Safety Data Collection Use Case 365
8.3.2 Consumer Education Use Case 365
8.3.3 Medical Education Use Case 366
8.3.4 Post–Market Monitoring Use Case 366
8.3.5 Drug Authentication Use Case 367
8.3.6 Social Media Use Case 367
8.3.7 Patient Compliance & Retention (Clinical Trials) Use Case 368
8.4 Medical Information & Healthcare Management Submarket Revenue: 2017 – 2030 369
8.4.1 Electronic Health/Medical Records & Tracking Tools Use Case 370
8.4.2 Diagnostic Tools & Medical Reference Use Case 370
8.4.3 Continuing Medical Education Use Case 371
8.4.4 Awareness through Alerts Use Case 371
8.4.5 Logistical & Payment Support Use Case 372
8.5 Healthcare & Fitness Submarket Revenue: 2017 – 2030 373
8.5.1 Medical Compliance Use Case 374
8.5.2 Fitness & Nutrition Apps Use Case 374
8.5.3 Clinical Decision Support Systems Use Case 375
8.5.4 Prescribable Mobile Apps Use Case 375
8.6 Remote Consultation/Diagnostic Services Submarket Revenue: 2017 – 2030 376
8.6.1 Mobile Video Consultations, Collaboration & Surgery Use Case 377
8.6.2 Non–Video Consultations & Collaboration Use Case 377
8.6.3 Remote Collaboration in Emergency Situations Use Case 378
8.7 IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue: 2017 – 2030 379
8.7.1 Health and Wellness Monitoring Use Case 380
8.7.2 Disease Surveillance/Remote Monitoring Use Case 380
8.7.3 Diagnostic Tools Use Case 381
8.7.4 Technical Logistics Use Case 381
8.8 Segmentation by Ecosystem Player 382
8.8.1 Mobile Operators & Connectivity Providers 382
8.8.2 Mobile & mHealth Device OEMs 383
8.8.3 Content & Application Providers 383
8.8.4 Healthcare Service Providers 384
8.8.5 Pharmaceutical Industry 384
8.9 Regional Outlook 385
8.10 Asia Pacific mHealth Revenue: 2017 – 2030 386
8.10.1 Country Level Segmentation 386
8.10.2 Australia 387
8.10.3 China 387
8.10.4 India 388
8.10.5 Japan 388
8.10.6 South Korea 389
8.10.7 Pakistan 389
8.10.8 Thailand 390
8.10.9 Indonesia 390
8.10.10 Malaysia 391
8.10.11 Taiwan 391
8.10.12 Philippines 392
8.10.13 Singapore 392
8.10.14 Rest of Asia Pacific 393
8.11 Eastern Europe mHealth Revenue: 2017 – 2030 394
8.11.1 Country Level Segmentation 394
8.11.2 Czech Republic 395
8.11.3 Poland 395
8.11.4 Russia 396
8.11.5 Rest of Eastern Europe 396
8.12 Latin & Central America mHealth Revenue: 2017 – 2030 397
8.12.1 Country Level Segmentation 397
8.12.2 Argentina 398
8.12.3 Brazil 398
8.12.4 Mexico 399
8.12.5 Rest of Latin & Central America 399
8.13 Middle East & Africa mHealth Revenue: 2017 – 2030 400
8.13.1 Country Level Segmentation 400
8.13.2 Israel 401
8.13.3 Qatar 401
8.13.4 Saudi Arabia 402
8.13.5 South Africa 402
8.13.6 UAE 403
8.13.7 Rest of the Middle East & Africa 403
8.14 North America mHealth Revenue: 2017 – 2030 404
8.14.1 Country Level Segmentation 404
8.14.2 USA 405
8.14.3 Canada 405
8.15 Western Europe mHealth Revenue: 2017 – 2030 406
8.15.1 Country Level Segmentation 406
8.15.2 Denmark 407
8.15.3 Finland 407
8.15.4 France 408
8.15.5 Germany 408
8.15.6 Italy 409
8.15.7 Spain 409
8.15.8 Sweden 410
8.15.9 Norway 410
8.15.10 UK 411
8.15.11 Rest of Western Europe 411
8.1 Global Outlook of mHealth Revenue: 2017 – 2030 362
8.2 Submarket Segmentation 363
8.3 Pharmaceutical Applications Submarket Revenue: 2017 – 2030 364
8.3.1 Safety Data Collection Use Case 365
8.3.2 Consumer Education Use Case 365
8.3.3 Medical Education Use Case 366
8.3.4 Post–Market Monitoring Use Case 366
8.3.5 Drug Authentication Use Case 367
8.3.6 Social Media Use Case 367
8.3.7 Patient Compliance & Retention (Clinical Trials) Use Case 368
8.4 Medical Information & Healthcare Management Submarket Revenue: 2017 – 2030 369
8.4.1 Electronic Health/Medical Records & Tracking Tools Use Case 370
8.4.2 Diagnostic Tools & Medical Reference Use Case 370
8.4.3 Continuing Medical Education Use Case 371
8.4.4 Awareness through Alerts Use Case 371
8.4.5 Logistical & Payment Support Use Case 372
8.5 Healthcare & Fitness Submarket Revenue: 2017 – 2030 373
8.5.1 Medical Compliance Use Case 374
8.5.2 Fitness & Nutrition Apps Use Case 374
8.5.3 Clinical Decision Support Systems Use Case 375
8.5.4 Prescribable Mobile Apps Use Case 375
8.6 Remote Consultation/Diagnostic Services Submarket Revenue: 2017 – 2030 376
8.6.1 Mobile Video Consultations, Collaboration & Surgery Use Case 377
8.6.2 Non–Video Consultations & Collaboration Use Case 377
8.6.3 Remote Collaboration in Emergency Situations Use Case 378
8.7 IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue: 2017 – 2030 379
8.7.1 Health and Wellness Monitoring Use Case 380
8.7.2 Disease Surveillance/Remote Monitoring Use Case 380
8.7.3 Diagnostic Tools Use Case 381
8.7.4 Technical Logistics Use Case 381
8.8 Segmentation by Ecosystem Player 382
8.8.1 Mobile Operators & Connectivity Providers 382
8.8.2 Mobile & mHealth Device OEMs 383
8.8.3 Content & Application Providers 383
8.8.4 Healthcare Service Providers 384
8.8.5 Pharmaceutical Industry 384
8.9 Regional Outlook 385
8.10 Asia Pacific mHealth Revenue: 2017 – 2030 386
8.10.1 Country Level Segmentation 386
8.10.2 Australia 387
8.10.3 China 387
8.10.4 India 388
8.10.5 Japan 388
8.10.6 South Korea 389
8.10.7 Pakistan 389
8.10.8 Thailand 390
8.10.9 Indonesia 390
8.10.10 Malaysia 391
8.10.11 Taiwan 391
8.10.12 Philippines 392
8.10.13 Singapore 392
8.10.14 Rest of Asia Pacific 393
8.11 Eastern Europe mHealth Revenue: 2017 – 2030 394
8.11.1 Country Level Segmentation 394
8.11.2 Czech Republic 395
8.11.3 Poland 395
8.11.4 Russia 396
8.11.5 Rest of Eastern Europe 396
8.12 Latin & Central America mHealth Revenue: 2017 – 2030 397
8.12.1 Country Level Segmentation 397
8.12.2 Argentina 398
8.12.3 Brazil 398
8.12.4 Mexico 399
8.12.5 Rest of Latin & Central America 399
8.13 Middle East & Africa mHealth Revenue: 2017 – 2030 400
8.13.1 Country Level Segmentation 400
8.13.2 Israel 401
8.13.3 Qatar 401
8.13.4 Saudi Arabia 402
8.13.5 South Africa 402
8.13.6 UAE 403
8.13.7 Rest of the Middle East & Africa 403
8.14 North America mHealth Revenue: 2017 – 2030 404
8.14.1 Country Level Segmentation 404
8.14.2 USA 405
8.14.3 Canada 405
8.15 Western Europe mHealth Revenue: 2017 – 2030 406
8.15.1 Country Level Segmentation 406
8.15.2 Denmark 407
8.15.3 Finland 407
8.15.4 France 408
8.15.5 Germany 408
8.15.6 Italy 409
8.15.7 Spain 409
8.15.8 Sweden 410
8.15.9 Norway 410
8.15.10 UK 411
8.15.11 Rest of Western Europe 411
9 Chapter 9: Conclusion & Strategic Recommendations 412
9.1 Moving Towards Connected Drug Delivery Platforms 412
9.2 Are Prescribable mHealth Apps a Threat to the Pharmaceutical Industry? 413
9.3 Will mHealth Requirements Drive HD Mobile Video Deployments? 413
9.4 Is mHealth Security an All-or-Nothing Decision? 414
9.5 Healthcare Industry Approval & Accreditation: Key to Success 414
9.6 Improving Operational Efficiency and Reducing Costs 415
9.7 Collaborations Help in Promoting mHealth 416
9.8 The Importance of End User Belief 416
9.9 Wearable Technology: Prospects in the mHealth Ecosystem 417
9.10 Are Mobile Operators Simply Connectivity Providers for mHealth? 418
9.11 Driving Investments in Big Data & Analytics 419
9.12 Implementing Successful mHealth Strategies in Hospitals 420
9.13 Strategic Recommendations 421
9.13.1 Recommendations for Mobile Operators 421
9.13.2 Recommendations for Enabling Technology Providers and mHealth Device OEMs 421
9.13.3 Recommendations for Application Developers 422
9.13.4 Recommendations for Healthcare Professionals and Providers 422
9.13.5 Recommendations for the Pharmaceutical Industry 422
9.1 Moving Towards Connected Drug Delivery Platforms 412
9.2 Are Prescribable mHealth Apps a Threat to the Pharmaceutical Industry? 413
9.3 Will mHealth Requirements Drive HD Mobile Video Deployments? 413
9.4 Is mHealth Security an All-or-Nothing Decision? 414
9.5 Healthcare Industry Approval & Accreditation: Key to Success 414
9.6 Improving Operational Efficiency and Reducing Costs 415
9.7 Collaborations Help in Promoting mHealth 416
9.8 The Importance of End User Belief 416
9.9 Wearable Technology: Prospects in the mHealth Ecosystem 417
9.10 Are Mobile Operators Simply Connectivity Providers for mHealth? 418
9.11 Driving Investments in Big Data & Analytics 419
9.12 Implementing Successful mHealth Strategies in Hospitals 420
9.13 Strategic Recommendations 421
9.13.1 Recommendations for Mobile Operators 421
9.13.2 Recommendations for Enabling Technology Providers and mHealth Device OEMs 421
9.13.3 Recommendations for Application Developers 422
9.13.4 Recommendations for Healthcare Professionals and Providers 422
9.13.5 Recommendations for the Pharmaceutical Industry 422
List of Figures (page number)
Figure 1: Global Connected Consumer Mobile Device vs. PC Shipments: 2017 – 2030 (Millions of Units) 41
Figure 2: Mobile Network Subscriptions by Region: 2017 – 2030 (Millions) 42
Figure 3: Annual Throughput of Mobile Network Data Traffic by Region: 2017 – 2030 (Exabytes) 43
Figure 4: Cost Saving Potential of mHealth by Region: 2017 – 2030 ($ Million) 45
Figure 5: The IoT Vision 52
Figure 6: IoT Network Architecture 53
Figure 7: Global IoT Connections for mHealth Applications: 2017 – 2030 (Millions) 55
Figure 8: Global Mobile Video Calling Users: 2017 – 2030 (Millions) 56
Figure 9: mHealth Use Case Categories 57
Figure 10: The mHealth Value Chain 61
Figure 11: mHealth Industry Roadmap: 2017 – 2030 65
Figure 12: Global mHealth Revenue: 2017 – 2030 ($ Million) 365
Figure 13: Global mHealth Revenue by Submarket: 2017 – 2030 ($ Million) 366
Figure 14: Global Pharmaceutical Applications Submarket Revenue: 2017 – 2030 ($ Million) 367
Figure 15: Global Pharmaceutical Applications Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 367
Figure 16: Global Safety Data Collection Use Case Revenue: 2017 – 2030 ($ Million) 368
Figure 17: Global Consumer Education Use Case Revenue: 2017 – 2030 ($ Million) 368
Figure 18: Global Medical Education Use Case Revenue: 2017 – 2030 ($ Million) 369
Figure 19: Global Post–Market Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 369
Figure 20: Global Drug Authentication Use Case Revenue: 2017 – 2030 ($ Million) 370
Figure 21: Global Social Media Use Case Revenue: 2017 – 2030 ($ Million) 370
Figure 22: Global Patient Compliance & Retention (Clinical Trials) Use Case Revenue: 2017 – 2030 ($ Million) 371
Figure 23: Global Medical Information & Healthcare Management Submarket Revenue: 2017 – 2030 ($ Million) 372
Figure 24: Global Medical Information & Healthcare Management Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 372
Figure 25: Global Electronic Health/Medical Records & Tracking Tools Use Case Revenue: 2017 – 2030 ($ Million) 373
Figure 26: Global Diagnostic Tools & Medical Reference Use Case Revenue: 2017 – 2030 ($ Million) 373
Figure 27: Global Continuing Medical Education Use Case Revenue: 2017 – 2030 ($ Million) 374
Figure 28: Global Awareness through Alerts Use Case Revenue: 2017 – 2030 ($ Million) 374
Figure 29: Global Logistical & Payment Support Use Case Revenue: 2017 – 2030 ($ Million) 375
Figure 30: Global Healthcare & Fitness Submarket Revenue: 2017 – 2030 ($ Million) 376
Figure 31: Global Healthcare & Fitness Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 376
Figure 32: Global Medical Compliance Use Case Revenue: 2017 – 2030 ($ Million) 377
Figure 33: Global Fitness & Nutrition Apps Use Case Revenue: 2017 – 2030 ($ Million) 377
Figure 34: Global Clinical Decision Support Systems Use Case Revenue: 2017 – 2030 ($ Million) 378
Figure 35: Global Prescribable Mobile Apps Use Case Revenue: 2017 – 2030 ($ Million) 378
Figure 36: Global Remote Consultation/Diagnostic Services Submarket Revenue: 2017 – 2030 ($ Million) 379
Figure 37: Global Remote Consultation/Diagnostic Services Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 379
Figure 38: Global Mobile Video Consultations, Collaboration & Surgery Use Case Revenue: 2017 – 2030 ($ Million) 380
Figure 39: Global Non–Video Consultations & Collaboration Use Case Revenue: 2017 – 2030 ($ Million) 380
Figure 40: Global Remote Collaboration in Emergency Situations Use Case Revenue: 2017 – 2030 ($ Million) 381
Figure 41: Global IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue: 2017 – 2030 ($ Million) 382
Figure 42: Global IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 382
Figure 43: Global Health and Wellness Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 383
Figure 44: Global Disease Surveillance/Remote Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 383
Figure 45: Global Diagnostic Tools Use Case Revenue: 2017 – 2030 ($ Million) 384
Figure 46: Global Technical Logistics Use Case Revenue: 2017 – 2030 ($ Million) 384
Figure 47: Global mHealth Revenue by Ecosystem Player: 2017 – 2030 ($ Million) 385
Figure 48: Global Mobile Network Operator & Connectivity Provider mHealth Revenue: 2017 – 2030 ($ Million) 385
Figure 49: Global Mobile & mHealth Device OEMs Revenue: 2017 – 2030 ($ Million) 386
Figure 50: Global mHealth Content & Application Providers Revenue: 2017 – 2030 ($ Million) 386
Figure 51: Global Healthcare Service Providers mHealth Revenue: 2017 – 2030 ($ Million) 387
Figure 52: Global Pharmaceutical Industry mHealth Revenue: 2017 – 2030 ($ Million) 387
Figure 53: mHealth Revenue by Region: 2017 – 2030 ($ Million) 388
Figure 54: Asia Pacific mHealth Revenue: 2017 – 2030 ($ Million) 389
Figure 55: Asia Pacific mHealth Revenue by Country: 2017 – 2030 ($ Million) 389
Figure 56: Australia mHealth Revenue: 2017 – 2030 ($ Million) 390
Figure 57: China mHealth Revenue: 2017 – 2030 ($ Million) 390
Figure 58: India mHealth Revenue: 2017 – 2030 ($ Million) 391
Figure 59: Japan mHealth Revenue: 2017 – 2030 ($ Million) 391
Figure 60: South Korea mHealth Revenue: 2017 – 2030 ($ Million) 392
Figure 61: Pakistan mHealth Revenue: 2017 – 2030 ($ Million) 392
Figure 62: Thailand mHealth Revenue: 2017 – 2030 ($ Million) 393
Figure 63: Indonesia mHealth Revenue: 2017 – 2030 ($ Million) 393
Figure 64: Malaysia mHealth Revenue: 2017 – 2030 ($ Million) 394
Figure 65: Taiwan mHealth Revenue: 2017 – 2030 ($ Million) 394
Figure 66: Philippines mHealth Revenue: 2017 – 2030 ($ Million) 395
Figure 67: Philippines mHealth Revenue: 2017 – 2030 ($ Million) 395
Figure 68: mHealth Revenue in the Rest of Asia Pacific: 2017 – 2030 ($ Million) 396
Figure 69: Eastern Europe mHealth Revenue: 2017 – 2030 ($ Million) 397
Figure 70: Eastern Europe mHealth Revenue by Country: 2017 – 2030 ($ Million) 397
Figure 71: Czech Republic mHealth Revenue: 2017 – 2030 ($ Million) 398
Figure 72: Poland mHealth Revenue: 2017 – 2030 ($ Million) 398
Figure 73: Russia mHealth Revenue: 2017 – 2030 ($ Million) 399
Figure 74: mHealth Revenue in the Rest of Eastern Europe: 2017 – 2030 ($ Million) 399
Figure 75: Latin & Central America mHealth Revenue: 2017 – 2030 ($ Million) 400
Figure 76: Latin & Central America mHealth Revenue by Country: 2017 – 2030 ($ Million) 400
Figure 77: Argentina mHealth Revenue: 2017 – 2030 ($ Million) 401
Figure 78: Brazil mHealth Revenue: 2017 – 2030 ($ Million) 401
Figure 79: Mexico mHealth Revenue: 2017 – 2030 ($ Million) 402
Figure 80: mHealth Revenue in the Rest of Latin & Central America: 2017 – 2030 ($ Million) 402
Figure 81: Middle East & Africa mHealth Revenue: 2017 – 2030 ($ Million) 403
Figure 82: Middle East & Africa mHealth Revenue by Country: 2017 – 2030 ($ Million) 403
Figure 83: Israel mHealth Revenue: 2017 – 2030 ($ Million) 404
Figure 84: Qatar mHealth Revenue: 2017 – 2030 ($ Million) 404
Figure 85: Saudi Arabia mHealth Revenue: 2017 – 2030 ($ Million) 405
Figure 86: South Africa mHealth Revenue: 2017 – 2030 ($ Million) 405
Figure 87: UAE mHealth Revenue: 2017 – 2030 ($ Million) 406
Figure 88: mHealth Revenue in the Rest of the Middle East & Africa: 2017 – 2030 ($ Million) 406
Figure 89: North America mHealth Revenue: 2017 – 2030 ($ Million) 407
Figure 90: North America mHealth Revenue by Country: 2017 – 2030 ($ Million) 407
Figure 91: USA mHealth Revenue: 2017 – 2030 ($ Million) 408
Figure 92: Canada mHealth Revenue: 2017 – 2030 ($ Million) 408
Figure 93: Western Europe mHealth Revenue: 2017 – 2030 ($ Million) 409
Figure 94: Western Europe mHealth Revenue by Country: 2017 – 2030 ($ Million) 409
Figure 95: Denmark mHealth Revenue: 2017 – 2030 ($ Million) 410
Figure 96: Finland mHealth Revenue: 2017 – 2030 ($ Million) 410
Figure 97: France mHealth Revenue: 2017 – 2030 ($ Million) 411
Figure 98: Germany mHealth Revenue: 2017 – 2030 ($ Million) 411
Figure 99: Italy mHealth Revenue: 2017 – 2030 ($ Million) 412
Figure 100: Spain mHealth Revenue: 2017 – 2030 ($ Million) 412
Figure 101: Sweden mHealth Revenue: 2017 – 2030 ($ Million) 413
Figure 102: Norway mHealth Revenue: 2017 – 2030 ($ Million) 413
Figure 103: UK mHealth Revenue: 2017 – 2030 ($ Million) 414
Figure 104: mHealth Revenue in the Rest of Western Europe: 2017 – 2030 ($ Million) 414
Figure 105: Global mHealth Centric Wearable Device Shipments: 2017 – 2030 (Millions of Units) 420
Figure 106: Global Big Data & Analytics Technology Investments in the Healthcare Sector: 2017 – 2030 ($ Million) 422
Figure 2: Mobile Network Subscriptions by Region: 2017 – 2030 (Millions) 42
Figure 3: Annual Throughput of Mobile Network Data Traffic by Region: 2017 – 2030 (Exabytes) 43
Figure 4: Cost Saving Potential of mHealth by Region: 2017 – 2030 ($ Million) 45
Figure 5: The IoT Vision 52
Figure 6: IoT Network Architecture 53
Figure 7: Global IoT Connections for mHealth Applications: 2017 – 2030 (Millions) 55
Figure 8: Global Mobile Video Calling Users: 2017 – 2030 (Millions) 56
Figure 9: mHealth Use Case Categories 57
Figure 10: The mHealth Value Chain 61
Figure 11: mHealth Industry Roadmap: 2017 – 2030 65
Figure 12: Global mHealth Revenue: 2017 – 2030 ($ Million) 365
Figure 13: Global mHealth Revenue by Submarket: 2017 – 2030 ($ Million) 366
Figure 14: Global Pharmaceutical Applications Submarket Revenue: 2017 – 2030 ($ Million) 367
Figure 15: Global Pharmaceutical Applications Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 367
Figure 16: Global Safety Data Collection Use Case Revenue: 2017 – 2030 ($ Million) 368
Figure 17: Global Consumer Education Use Case Revenue: 2017 – 2030 ($ Million) 368
Figure 18: Global Medical Education Use Case Revenue: 2017 – 2030 ($ Million) 369
Figure 19: Global Post–Market Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 369
Figure 20: Global Drug Authentication Use Case Revenue: 2017 – 2030 ($ Million) 370
Figure 21: Global Social Media Use Case Revenue: 2017 – 2030 ($ Million) 370
Figure 22: Global Patient Compliance & Retention (Clinical Trials) Use Case Revenue: 2017 – 2030 ($ Million) 371
Figure 23: Global Medical Information & Healthcare Management Submarket Revenue: 2017 – 2030 ($ Million) 372
Figure 24: Global Medical Information & Healthcare Management Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 372
Figure 25: Global Electronic Health/Medical Records & Tracking Tools Use Case Revenue: 2017 – 2030 ($ Million) 373
Figure 26: Global Diagnostic Tools & Medical Reference Use Case Revenue: 2017 – 2030 ($ Million) 373
Figure 27: Global Continuing Medical Education Use Case Revenue: 2017 – 2030 ($ Million) 374
Figure 28: Global Awareness through Alerts Use Case Revenue: 2017 – 2030 ($ Million) 374
Figure 29: Global Logistical & Payment Support Use Case Revenue: 2017 – 2030 ($ Million) 375
Figure 30: Global Healthcare & Fitness Submarket Revenue: 2017 – 2030 ($ Million) 376
Figure 31: Global Healthcare & Fitness Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 376
Figure 32: Global Medical Compliance Use Case Revenue: 2017 – 2030 ($ Million) 377
Figure 33: Global Fitness & Nutrition Apps Use Case Revenue: 2017 – 2030 ($ Million) 377
Figure 34: Global Clinical Decision Support Systems Use Case Revenue: 2017 – 2030 ($ Million) 378
Figure 35: Global Prescribable Mobile Apps Use Case Revenue: 2017 – 2030 ($ Million) 378
Figure 36: Global Remote Consultation/Diagnostic Services Submarket Revenue: 2017 – 2030 ($ Million) 379
Figure 37: Global Remote Consultation/Diagnostic Services Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 379
Figure 38: Global Mobile Video Consultations, Collaboration & Surgery Use Case Revenue: 2017 – 2030 ($ Million) 380
Figure 39: Global Non–Video Consultations & Collaboration Use Case Revenue: 2017 – 2030 ($ Million) 380
Figure 40: Global Remote Collaboration in Emergency Situations Use Case Revenue: 2017 – 2030 ($ Million) 381
Figure 41: Global IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue: 2017 – 2030 ($ Million) 382
Figure 42: Global IoT, Wearable Technology, Sensor & Monitoring Applications Submarket Revenue by Use Case Category: 2017 – 2030 ($ Million) 382
Figure 43: Global Health and Wellness Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 383
Figure 44: Global Disease Surveillance/Remote Monitoring Use Case Revenue: 2017 – 2030 ($ Million) 383
Figure 45: Global Diagnostic Tools Use Case Revenue: 2017 – 2030 ($ Million) 384
Figure 46: Global Technical Logistics Use Case Revenue: 2017 – 2030 ($ Million) 384
Figure 47: Global mHealth Revenue by Ecosystem Player: 2017 – 2030 ($ Million) 385
Figure 48: Global Mobile Network Operator & Connectivity Provider mHealth Revenue: 2017 – 2030 ($ Million) 385
Figure 49: Global Mobile & mHealth Device OEMs Revenue: 2017 – 2030 ($ Million) 386
Figure 50: Global mHealth Content & Application Providers Revenue: 2017 – 2030 ($ Million) 386
Figure 51: Global Healthcare Service Providers mHealth Revenue: 2017 – 2030 ($ Million) 387
Figure 52: Global Pharmaceutical Industry mHealth Revenue: 2017 – 2030 ($ Million) 387
Figure 53: mHealth Revenue by Region: 2017 – 2030 ($ Million) 388
Figure 54: Asia Pacific mHealth Revenue: 2017 – 2030 ($ Million) 389
Figure 55: Asia Pacific mHealth Revenue by Country: 2017 – 2030 ($ Million) 389
Figure 56: Australia mHealth Revenue: 2017 – 2030 ($ Million) 390
Figure 57: China mHealth Revenue: 2017 – 2030 ($ Million) 390
Figure 58: India mHealth Revenue: 2017 – 2030 ($ Million) 391
Figure 59: Japan mHealth Revenue: 2017 – 2030 ($ Million) 391
Figure 60: South Korea mHealth Revenue: 2017 – 2030 ($ Million) 392
Figure 61: Pakistan mHealth Revenue: 2017 – 2030 ($ Million) 392
Figure 62: Thailand mHealth Revenue: 2017 – 2030 ($ Million) 393
Figure 63: Indonesia mHealth Revenue: 2017 – 2030 ($ Million) 393
Figure 64: Malaysia mHealth Revenue: 2017 – 2030 ($ Million) 394
Figure 65: Taiwan mHealth Revenue: 2017 – 2030 ($ Million) 394
Figure 66: Philippines mHealth Revenue: 2017 – 2030 ($ Million) 395
Figure 67: Philippines mHealth Revenue: 2017 – 2030 ($ Million) 395
Figure 68: mHealth Revenue in the Rest of Asia Pacific: 2017 – 2030 ($ Million) 396
Figure 69: Eastern Europe mHealth Revenue: 2017 – 2030 ($ Million) 397
Figure 70: Eastern Europe mHealth Revenue by Country: 2017 – 2030 ($ Million) 397
Figure 71: Czech Republic mHealth Revenue: 2017 – 2030 ($ Million) 398
Figure 72: Poland mHealth Revenue: 2017 – 2030 ($ Million) 398
Figure 73: Russia mHealth Revenue: 2017 – 2030 ($ Million) 399
Figure 74: mHealth Revenue in the Rest of Eastern Europe: 2017 – 2030 ($ Million) 399
Figure 75: Latin & Central America mHealth Revenue: 2017 – 2030 ($ Million) 400
Figure 76: Latin & Central America mHealth Revenue by Country: 2017 – 2030 ($ Million) 400
Figure 77: Argentina mHealth Revenue: 2017 – 2030 ($ Million) 401
Figure 78: Brazil mHealth Revenue: 2017 – 2030 ($ Million) 401
Figure 79: Mexico mHealth Revenue: 2017 – 2030 ($ Million) 402
Figure 80: mHealth Revenue in the Rest of Latin & Central America: 2017 – 2030 ($ Million) 402
Figure 81: Middle East & Africa mHealth Revenue: 2017 – 2030 ($ Million) 403
Figure 82: Middle East & Africa mHealth Revenue by Country: 2017 – 2030 ($ Million) 403
Figure 83: Israel mHealth Revenue: 2017 – 2030 ($ Million) 404
Figure 84: Qatar mHealth Revenue: 2017 – 2030 ($ Million) 404
Figure 85: Saudi Arabia mHealth Revenue: 2017 – 2030 ($ Million) 405
Figure 86: South Africa mHealth Revenue: 2017 – 2030 ($ Million) 405
Figure 87: UAE mHealth Revenue: 2017 – 2030 ($ Million) 406
Figure 88: mHealth Revenue in the Rest of the Middle East & Africa: 2017 – 2030 ($ Million) 406
Figure 89: North America mHealth Revenue: 2017 – 2030 ($ Million) 407
Figure 90: North America mHealth Revenue by Country: 2017 – 2030 ($ Million) 407
Figure 91: USA mHealth Revenue: 2017 – 2030 ($ Million) 408
Figure 92: Canada mHealth Revenue: 2017 – 2030 ($ Million) 408
Figure 93: Western Europe mHealth Revenue: 2017 – 2030 ($ Million) 409
Figure 94: Western Europe mHealth Revenue by Country: 2017 – 2030 ($ Million) 409
Figure 95: Denmark mHealth Revenue: 2017 – 2030 ($ Million) 410
Figure 96: Finland mHealth Revenue: 2017 – 2030 ($ Million) 410
Figure 97: France mHealth Revenue: 2017 – 2030 ($ Million) 411
Figure 98: Germany mHealth Revenue: 2017 – 2030 ($ Million) 411
Figure 99: Italy mHealth Revenue: 2017 – 2030 ($ Million) 412
Figure 100: Spain mHealth Revenue: 2017 – 2030 ($ Million) 412
Figure 101: Sweden mHealth Revenue: 2017 – 2030 ($ Million) 413
Figure 102: Norway mHealth Revenue: 2017 – 2030 ($ Million) 413
Figure 103: UK mHealth Revenue: 2017 – 2030 ($ Million) 414
Figure 104: mHealth Revenue in the Rest of Western Europe: 2017 – 2030 ($ Million) 414
Figure 105: Global mHealth Centric Wearable Device Shipments: 2017 – 2030 (Millions of Units) 420
Figure 106: Global Big Data & Analytics Technology Investments in the Healthcare Sector: 2017 – 2030 ($ Million) 422
Thank you once again and looking forward to hearing from you.
Kind Regards
Andy Silva
Marketing Executive
To unsubscribe please send an email with unsubscribe in the subject line to: remove@snsreports.com
Подписаться на:
Сообщения (Atom)