community maintained fork of the original
JavaScript CSS Shell
Clone or download
Pull request Compare This branch is 1 commit ahead, 4344 commits behind nightscout:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin
lib
static
testing
tests
.bowerrc
.deployment
.gitignore
.travis.yml
Makefile
README.md
Vagrantfile
bower.json
database_configuration.json
deploy.sh
env.js
package.json
server.js
setup.sh

README.md

cgm-remote-monitor (a.k.a. NightScout)

Build Status Dependency Status Gitter chat

This acts as a web-based CGM (Continuous Glucose Montinor) to allow multiple caregivers to remotely view a patients glucose data in realtime. The server reads a MongoDB which is intended to be data from a physical CGM, where it sends new SGV (sensor glucose values) as the data becomes available. The data is then displayed graphically and blood glucose values are predicted 0.5 hours ahead using a autoregressive second order model. Alarms are generated for high and low values, which can be cleared by any watcher of the data.

Community maintained fork of the original cgm-remote-monitor.

Install

Requirements:

Clone this repo then install dependencies into the root of the project:

$ npm install

Vagrant install

Optionally, use Vagrant with the included Vagrantfile and setup.sh to install OS and node packages to a virtual machine.

host$ vagrant up
host$ vagrant ssh
vm$ setup.sh

The setup script will install OS packages then run npm install.

The Vagrant VM serves to your host machine only on 192.168.33.10, you can access the web interface on http://192.168.33.10:1337

Usage

The data being uploaded from the server to the client is from a MongoDB server such as mongolab. In order to access the database, the appropriate credentials need to be filled into the JSON file in the root directory. SGV data from the database is assumed to have the following fields: date, sgv. Once all that is ready, just host your web app on your service of choice.

Environment

You can use the default null database_configuration.json config if you set the following environment variables instead. (Hosting providers often make this easy, and this allows you to avoid editing anything.)

  • CUSTOMCONNSTR_mongo - the mongo connection string, corresponds to DB.url.
  • CUSTOMCONNSTR_mongo_collection - the mongo collection to use, corresponds to DB.collection.

Easy to emulate on the commandline:

echo 'CUSTOMCONNSTR_mongo="mongodb://sally:sallypass@mymongohost.com/db"' >> my.env
echo 'CUSTOMCONNSTR_mongo_collection="sallyCGMCollection"' >> my.env

From now on you can run using

$ env $(cat my.env) PORT=1337 node server.js

Your hosting provider probably has a way to set these through their GUI.

More questions?

Feel free to post an issue, but read the wiki first.

License

This is experimental software and NOT intended for treatment of any kind. It is provided under the MIT license, so you can do with it whatever you wish except hold me responsible if it does something you don't like.