Bluetooth Transport Support for SDPi: Implementation Guidance
@DarenShamoun is already working on this.
Since Nov 21, 2025.
- Dominant language
- Kotlin
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
NOTE: Issue created on behalf of BD/Daren Shamoun Daren.Shamoun@bd.com
Summary
We are researching Bluetooth connectivity (BLE, Classic, or other profiles) for bidirectional medical device communication within the SDPi framework. We seek guidance on technical feasibility and recommended implementation approaches.
Context
We are evaluating implementation approaches for bidirectional Bluetooth medical device connectivity and seeking guidance on alignment with SDPi architecture and standards.
Questions
-
Alternative Transport Specifications: -Are there SDPi transport specifications being developed for non-IP protocols? If so: -Do any support Bluetooth connectivity (BLE, Classic, or dual-mode)? -What are the timelines for these specifications?
-
Bluetooth Use Cases in SDPi: -What are the current or planned use cases for Bluetooth in SDPi networks? -Are there technical or architectural constraints limiting Bluetooth to specific device categories or profiles? -Can Bluetooth support bidirectional communication for acute care medical device connectivity?
-
Gateway Architecture: -For integrating Bluetooth devices into SDPi networks, is a gateway architecture the recommended approach? -Which gateway actor type is appropriate (SOMDS Sensor Gateway, SOMDS FHIR Gateway, or other)? -Are there reference implementations or examples available?
-
Security Requirements for Bluetooth: -What security requirements must be satisfied for Bluetooth transport within SDPi? -Can you clarify security profiling requirements for non-IP transports? -Are there existing security profiles for alternative transports?
-
Resources and Documentation: -Where can we find: -Specifications for alternative transport layers -Reference implementations or guidance documents.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.