Key Features
Ignifyr empowers healthcare organizations to transform diverse data sources into standardized FHIR resources with ease and efficiency. Explore the key features that make Ignifyr the ultimate solution for seamless data integration and streamlined interoperability.
Seamless Data Integration
Ignifyr seamlessly integrates with diverse data sources, allowing you to extract data and convert it into FHIR resources with ease. Ignifyr handles data source connection details for you.
Extensive Compatibility
Ignifyr reads from file systems (CSV, TSV, Parquet, JSON, NDJSON), SQL databases, REDCap projects, FHIR servers and Apache Kafka streams. Results go to any FHIR server or to NDJSON, CSV, Parquet and Delta Lake files.
User-Friendly Web Interface
Our intuitive interface makes the ETL process a breeze. You don't need to be a coding expert to work with Ignifyr: infer schemas, import FHIR profiles, and configure, test and execute your mappings with a FHIRPath editor that offers smart auto-completion.
Off-the-shelf Mappings
Ignifyr ships with already available mappings from standard data models such as OMOP CDM, i2b2 CDM, HL7 CDA, FHIR R4 etc. to FHIR R4 and R5.
Automated Testing & Validation
Test your mappings on a sample of the source data at any time during development. Generated FHIR resources are validated against their target profiles through your FHIR server's $validate operation, with issues grouped per source row.
Execution Monitoring Platform
Run, stop and schedule jobs, follow progress batch by batch and inspect error logs per mapping. Enterprise deployments ship execution logs to Elasticsearch with ready-made Kibana dashboards.
Scales to Millions of Records
Built on Apache Spark. The batching strategy splits sources with 10 million+ rows into parameterised batches. Jobs can also run as streams (folder watch, Kafka) or on cron schedules with incremental pulls.
Any Profile, Any Target Model
Target FHIR R4 or R5 and map directly to US Core, the International Patient Summary, the German MII core data set or your own implementation guide, imported from a FHIR server or a ZIP file. Your target does not have to be FHIR: define your own schema, for example for an OMOP-based common data model, and map to it the same way.
Terminology & Code Systems
Translate local codes through FHIR terminology services or local concept maps, and convert units to UCUM. Works with SNOMED CT, LOINC, ICD-10 and ATC, with RxNorm functions in Enterprise.
Ignifyr has greatly optimized our data transformation process. This tool has not only saved us time and effort but also enhanced the quality of our data, making it more valuable for machine learning in health research.
A. Anil Sinaci, AICCELERATE
Use Cases
Ignifyr is the data integration engine behind large European research projects in cardiology, oncology, paediatric palliative care and hospital care. It maps the data of clinical sites to FHIR-based and OMOP-based common data models for federated learning and AI, without the data ever leaving the hospital. The FHIR-based models also hold public datasets such as MIMIC-IV.
DataTools4Heart
Ignifyr maps the data of each clinical site to a FHIR-based common data model. Federated learning then runs on harmonised data that stays inside the hospital.
- 8 clinical sites in 7 countries
- 3 use cases
- FHIR-based common data model with 37 profiles
AI4HF
Ignifyr maps the data of each clinical site to the same FHIR-based common data model as DataTools4Heart. The data feeds AI model training and online heart-failure risk assessment.
- 10 clinical sites in 7 countries
- 6 use cases
- FHIR-based common data model with 37 profiles
AICCELERATE
Ignifyr mapped the data of each clinical site to a FHIR-based common data model for AI in patient flow, Parkinson's disease and paediatric care. A single use case produced more than 7 million FHIR resources.
- 5 clinical sites in 3 countries
- 7 use cases in 3 pilots
- FHIR-based common data model with 102 profiles
MIMIC-IV
Ignifyr maps the MIMIC-IV hosp module to the FHIR-based common data model of DataTools4Heart and AI4HF, in FHIR R5.
- 364,627 patients
- 236M FHIR resources
- FHIR-based common data model with 37 profiles
Standards & Compliance
Map to US Core or any other FHIR profile, and keep your data inside your own infrastructure. Whether you work under HIPAA in the United States or the GDPR in Europe, Ignifyr gives you the technical building blocks for standards-based and privacy-preserving data processing.
Map to US Core and any FHIR profile
Load US Core, the International Patient Summary or any implementation guide and pick target profiles for each mapping. Validate the output against those profiles on your FHIR server before you run at scale.
GDPR-ready processing
Ignifyr runs inside your own infrastructure, so personal data stays under your control. Map only the elements a use case needs, replace source identifiers with deterministic hashed IDs and keep a log of every execution.
HIPAA-ready deployments
Deploy on-premises or in your private cloud so protected health information never leaves your environment. Serve the API over TLS and secure source and target FHIR servers with OAuth2 client credentials, bearer tokens or basic authentication.
Privacy by design in federated research
In DataTools4Heart and AI4HF, Ignifyr runs at each clinical site as part of a federated platform. Data is harmonised locally, and only models and aggregate results leave the site.
Ignifyr provides technical controls that support your HIPAA and GDPR obligations. Compliance also depends on how the whole system is deployed and operated, and on your policies and agreements. Our team can help you configure Ignifyr for your requirements.
Why Choose Ignifyr
Choosing the right tool for data transformation is essential to unlock the full potential of healthcare data. Discover why Ignifyr stands out as the ideal solution to ensure interoperability, integration with and support your unique data needs with efficiency and reliability.
Save time and effort
Ignifyr simplifies the complex ETL task of converting various data sources into FHIR resources, significantly reducing manual work and helping you reclaim valuable time for other priorities.
Enhanced data interoperability
By leveraging the HL7 FHIR® standard, Ignifyr facilitates seamless data exchange across healthcare systems and applications, opening doors to health research and improved patient care.
Flexibility and customization
With specialized templates and standard FHIRPath expressions, Ignifyr offers the flexibility to tailor your data transformations and mappings according to your unique requirements.
Easy integration
Ignifyr integrates smoothly with your existing data ecosystem and allows you to write the generated FHIR resources to a configured FHIR endpoint, ensuring smooth integration with your healthcare infrastructure.
Reliable and responsive support
Our expert support team is available to assist you throughout your Ignifyr journey, ensuring a smooth experience and resolving any issues you may encounter.
Professional integration services
Our highly experienced data professionals are available to provide integration services, helping you implement Ignifyr quickly and effectively while ensuring your data is HL7 FHIR-ready.
We could quickly and effortlessly develop our next-generation healthcare applications using Ignifyr, integrating them with the existing healthcare systems in several European countries within the scope of AI4HF project.
Gokce B. Laleci Erturkmen, AI4HF
Pricing
Ignifyr offers flexible deployment options tailored to meet the needs of various organizations, from open-source single-server setups to robust enterprise solutions. Explore our plans to find the version that best aligns with your data integration and performance requirements.
Open Source
- Apache 2.0 licensed mapping engine and command-line tool
- File (CSV, TSV, Parquet) and SQL database sources
- Output to FHIR servers and NDJSON, CSV or Parquet files
- Batch execution, FHIR R4 and R5
- Local and FHIR terminology services
- Web interface and REST API for ETL configuration and execution monitoring
- Streaming, scheduling and Kafka, FHIR server and REDCap sources
- Full support
Enterprise
- Everything in Open Source
- Advanced web interface and REST API for ETL configuration and execution monitoring
- Apache Kafka, FHIR server and REDCap sources, JSON and NDJSON input, Delta Lake output
- Streaming and cron-scheduled jobs with incremental pulls
- Batching strategy for sources with 10 million+ rows
- RxNorm functions and Elasticsearch/Kibana observability dashboards
- Full support and professional integration services
Cloud
Our cloud service offer will be announced soon!
Frequently Asked Questions
Have questions about how Ignifyr works or what it can do for your organization? Explore our FAQs to find answers to common queries and learn how to get the most out of Ignifyr.
-
What is Ignifyr, and how does it work?
Ignifyr is a powerful ETL (Extract, Transform, Load) tool that transforms healthcare data from various sources into HL7 FHIR® resources. Through its highly-functional web-based interface, you can configure the mappings, test them and execute them to generate corresponding FHIR resources and load them to a FHIR server.
-
Who can benefit from using Ignifyr?
Ignifyr is ideal for hospitals, regional health services or any healthcare organizations looking to enable data interoperability across different healthcare systems, prepare healthcare data for research or clinical use in FHIR format, and implement HL7 FHIR® standards within their infrastructure without extensive coding expertise.
-
What do I need to get started with Ignifyr?
You will need access to your data sources, a basic understanding of your data structure, and a deployment environment for Ignifyr (local, cloud, or containerized setup). Our team can assist you with the setup and configuration.
-
Is Ignifyr open-source, or do I need to purchase a license?
Ignifyr offers an open-source version that allows you to freely test its core functionality. For enhanced features such as a web-based graphical interface, high-performance scalability, advanced mapping configurations, and dedicated support, the Ignifyr Enterprise license is available.
-
Can Ignifyr map my data to US Core profiles?
Yes. Import the US Core StructureDefinitions from a FHIR server or as a ZIP file, and select the US Core profile as the target of each mapping. The same works for the International Patient Summary, the German MII core data set or your own implementation guide. Generated resources can then be validated against these profiles on your FHIR server.
-
Is Ignifyr suitable for HIPAA and GDPR environments?
Yes. Ignifyr is deployed inside your own infrastructure, so health data does not need to leave your environment. It supports data minimisation through mappings, deterministic hashed identifiers, TLS and authenticated connections to FHIR servers, and a log of every execution. Compliance also depends on your overall deployment and policies, and our team can help you configure Ignifyr accordingly.
Contact
Have questions or need more information about Ignifyr? Get in touch with us using the details below or fill out the contact form, and our team will be happy to assist you.
Location:
Pontegra Software Technologies B.V.
Amsterdam, Netherlands