Difference between revisions of "Phonegap Healthcare Adapter Questions"
Cwdesautels (talk | contribs) |
|||
| Line 4: | Line 4: | ||
'''''NexJ Medical Peripheral Mobile Adapter''''' Will be designed to enable NexJ's Mobile Healthcare solutions to interact with Bluetooth peripherals. | '''''NexJ Medical Peripheral Mobile Adapter''''' Will be designed to enable NexJ's Mobile Healthcare solutions to interact with Bluetooth peripherals. | ||
| − | + | : ''{{Main|Mobile Medical Device Integration}}'' | |
== Project Scope == | == Project Scope == | ||
Revision as of 14:06, 24 August 2012
NexJ Medical Peripheral Mobile Adapter Will be designed to enable NexJ's Mobile Healthcare solutions to interact with Bluetooth peripherals.
- Main article: Mobile Medical Device Integration
Project Scope
- Where do the responsibilities of the adapter end? Confirm that it is an interface to provide data for the mobile solution.
- Correct. You will provide an API to query the measurement devices for data.
- The need for persistence is apparent; where will this responsibility lie?
- No need for persistence. Any set up information you need will be provided to the API when initializing.
- What is the adapter's relationship with Bluetooth pairing, if there are no assumptions the adapter is responsible for device pairing at any time?
- It is safe to assume the Bluetooth device is already paired. At a later phase it might be nice to pair from within the application but out of scope for now.
