201809 FHIR Storage and Analytics

Return to Fall 2018 Proposals

• Zulip Analytics stream

Previous tracks:

• 2018-05

Track Name

FHIR Storage & Analytics ([1])

Track Overview

With this track we want to put together people, which are interested in implementation and usage of FHIR persistence layer, implementing FHIR servers on top and analysing FHIR data.

We hope this group can produce useful feedback for FHIR community and potentially propose new aspects for standard - like SQL on FHIR or FHIRPath for databases.

Another goal is to collect solutions and best practices to store and query FHIR data, using popular databases.

Please fill out: TODO [TODO Track Registration Spreadsheet]

Submitting WG/Project/Implementer Group

We want to create S&A working group or FHIR Foundation Project.

Justification

Initial set of questions to be answered or discussed

• How we can organise our group (WG || FHIR Foundation Project || Just informal meetings)?
• How to store FHIR data?
• What is database schema design?
• SQL (as common query language) on FHIR
• FHIR data representation for storage
• FHIRPath subset for databases
• How to approach FHIR search?
• Best practices for popular databases (postgresq, spark, mongo, bigquery etc)?

Proposed Track Lead

Nikolai Ryzhikov

Participants

• Ryan Brush (Cerner)
• Patrik Sundberg (Google)
• Kenny Blanchette ?
• Nikolai Ryzhikov & Mike Lapshin (Health Samurai)
• Alexander Zautke ? (Firely)
• ADD YOURSELF!

Roles

• Database Provider: provides access to database with FHIR data
• Database User: design queries

Discussions

SQL on FHIR

Initial notes for creating a standard representation of FHIR that is directly usable in scalable SQL-based systems.

Original document by Ryan Brush - https://docs.google.com/document/d/1IPyI-4GYlF400vmZvrtjDYL6jauHdjeLfjGJMo6yWtA/edit#heading=h.ch8y6lqurlaj

FHIR data representation in database

JSON and other JSON like formats like yaml, edn, avro, protobuf are very popular in avantе-garde of programmers, some modern databases now could understad JSON as first-class data-structures, that’s why we think, good design for it is strictly required for FHIR adoption.

Original github - https://github.com/fhir-fuel/fhir-fuel.github.io/issues

FHIRPath subset for databases

It worth to discuss subset of FHIRPath, which is implementable in databases

Issue to discuss - https://github.com/fhir-fuel/fhir-fuel.github.io/issues/10

Scenarios

Scenario: Bulk Loader

Implement and demonstrate bulk loader script for your specific database.

• Provide Bulk Loader for your specific database to easily and efficiently load data from FHIR server thro Bulk API into db.
• Loader for Mitre Synthea (https://github.com/synthetichealth/synthea) - where source is file system as synthea generate.
• Loader for FHIR examples - zipped dir of resources and bundles in json

Discussion at https://github.com/fhir-fuel/fhir-storage-and-analytics-track/issues/6