Omron

Comparison between Telehealth Device and OMRON connect App

Integration
using Omron Telehealth Device
Integration via OMRON connect App
Integration via the server Integration via OMRON connect App provided by OMRON
Description Using Omron Telehealth Device
adopting standard Services and Profiles
designated by Bluetooth SIG
Integration via the server provided by OMRON Integration via OMRON connect App provided by OMRON
Released Area
(As of Apr 2024)

North America:
USA, Canada

Latin America:
Mexico, Brazil, Argentina

Asia Pacific:
India, Korea, Japan, Thailand, Taiwan, China, Australia, Indonesia, Philippines, Singapore, Viet Nam

Asia Pacific:
Japan, Taiwan, South Korea, Australia, Malaysia, Singapore, Thailand, Vietnam, Indonesia, New Zealand, Bangladesh, Philippines, Mongolia

Latin America:
Mexico, Chile, Colombia, Peru, Argentina, Ecuador, Uruguay, Panama, Guatemala, Costa Rica, Bolivia, Paraguay, Nicaragua, El Salvador, Honduras, Dominican Republic, Brazil, Venezuela

Asia Pacific:
Taiwan, Australia, Malaysia, Vietnam, Thailand, Singapore, HongKong, Philippines, Japan, New Zealand, Indonesia, India, South Korea, Myanmar, Bangladesh, Cambodia, Sri Lanka, Macau, Laos, Mongolia

EMEA:
Russia

Expected use case Telehealth service company who integrates with multiple manufacturers' devices For service provider who provides the service on the server ・For service provider who provides service without the server (App only)
・Integration via Apple Health
Integration flow
OS iOS / Android iOS / Android iOS / Android
Data communication
technology
BLE4.0 BLE4.0 BLE4.0
How to Distribute
Omron device?
B to B to C
(Distributor / 3rd Party would purchase Omron device and Distribute to end users.)
B to C (Retail)
What does Omron provide? ・StarterKit
(Data communication specification doc. , Sample data communication App using standard Services and Profiles designated by Bluetooth SIG)
・DataServerAPI Specification doc.
・Integration AppID for 3rd Party
・OMRON connect App for testing
・Reference Manual for App integration doc.
・Integration AppID for 3rd Party
・OMRON connect App for testing
・Test App for URL scheme verification (including Source code)

(The following are needed in case Android)
・Wrapper Function library
・Test App for library verification (including Source code)
Dev/Support cost of
3rd Party
Middle Very Low Low
  ・Regarding the function of data integration with Omron device, 3rd party does NOT need to modify the App for corresponding OS updates and latest smartphone models themselves, because Omron will update OMRON connect App.

・Just Use the API (OAuth2.0, REST). No need to modify 3rd party system.
・Regarding the function of data integration with Omron device, 3rd party does NOT need to modify the App corresponding OS updates and latest smartphone models themselves,because Omron will update OMRON connect App.
・3rd party needs to modify the App corresponding to OS updates and latest smartphone models themselves, although Omron will update Sample data communication App after assessing global based request.

・3rd Party need to develop the function of data integration with Omron device by themselves, referring to Omron Sample App.
  ・3rd Party needs to include Wrapper function library to 3rd party App.
User Experience Good Good Good
・User just need to install 3rd party App ・User can store not only standard index designated by Bluetooth SIG but also OMRON original index ・User can store not only standard index designated by Bluetooth SIG but also OMRON original index
・User can store only standard index designated by Bluetooth SIG ・User need to install two App, 3rd party App and OMRON connect App (Although OMRON connect App can work in the background without user's awareness.)

・User need to create the account for OMRON connect server service
・User need to install two Apps, 3rd party App and OMRON connect App (Although OMRON connect App can work in the background without user's awareness.)