Blue Button Web Server
This server serves as a data provider for sharing Medicare claims data with third parties. The server connects to MyMedicare.gov for authentication, and uses OAuth2 to confirm permission grants to external app developers. The data itself comes from a back end FHIR server (https://github.com/CMSgov/bluebutton-data-server), which in turn pulls data from the CMS Chronic Conditions Warehouse (https://www.ccwdata.org)
For more information on how to connect to the API implemented here, check out our developer documentation at https://cmsgov.github.io/bluebutton-developer-help/. Our most recent deployment is at https://sandbox.bluebutton.cms.gov, and you can also check out our Google Group at https://groups.google.com/forum/#!forum/developer-group-for-cms-blue-button-api for more details.
The information below outlines setting up the server for development or your own environment. For general information on deploying Django see https://docs.djangoproject.com/en/1.11/howto/deployment/.
These instructions provide a quick start for developers new to the project. Follow these steps on the command line.
# prepare your repository folder git clone https://github.com/CMSGov/bluebutton-web-server.git cd bluebutton-web-server # create the virtualenv python3 -m venv venv # Install any prerequisites (C headers, etc. This is OS specific) # Ubuntu example sudo apt-get install python3-dev libxml2-dev libxslt1-dev # install the requirements pip install --upgrade pip==9.0.1 pip install pip-tools pip install -r requirements/requirements.txt # prepare Django settings cp hhs_oauth_server/settings/local_sample.txt hhs_oauth_server/settings/local.py
Note that most settings can be overridden by environment variables. See custom environment variables section below. Please ensure to create and use your own keys and secrets. See https://docs.djangoproject.com/en/1.11/topics/settings/ for more information. Continue the installation by issuing the following commands:
python manage.py migrate python manage.py loaddata apps/accounts/fixtures/scopes_and_groups.json python manage.py createsuperuser python manage.py create_admin_groups python manage.py create_blue_button_scopes python manage.py setup_bluebutton python manage.py create_test_user_and_application
The next step is optional: If your backend HAPI FHIR server is configured to require x509
certificates to access it then you need to obtain that keypair and place those files in
certificate folder called
mkdir ../certstore (copy both x509 files, in PEM format, inside certstore)
If your backend FHIR server does not require certificate-based authorization then the previous step can be omitted.
Making calls to a back-end FHIR server requires that you set a series of variables before running tests or the server itself.
#Run the development server python manage.py runserver
Note you can find the path to your Python3 binary by typing
Instructions for running the development environment via
docker-compose can be found here
How to View the CSS/Styles Locally
To keep our CSS organized and consolidated across our applications, we use a dedicated Blue Button CSS Repo.
In order to be able to see the styles locally for this project, you'll just need to clone the Blue Button CSS Repo at the root of this project.
bluebutton-web-server, run the following commands (Bash):
git clone email@example.com:CMSgov/bluebutton-css.git
That sould be all you need to get the styles working. The instructions below will tell you how to work with or update the SCSS.
To get started making changes to the styles:
You'll need to make sure you have NodeJS installed. Click here to find out more about NodeJS. Once you have NodeJs installed, run:
Finally, make sure you have Gulp 4.0 installed:
npm i gulp@4
To export the CSS once, run:
To watch the SCSS files for changes, run:
Run the following:
You can run individual applications tests as well. See https://docs.djangoproject.com/en/1.11/topics/testing/overview/#running-tests for more information.
Using this Project
This project is free and open source software under the Apache2 license. You may add additional applications, authentication backends, and styles/themes are not subject to the Apache2 license.
In other words, you or your organization are not in any way prevented from build closed source applications on top of this tool. Applications that you create can be licensed in any way that suits you business or organizational needs. Any 3rd party applications are subject to the license in which they are distributed by their respective authors.
This project is free and open source software under the Apache 2 license. See LICENSE for more information.