FHIR Universal Conversion Kit (Project F.U.C.K)

FHIR Universal Conversion Kit (F.U.C.K.) is an awesome and sexy tool that can convert arbitrary medical data into HL7 FHIR format and supports uploading to FHIR Server.

For Chinese documentation, please refer to README_zh-TW.md

Introduction

What the F.U.C.K.?

F.U.C.K. is a tool designed to convert various medical data into FHIR format and supports uploading to FHIR Server. Traditional medical data integration between different systems often requires writing a conversion program for each data format, which can be burdensome for developers. F.U.C.K. offers a Low-Code or even No-Code solution, allowing users to simply write a configuration file to convert various data into FHIR format. Subsequently, the FHIR format can be used for cross-hospital or cross-system data exchange.

Why is it called F.U.C.K.?

F.U.C.K. stands for "FHIR Universal Conversion Kit", so the middle dot should not be omitted. :P

Why should I F.U.C.K.?

• Multi-FHIR Version Support: Supports multiple FHIR versions, ensuring broad compatibility.
• Data Validation: Converts and validates data, then automatically uploads to FHIR Server.
• Data Pre/Post-processor: Offers options for pre-processing and post-processing of data.
• Auto Uploader: Converts and validates data, then automatically uploads to FHIR Server.
• Less Coding: Provides a GUI for creating configuration files without writing code.
• Efficiency: Save your ass and NEVER write code to convert medical data again!

Development Progress

• ✅ Core Conversion Engine
• ✅ Multiple Configuration File Support
• ✅ Data Preprocessor
• ✅ FHIR Data Uploader
• ✅ Detailed Error Handling
• ✅ FHIR Resource Validator
• ✅ GUI Configuration Builder
• ➡️ Multi-source Data Support
• ➡️ TW Core IG Built-in Support

How to get F.U.C.K.ed?

Requirements

• Node.js 20.18.0 or higher

Installation

Install F.U.C.K. using npm:

npm install @fhir-uck/fhir-converter-core

Go F.U.C.K. yourself!

As a Library

You can use F.U.C.K. directly in your Node.js application:

const { Convert, Validator } = require('@fhir-uck/fhir-converter-core');

const config = 'your_config_name';
const data = [/* your data array */];

async function convertAndValidateData() {
  const convert = new Convert(config);
  const result = await convert.convert(data);
  
  const validator = new Validator();
  const validationResult = await validator.validate(result);
  
  console.log(result);
  console.log(validationResult);
}

convertAndValidateData();

As an API

To deploy F.U.C.K. as an API, you'll need to create a server application. Here's a basic example using Express:

1. Install Express:

   npm install express

2. Create a server file (e.g., server.js):

   const express = require('express');
   const { Convert, Validator } = require('@fhir-uck/fhir-converter-core');
   
   const app = express();
   app.use(express.json());
   
   app.post('/api/convert', async (req, res) => {
     const { config, data, validate } = req.body;
     
     try {
       const convert = new Convert(config);
       const result = await convert.convert(data);
       
       if (validate) {
         const validator = new Validator();
         const validationResult = await validator.validate(result);
         res.json({ result, validationResult });
       } else {
         res.json({ result });
       }
     } catch (error) {
       res.status(500).json({ error: error.message });
     }
   });
   
   const PORT = process.env.PORT || 3000;
   app.listen(PORT, () => console.log(`Server running on port ${PORT}`));

3. Start the server:

   node server.js

4. Make a POST request to the API endpoint:

   POST http://localhost:3000/api/convert
   

   With the following JSON payload:

   {
     "config": "your_config_name",
     "data": [/* your data array */],
     "validate": true  // Set to true if you want to validate the converted data
   }

Running the Example Conversion

To run a conversion using an example script, create a new file (e.g., example_convert.js) with the following content:

const { Convert, Validator } = require('@fhir-uck/fhir-converter-core');

const config = 'example_config'; // Replace with your config name
const data = [/* your example data */];

async function exampleConvert() {
  const convert = new Convert(config);
  const result = await convert.convert(data);
  
  const validator = new Validator();
  const validationResult = await validator.validate(result);
  
  console.log('Conversion result:', result);
  console.log('Validation result:', validationResult);
}

exampleConvert();

Then run the script:

node example_convert.js

Configuration Files

Configuration files are located in the config folder. Each configuration file defines:

• Data source format
• Conversion rules
• Pre-processing and post-processing hooks
• Validation rules

You can create new configuration files by adding .js files to the config folder, or use the GUI builder to create configuration files.

Conversion Process

The conversion process follows this workflow:

1. Load configuration
2. Pre-process data (if defined)
3. Convert individual fields
4. Post-process data (if defined)
5. Validate the resulting FHIR Bundle (if enabled)
6. Return or upload the resulting FHIR Bundle

Using the GUI Configuration Builder

F.U.C.K. provides a user-friendly GUI for creating and editing configuration files. To use the GUI:

1. Open the config_builder/index.html file in your web browser.
2. Use the interface to set up your configuration, including field mappings, preprocessors, and postprocessors.
3. Click the "Download Config" button to save your configuration file.
4. Place the downloaded configuration file in the config folder of your F.U.C.K. installation.

Configuration File Structure

Here's an example of a configuration file:

const uuid = require('uuid');

const organizationId = uuid.v4();

module.exports.config = {
    name: 'example_config',
    version: '1.0.0',
    fhirServerBaseUrl: 'https://hapi.fhir.org/baseR4',
    action: 'upload', // 'upload' or 'return'
}

module.exports.globalResource = {
    // Define global FHIR Resource templates here
    // You can customize FHIR Resource Template, if not defined, it will use FHIR default Resource Template
}

module.exports.fields = [
    // Define field mappings here
    {
      source: 'source field name',
      target: 'target FHIR field name, using FHIR Path',
      beforeConvert: (data) => {
        // Process the data field before conversion
        return data;
      }
    }
]

module.exports.beforeProcess = (data) => {
    // Pre-processing logic
    return data;
}

module.exports.afterProcess = (bundle) => {
    // Post-processing logic
    return bundle;
}

FHIR Resource Validator

F.U.C.K. includes a built-in FHIR Resource Validator, which can be used to validate whether the converted FHIR resources comply with FHIR specifications. The validator checks:

• The accuracy of resource structure
• Mandatory fields
• Data type consistency
• Value set regulations

The validator has two operating modes:

1. Automatic Validation in Configuration File

You can enable automatic validation in the configuration file. This way, every conversion will automatically include validation:

module.exports.config = {
    name: 'example_config',
    version: '1.0.0',
    fhirServerBaseUrl: 'https://hapi.fhir.org/baseR4',
    action: 'upload',
    validate: true  // Enable automatic validation
}

When validate is set to true, the conversion process will automatically include validation steps. If validation fails, the conversion result will include validation error information.

2. Independent Use

You can also use the validator independently, allowing you to manually validate when needed:

const { Validator } = require('path/to/src');

const validator = new Validator();
const validationResult = await validator.validate(fhirBundle);

if (validationResult.valid) {
  console.log('FHIR resource is valid');
} else {
  console.log('Validation errors:', validationResult.errors);
}

This approach allows you to validate at any time outside of the conversion process, providing you with greater flexibility.

Error Handling

F.U.C.K. provides detailed error messages, including:

• Server response status
• Response body
• Validation errors

If the conversion fails, it will return an error message with an error code for easy debugging.

Contributing

If you have any new ideas, feel free to submit an Issue or Pull Request.

License

For users outside Taiwan: This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License (CC BY-NC-SA 4.0).

You are free to:

• Share — copy and redistribute the material in any medium or format
• Adapt — remix, transform, and build upon the material

Under the following terms:

• Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
• NonCommercial — You may not use the material for commercial purposes.
• ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.

For more details, please refer to the LICENSE file.

© 2023 Lorex and Sitatech Information Services Co., Ltd. All Rights Reserved.