All Projects → simpledotorg → Simple Android

simpledotorg / Simple Android

Licence: mit
An Android app for recording hypertension-related data.

Programming Languages

kotlin
9241 projects

Projects that are alternatives of or similar to Simple Android

Mdapp
Useful and intuitive app for doctors and other health care workers in Norway
Stars: ✭ 15 (-90.57%)
Mutual labels:  healthcare
Hapi Fhir
🔥 HAPI FHIR - Java API for HL7 FHIR Clients and Servers
Stars: ✭ 1,197 (+652.83%)
Mutual labels:  healthcare
2019 Ncov
Use Google Maps Timeline data to compare with COVID-19 patient history location.
Stars: ✭ 116 (-27.04%)
Mutual labels:  healthcare
Openmrs Core
OpenMRS API and web application code
Stars: ✭ 979 (+515.72%)
Mutual labels:  healthcare
Mri Analysis Pytorch
MRI analysis using PyTorch and MedicalTorch
Stars: ✭ 55 (-65.41%)
Mutual labels:  healthcare
Dicom Server
OSS Implementation of DICOMweb standard
Stars: ✭ 101 (-36.48%)
Mutual labels:  healthcare
Zato
ESB, SOA, REST, APIs and Cloud Integrations in Python
Stars: ✭ 889 (+459.12%)
Mutual labels:  healthcare
Medcat
Medical Concept Annotation Tool
Stars: ✭ 133 (-16.35%)
Mutual labels:  healthcare
Fhir.resources
FHIR Resources https://www.hl7.org/fhir/resourcelist.html
Stars: ✭ 73 (-54.09%)
Mutual labels:  healthcare
Sytora
A sophisticated smart symptom search engine
Stars: ✭ 111 (-30.19%)
Mutual labels:  healthcare
Hcc Python
An implementation of the HCC Risk Adjustment Algorithm in Python
Stars: ✭ 47 (-70.44%)
Mutual labels:  healthcare
Erpnext
Free and Open Source Enterprise Resource Planning (ERP)
Stars: ✭ 10,220 (+6327.67%)
Mutual labels:  healthcare
Mne Cpp
MNE-CPP: A Framework for Electrophysiology
Stars: ✭ 104 (-34.59%)
Mutual labels:  healthcare
Openhospital Core
Open Hospital Core library
Stars: ✭ 31 (-80.5%)
Mutual labels:  healthcare
Openemr
The most popular open source electronic health records and medical practice management solution.
Stars: ✭ 1,762 (+1008.18%)
Mutual labels:  healthcare
Symptom Disease
Finds out symptoms similar to a given symptom, from a symptom-disease data set.
Stars: ✭ 24 (-84.91%)
Mutual labels:  healthcare
Ehr
The code repository for the prototypes included in the eBook "Inspired EHRs - Designing for Clinicians" (inspiredEHRs.gov). The code of the prototypes is made available under the Apache 2.0 open source license. This license agreement allows anyone to freely use the code and ideas presented in this book, subject to the conditions listed at http://opensource.org/licenses/Apache-2.0.
Stars: ✭ 83 (-47.8%)
Mutual labels:  healthcare
Survival Analysis Using Deep Learning
This repository contains morden baysian statistics and deep learning based research articles , software for survival analysis
Stars: ✭ 139 (-12.58%)
Mutual labels:  healthcare
Fhir Works On Aws Deployment
A serverless implementation of the FHIR standard that enables users to focus more on their business needs/uniqueness rather than the FHIR specification
Stars: ✭ 131 (-17.61%)
Mutual labels:  healthcare
All In One
👔 Health care application for reminding health-todo lists and making healthy habits every day.
Stars: ✭ 109 (-31.45%)
Mutual labels:  healthcare

Build Status pullreminders

Simple

An Android app for recording blood pressure measurements.

Pre-requisites

The application currently requires JDK 1.8 to build. If you already have JDK 1.8 installed, skip this step.

Check if the right JDK is already available

Run the command java -version. If you have the right version of the JDK installed, you should see something like:

openjdk version "1.8.0_232"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.232-b09, mixed mode)

If this command has an error, or shows a different version, you can follow the instructions below to install the JDK.

Install the JDK

We recommend using jEnv to manage your JDK installations. Here are instructions to setup a working JDK 1.8 installation (macOS only):

  1. Setup up Homebrew.

  2. Install jEnv using Homebrew.

brew install jenv
  1. Add the following lines to your shell configuration file (~/.bash_profile if you're using bash, or ~/.zshrc if you're using zsh).
export PATH="$HOME/.jenv/bin:$PATH"
eval "$(jenv init -)"
  1. Once this is done, you'll need to restart the terminal or reload the configuration file in order for the jenv command to be recognised.
source <path to shell configuration file>
  1. Install the JDK using Homebrew.
brew tap AdoptOpenJDK/openjdk
brew cask install adoptopenjdk8
  1. Add the installed JDK to jEnv
jenv add /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home
  1. Run the command jenv versions. You should see something like:
  system
* 1.8
  1.8.0.222

How to build

Clone the project using git.

Run the following command in a terminal.

$ git clone [email protected]:simpledotorg/simple-android.git

Install Android Studio

Download and install Android Studio from their website.

Import the project into Android Studio.

When Android Studio starts up, it will prompt you to create a new project or import an existing project. Select the option to import an existing project, navigate to the simple-android directory you cloned earlier, and select it.

When building for the first time, gradle will download all dependencies so it'll take a few minutes to complete. Subsequent builds will be faster.

Running locally

The Simple App can be run locally on an Android emulator using Android Studio. To do this,

Install the NDK library

The NDK library is currently required by the project to enable an SQLite extension. To install it:

  • Open the SDK Manager through Tools -> SDK Manager
  • Select Appearance & Behavior -> System Settings -> Android SDK in the left sidebar
  • Select the SDK Tools tab in the main window
  • Activate NDK (Side by Side) and click Apply

NDK will now be installed.

Create a Run/Debug configuration

  • Open the Run/Debug configurations window through Run -> Edit Configurations (ref)
  • Create a new configuration using the Android App template
  • Set the module to app, and finish creating the configuration

Create a virtual device

  • Create an Android Virtual Device (AVD) using the AVD Manager, usually found in Tools -> AVD Manager. (ref)
  • Select a device and operating system
  • Note: You will have to download one of the available OS options the first time you create an AVD

Set the right build variant

  • Open the Build Variants window through View -> Tool Windows -> Build Variants, or clicking the item in the lower left corner of the main window
  • Set the Build Variant of the app module to qaDebug

Run the app

  • Click "Run", either through Run -> Run, or the green play button in the top toolbar.

Code styles

The code styles which the project uses have been exported as an IntelliJ code style XML file and are saved as quality/code-style.xml. To import them into Android Studio,

  1. Open the Android Studio preferences page, and navigate to Editor -> Code Style.
  2. Click on the gear/settings button next to the "Scheme" label.
  3. In the drop-down menu, select "Import scheme".
  4. In the file picker, navigate to <project>/quality/code-style.xml.
  5. Import the Simple scheme into the IDE and set it as the project code style.

Tooling

An Android Studio plugin that provides some quality of life improvements like live templates can be found HERE.

Building an APK with a different build variant

There are currently 2 ways to build an app pointing to different environments:

  1. Changing the qa API URL in gradle.properties file to point to the environment you want. These builds will be debuggable and require us to clone the project and build it using Android Studio. [Warning: These changes should not be commited back to master branch]
  2. Use Bitrise workflows to build APKs of different build variants. These builds will not be debuggable, unless for build-debuggable-sandbox-apk.

Build and deploy Simple Server

Simple Server is in a separate repository, and you should follow the instructions there.

Resources

Check out the following documents for more information.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].