Skip to content

Instantly share code, notes, and snippets.

@esperlu
esperlu / mysql2sqlite.sh
Created April 27, 2011 05:46
MySQL to Sqlite converter
#!/bin/sh
# Converts a mysqldump file into a Sqlite 3 compatible file. It also extracts the MySQL `KEY xxxxx` from the
# CREATE block and create them in separate commands _after_ all the INSERTs.
# Awk is choosen because it's fast and portable. You can use gawk, original awk or even the lightning fast mawk.
# The mysqldump file is traversed only once.
# Usage: $ ./mysql2sqlite mysqldump-opts db-name | sqlite3 database.sqlite
# Example: $ ./mysql2sqlite --no-data -u root -pMySecretPassWord myDbase | sqlite3 database.sqlite
@jmandel
jmandel / 0-getting-started.md
Last active November 27, 2019 16:20
Quick Start Guide for SMART on FHIR Servers: Growth Charts

Getting started implementing a SMART on FHIR server

This is a getting-started guide for SMART on FHIR server developers who want to support the SMART Growth Charts app. For background, SMART on FHRI is a plug-in app platform for health apps based on open standards.

To run SMART's open-source Growth Charts app against your own SMART on FHIR server, you'll need to:

  1. Expose clinical data using FHIR Patient and Observation resources
  2. Protect your clinical data via the SMART on FHIR Authorization protocols(based on OAuth2).

To get up and running as easily as possible, this Quick-start guide helps you through two scenarios: first, to run the app in debugging mode against an unprotected server, and second, to get the app running against an OAuth2-protected server.

Use cases
This document describes a way of granting an application access to data on a set of patients.
The application can request a copy of all pertinent (clinical) access to the patients in a
single download. Note: We expect that this data will be pretty large.
Authorizing Access
Access to the data is granted by using the SMART backend services spec
(url: http://docs.smarthealthit.org/authorization/backend-services/).