OMOP CDM 5.3 and 5.4 are both built into Ignifyr Enterprise, so a version upgrade becomes a set of mappings between the tables: renamed columns, new required columns and new tables, tested on sample rows and written by the OMOP Database sink...

An OMOP database is a source like any other. With the built-in OMOP CDM tables, map person, condition_occurrence and the other tables to US Core resources, look codes up in the vocabulary, validate inside Ignifyr and write to your FHIR server...

toFHIR has become Ignifyr, the engine has moved to its 2.x line and the web interface to version 4.0. Discover the batching strategy for very large sources, the new plugin architecture, Delta Lake output, RxNorm functions and more...

When defining a mapping from your EHR data to a FHIR resource, it's important to test the mapping before executing it on the entire dataset. Running the full mapping process each time can be time-consuming and inefficient. Instead, you may want to test the mapping on...

In the complex landscape of healthcare data, ensuring that different systems can communicate with each other is a significant challenge. Medical terminologies, with their vast and varied vocabularies, often become a barrier to data exchange. This is where terminology services become essential...

REDCap (Research Electronic Data Capture) is one of the most widely used platforms for collecting healthcare data in research and clinical studies. It is utilized by universities, hospitals, and other institutions worldwide.

Manually defining schemas in Ignifyr can be a tedious and time-consuming process. You often need to go through each column one by one, carefully specifying its structure, and then repeatedly test your mappings to make sure everything aligns with...