Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

 SDK stands for software development kit or devkit for short.

It’s a set of software tools and programs used by developers to create applications for specific platforms. SDK tools will include a range of things, including libraries, documentation, code samples, processes, and guides that developers can use and integrate into their own apps. SDKs are designed to be used for specific platforms or programming languages.

 

Purpose of Document

 The purpose of this documentation is to provide an overview of the SDK, its features, and how to integrate it into your application.

Purpose of SDK

 The purpose of SDK is to avoid reusing code so that the development team can concentrate on creative work. SDK provides all of the necessary code that a user will need to build an application that uses API.

Getting Started:

To begin using our SDK, you will need to have an active account with us. Once you have an account, you can access the SDK documentation and download the SDK from our website.

The EXI SDK

The EXI SDK is an exercise prescription SDK that delivers personalized exercises that are clinically validated and digitally delivered for people with or at risk of chronic conditions. It will deal with approximately 23 chronic conditions.

SDK Features

 The SDK provides the following features:

  1. Health Condition Assessment: The SDK assesses the user's health condition based on their medical history and health data, including age, gender, weight, height, and medical conditions.

  2. Physical Activity Recommendations and extend prescription: Based on the user's health condition assessment, the SDK recommends a set of physical activities that are safe and appropriate for the user. The activities are categorized based on their type, intensity level, and duration.

  3. Customization: The SDK can be customized to meet the specific needs of your application, including branding, user interface, and language support.

Integration Requirements

 To integrate the SDK into your application, you need the following:

  1. Access to the SDK: You can obtain access to the SDK by contacting the provider of the SDK.

  2. Development Environment: The SDK supports multiple programming languages, including Kotlin and Swift. You should have a development environment that supports the language of your choice.

  3. API Key: You need an API key to authenticate your application with the SDK. The API key is provided by the SDK provider. To check the steps to get access to API key and JWS Token go to Setup Guide Page.

SDK Overview

 EXI provides a client-side SDK for Android and iOS development.

EXI provides a convenient collection of objects, methods, and events to connect your client-side application to Conversations.

For the most up-to-date installation methods, version history, and documentation, please check out:

Integration Steps

 The following steps describe how to integrate the SDK into your application:

Step 1: Obtain Access to the SDK

Contact the SDK provider to obtain access to the SDK. The provider will provide you with the necessary information and documentation to use the SDK.

Step 2: Choose a Programming Language

Choose a programming language that is supported by the SDK and set up your development environment.

Step 3: Obtain an API Key

Obtain an API key from the SDK provider. The API key is used to authenticate your application with the SDK.

Step 4: Add the SDK to Your Project

Add the SDK to your project by including the SDK library in your project's dependencies.

Step 5: Initialize the SDK

Initialize the SDK by passing the Context, API key, and enableMockResponse(optional) to the SDK constructor. When enableMockResponse is enabled only a sample hardcoded response is returned by the SDK, this will be helpful during the development when in offline mode.

Step 6: Set JWS Token

Set the JWS token which is used to authorize users of the SDK and also identify each user of the SDK.

Step 7: Assess the User's Health Condition

Use the SDK's health condition assessment feature to assess the user's health condition based on their medical history and health data.

Step 8: Get Physical Activity Recommendations and prescription.

Use the SDK's physical activity recommendation feature to get a list of physical activities that are safe and appropriate for the user along with prescriptions letting users know about durations to perform activities.

 Step 9: Log Activity

Use the SDK's Log Activity feature to track the user's physical activity.

Step 10: Get Prescription Progress

Use the SDK's Prescription progress to track the user's physical activity.

  

Conclusion

The SDK provides a solution for e-prescribing physical activities based on a user's health condition. It assesses the user's health condition, recommends physical activities, integrates with wearable devices, and can be customized to meet the specific needs of your application. Follow the integration steps to integrate the SDK into your application and provide personalized physical activity recommendations to your users.

  • No labels