HTTPS hg clone plugin library SSH hg clone plugin library

Transcription

1 Contents Introduction... 2 Native Android Library... 2 Development Tools... 2 Downloading the Application... 3 Building the Application... 3 A&D... 4 Polytel... 6 Bluetooth Commands... 8 Fitbit and Withings... 9 MyOscar... 12

2 Introduction This project is made up of three sub projects. The first is a PhoneGap library which was created to communicate with Bluetooth enabled medical devices, specifically A&D's weight scale and blood pressure monitor, and Polytel's glucometer accessory. The library is available here: bluetooth adapters Although this library was written in Java, it was not compatible with a native Android application. The Bluetooth library was modified to allow it to be used in a native Android application. More information on the modified version of the Bluetooth library is available in the next section. The final part of the project is the demo Android application. This application uses the native Android version of the Bluetooth library to demo Bluetooth communications with medical devices. It also contains demos for communicating with the following web service APIs: Withings Fitbit MyOscar For more information about the project, including development information, see: Native Android Library In order to use the mobile Bluetooth adapters library in a native Android environment, it needed to be modified slightly. The native Android version of the device plug in library removes the dependency for PhoneGap and Cordova, allowing you to use the library from native Android code. The source code is available here: plugin library To download it using mercurial execute either of the following commands: HTTPS hg clone plugin library SSH hg clone ssh://hg@bitbucket.org/dsegna/device plugin library Additionally, a download of the source code, is available on the downloads page: plugin library/downloads The library exported as a jar is also available on the downloads page. The majority of this library is not meant to be directly edited. It builds its source files using the PhoneGap/Cordova mobile Bluetooth adapters library. For more information on how to edit or build this library, read the README.txt included with the library. Development Tools

3 This project was developed using the Android Developer Tools, available for download here : Included are the Eclipse IDE with ADT plug in, the SDK Manager which allows easy downloading of different SDK libraries and packages, and the AVD Manager for managing virtual Android devices. If you are unfamiliar with these development tools, the following tutorials are available: Eclipse with ADT Plug in Android SDK Manager manager.html AVD Manager manager.html Downloading the Application The Android application is available for download here: health native/ To download it using mercurial execute either of the following commands: HTTPS hg clone health native/ SSH hg clone ssh://hg@cdot.senecacollege.ca/hg/seneca health native/ Building the Application The application is built using Android SDK version 19 (Android 4.4). This can be seen in the AndroidManifest.xml file in the application's root folder. <uses sdk android:minsdkversion="5" android:targetsdkversion="19" /> Note that the minimum SDK version is 5. This means the application will be backwards compatible up to Android 2.0 To build the project, you must have downloaded and installed the SDK platform for Android API version 19 from the SDK Manager.

4 A&D Receiving measurements from the A&D Bluetooth weight scale and blood pressure monitor is done using the MedicalDevicePlugin class. To use the MedicalDevicePlugin class, you must create an activity that extends CordovaActivity and implements MedicalDeviceActivity like so: public class MyActivity extends CordovaActivity implements MedicalDeviceActivity{ You will also need a CallbackContext object along with the MedicalDevicePlugin. To initialize them you must pass the Activity that is creating them. MedicalDevicePlugin plugin = new MedicalDevicePlugin(this); CallbackContext callbackcontext = new CallbackContext(this); If the medical device has not been paired with the phone, the phone must be set to be discoverable prior to connecting to the medical device by doing the following: plugin.execute("discoverable", params, callbackcontext); Once the phone has been set to discoverable, continue with the measurement process. When the device connects to the phone to send a measurement, it will require the PIN that comes with the device. After entering the PIN the measurement will be received, and the medical device and phone will be paired. You can now begin receiving measurements through Bluetooth. To begin listening for a Bluetooth connection: JSONObject param = new JSONObject(); param.put("brand", "AND"); param.put("num", 0); params.put(param); plugin.execute("connect", params, callbackcontext); To stop listening for a Bluetooth connection: JSONObject brand = new JSONObject(); brand.put("brand", "AND"); params.put(brand); plugin.execute("disconnect", params, callbackcontext); When a Bluetooth event occurs, the MedicalDevicePlugin will call the Activity's returnresult(pluginresult result) function which is implemented from the MedicalDeviceActivity interface. The results can be retrieved by calling:

5 result.getmessage() Depending on the command executed this may be true, false, or a JSON formatted string containing the measurement information that was received. This JSON string can be used the create an ANDWeightResult or ANDBloodPressureResult object by calling: MeasurementResult.ResultFactory(result.getMessage()) If you would rather work directly with the received JSON, they look like this: A&D Weight Result: { system : lb time : weight : 66.0 type : weight serial : A&D Blood Pressure Result: { mean : 86 time : pulse : 85 type : blood pressure diastolic : 78 systolic : 94 serial :

6 Polytel Receiving measurements from the Polytel Glucometer Bluetooth Accessory is done using the MedicalDevicePlugin class. To use the MedicalDevicePlugin class, you must create an activity that extends CordovaActivity and implements MedicalDeviceActivity like so: public class MyActivity extends CordovaActivity implements MedicalDeviceActivity{ You will also need a CallbackContext object along with the MedicalDevicePlugin. To initialize them you must pass the Activity that is creating them. MedicalDevicePlugin plugin = new MedicalDevice Plugin(this); CallbackContext callbackcontext = new CallbackContext(this); If the medical device has not been paired with the phone, the phone must be set to be discoverable prior to connecting to the medical device by doing the following: plugin.execute("discoverable", params, callbackcontext); Once the phone has been set to discoverable, continue with the measurement process. When the device connects to the phone to send a measurement, it will require the PIN that comes with the device. After entering the PIN the measurement will be received, and the medical device and phone will be paired. You can now begin receiving measurements through Bluetooth. To begin listening for a Bluetooth connection: JSONObject param = new JSONObject(); param.put("brand", "Polytel"); param.put("num", 0); params.put(param); plugin.execute("connect", params, callbackcontext); To stop listening for a Bluetooth connection: JSONObject brand = new JSONObject(); param.put("brand", "Polytel"); params.put(brand); plugin.execute("disconnect", params, callbackcontext); When a Bluetooth event occurs, the MedicalDevicePlugin will call the Activity's returnresult(pluginresult result) function which is implemented from the MedicalDeviceActivity interface. The results can be retrieved by calling:

7 result.getmessage() Depending on the command executed this may be true, false, or a JSON formatted string containing the measurement information that was received. This JSON string can be used the create a PolytelGlucoseResult by calling: MeasurementResult.ResultFactory(result.getMessage()) If you would rather work directly with the received JSON, it looks like this: { type : blood glucose brand : Polytel meter : metername time : reading: 4.3 system : mmol/l serial : serialnumber battery status(%): 75.0

8 Bluetooth Commands You can use the MedicalDevicePlugin class to execute various Bluetooth commands. Enable Bluetooth: plugin.execute("enable", params, callbackcontext); Disable Bluetooth: plugin.execute("disable", params, callbackcontext); Set phone to discoverable: plugin.execute("discoverable", params, callbackcontext);

9 Fitbit and Withings Before attempting to connect with Fitbit or Withings, you must add your Api key and secret to the apiinfo.json file in the assets folder. If you don't have your Api key and secret you may get them here: Fitbit Withings After adding your Api key and secret, your apiinfo.json should look something like this: { "fitbitapi": { "apikey": "applicationkey", "apisecret": " applicationsecret", "withingsapi": { "apikey": " applicationkey", "apisecret": " applicationsecret" The Fitbit and Withings Api Wrappers will read this file when constructed, using the FileHelper class. Before creating an Api Wrapper, it is necessary to call FileHelper.initAssetManager(getAssets()) from any Activity. This only needs to be done once, so it is recommended to call this during the creation of your home activity. The next step is to have the user authenticate your app to access their personal data. This will require internet access, so it is important to check for network availability before continuing. This can be done like so: if(networkhelper.networkavailable(this)){ //network is available else{ //no network available Both Fitbit and Withings use the OAuth authentication process for this. This requires the user be sent to the specific Api's webpage, where they will sign in with their Fitbit or Withings account. The initialize() function will handle this process. It must be supplied with the Activity calling it, a WebView, and a View like so: initialize(this, webview, mainview);

10 If the Api Wrapper requires the user to login, it will switch the visible view to webview. Once the user is done authenticating the app, it will return visibility to mainview and hide webview. The Api Wrapper will save the user's authentication information in local storage so that the user does not need to sign in every time the app is run. If the user does not delete app data or change their Fitbit or Withings account, they will only be required to login the first time the app is run. With authentication complete, you may now begin accessing the user's data. Due to constraints on data retrieval, specifically Fitbit's lack of support for time range data retrieval, only weight data syncing was implemented for both Apis. Fitbit also limits data retrieval to 30 days in the past, so this should be considering when retrieving data from a user's Fitbit account. The WithingsApiWrapper however also allows blood pressure data syncing, and is not limited to 30 days. To get this data you can call: syncweight(calendar lastupdate) syncbloodpressure(calendar lastupdate) where lastupdate is the date to sync to. This will return an array of JSON objects that can be used to construct a MeasurementResult, specifically FitbitWeightResult, WithingsWeightResult, and WithingsBPResult. Since Android does not allow network calls on the UI thread, these calls need to be done asynchronously. Using Android's AsyncTask is the easiest way to accomplish this. For example: private class getweight extends AsyncTask<Calendar, Void, Boolean>{ ArrayList<JSONObject> protected Boolean doinbackground(calendar... params) { try { results = fitbit.syncweight(params[0]); catch (JSONException e) { return false; return protected void onpostexecute(boolean result) { if(result){ if(results.size()==0) //No new measurements else{ //Do something with the results else { //An error occurred while syncing with Fitbit

11 new getweight().execute(lastupdate); Although you have previously ensured network availability, it is possible that the phone has lost network access since it was last checked. Therefore you should check for network availability before making any data retrieval calls every time. Final Note: Although Fitbit does not support time range data retrieval, it does allow single date retrieval. Implementation of this is available in the FitbitApiWrapper class.

12 MyOscar Before attempting to connect with MyOscar, you must add the MyOscar Api endpoints to the MyOscarEndpoints.json file in the assets folder. These can be found in your MyOscar server's WSDL file. After adding the Api endpoints your MyOscarEndpoints.json should look something like this: { "AccountWsUrl": " "LoginWsUrl": " "MedicalDataWsUrl": " "MessageWsUrl": " "RemoteComponentWsUrl": " "ReportsWsUrl": " "SurveyWsUrl": " "SystemInfoWsUrl": " The MyOscar wrapper will read this file when constructed, using the FileHelper class. Before creating an Api Wrapper, it is necessary to call FileHelper.initAssetManager(getAssets()) from any Activity. This only needs to be done once, so it is recommended to call this during the creation of your home activity. The next step is to have the user authenticate your app to access their personal data. This will require internet access, so it is important to check for network availability before continuing. This can be done like so: if(networkhelper.networkavailable(this)){ //network is available else{ //no network available

13 You will need to have the user enter their MyOscar username and password so they can be used to call initialize(), which takes the Activity calling it, a username, and a password like so: initialize(this, username, password); Since Android does not allow network calls on the UI thread, this call needs to be done asynchronously. Using Android's AsyncTask is the easiest way to accomplish this. For example: private class MyOscarLogin extends AsyncTask<String, Void, protected Boolean doinbackground(string... params) { try { myoscar.initialize(cxt, params[0], params[1]); return true; catch (Exception e) { return protected void onpostexecute(boolean result) { if(result) //login was successful else //Failed to log in to MyOscar String [] params = {"username", "password"; new MyOscarLogin().execute(params); The MyOscarWrapper will save the user's authentication information in local storage so that the user does not need to sign in every time the app is run. However, it has been observed that MyOscar authentication credentials will expire after approximately hours. With authentication complete, you may now begin uploading data to MyOscar. The following functions are available for uploading data to MyOscar: addbloodpressuredata(int systolic, int diastolic, int heartrate, boolean onmeds, Calendar date) addglucosedata(float reading, GlucoseUnit unit, String details, Calendar date) addglucosea1cdata(int glucose, String details, Calendar date) addheightweightdata(string height, HeightUnit hunit, String weight, WeightUnit wunit, Calendar date) You may also use the following function if you require more control over the data you are transferring: addmedicaldata(medicaldatatransfer transfer) This requires you to be familiar with how MyOscar formats it's medical data. You can learn more about this here: data/

14 Additionally, the MeasurementResult class provides access to an uploadtomyoscar() function. Any of the classes which have been implemented that extend MeasurementResult can simply call uploadtomyoscar() to upload the data they contain. Like initialize(), all data upload calls must be executed asynchronously, and network availability should be ensured prior to execution.