<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>May</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Preparation: A Use Case on Disparity in Access to Health Care</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Paulo Pinheiro</string-name>
          <email>paulo@psemantica.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Henrique Santos</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Miao Qi</string-name>
          <email>qimiaorpi@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kristin P. Bennett</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Deborah L. McGuinness</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Parcela Semântica</institution>
          ,
          <addr-line>Funchal</addr-line>
          ,
          <country country="PT">Portugal</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Rensselaer Polytechnic Institute</institution>
          ,
          <addr-line>Troy NY</addr-line>
          ,
          <country country="US">United States</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2023</year>
      </pub-date>
      <volume>29</volume>
      <issue>2023</issue>
      <abstract>
        <p>Data preparation is a time-consuming task required for data analytics. In the biomedical field, we observe that datasets tend to have a large number of diversified variables, especially when we consider data coming from healthcare facilities. When data analytics depends on variables from several studies, one approach is to use semantics to annotate and support the alignment and combination of variables. We propose a novel use of semantics to support biomedical data preparation, specifically the use of semantic variable normalization in support of machine-assisted biomedical data preparation. To illustrate our approach, we present a use case in disparity in access to health care using data from the U.S. National Health and Nutrition Examination Surveys (NHANES), one of the most studied biomedical datasets in the U.S. This use case is a multi-cycle study of disparities in access to needed care that requires the semantic combination of data from three survey cycles. We demonstrate that NHANES data can be normalized and accessed regardless of cycle by the use of a semantic representation of study variables and a semantically-enabled faceted search. This approach can reduce the time required for data understanding and preparation, especially in settings like NHANES where it is common to combine data from several cycles.</p>
      </abstract>
      <kwd-group>
        <kwd>data preparation</kwd>
        <kwd>NHANES</kwd>
        <kwd>semantic variable normalization</kwd>
        <kwd>health informatics</kwd>
        <kwd>Health Disparity</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>A</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>
        The typical input for data analysis activities is a dataset rather than the raw data from data
ifles [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Data preparation is commonly used to describe time-consuming processes that combine
data manipulation operations and culminate in the generation of a dataset out of data file
content [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. A data preparation criterion, which specifies the variables from one or more sources
that are required to perform a data analysis activity, guides the execution of data preparation
activities. As an example, an (over-simplified) description such as “all known demographic data
nEvelop-O
in a given study” can be understood as a data preparation criterion that is expected to identify
the required elements for generating a dataset out of a collection of data files. The assumption
is that the content of the dataset resulting from successful data preparation, i.e., the “prepared
data”, is made of data values that meet the inclusion statement in the data preparation criterion.
      </p>
      <p>
        In the biomedical context, we observe the complexity in analyzing data is often related to
a set of variables that is much larger than we can observe in non-biomedical data [
        <xref ref-type="bibr" rid="ref3 ref4">3, 4</xref>
        ]. For
example, in the context of analyzing financial and marketing data, we observe companies
performing data analysis in extremely large datasets, e.g., tabular data with literally billions
of rows, although with a very reduced number of variables. Nevertheless, this large set of
variables behind biomedical data tends to include a complex network of relationships between
the entities behind the variables containing the biomedical data.
      </p>
      <p>NHANES is the main national weighted survey for the United States that was started in 1971
and continues to be conducted. Continuous implementation of NHANES has occurred since
1999. NHANES gave origin to thousands of derived studies, and many more studies will be
derived from it in the future. Naturally, it is overwhelming for a person who is new to NHANES
data, policies, and documentation to confidently perform data preparation. In addition, NHANES
data preparation is usually performed to support a single study (or a constrained set of studies).
Thus, this efort is rarely translated into knowledge and tools that can simplify the future task
of someone preparing NHANES data for new data analysis activities. Because NHANES data
has resulted from a careful and complex survey design, conclusions from NHANES can be
very accurate if properly combined and analyzed. Otherwise, results may be biased potentially
leading to inaccurate conclusions.</p>
      <p>
        In this paper, we explore the problem of using data from the National Health and Nutrition
Examination Survey (NHANES) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] to perform data analysis to assess disparity in access to
health care in the U.S. More specifically, we discuss semantic challenges that may arise when
accessing the original data from NHANES. We present an approach based on semantic web
technologies for facilitating biomedical data preparation, more specifically for the task of
uniformly selecting variables from diferent studies. We propose the abstraction of variables as
semantic variables that use properties of entities that are shared among several variables. We
operationalize this approach in a use-case for quantifying disparity in access to antidiabetic
medication and immunization using NHANES data from three cycles. Further, we discuss that
many of the semantic challenges one may experience while using NHANES can be partially
mitigated by using a data ingestion framework that is capable of creating semantic normalized
and annotated variables from NHANES’ original variables.
      </p>
    </sec>
    <sec id="sec-3">
      <title>2. NHANES Background</title>
      <p>
        NHANES is a list of cross-sectional studies starting in 1971. Since 1999, a new study is added
to the list of studies every two years, and each one of these studies done since 1999 has
approximately ten thousand subjects. NHANES is based on a sampling design that is used to
select participants representative of the civilian, non-institutionalized US population. Each of
these periods of two years is called a “cycle.” For each cycle, NHANES uses a complex survey
design including oversampling, survey non-response, and post-stratification adjustment to
match total population counts from the Census Bureau [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. A statistical weight is associated
with each survey participant to identify how many members of the US population that participant
represents. Therefore, the sampling weights must be used for all subsequent analyses to make
valid conclusions based on the NHANES data. A further complication is that the variables
included in each cycle evolve over time. Variables may be added and removed between diferent
cycles, and/or the names and/or definitions of the variables may change (e.g. the variable
RIDRETH3 - Race/Hispanic origin w/ NH Asian introduced in 2011 to include the Non-Hispanic
Asian category). Considerable analyst expertise is needed to identify the variables available
for analysis in each cycle, to appropriately combine data from diferent cycles for analysis, to
calculate the correct survey weights, and to perform the appropriate survey-weighted design.
      </p>
      <p>NHANES data is acquired for properties of any subject in any cycle just once. The
crosssectional nature of each cycle implies that every observation of a subject occurs once within
the entire project. We note that other than the weights associated with each subject, the overall
collection of subjects of all cycles are providing the same kind of information. Thus, it is
common practice to combine multiple adjacent cycles to create a larger sample size leading
to more robust conclusions. This means that if one wants to analyze NHANES data with a
very large sample population, one needs to keep aggregating cycles to the pool of subjects to
be analyzed since approximately ten thousand new subjects are added for each cycle that is
aggregated.</p>
      <sec id="sec-3-1">
        <title>2.1. NHANES Cycle Aggregation Challenges</title>
        <p>According to NHANES documentation, the only concern one needs to be aware of while
aggregating cycles is the fact that the cycles need to be adjacent (i.e., consecutive years with
no gaps), and that any weighted variable needs to be averaged by the total number of cycles
being aggregated. In practical terms, however, cycle aggregation is a semantic challenge when
it comes to understanding how variables of multiple studies are harmonized – reminding us
that each cycle is an individual study. Below we list six of these challenges.</p>
        <p>• For variables available in one cycle, it is not assured that corresponding variables are
available in the next cycle. For example, if one decides to aggregate three consecutive
cycles, it is possible that a variable available in the first and third cycles is not available in
the second cycle (e.g. Generalized Anxiety Disorder scores only exist in the 1999-2004
cycles).
• Codebooks of categorical variables can change over time, meaning that a manual process
of reading the NHANES documentation, understanding codebook changes over time,
and developing code to harmonize those variables for a given selection of cycles may be
required (e.g. removal of Spanish-speaking countries codes from the country of birth
variable in 2011).
• NHANES data contain some “split-categorical variables” where a set of distinct variables
represents a single property. To understand the meaning of these variables, one is required
to carefully read the documentation to realize these split variables are indeed values of
a common property and that they are often used when the study may accept multiple
values for the property behind these split variables (e.g. several variables to characterize
health insurance coverage).
• NHANES data contain some “merged variables.” We consider a variable to be “merged”
when the values of the variable are from two or more distinct properties but are put
together as a single variable. An example of a merged variable in NHANES is the variable
about “drug usage”. We consider this variable to be merged because some of its values
are about “drug usage for disease treatment” while the other values are for “drug usage
for disease prevention.”
• None of the knowledge required to address the previous challenges can be obtained from
NHANES’ original data. Instead, this is knowledge provided as documentation that needs
to be interpreted by humans and translated into data preparation solutions based on code.</p>
        <p>An approach to mitigate the challenges above is for scientists to share their data preparation
code, hoping it will be very similar for someone doing data preparation with the same set of
selected variables. But, as explained above, simply using another cycle’s data and performing
the same analysis that was done in the past is likely to lead to incorrect results. There are
significant chances that the code may run and produce some results that are apparently correct
but biased. Thus, we do consider a risk for scientific accuracy the strategy of reusing existing
data analytic code without revisiting the overall NHANES documentation, understanding what
are the variables of interest in a selected set of cycles, and understanding changes that may
have occurred during selected cycles, every time a new data preparation criterion is established.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>3. Semantic Solutions</title>
      <p>Before we dive into our semantic infrastructure that enables semantic variable normalization,
we need to revisit some definitions and introduce the notion of semantic variable used in this
paper.</p>
      <sec id="sec-4-1">
        <title>3.1. Variables and Semantic Variables</title>
        <p>A Variable, from the point of view of a tabular data file, is a column in the file. Each variable
value, i.e., a value in a column of the table corresponding to our variable of concern, is the
measured, elicited, or simulated value of an entity’s attribute. For example, for the cycle
20172018 of NHANES there is a variable named RIDAGEYR that corresponds to the attribute “age’’ of
an entity of type “human subject’’, and it is stated in “years’’. We consider all information about
the variable (such as attribute, entity, and unit, in this example) as properties of the variable. For
example, “age’’ is the property Attribute of the variable, “human subject’’ is the property Entity
associated with the variable, and “years’’ is the property Unit of the variable. It is important
to mention that the US population in 2017-2018 is the property Population of the RIDAGEYR
variable for the 2018-2018 cycle.</p>
        <p>A Variable Specification is the description of the properties of a variable. The population “US
Population in 2017-18”, the attribute “age”, the entity “human subject”, and the unit “years”
are all part of the specification of the RIDAGEYR variable for the 2017-2018 cycle. We observe
that some properties are present in some variable specifications while others may be not.
For instance, not all variables required a property “Unit”, especially when these variables are
categorical like “Biological sex”. A comprehensive discussion about variable specification
formalization is beyond the scope of this paper. However, we would like to particularly stress
that variable specifications may be missing essential content if their properties Entity, Attribute,
and Population are not provided, or are provided as empty definitions.</p>
        <p>From our definition of Variable Specification, we define a Semantic Variable as a variable
specification that does not include a population property. From the variable definition above,
each variable is bound to a given population. When the only distinction between the set of
properties of any two variables is their populations, we would say that the two variables have
the same semantic variable, i.e., the two variables share a common semantic variable. In this
case, we can say that RIGAGEYR for the 2015-2016 cycle and RIDAGEYR for the 2017-2018 cycle
are two variables with the same semantic variable (“age of the participant in years”) reference.
In fact, the only distinction between these two variables is their populations: the population of
the first variable is the US population in 2015-2016 while the second is the US population in
2017-2018. The reuse of variable names across cycles is an informal way of NHANES handling
the notion that many variables share the same semantic variable. This however can quickly
become confusing for a new NHANES user since tools like the use of NHANES variable search 1
to look for RIDAGEYR would return multiple entries. For example, as shown in Figure 1, the
search for RIDAGEYR returns 11 entries, one entry for each cycle of NHANES’s continuous
period.</p>
      </sec>
      <sec id="sec-4-2">
        <title>3.2. HADatAc: A Data Ingestion Solution for Data Preparation</title>
        <p>
          A data ingestion is an activity within studies that, like data preparation, also manipulates the
content of data files. However, in contrast with data preparation that focuses on dataset generation,
data ingestion focuses on persisting study content in data stores (i.e. databases, search engines,
graphs, etc.) to support data analysis activities [
          <xref ref-type="bibr" rid="ref7 ref8 ref9">7, 8, 9</xref>
          ], as well as data harmonization activities
across studies [
          <xref ref-type="bibr" rid="ref10 ref11">10, 11</xref>
          ]. A data ingestion activity, by allowing each data value to be retrieved
from a single source, mitigates potential time-consuming tasks such as handling distinct data
ifle formats, unstructured data, data harmonization, missing values, provenance, and more.
        </p>
        <sec id="sec-4-2-1">
          <title>1https://wwwn.cdc.gov/nchs/nhanes/search/</title>
          <p>We use the Human-Aware Data Acquisition Framework (HADatAc) [12] to support a data
ingestion approach centered around the construction of a knowledge graph that comprehensively
describes a collection of scientific studies. HADatAc employs an extensive set of concepts and
associated terms used to represent studies’ components (i.e. activities, subjects, samples, etc.),
while logically connecting each data value to its related KG entities. Our data ingestion activity
follows a systematic approach for acquiring knowledge from ontologies, semantic documents,
and data files to build its knowledge graphs. With the use of data preparation criteria as
described in Section 4, datasets ready for data analysis are automatically generated from data
ingestion-generated knowledge graphs. The HADatAc data ingestion process also provides a
systematic, normalized, and reusable way of organizing variables and variable data than is not
an expected output of traditional extract-transform-load (ETL) tools, used in support of data
preparation.</p>
          <p>Figure 2 shows the role of a data ingestion process in the context of acquiring new knowledge
from a data file to use the data in support of machine learning. The entire process starts with the
acquisition of raw data from sources like physical instruments, questionnaires, and computer
models. From the raw data and through the use of several operations, a knowledge graph is
built with the use of data ingestion. Figure 2 assumes the use of data ingestion since its output
is a knowledge graph that is later used to generate datasets from data preparation requests.
HADatAc covers several aspectDsoafdtataainPgersteionpaandrdaattaiporepnaration as outlined above.</p>
          <p>HADatAc</p>
          <p>Data Ingestion</p>
          <p>Raw
Data</p>
          <p>Data Preparation
cleaning
integration</p>
          <p>Dataset
selection Prepared
Cleaned/In transformation Data
tegrated</p>
          <p>Data
Instruments
(including models and
questionnaires)</p>
          <p>Data Analytics</p>
          <p>Evaluation
Machine
Learning
patterns</p>
          <p>Knowledge
• It is a process that involves many different tasks and which cannot be fully automated.
Figure 2•: MDaantya opfrethpeardaattiaonprienptahraeticoonnatecxtitviotifedsaatrae irnoguetsintieo,nteadnidoudsa,taanadntaimlyteiccso.nsuming.
• It has been estimated that data preparation accounts for 60%-80% of the time spent on a data
mining project.</p>
        </sec>
      </sec>
      <sec id="sec-4-3">
        <title>3.3. Semantic Data Normalization</title>
        <p>Semantic data normalization is the process o[1f] https://www.datapreparator.com/what_is_data_preparation.html withoafdaoptraitigonisnal
transforming a dataset based on a set
variables of a given study into a corresponding set of normalized variables. The variable
normalization process consists of two steps: the first step is a manual analysis of any available
documentation and metadata of each original variable identifying its semantic variable
properties; the second step is the process of encoding the semantic variable properties as annotation
of the data. The list below shows essential semantic variables properties identified during the
normalization process:
• type of the variable’s entity of interest;
• type of the attribute that characterized the property of the variable’s entity of interest;
• in the case of continuous variables, and optionally for some categorical values, the
variable’s unit;
• in the case of categorical variables, their codebooks;
• any spatial restriction related to the variable, E.g., a location where the variable was
acquired;
• any temporal restriction related to the variable. E.g., when the variable was acquired.</p>
        <p>The information above about each variable is described in the NHANES documentation
through its data dictionaries, codebooks, file descriptions, interview descriptions, questionnaire
descriptions, and many other auxiliary pieces of documentation.</p>
        <p>After the properties of variables are annotated, the normalization process is considered
completed after the adjustment of original variables regarding split-variables and merged-variables.
Two or more original variables are said to be split-variables if they share a common semantic
variable, i.e., all the properties of their semantic variables are the same. NHANES data about
insurance coverage from survey participants is an example of merged variables. The Insurance
datasets contain about seven variables (depending on the cycle) to fully characterize insurance
coverage. Each variable contains the participation status of the survey participant in one
specific type of insurance (such as Medicaid, Medicare, Private insurance, etc.). However, we
understand insurance coverage as not the value of a single variable but the combination of
several variables insurance-related variables, all contributing to the insurance coverage attribute
of the participant. For example, we can only infer if a person does not have insurance coverage
if all variables contain the information of not being covered.</p>
        <p>Merged-variable adjustment occurs when one original variable in NHANES cannot be
represented by a single semantic variable i.e., the values of the original variable may require to be
separated into two or more distinct semantic variables. One example of a merged variable is the
Prescription Drug Usage dataset. This dataset’s contents convey information on drugs being
taken by survey participants to treat and/or prevent some diseases. The diseases and drugs
are identified by codes (such as ICD10-CM). However, the dataset organizes the diferentiation
between treatment and prevention by modifying the original ICD-10CM codes to append a ‘P‘
when the disease is being prevented (they remain unmodified for treatment).</p>
      </sec>
      <sec id="sec-4-4">
        <title>3.4. Semantic Faceted Data Search</title>
        <p>HADatAc provides a user interface where all the variables and studies are shown at once.
Variable normalization as described in Section 3.3 is a key enabler for a uniform faceted data
search for NHANES: semantic variable properties are indexed and treated as facets and used
to facilitate variable selection; variable availability can be explored by executing data search.
Therefore, through the use of a semantic faceted data search, one can browse and select available
studies, study data files, hierarchies of entities, hierarchies of attributes, codebooks, time
restrictions, space restrictions, and all of the above together.</p>
        <p>Once a user of the faceted search selects the desirable values in each facet, the user can press
the search button to verify if there is actual data matching the search request. If just a fraction
of the requested data is returned or if no value is returned, that means that not all requested
data is available. The search process can be done gradually since one can further perform a
search over the result of a previous search. By performing many searches, one is capable of
probing NHANES content for many combinations of cycles and variables.</p>
        <p>The machine’s capability of processing the search request described above and showing what
is available is the result of two features from HADAtAc: the indexing of available context, and
the fact that available content is data coming from normalized variables.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>4. Data Preparation Use-case: Demographic Determinants of</title>
    </sec>
    <sec id="sec-6">
      <title>Access to Care</title>
      <p>The use-case used as a running data analytics example is based on survey-weighted logistic
regression models and an equity-focused approach used to identify demographic and
socioeconomic factors associated with patients’ health care. A full description of the use case with the
complete set of data analysis results can be found at [13]. We first focus on the survey-weighted
logistic regression analysis. The task of selecting and preparing NHANES data for logistic
regression analysis in the R code requires a deep understanding of the internals of NHANES.</p>
      <p>To support this use-case, we produced several Semantic Data Dictionaries (SDDs) [14] (as
well as additional metadata templates required by HADatAc) to describe NHANES datasets2.
SDD is a specification that formalizes the assignment of a semantic representation of data,
which can enable standardization and harmonization across diverse datasets. Specifically, SDDs
allow the characterization of columns in tabular data using objects, attributes, and units defined</p>
      <sec id="sec-6-1">
        <title>2https://github.com/tetherless-world/nhanes-hadatac</title>
        <p>Column
RIDAGEYR
RIDRETH1</p>
        <p>Attribute
sio:SIO_001013
hhear:00609
attributeOf
??participant
??participant</p>
        <p>Unit
sio:SIO_000428
in existing ontologies. In addition, for columns containing categorical values, SDDs support the
representation of codebooks that resolve literal values to resources in ontologies.</p>
        <p>The SDDs covered four survey cycles and about 40 datasets. Table 1 shows part of the SDD that
models the RIDAGEYR and RIDETH1 variables (from the Demographics dataset). The RIDAGEYR
variable is defined as the attribute sio:SIO_001013 (“age”) of the survey participant (denoted
by SDD’s object notation ??participant), measured in the sio:SIO_000428 (“year”) unit. The
RIDETH1 variable is defined as the attribute hhear:00609 (“Race or Ethnicity Combined”) of
the survey participant. This variable does not have a unit because it is a categorical variable
with an associated codebook.</p>
        <p>We then used HADatAc to process all the produced SDDs and associated NHANES datasets
to bootstrap a knowledge graph using the metadata. As an example, Figure 4 shows the “Age in
years at screening” semantic variable RDF representation. Semantic variables are represented
as RDF resources that compose an SDD (using the partOfSchema predicate). We represent
semantic variable properties using specific predicates. In this case, we use hasUnit, hasEvent,
and hasEntity to assert unit, time, and entity properties. We also show how a semantic variable
is related to an object by using the isAttributeOf predicate. In this case, “Age in years at
screening” is an attribute of the survey participant.</p>
        <p>DAS-NHANES-DEMO
partOfSchema
partOfSchema
DASA-NHANES-DEMO-RIDAGEYR
DASO-NHANES-DEMO-participant
hasUnit</p>
        <p>Year
(sio:SIO_001013)
hasEvent</p>
        <p>DASO-NHANESDEMO-screening
hasEntity</p>
        <p>Human
(sio:SIO_000485)
isAttributeOf</p>
        <p>Once the NHANES Knowledge Graph was created within HADatAc, we utilized the semantic
faceted data search to select the desired NHANES cycles. Then, we selected the semantic
variables of interest, which included the race/ethnicity of survey participants, prescription drug
usage (only antidiabetic drugs), drug classification, and immunization. Based on this selection,
HADatAc generated a tabular dataset containing these semantic variables for analysis. More
details about the NHANES knowledge graph creation in HADatAc can be found in [15].</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>5. Results</title>
      <p>Utilizing the generated dataset, we examined equity of access to needed care with respect to
race/ethnicity in the United States with data prepared using the proposed approach. To illustrate
the flexibility of the approach, we looked at two problems: access of adult subjects with Type-2
Diabetes (T2D) to anti-diabetic drugs, and access to vaccines for hepatitis A (HAV), the hepatitis
B (HBV), and the human papillomavirus (HPV). A logistic regression model was constructed
as a function of race/ethnicity, age, gender, educational attainment, insurance type, poverty
level, comorbidity severity based on CCI, and HbA1c condition. The model calculates the odds
ratio (OR), which is the odds of drug/vaccination access and utility of a racial-ethnic subgroup
divided by the odds of the same healthcare source access and utility in a reference non-Hispanic
White group. The reader should consult [13] for full details of the analysis as well as a more
extensive analysis of equity of access with respect to other social determinants of health.</p>
      <p>Vaccine
NH Black
NH Asian
Hispanic
logistic regression model shows that, non-Hispanic Asians had a similar prescribing rate for
insulin compared to White populations, they had a disproportionate utilization based on the
overall U.S. racial/ethnic distribution among the T2DM population.</p>
    </sec>
    <sec id="sec-8">
      <title>6. Related Work</title>
      <p>The problem of systematically accessing variables in a setting like NHANES is not new and has
been somewhat explored in the literature. The NHANES Unified Dataset [ 17] was an efort to
integrate several NHANES datasets in a unified way using an API. One of the contributions
of this research was to support the examination beyond a few variables (usually constrained
to a single survey cycle), using a method that can combine multiple variables across several
NHANES survey cycles.</p>
      <p>The earlier work in [18] performed a similar, but constrained to a subset of variables, method to
preprocess NHANES’ datasets to classify variables in three categories (environmental chemicals,
health biomarkers, and questionnaire responses). In addition, this work performed several
finegrained variable normalizations based on the requirements of the study (such as the identification
of cardiovascular disease and diabetes). The normalized variables across the 1999-2010 cycles
were used in conjunction with their data analysis pipeline.</p>
      <p>In terms of facilitating data analysis from R environments, a few packages for working with
NHANES data exist. RNHANES [19] provides simple search capabilities for retrieving datasets
and variables from specific NHANES components (such as lab results) and cycles. This package
allows data to be downloaded and used directly. nhanesA [20] is a package that provides similar
features, while also allowing access to some of the associated metadata such as codebooks. This
metadata can be used in conjunction with data to resolve values, such as replacing codes with
their natural language values in the codebook.</p>
      <p>These previous eforts have provided solutions for specific parts of the challenge we are
tackling. Our work expands these earlier accomplishments and starts to provide a more
systematic method for formalizing semantic variables using semantic web technologies, as a basis for
building data preparation pipelines that have an increased level of automation.</p>
      <p>Going forward, the review in [21] suggests that “validation through independent replication
will be critical in data-driven studies”, in response to the problem that exposure measurement
errors are common. Our approach aims to support the consistent use of variables that can lead
to reproducibility.</p>
    </sec>
    <sec id="sec-9">
      <title>7. Conclusion</title>
      <p>We presented an approach for facilitating biomedical data preparation based on the notion
of semantic variables. In this work, we abstract the meaning of a variable and represent it
as a semantic variable, using semantic web technologies. A semantic variable is a human
understanding of a property of an entity (and related aspects such as a unit of measurement)
that can be shared among several variables. In a setting like NHANES, in which variables
are being revised and evolved in each cycle, leading to new variables being created, semantic
variables support data users in consistently finding and using relevant variables in their studies.</p>
      <p>We have demonstrated this approach in a cross-sectional subgroup disparity analysis of
2013-2018 NHANES (3 cohorts) on U.S. adults for receipt of diabetes treatments and vaccines
against Hepatitis A, Hepatitis B, and Human Papilloma. The results show that race/ethnicity is
a determinant in access to certain diabetes medication classes and certain vaccines. While our
current scenarios are based on NHANES’s cycle aggregation (which is very specific to NHANES),
the description of variable normalization and variable harmonization are generalizable to most
studies.</p>
      <p>In future work, we plan to continue applying this data preparation method to more analysis
pipelines. Specifically, we are currently developing an experiment intended to reproduce existing
studies based on NHANES and formally compare the obtained results in terms of the amount
of time reduced in data preparation and error mitigation. For this, we are seeking to develop
metrics that could quantify these aspects. This work could be directly generalized to the Health
Examination Survey Methods that are similar to NHANES in other nations including Brazil,
Chile, Colombia, Mexico, England, and Scotland [22]. By removing data preparation barriers
and supporting appropriate survey-weighted analyses of NHANES and related datasets, the
proposed machine-assisted approach can potentially help conduct and accelerate many future
public health studies leading to a better understanding of and improvements in human health.</p>
    </sec>
    <sec id="sec-10">
      <title>Acknowledgments</title>
      <p>This work was partially supported by IBM Research AI Horizons Network and NIEHS’ Human
Health Exposure Analysis Resource (HHEAR), project number 5U2CES026555-05. Further
thanks to Marcello P. Bax, Ph.D. who collaborated in the creation of Figure 2.
[12] P. Pinheiro, H. Santos, Z. Liang, Y. Liu, S. M. Rashid, D. L. McGuinness, M. P. Bax, HADatAc:
A Framework for Scientific Data Integration using Ontologies, in: The 17th International
Semantic Web Conference Posters &amp; Demonstrations Track, Monterey, CA, 2018.
[13] M. Qi, H. Santos, P. Pinheiro, D. L. McGuinness, K. P. Bennett, Demographic and
socioeconomic determinants of access to care: A subgroup disparity analysis using new
equity-focused measurements, Under review (2023).
[14] S. M. Rashid, J. P. McCusker, P. Pinheiro, M. P. Bax, H. Santos, J. A. Stingone, A. K. Das,
D. L. McGuinness, The Semantic Data Dictionary – An Approach for Describing and
Annotating Data, Data Intelligence 2 (2020) 443–486.
[15] H. Santos, P. Pinheiro, D. L. McGuinness, Knowledge Graph Construction from Data, Data
Dictionaries, and Codebooks: the National Health and Nutrition Examination Surveys
Use Case, in: 4th U.S. Semantic Technologies Symposium, Michigan State University, East
Lansing, MI, 2022.
[16] M. Qi, O. Cahan, M. A. Foreman, D. M. Gruen, A. K. Das, K. P. Bennett, Quantifying
representativeness in randomized clinical trials using machine learning fairness metrics,
JAMIA Open 4 (2021) ooab077.
[17] C. J. Patel, N. Pho, M. McDufie, J. Easton-Marks, C. Kothari, I. S. Kohane, P. Avillach, A
database of human exposomes and phenomes from the US National Health and Nutrition
Examination Survey, Scientific Data 3 (2016) 160096.
[18] S. M. Bell, S. W. Edwards, Identification and Prioritization of Relationships between
Environmental Stressors and Adverse Human Health Impacts, Environmental Health
Perspectives 123 (2015) 1193–1199.
[19] H. Susmann, RNHANES: Facilitates Analysis of CDC NHANES Data, 2016. URL: https:
//CRAN.R-project.org/package=RNHANES, R package version 1.1.0.
[20] C. Endres, nhanesA: NHANES Data Retrieval, 2023. URL: https://CRAN.R-project.org/
package=nhanesA, R package version 0.7.2.
[21] A. K. Manrai, Y. Cui, P. R. Bushel, M. Hall, S. Karakitsios, C. J. Mattingly, M. Ritchie,
C. Schmitt, D. A. Sarigiannis, D. C. Thomas, D. Wishart, D. M. Balshaw, C. J. Patel,
Informatics and Data Analytics to Support Exposome-Based Discovery for Public Health,
Annual Review of Public Health 38 (2017) 279–294.
[22] J. S. Mindell, A. Moody, A. I. Vecino-Ortiz, T. Alfaro, P. Frenz, S. Scholes, S. A.
Gonzalez, P. Margozzini, C. de Oliveira, L. M. Sanchez Romero, A. Alvarado, S. Cabrera, O. L.
Sarmiento, C. A. Triana, S. Barquera, Comparison of Health Examination Survey Methods
in Brazil, Chile, Colombia, Mexico, England, Scotland, and the United States, American
Journal of Epidemiology 186 (2017) 648–658.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Pyle</surname>
          </string-name>
          ,
          <article-title>Data Preparation for Data Mining</article-title>
          , Morgan Kaufmann, San Francisco, Calif,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A.</given-names>
            <surname>Ruiz</surname>
          </string-name>
          ,
          <source>The 80/20 data science dilemma</source>
          ,
          <year>2017</year>
          . URL: https://www.infoworld.com/article/ 3228245/the-80-20
          <article-title>-data-science-dilemma</article-title>
          .html.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>W.</given-names>
            <surname>Raghupathi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Raghupathi</surname>
          </string-name>
          ,
          <article-title>Big data analytics in healthcare: promise and potential</article-title>
          ,
          <source>Health Information Science and Systems</source>
          <volume>2</volume>
          (
          <year>2014</year>
          )
          <article-title>3</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Kung</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T. A.</given-names>
            <surname>Byrd</surname>
          </string-name>
          ,
          <article-title>Big data analytics: Understanding its capabilities and potential benefits for healthcare organizations</article-title>
          ,
          <source>Technological Forecasting and Social Change</source>
          <volume>126</volume>
          (
          <year>2018</year>
          )
          <fpage>3</fpage>
          -
          <lpage>13</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] Centers for Disease Control and Prevention (CDC)</article-title>
          .
          <source>National Center for Health Statistics (NCHS)</source>
          ,
          <source>National Health and Nutrition Examination Survey Data</source>
          ,
          <year>2023</year>
          . URL: https://www. cdc.gov/nchs/nhanes/.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>NHANES</given-names>
            <surname>Tutorials - Weighting Module</surname>
          </string-name>
          ,
          <year>2023</year>
          . URL: https://wwwn.cdc.gov/nchs/nhanes/ tutorials/weighting.aspx.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>C. H.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <article-title>Exploratory Data Analysis</article-title>
          ,
          <source>in: Psychology</source>
          , Oxford University Press,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>T. G.</given-names>
            <surname>Dietterich</surname>
          </string-name>
          ,
          <string-name>
            <surname>Machine-Learning</surname>
            <given-names>Research</given-names>
          </string-name>
          ,
          <source>AI Magazine</source>
          <volume>18</volume>
          (
          <year>1997</year>
          )
          <fpage>97</fpage>
          -
          <lpage>97</lpage>
          . Number:
          <volume>4</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>P.</given-names>
            <surname>Domingos</surname>
          </string-name>
          ,
          <article-title>A few useful things to know about machine learning</article-title>
          ,
          <source>Communications of the ACM</source>
          <volume>55</volume>
          (
          <year>2012</year>
          )
          <fpage>78</fpage>
          -
          <lpage>87</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>I.</given-names>
            <surname>Fortier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. R.</given-names>
            <surname>Burton</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. J.</given-names>
            <surname>Robson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Ferretti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Little</surname>
          </string-name>
          ,
          <string-name>
            <surname>F. L'Heureux</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Deschênes</surname>
            ,
            <given-names>B. M.</given-names>
          </string-name>
          <string-name>
            <surname>Knoppers</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Doiron</surname>
            ,
            <given-names>J. C.</given-names>
          </string-name>
          <string-name>
            <surname>Keers</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Linksted</surname>
            ,
            <given-names>J. R.</given-names>
          </string-name>
          <string-name>
            <surname>Harris</surname>
            , G. Lachance,
            <given-names>C.</given-names>
          </string-name>
          <string-name>
            <surname>Boileau</surname>
            ,
            <given-names>N. L.</given-names>
          </string-name>
          <string-name>
            <surname>Pedersen</surname>
            ,
            <given-names>C. M.</given-names>
          </string-name>
          <string-name>
            <surname>Hamilton</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          <string-name>
            <surname>Hveem</surname>
            ,
            <given-names>M. J.</given-names>
          </string-name>
          <string-name>
            <surname>Borugian</surname>
            ,
            <given-names>R. P.</given-names>
          </string-name>
          <string-name>
            <surname>Gallagher</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>McLaughlin</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Parker</surname>
            ,
            <given-names>J. D.</given-names>
          </string-name>
          <string-name>
            <surname>Potter</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <string-name>
            <surname>Gallacher</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Kaaks</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Sprosen</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Vilain</surname>
            ,
            <given-names>S. A.</given-names>
          </string-name>
          <string-name>
            <surname>Atkinson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Rengifo</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Morton</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Metspalu</surname>
            ,
            <given-names>H. E.</given-names>
          </string-name>
          <string-name>
            <surname>Wichmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Tremblay</surname>
            ,
            <given-names>R. L.</given-names>
          </string-name>
          <string-name>
            <surname>Chisholm</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Garcia-Montero</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Hillege</surname>
            ,
            <given-names>J.-E.</given-names>
          </string-name>
          <string-name>
            <surname>Litton</surname>
            ,
            <given-names>L. J.</given-names>
          </string-name>
          <string-name>
            <surname>Palmer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Perola</surname>
            ,
            <given-names>B. H.</given-names>
          </string-name>
          <string-name>
            <surname>Wolfenbuttel</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          <string-name>
            <surname>Peltonen</surname>
            ,
            <given-names>T. J.</given-names>
          </string-name>
          <string-name>
            <surname>Hudson</surname>
          </string-name>
          ,
          <article-title>Quality, quantity and harmony: the DataSHaPER approach to integrating data across bioclinical studies</article-title>
          ,
          <source>International Journal of Epidemiology</source>
          <volume>39</volume>
          (
          <year>2010</year>
          )
          <fpage>1383</fpage>
          -
          <lpage>1393</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>J.</given-names>
            <surname>Kalter</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. G.</given-names>
            <surname>Sweegers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>I. M.</given-names>
            <surname>Verdonck-de Leeuw</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Brug</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. M.</given-names>
            <surname>Bufart</surname>
          </string-name>
          ,
          <article-title>Development and use of a flexible data harmonization platform to facilitate the harmonization of individual patient data for meta-analyses</article-title>
          ,
          <source>BMC Research Notes</source>
          <volume>12</volume>
          (
          <year>2019</year>
          )
          <fpage>164</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>