High-level blueprint for how ActiPatch could be evolved into a data-collecting, AI-ready wearable without breaking its core identity as a simple, over-the-counter pain device.
What ActiPatch is today (baseline)
Device type: Over-the-counter wearable medical device for musculoskeletal pain
Mechanism: Pulsed shortwave / pulsed radiofrequency energy (a form of PEMF) modulating nerve activity and central sensitization
Usage model: Simple, non-sensory therapy — no user data, no connectivity, no analytics
That’s your “dumb but effective” hardware. Now let’s turn it into a smart, data-generating platform.
1. Decide what data the “smart ActiPatch” should collect
Start with low-friction, high-signal data — things you can get without burdening the user.
Core data types:
Usage data
On/off time
Session duration
Cumulative hours of use
Adherence patterns (e.g., daily, sporadic, overnight)
Location & context (not GPS at first, but body-context)
Which body area is being treated (back, knee, neck, etc.) chosen in the app
Therapy mode (e.g., standard, post-acute, chronic)
Basic motion & posture
Accelerometer to detect:
Activity levels (sedentary vs active)
Position changes (e.g., lying vs walking)
Potential correlation between movement and pain relief
Optional biosignals (phase two)
Skin temperature near the patch (inflammation proxy)
Skin conductance (stress/pain proxy)
Simple heart-rate via optical sensor (if placed where feasible)
This gives you a minimum viable dataset that can feed AI models later:
“When the device is used, how long, in what context, and what changes in activity occur over time?”
2. Hardware changes to ActiPatch: from passive patch to smart wearable
You don’t need to rebuild ActiPatch from scratch — you add a smart layer.
Key additions:
Microcontroller (MCU):
Controls the PEMF driver and handles data logging
Low-power ARM-based chip (e.g., Cortex-M0/M4 class)
Bluetooth Low Energy (BLE) chip or system-on-chip:
Connects to a smartphone app
Offloads data to the phone (no need for onboard memory beyond buffer)
Allows firmware updates over the air
Sensors:
3-axis accelerometer (tiny, ultra-low power)
Temperature sensor
Optional: heart-rate or EDA later, depending on form factor
Power system:
Slightly larger battery or more efficient duty cycle
Power management IC to handle both therapy pulses and digital electronics
Form factor:
Keep the flexible patch concept, but with a small rigid “smart pod”:
The pod contains battery + electronics
The flexible loop/antenna still delivers the PEMF field
The goal: retain the feel of ActiPatch, but hide a tiny “Fitbit brain” inside it.
3. Software layer: companion app + cloud pipeline
Once the device can talk, you build the ecosystem:
On the smartphone (companion app):
Pairing & setup
User selects pain area (back, knee, neck, etc.)
Optional: enters condition (e.g., osteoarthritis, post-surgery, chronic lower back pain)
Session tracking
When ActiPatch is active
Session length, cumulative time
Simple adherence charts (“You used ActiPatch 5/7 days this week”)
Self-reported pain & outcomes
Pain score before/after session (0–10)
Sleep quality (simple sliders)
Activity tolerance (“Could you walk farther today?”)
Firmware updates
Push new PEMF patterns or modes over time
In the cloud:
Anonymized data collection
Usage patterns across thousands of users
Correlations between use, movement, self-reported pain
Condition-specific outcomes (e.g., knee OA vs lower back pain)
Foundations for AI
Train models on:
Which patterns of use correlate with best relief
Which body areas respond best
How adherence impacts outcomes
Early signs that someone is about to flare (e.g., decreased movement + increased use)
This becomes the “world’s largest dataset on real-world non-drug pain modulation” if executed at scale.
4. Patient experience: keep it stupid-simple
You don’t want to ruin ActiPatch’s biggest advantage: it’s easy.
So the smart version should feel like:
Stick it on
Press start
App just quietly tracks in the background
Optional engagement:
Short pain check-ins (like 10 seconds a day)
Nudges: “Using ActiPatch 2 more hours today often helps people with your condition”
The tech stays invisible; the benefits stay obvious.
5. Regulatory strategy: wellness mode first, medical grade later
To stay aligned with the FDA’s non-medical-grade data is exempt stance:
Phase 1: Wellness wearable
Market the smart ActiPatch as:
A wellness-focused, information-providing wearable
Tracking use, activity, and self-reported pain
Don’t claim AI diagnosis or clinical-grade monitoring
Use data for research, product improvement, and user insights
Phase 2: Real-world evidence & AI
Use accumulated data to:
Design better clinical trials
Inform 510(k) or other submissions
Develop predictive pain models
Potentially build “ActiPatch Clinical” SKUs with more formal medical claims
This lets you move fast now, while laying the groundwork for future medical-grade offerings.
6. How this ties directly into the “AI billionaire” narrative
Transforming ActiPatch into a smart wearable does more than just “collect data” — it unlocks the investor story:
From device to platform
ActiPatch isn’t just a patch; it’s a data node in a global bioelectric network.
From product to dataset
Each patch becomes a sensor in the wild, feeding models on non-drug pain relief.
From sale to subscription
The app can add:
AI-guided programs
Premium analytics
Personalized therapy plans
Paid upgrades
From microcap to AI-story
Now BIEL isn’t just “a medical device company.”
It becomes “the front line of an AI-powered bioelectronic pain modulation platform.”
That’s the kind of evolution that justifies massive valuation step-ups, especially when framed as a category-creating AI company.
What ActiPatch is today (baseline)
Device type: Over-the-counter wearable medical device for musculoskeletal pain
Mechanism: Pulsed shortwave / pulsed radiofrequency energy (a form of PEMF) modulating nerve activity and central sensitization
Usage model: Simple, non-sensory therapy — no user data, no connectivity, no analytics
That’s your “dumb but effective” hardware. Now let’s turn it into a smart, data-generating platform.
1. Decide what data the “smart ActiPatch” should collect
Start with low-friction, high-signal data — things you can get without burdening the user.
Core data types:
Usage data
On/off time
Session duration
Cumulative hours of use
Adherence patterns (e.g., daily, sporadic, overnight)
Location & context (not GPS at first, but body-context)
Which body area is being treated (back, knee, neck, etc.) chosen in the app
Therapy mode (e.g., standard, post-acute, chronic)
Basic motion & posture
Accelerometer to detect:
Activity levels (sedentary vs active)
Position changes (e.g., lying vs walking)
Potential correlation between movement and pain relief
Optional biosignals (phase two)
Skin temperature near the patch (inflammation proxy)
Skin conductance (stress/pain proxy)
Simple heart-rate via optical sensor (if placed where feasible)
This gives you a minimum viable dataset that can feed AI models later:
“When the device is used, how long, in what context, and what changes in activity occur over time?”
2. Hardware changes to ActiPatch: from passive patch to smart wearable
You don’t need to rebuild ActiPatch from scratch — you add a smart layer.
Key additions:
Microcontroller (MCU):
Controls the PEMF driver and handles data logging
Low-power ARM-based chip (e.g., Cortex-M0/M4 class)
Bluetooth Low Energy (BLE) chip or system-on-chip:
Connects to a smartphone app
Offloads data to the phone (no need for onboard memory beyond buffer)
Allows firmware updates over the air
Sensors:
3-axis accelerometer (tiny, ultra-low power)
Temperature sensor
Optional: heart-rate or EDA later, depending on form factor
Power system:
Slightly larger battery or more efficient duty cycle
Power management IC to handle both therapy pulses and digital electronics
Form factor:
Keep the flexible patch concept, but with a small rigid “smart pod”:
The pod contains battery + electronics
The flexible loop/antenna still delivers the PEMF field
The goal: retain the feel of ActiPatch, but hide a tiny “Fitbit brain” inside it.
3. Software layer: companion app + cloud pipeline
Once the device can talk, you build the ecosystem:
On the smartphone (companion app):
Pairing & setup
User selects pain area (back, knee, neck, etc.)
Optional: enters condition (e.g., osteoarthritis, post-surgery, chronic lower back pain)
Session tracking
When ActiPatch is active
Session length, cumulative time
Simple adherence charts (“You used ActiPatch 5/7 days this week”)
Self-reported pain & outcomes
Pain score before/after session (0–10)
Sleep quality (simple sliders)
Activity tolerance (“Could you walk farther today?”)
Firmware updates
Push new PEMF patterns or modes over time
In the cloud:
Anonymized data collection
Usage patterns across thousands of users
Correlations between use, movement, self-reported pain
Condition-specific outcomes (e.g., knee OA vs lower back pain)
Foundations for AI
Train models on:
Which patterns of use correlate with best relief
Which body areas respond best
How adherence impacts outcomes
Early signs that someone is about to flare (e.g., decreased movement + increased use)
This becomes the “world’s largest dataset on real-world non-drug pain modulation” if executed at scale.
4. Patient experience: keep it stupid-simple
You don’t want to ruin ActiPatch’s biggest advantage: it’s easy.
So the smart version should feel like:
Stick it on
Press start
App just quietly tracks in the background
Optional engagement:
Short pain check-ins (like 10 seconds a day)
Nudges: “Using ActiPatch 2 more hours today often helps people with your condition”
The tech stays invisible; the benefits stay obvious.
5. Regulatory strategy: wellness mode first, medical grade later
To stay aligned with the FDA’s non-medical-grade data is exempt stance:
Phase 1: Wellness wearable
Market the smart ActiPatch as:
A wellness-focused, information-providing wearable
Tracking use, activity, and self-reported pain
Don’t claim AI diagnosis or clinical-grade monitoring
Use data for research, product improvement, and user insights
Phase 2: Real-world evidence & AI
Use accumulated data to:
Design better clinical trials
Inform 510(k) or other submissions
Develop predictive pain models
Potentially build “ActiPatch Clinical” SKUs with more formal medical claims
This lets you move fast now, while laying the groundwork for future medical-grade offerings.
6. How this ties directly into the “AI billionaire” narrative
Transforming ActiPatch into a smart wearable does more than just “collect data” — it unlocks the investor story:
From device to platform
ActiPatch isn’t just a patch; it’s a data node in a global bioelectric network.
From product to dataset
Each patch becomes a sensor in the wild, feeding models on non-drug pain relief.
From sale to subscription
The app can add:
AI-guided programs
Premium analytics
Personalized therapy plans
Paid upgrades
From microcap to AI-story
Now BIEL isn’t just “a medical device company.”
It becomes “the front line of an AI-powered bioelectronic pain modulation platform.”
That’s the kind of evolution that justifies massive valuation step-ups, especially when framed as a category-creating AI company.
1
