CGM & Connected Monitoring
CGM & Connected Monitoring
A connected monitoring platform built around a single-use upper-arm glucose sensor, compatible watch displays and a companion app. Explore the S10 system, understand the sensor-to-display architecture and start a B2B project discussion.
System Architecture
One sensor. One connected display layer.
The S10 system is easiest to understand as a simple product platform: the adhesive sensor measures, while the watch and app present synchronized data.
Adhesive upper-arm sensor
The single-use sensor is the measurement element. It is worn on the upper arm for the documented wear period.
Wireless data transfer
Readings move from the sensor to a compatible display device or companion app. Compatibility is confirmed per configuration.
Watch and app display
The watch and app show synchronized readings. They are display endpoints, not separate glucose sensors.
Programme Fit
A connected monitoring platform for three buyer paths
Use the category page to identify the platform, then move to the S10 page or contact route for project-specific documentation.
Health brands
Add a connected glucose-monitoring line with a clear sensor-to-display story.
Regional distributors
Review the available documentation and territory-specific registration path before listing.
Digital-health teams
Scope the data workflow, display endpoints and downstream integration requirements.
Resources
Go deeper when the project needs it
The overview stays concise. These two pages hold the technical and procurement detail.
Frequently Asked Questions
Questions buyers usually need answered first
Practical answers about product selection, everyday use and planning your project.
Visit the FAQ pageIs the glucose sensor inside the watch or the ring?
No. The sensing element in the S10 CGM system is a separate, single-use adhesive sensor applied to the upper arm. The connected smartwatch, the ring and the smartphone application are display endpoints for synchronized data — they present readings, they do not obtain them. No device in this system reads glucose from the wrist or the finger, and no non-invasive sensing is claimed.
Which parts make up the system, and how does data move between them?
Two physically distinct parts. First, the single-use adhesive upper-arm sensor. Second, a display layer of compatible LUROGEF smartwatches and the companion smartphone application. Data moves wirelessly from the sensor to a paired display device or the app, and both can present synchronized readings. What happens to data beyond the app — export format, hosting and third-party integration — is not yet confirmed and is one of the items this page flags as open.
What do the published performance figures mean in practice?
The sensor is worn for 15 days and takes a reading every 3 minutes, with a published accuracy of MARD 8.32%. MARD — mean absolute relative difference — is the standard accuracy measure for continuous glucose monitoring, and it is an average across a study population: it describes typical agreement with a reference measurement, not the error on any individual reading. A single reading can be further off than the MARD figure suggests. If you are building a programme on these numbers, tell us the population and the clinical workflow you have in mind, and we will walk you through what the figure covers.
Is this system registered, and where can it be sold?
The system holds Chinese registrations Guo Xie Zhu Zhun 20253071982 and Yue Xie Zhu Zhun 20242071765. Continuous glucose monitoring systems are regulated as medical devices in most markets, and registration is both territory- and model-specific, so a registration held in China does not by itself authorise sale elsewhere. A partner placing the product on another market carries that market’s duty, and we work through the documentation for your market with you before you commit.
What can we customise, and what should we request in writing before we commit?
Company material describes software, app and hardware customisation capability and a cloud health platform with third-party integration. What is specific to this system — app publishing ownership, SDK or API availability, data-export format, packaging and branding scope, MOQ and lead time — is not yet confirmed and is not promised on this page. Before committing, request the system specification, the verified display-device and app compatibility list, the kit contents, the original certificates behind any registration number, and the validation file behind any performance figure.