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.

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.

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.

With its intuitive interface and guided tutorials, users can learn the basics of developing mappings within a few hours. Advanced mappings using the FHIRPath editor may take additional time based on your familiarity with the FHIR standard and FHIRPath expressions.

With our team’s professional services, an initial set of mappings can be developed within 1 month given that all source data, data schema, required documentation and the infrastructure are available during the development. With extensive tests, archiving and security configurations, generally we make everything operational within 3 months.

During mapping development, it is quite easy to provide the target profiles for the resource types for which the mappings are being developed. On the other hand, Ignifyr can automatically process profile definitions and guide the user during the mapping development accordingly.

Yes, Ignifyr allows flexibility in transformations. You can configure mappings to produce both FHIR resources and a flat data structure as needed. This means, Ignifyr can read FHIR resources and map them to flat structures such as CSV files.

Yes, Ignifyr can aggregate data from different data sources (e.g., some from a relational database, some from CSV files) to map to a single FHIR resource. 1-to-1, 1-to-many and many-to-1 mappings are possible.

Yes, Ignifyr supports external terminology servers provided that it conforms to FHIR Terminology Server specification.

Ignifyr can automatically integrate FHIR terminology servers and the corresponding terminology service function calls (within FHIRPath) interacts with the configured terminology server. On the other hand, Ignifyr ships with a local terminology server to which code systems, value sets and terminology translations can be loaded and then used during the mappings.

Ignifyr supports a wide range of data sources, including file systems (Excel, CSV, TSV, JSON, Parquet), SQL databases, REDCap projects, FHIR endpoints, and Apache Kafka streams. When possible, these sources can be configured as streaming sources so that Ignifyr processes every newcoming or updated source data.

Yes, Ignifyr can connect to platforms like REDCap and LimeSurvey and allows you to use their data within your mappings. That is, REDCap or LimeSurvey results can be mapped to corresponding FHIR resources.

Based on your preference, created FHIR resources can be sent to a FHIR server (such as Repofyr, HAPI, Firely etc.) or saved to the file system in NDJSON format or Parquet format.

Ignifyr belongs to an ecosystem of products that we develop around FHIR. We offer Repofyr that is a high-performant FHIR repository. You can also use its limited open-source version to test your Ignifyr installation.

Ignifyr provides an automated environment for testing and validating mappings and scripts at any stage of development. It offers a powerful FHIRPath editor with smart auto-completion to making it easier to create accurate mappings. Additionally, Ignifyr includes validation tools to verify that the generated FHIR resources conform to their respective FHIR profiles.

Yes, Ignifyr supports mappings from FHIR R4 to R5. We already have the mappings from FHIR R4 to R5, that is, once you connect Ignifyr to your data, you can transform to R5 right away.

Not necessarily. Once mappings are configured, Ignifyr can automate the process and allow you to reuse mappings for recurring data transformations. This can be done through scheduled executions within Ignifyr or by configuring your source as a stream.

Yes, Ignifyr supports both batch processing and real-time streaming for continuous data ingestion.

Yes, Ignifyr provides a user-friendly web interface where you can set up and customize your mappings and monitor the execution of mapping processing in real-time through an execution monitoring platform.

Our dedicated support team is available to assist with technical issues, provide guidance, and resolve any challenges you encounter. Support plans are included with the Enterprise license.

Yes, we offer professional integration services to help you develop mappings on Ignifyr quickly and effectively. Our team will help you to transform your data to be HL7 FHIR-ready while meeting your specific requirements.