1. Connectors
The Tuva Data Model makes raw clinical and claims data useful in many ways, checking quality, restructuring data for easy calculations, and adding important features that improve interpretability like terminology, value sets and other clinical concepts.
The key to unlocking these features is mapping your data to the Input Layer. The Input Layer is nothing more than a set of data dictionaries to common healthcare data sources, like claims or EMR records. These data come in all different formats, with different numbers of columns, different column names, different data types, etc.
A connector is simply a set of code/logic that converts data from whatever source it came from into the tables, columns, column names and other standard conventions defined in the Tuva input layer (data dictionaries). Building and running a connector transforms your data into the format expected by the Tuva Data Model.
For more details on building a custom connector to map your own data to the Tuva Project Input Layer, visit the next section on Building a Connector.
Pre-Built Connectors
The Tuva Project also has a library of Pre-Built Connectors that you can use to map common claims or clinical data sources to the Tuva Input Layer.
Claims Flat Files:
EHR Databases:
FHIR:
ADT Flat Files: