Difference between revisions of "Phonegap Healthcare Adapter Design"
Cwdesautels (talk | contribs) (→Class Diagram) |
Cwdesautels (talk | contribs) (→Class Diagram) |
||
| Line 9: | Line 9: | ||
== Class Diagram == | == Class Diagram == | ||
[[File:NexjBluetooth.png|left]] | [[File:NexjBluetooth.png|left]] | ||
| + | === Classes === | ||
| + | ==== phonegapMedicalDeviceInterface ==== | ||
| + | * Interface to a medical device for use by the NexJ mobile health solution | ||
| + | * Implemented in Javascript | ||
| + | ==== medicalDevice ==== | ||
| + | * Representation of a medical device | ||
| + | * Delegates to a native medical device interface | ||
| + | * Implemented in Javascript | ||
| + | ==== nativeMedicalDeviceInterface ==== | ||
| + | * Private interface to physical medical devices | ||
| + | * Implemented in native code (Objective C on iOS, java on Android) | ||
| + | ==== bluetoothAdapter ==== | ||
| + | * Adapter to allow medical device objects to interact with communication libraries on the device | ||
| + | * In the future a Wifi adapter will also be needed to fulfill the same role of communication over another protocol | ||
| + | * Implemented in native code | ||
| + | ==== bloodPressureBluetoothAdapter ==== | ||
| + | * Adapter to allow medical device objects to interact with specific medical peripherals | ||
| + | * These will be needed for each type of medical peripheral | ||
| + | * Implemented in native code | ||
| + | ==== Native Bluetooth API ==== | ||
| + | * Libraries on the mobile devices SDK that allows programmable interaction with Bluetooth devices | ||
| + | ==== Blood Pressure Device ==== | ||
| + | * Physical medical device peripheral | ||
| + | === Flaws === | ||
| + | * Should we be concerned about managing the instances of ''medicalDevice'' or will the rest of the solution | ||
| + | * bloodPressureBluetoothAdapter should know about specific device communication without relying on any specific communication protocol, otherwise it will need be reimplemented per communication adapter(eg. BluetoothAdapter, WifiAdapter) | ||
Revision as of 11:22, 16 August 2012
NexJ Medical Peripheral Mobile Adapter Will be designed to enable NexJ's Mobile Healthcare solutions to interact with Bluetooth peripherals.
- Main article: Phonegap Healthcare Adapter
Contents
Class Diagram
Classes
phonegapMedicalDeviceInterface
- Interface to a medical device for use by the NexJ mobile health solution
- Implemented in Javascript
medicalDevice
- Representation of a medical device
- Delegates to a native medical device interface
- Implemented in Javascript
nativeMedicalDeviceInterface
- Private interface to physical medical devices
- Implemented in native code (Objective C on iOS, java on Android)
bluetoothAdapter
- Adapter to allow medical device objects to interact with communication libraries on the device
- In the future a Wifi adapter will also be needed to fulfill the same role of communication over another protocol
- Implemented in native code
bloodPressureBluetoothAdapter
- Adapter to allow medical device objects to interact with specific medical peripherals
- These will be needed for each type of medical peripheral
- Implemented in native code
Native Bluetooth API
- Libraries on the mobile devices SDK that allows programmable interaction with Bluetooth devices
Blood Pressure Device
- Physical medical device peripheral
Flaws
- Should we be concerned about managing the instances of medicalDevice or will the rest of the solution
- bloodPressureBluetoothAdapter should know about specific device communication without relying on any specific communication protocol, otherwise it will need be reimplemented per communication adapter(eg. BluetoothAdapter, WifiAdapter)
