This project provides the source for the SQL on FHIR Implementation Guide.
SQL on FHIR is a specification that defines a standard way to define portable, tabular projections of FHIR data.
The FHIR® standard is a great fit for RESTful and JSON-based systems, helping make healthcare data liquidity real. This spec aims to take FHIR usage a step further, making FHIR work well with familiar and efficient SQL engines and surrounding ecosystems.
We do this by creating simple, tabular views of the underlying FHIR data that are tailored to specific needs. Views are defined with FHIRPath expressions in a logical structure to specify things like column names and unnested items.
Check the existing implementations page or register your own (see the sql-on-fhir.js repository).
Check out the interactive playground.
Content as markdown is now found in input/pagecontent. Also see sushi-config.yaml for additional settings, including configuration for the menu.
This is a Sushi project and can use HL7 IG Publisher to build locally:
- Clone this repository
- Install dependencies:
npm install - Update the IG publisher:
npm run update:publisher - Build the IG:
npm run build:ig - View the IG:
npm run open:ig
Available npm scripts:
npm run update:publisher- Downloads the latest IG publishernpm run build:ig- Generates the IG oncenpm run build:ig:continuous- Generates the IG continuously (watches for changes)npm run serve:ig- Serves the built IG using http-servernpm run open:ig- Opens the built IG in your browser
-
Clone this respository
-
Run
./scripts/_updatePublisher.shto get the latest IG publisher -
Install
sushiif you don't have it already with:npm i fsh-sushi -
Run
./scripts/_genonce.shto generate the IG -
Run
open output/index.htmlto view the IG websiteInstructions for viewing the IG in a local
http-server...npm i http-server cd output http-server # Will launch the content in a new browser tab.
The JavaScript reference implementation, the shared JSON test suite and the test report site (including the interactive playground) live in a separate repository:
That repository documents how to run the test suite, build a test runner, publish a test report and register an implementation on the implementations page.