Load Firely Server data in Python using dltHub

Build a Firely Server-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Firely Server data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source def firely_server_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:4080/", "auth": { "type": "bearer", "token": access_token, } }, "resources": [ "Observation", "Patient?_has:Observation:subject:_id=1`" ], } [...] yield from rest_api_resources(config) def get_data() -> None: # Connect to destination pipeline = dlt.pipeline( pipeline_name='firely_server_pipeline', destination='duckdb', dataset_name='firely_server_data', ) # Load the data load_info = pipeline.run(firely_server_source()) print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from firely_server’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Patient Endpoints: Endpoints related to patient resources, allowing retrieval and manipulation of patient data.

    • /Patient/1: Access a specific patient by their ID.
    • /Patient?_id=1: Query to find a patient by their ID.
    • /Patient?_revinclude=Observation:subject: Retrieve patients with included observations related to them.
    • /Patient?_has:Observation:subject:_id=1: Find patients that have a specific observation as a subject.
  • Observation Endpoints: Endpoints related to observation resources, enabling access to various observation data.

    • /Observation?_id=1: Access a specific observation by its ID.
    • /Observation?_include=Observation:subject: Retrieve observations with included subjects.
    • /Observation?subject:Patient._id=1: Query for observations related to a specific patient.
    • /Observation/1: Access a specific observation by its ID directly.
  • Metadata Endpoint: Provides information about the server and the FHIR implementation.

    • /metadata: Access metadata related to the FHIR server, including supported resources and operations.

You will then debug the Firely Server pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡

Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install "dlt[workspace]"

    Initialize a dlt pipeline with Firely Server support.

    dlt init dlthub:firely_server duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Firely Server API, as specified in @firely_server-docs.yaml Start with endpoints Observation and Patient?_has:Observation:subject:_id=1` and skip incremental loading for now. Place the code in firely_server_pipeline.py and name the pipeline firely_server_pipeline. If the file exists, use it as a starting point. Do not add or modify any other files. Use @dlt rest api as a tutorial. After adding the endpoints, allow the user to run the pipeline with python firely_server_pipeline.py and await further instructions.
  3. 🔒 Set up credentials

    Use Firely Auth as your SMART on FHIR optimized authorization service, and for more information on implementation, visit the Getting started with Firely Auth guide.

    To get the appropriate API keys, please visit the original source at https://docs.fire.ly/projects/Firely-Server/en/6.0.0/reference/reference.html. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python firely_server_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

    Pipeline firely_server load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset firely_server_data The duckdb destination used duckdb:/firely_server.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline firely_server_pipeline show
  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt data = dlt.pipeline("firely_server_pipeline").dataset() # get "Observation" table as Pandas frame data."Observation".df().head()

Extra resources:

Next steps