You make a wearable
A ring, a watch, a patch
Your device already reads a pulse. You want the analysis that turns it into a rhythm assessment, without building it or certifying it yourself.
Your signal, our analysis → →
Integrations Heart rhythm analysis, built into what you already run.
FibriCheck separates capturing a pulse from analysing it. That means there is more than one way in, and the right one depends on what you have already built rather than on which technology you prefer.
Three ways in
Start from what you already have
Pick the one that describes you. Each has its own route, and its own conversation.
You have an app and an audience
Remote monitoring, health apps, insurers, resellers
You have the users but no sensor. The phone already in their pocket becomes the measuring device, either inside your app or alongside it.
Two ways to offer it → →
You run the systems
Hospitals, platforms, records
You need the results to arrive where the care already happens: your dashboards, your workflow, your patient records.
The ecosystem layer → → Chapter one
You already capture the signal. We turn it into an answer.
A ring, a watch or a patch already reads a pulse. Because FibriCheck keeps capture and analysis separate, your sensor can feed our arrhythmia analysis directly. You keep your hardware and your experience; you do not have to build cardiology, or carry it through a regulatory process.
-
Your sensor, our algorithm
You send the pulse signal your device already produces. We return the rhythm assessment.
-
The regulatory weight stays with us
The analysis is part of a certified medical device. That is the part which is slow and expensive to build alone.
-
Built for continuous, not occasional
Designed to keep working night after night at volume, rather than one measurement at a time.
How a wearable integration starts The signal contract depends on your sensor, so this one begins as a conversation rather than a download.
Talk to us about a wearable integration
In production Night after night, inside a smart ring
Our integration with the Ultrahuman Ring analyses night-time pulse measurements continuously, at a scale that runs around the clock. It is the clearest example of what this looks like once it is live rather than planned.
Chapter two
You already have the users. We bring the measurement.
No hardware, no shipping, no sensor to source. The smartphone your users already carry becomes the measuring device. From there it is one question: do you want the measurement inside your own app, or would you rather not build anything at all?
Build it in
- The measurement happens in your own app, in your own interface, under your own brand.
- A camera component records the pulse on the device; a cloud component handles the analysis.
- Native iOS and Android, plus React Native, Flutter, Cordova and JavaScript.
- For teams who own the product experience and want to keep the user in one place.
Your app, your design
Hand it over
- Send your user into the FibriCheck app for the measurement, then bring them back to yours.
- Read their results through our cloud once the measurement is done.
- No camera work, no signal processing, no mobile release of your own.
- The usual route for insurers, resellers and anyone distributing FibriCheck rather than building with it.
Nothing to build
If you are an insurer or a reseller You may not need an integration at all. If the question is how to offer FibriCheck to a member population rather than how to embed it, that conversation starts on the partner page.
FibriCheck for partnersWhichever door you come through, the data leaves the same way
A measurement is only worth taking if it reaches the person who acts on it. This is not a third option to choose between. Every integration above uses it.
-
A REST API for the whole object model
Users, prescriptions, measurements and reports, so your own systems can read and drive FibriCheck rather than sitting beside it.
-
Webhooks, so you are not polling
Your system is notified the moment a result is ready. Your side of the integration stays event-driven instead of checking on a timer.
-
A report a clinician can actually use
Every measurement produces a structured report, built to be read by a doctor and attached to a patient's documentation.
-
Into the electronic health record
In the Netherlands, results reach hospital records through our partners, so follow-up happens in the system the care team already works in.
Before you get in touch
The questions we are usually asked first
We make a wearable. Do we need your camera SDK?
No. The camera component exists for products that use a phone camera to record the pulse. If your device already captures its own signal, that step is yours and the analysis is ours. Because the exact signal contract depends on your sensor, we scope this with you rather than handing over a download.
Which route should we choose?
It comes down to how much of the experience you want to own. Measurement inside your own app means the SDK. Something running quickly, with no mobile work on your side, means app-to-app. A platform or hospital pulling data into a system you already run means the API. It is a short conversation and we are glad to have it before you commit to anything.
Do you have an SDK, or only an API?
Both. There are software development kits for iOS and Android, plus cross-platform support for React Native, Flutter, Cordova and JavaScript, alongside a REST API. The developer documentation sets out what each one covers.
What does it cost?
Commercial terms depend on which route you take, the volume you expect and the markets you operate in, so there is no single price to quote here. Tell us what you are building and we will come back with something concrete.
Does integrating a medical device create obligations for us?
FibriCheck is a certified medical device, and that carries requirements which extend to how a partner presents and uses it. Our documentation sets out what we expect from a partner-facing product, and we work through it with you during the integration rather than leaving you to discover it later.
How long does an integration take?
Genuinely dependent on the route and on your team, which is why we would rather scope it with you than publish a number that turns out to be wrong for your case.
Anything not covered here is better answered by a person.
Email our integrations teamTell us what you are building and we will tell you how it connects
A short introduction call is usually enough to work out which route fits and what the next step looks like. Reach out through the form, or email integrations@fibricheck.com directly.