Bluetooth Transport Support for SDPi: Implementation Guidance

Aperta
  • Qualcosa non va?
#495 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@DarenShamoun ci sta già lavorando.

Dal 21/11/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Comment General Transport Capability

NOTE: Issue created on behalf of BD/Daren Shamoun [email protected]

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

  1. 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?

  2. 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?

  3. 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?

  4. 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?

  5. Resources and Documentation: -Where can we find: -Specifications for alternative transport layers -Reference implementations or guidance documents.

Lingua principale
Kotlin
Stelle
17
Fork
4
Merge medio
4h 52m
PR unite (30g)
6

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di IHE/DEV.SDPi

Tutte le issue di IHE/DEV.SDPi

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.