Skip to content
Firemetrics

Platform · All data. One foundation.

One data foundation for every source. Open to any app and AI. Tools for every day.

The Firemetrics platform is a FHIR-native, fully transactional Clinical Data Repository. Use it with your own tools, connect any application or AI to it, or work with ours.

Book a technical deep-diveRead the docs
  1. Tools
  2. Open access
  3. Data foundation
  • EHR
  • LIS
  • RIS
  • PACS
  • ERP

First the foundation. Then the AI.

Hospitals are missing the middle layer

Gartner's three-layer model has been standard in other industries for decades. In hospitals the middle layer is missing almost everywhere, so innovations fail at the connection, not at the technology.

With the layer in place, both sides are decoupled. The EHR can be replaced without the applications noticing, and the layer keeps running as a fallback.

  1. 03

    Systems of innovation

    Everyone wants them

    Discharge letters, radiology AI, OR analytics, discharge management, scoring and decision support. Replaced every two to three years.

  2. 02

    Systems of differentiation

    Missing in most hospitals today

    A shared, FHIR-native data layer: the Clinical Data Repository. Barely visible, but without it no innovation lasts in the hospital.

  3. 01

    Systems of record

    Everyone has them

    EHR, LIS, PACS, ERP. This is where data is created, often in many separate installations.

Architecture

One engine. All systems.

Every source system is connected once. The core engine stores everything as relational FHIR with terminologies built in. Every application, dashboard and AI tool reads from the same place through standard interfaces.

Terminology Services

  • LOINC
  • SNOMED
  • ICD-10
  • RadLex
  • OPS
  • Alpha
  • ATC

  • FHIR Client

    REST
    Fuego
    SQL

  • Dashboards

    SQL

  • Data Science

    SQL

  • 3rd party applications

    REST
    SQL

  • Agentic AI / FLAME

    SQL + MCP

  • Research Portal

    REST
    Structured Query Translator
    SQL | CQL

Firemetrics Core Engine

  • Relational FHIR
  • DICOM
  • Teable
  • Tasks
  • ...

  • Automated Import

    EMRLISPISGIMSERPRIS

  • PACS

  • CSV

Core capabilities

Six capabilities. One system.

  • Relational FHIR storage

    Fully transactional CRUD with SQL-compatible querying.

  • FHIR facade

    Full FHIR API functionality, including SMART on FHIR.

  • Real-time analytics

    SQL and Grafana dashboards on live data.

  • DICOM integration

    Ingest, store and link imaging data with FHIR.

  • AI-ready

    Full-text search and MCP endpoints for agentic AI workflows.

  • Natural language

    Query clinical data in plain language with FLAME.

Layer 1 in practice

Your IT queries it directly

No separate data warehouse, no nightly batch. Your BI and data teams work with plain SQL on live data, and every dashboard updates in real time.

SQL
-- Patients with heart failure admitted as inpatients this monthSELECT count(DISTINCT es._reference_id)FROM encounter eJOIN encounter_subject es  ON es._resource = e._id  AND es._reference_type = 'Patient'JOIN encounter_period ep  ON ep._resource = e._idJOIN encounter_class ec  ON ec._resource = e._idJOIN condition_subject cs  ON cs._reference_id = es._reference_id  AND cs._reference_type = 'Patient'JOIN condition_code cc  ON cc._resource = cs._resourceJOIN condition_code_coding ccc  ON ccc._parent = cc._id-- inpatientWHERE fmx_read_code(ec.code) = 'IMP'  -- ICD-10 heart failure  AND fmx_read_code(ccc.code) LIKE 'I50%'  AND lower(ep.start) >= date_trunc('month', now());
Illustrative query. Table and column names follow the Firemetrics schema.

How it fits together

One foundation, open access, tools for every day

Use the layers with your own tools, ours, or both. Every application reads from the same data.

  1. Layer 1

    One data foundation

    Every source in one relational, transactional FHIR repository. Your team queries it with SQL.

    • Relational FHIR Engine
    • Terminologies built in
    • Roles, permissions, audit log

  2. Layer 2

    Open access for any app and AI

    Standard interfaces. New software no longer needs its own data project.

    • SQL
    • FHIR API
    • SMART on FHIR
    • MCP server

  3. Layer 3

    Tools for daily work

    Ready-to-use applications, configured per department.

    • Studio
    • FLAME local AI
    • Real-time dashboards
    • Patient viewer

Your source systems stay

  • EHR
  • LIS (lab)
  • RIS (radiology)
  • PACS (DICOM)
  • ERP
  • Files and CSV

Your data stays yours

Open standards throughout. Read everything at any time with SQL or FHIR, also if you change vendors.

Connect your AI or use oursSee the tools
Back toOverview Next Connect your AI or use oursAny application and any AI tool connects through standard interfaces, so each new tool costs less than the one before.

See the platform on your own architecture.

A technical deep-dive with our engineers.

Book a technical deep-diveSee the integrations