curedao / health-reference-data

Standard health reference databases including units of measurement, biomarkers, medical codes, medications, side-effects, supplements, foods, ingredients, and more.

Health Reference Databases

Standard health reference databases including units of measurement, biomarkers, medical codes, medications, side-effects, supplements, foods, ingredients, and more.

The health reference data repository is part of our core module The Unified Health API (UHA), which has the main purpose to provide a single storage and query solution for the analysis of health data.

Reference Database

To generate a common language for health data we put all health data references into a single table and call them variables. Pretty much anything quantifying a certain state of a human being could be used as health data and its analysis to find new insights.

The variables are:

• Biomarkers (Wearables, Labs, Multiomics)
• Outcomes
• Conditions, Symptoms and Diseases
• Interventions (Medication, Supplements, Therapies)
• Data from Insurance and Healthcare
• Nutritional Intake
• Environment
• Social and Digital markers
• Any other health related data

DB Schema Repository

How it works

Using The Unified Health API (UHA) imported data points will be mapped to a measurement schema, which pulls the reference information from this reference database to validate measurement values and to tag the data with the common identifiers.

Existing reference databases such as LOINC codes, used in healthcare for lab-tests for example, are pulled in together. Additional information on top of these databases, such as fixed units, synonyms and cross references are necessary for the purpose of more efficient data analysis. These additions are community maintained and version controlled for an ecosystem wide shared use to create seamless interoperability. The magic comes in with completely new entries, where standards are still missing. E.g. new digital biomarkers in development can be easily implemented in an own instance and published as proposal for being added to the commonly used reference.

This storage solution is also applied in applications, where users create their own marker references in a private environment, so that a seamless use of all tools in the infrastructure are still available.

Online Data Browser

To browse the references online go to our Online Reference Browser

To browse the references in a comprehensive database visit Reference Browser Database

Contact [email protected] if you desire access.

Contribution

We encourage the community to help build out the additions to use existing and non-existing standards for the purpose of more effective health data analysis and to fill missing gaps for e.g. new biomarkers.

The process is currently in the making, please join our Discord to learn more.

Reference Data Sources

1. Units of Measurement

2. Nutritional Supplements

3. Medication

4. Conditions, Symptoms and Diseases

5. Observations, Lab Test Results, and Biomarkers

6. Clinical Trials

7. Medical Codes, Terms, and Synonyms

8. Wearables

9. Nutrition

10. Additions

Variables Data Schema

Variables schema documentation

Variables schema definition

Git Large File Storage

This repository requires that you install the Git Large File Storage plugin to store large files in Git.

health-reference-data's Issues

What is the shared ID for a variable across the ecosystem?

Requirements to the variables schema and the reference database

• I as OpenCures I need a variables table with entries i made manually (public CureDAO ecosystem can read, only I can write)
• I need to query one specific entry directly through an id (e.g. to render a detail page of this variable)
• I want to change the content like the name later, but already shared data should still map to it (e.g if slug is changed after name change)
• Measurements created with this attached variable id should be useable for any stakeholder in this ecosystem

The API response should contain this:

.../api/variables/blood_testosterone ->

// Testosterone
{
    id: 'blood_testosterone',   // used also as api property if needed, snake case
    slug: 'blood-testosterone', // used for urls
    category: 'laboratory',
    ref_loinc_id: '2986-8',
    // With the loinc id there is an assay/measurement method definition attached, would be evtl. needed with other biomarkers e.g. heartrate with ppg sensor or manually including the mean error
    abbreviated_name: 'T',
    name: 'Testosterone',
    description: "This is a custom OpenCures description tailored to the specific feature i use this for",
    unit: 'ng/dL',
    synonyms: ['Testosterone, Total', 'Testosterone, Serum', 'Testosteron ges.', 'Testosteron gesamt'],
    references: ['https://www.labcorp.com/tests/004226/testosterone-total', 'https://www.netdoktor.de/Diagnostik+Behandlungen/Laborwerte/Testosteron-1522.html'],
    ranges: {
        male: {
            norm: {
                0: [0, 0, 5, 5, 495, 495, 2000, 2000],
                1: [0, 0, 3, 3, 32, 32, 2000, 2000],
                7: [0, 0, 3, 3, 32, 32, 2000, 2000],
                8: [0, 0, 2, 2, 882, 882, 2000, 2000],
                18: [0, 0, 2, 2, 882, 882, 2000, 2000],
                19: [0, 0, 280, 280, 800, 800, 2000, 2000],
                20: [0, 0, 132, 132, 906, 906, 2000, 20000],
                60: [0, 0, 132, 132, 906, 906, 2000, 2000],
            }
        },
        female: {
            norm: {
                0: [0, 0, 3, 3, 161, 161, 2000, 2000],
                1: [0, 0, 3, 3, 32, 32, 2000, 2000],
                7: [0, 0, 3, 3, 32, 32, 2000, 2000],
                8: [0, 0, 4, 4, 38, 38, 2000, 2000],
                18: [0, 0, 4, 4, 38, 38, 2000, 2000],
                19: [0, 0, 6, 6, 82, 82, 2000, 2000],
                20: [0, 0, 2, 2, 52, 52, 2000, 2000],
            }
        },
    },

    // And the other already agreed stuff of course, not subject of this discussion
    created_at: "timestamp",
    updated_at: "timestamp",
    version_first_released: "",
    version_last_changed: "",
    // ...
};