Difference between revisions of "Phonegap Healthcare Adapter Questions"
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Admon/obsolete}} | ||
| + | |||
[[Category: NexJ_Express]] | [[Category: NexJ_Express]] | ||
[[category: NexJ Express PhoneGap]] | [[category: NexJ Express PhoneGap]] | ||
| Line 4: | Line 6: | ||
'''''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 == | ||
Latest revision as of 19:35, 26 January 2014
This page may be obsolete.
It contains historical information.
It contains historical information.
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.
