LogoLogo
  • Home
  • Protocol Overview
    • Introduction
    • Architecture
  • Protocol Guide
    • Get Started
      • Components
      • Definition of Terms
    • Build a dApp
      • Network Configuration
      • TuumIO Data Node
      • TuumIO Ledgers
      • Roles and Journeys
      • Card Definitions
        • Tiles
        • Functions
      • Events and Event Handlers
      • Node Event Handlers
      • Python Event Handlers
      • Transactional Data
    • Test and Publish
      • Publishing the protocol
      • Testing the app using BrowserStack
  • TuumIO Wallet User Manual
    • About TuumIO Wallet
    • User Access
    • SOLVE Tokens
    • Caira - AI Assistant
    • User Profile
    • Care.Trials
      • Overview
      • Participant
      • Site Admin
      • Trial Admin
      • Physician
      • Nurse
  • Tutorials
    • Create an Event Booker
    • Create a Library Explorer
  • Support
Powered by GitBook
LogoLogo

© Solve.Care. All rights reserved.

On this page
  • How TuumIO Data Node works?
  • Data definition file

Was this helpful?

Edit on GitHub
Export as PDF
  1. Protocol Guide
  2. Build a dApp

TuumIO Data Node

PreviousNetwork ConfigurationNextTuumIO Ledgers

Last updated 8 months ago

Was this helpful?

How TuumIO Data Node works?

The TuumIO Data Node (TDN) is responsible for storing and exchanging data files within the TuumIO Network. It can convert external data files into events, and events into external data files. When receiving data files, the TuumIO Data Node extracts and transforms the data, and then creates events. Event handlers can be created in TuumIO Protocol to manage the events generated by the TuumIO Data Node.

Data definition file

The data definition file (DDF) defines the model and structure for organizing data in the TDN. This file is used in TDN to process incoming data files and generate events for distribution to TuumIO Nodes. The DDF and raw CSV files are uploaded to the environment repository for processing. For more information, see .

The following example shows data definition in ddf/us-doctors-sample.json.

Example:
{
    "ddf_type": "us-doctors-sample",
    "meta_data": {
        "description": "Sample"
    },
    "messages": [
        {
            "message_category": "CSV",
            "message_type": "Doctors",
            "meta_data": {
                "description": "Sample",
                "indices": "us-doctors-sample"
            },
            "events": [
                {
                    "to_role": "rl-patient",
                    "event": "ev-cdn-broadcast"
                }
            ],
            "attributes": [
                {
                    "name": "Provider",
                    "description": "Provider",
                    "required": false,
                    "index_field": true,
                    "type": "integer",
                    "data_location": "Provider"
                },
                {
                    "name": "License",
                    "description": "License",
                    "required": false,
                    "index_field": true,
                    "type": "string",
                    "data_location": "License"
                },
                {
                    "name": "Specialization",
                    "description": "Specialization",
                    "required": false,
                    "index_field": true,
                    "type": "string",
                    "data_location": "Specialization"
                },
                {
                    "name": "Address",
                    "description": "Address",
                    "required": false,
                    "index_field": true,
                    "type": "string",
                    "data_location": "Address"
                }
            ]
        }
    ]
}
Updating TDN