<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" article-type="research-article" dtd-version="2.0">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v10i4e36481</article-id>
      <article-id pub-id-type="pmid">35416792</article-id>
      <article-id pub-id-type="doi">10.2196/36481</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Big Data Health Care Platform With Multisource Heterogeneous Data Integration and Massive High-Dimensional Data Governance for Large Hospitals: Design, Development, and Application</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Lovis</surname>
            <given-names>Christian</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Lei</surname>
            <given-names>Jianbo</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Meng</surname>
            <given-names>Weihua</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author">
          <name name-style="western">
            <surname>Wang</surname>
            <given-names>Miye</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-4137-0310</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Li</surname>
            <given-names>Sheyu</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0060-0287</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Zheng</surname>
            <given-names>Tao</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6726-0710</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Li</surname>
            <given-names>Nan</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7933-3101</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Shi</surname>
            <given-names>Qingke</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2324-875X</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Zhuo</surname>
            <given-names>Xuejun</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-0366-6997</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Ding</surname>
            <given-names>Renxin</given-names>
          </name>
          <degrees>BSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-2911-8152</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Huang</surname>
            <given-names>Yong</given-names>
          </name>
          <degrees>MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Engineering Research Center of Medical Information Technology</institution>
            <institution>West China Hospital of Sichuan University</institution>
            <institution>Ministry of Education</institution>
            <addr-line>Information Center, West China Hospital</addr-line>
            <addr-line>No. 37, Guoxue Road, Wuhou District</addr-line>
            <addr-line>Chengdu, Sichuan Province, 610041</addr-line>
            <country>China</country>
            <phone>86 18980601030</phone>
            <email>huangyong@wchscu.cn</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6424-1928</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Engineering Research Center of Medical Information Technology</institution>
        <institution>West China Hospital of Sichuan University</institution>
        <institution>Ministry of Education</institution>
        <addr-line>Chengdu, Sichuan Province</addr-line>
        <country>China</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Endocrinology and Metabolism</institution>
        <institution>MAGIC China Centre, Cochrane China Centre</institution>
        <institution>West China Hospital, Sichuan University</institution>
        <addr-line>Chengdu</addr-line>
        <country>China</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Yong Huang <email>huangyong@wchscu.cn</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>4</month>
        <year>2022</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>13</day>
        <month>4</month>
        <year>2022</year>
      </pub-date>
      <volume>10</volume>
      <issue>4</issue>
      <elocation-id>e36481</elocation-id>
      <history>
        <date date-type="received">
          <day>16</day>
          <month>1</month>
          <year>2022</year>
        </date>
        <date date-type="rev-request">
          <day>4</day>
          <month>2</month>
          <year>2022</year>
        </date>
        <date date-type="rev-recd">
          <day>17</day>
          <month>2</month>
          <year>2022</year>
        </date>
        <date date-type="accepted">
          <day>25</day>
          <month>2</month>
          <year>2022</year>
        </date>
      </history>
      <copyright-statement>©Miye Wang, Sheyu Li, Tao Zheng, Nan Li, Qingke Shi, Xuejun Zhuo, Renxin Ding, Yong Huang. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 13.04.2022.</copyright-statement>
      <copyright-year>2022</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2022/4/e36481" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>With the advent of data-intensive science, a full integration of big data science and health care will bring a cross-field revolution to the medical community in China. The concept <italic>big data</italic> represents not only a technology but also a resource and a method. Big data are regarded as an important strategic resource both at the national level and at the medical institutional level, thus great importance has been attached to the construction of a big data platform for health care.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>We aimed to develop and implement a big data platform for a large hospital, to overcome difficulties in integrating, calculating, storing, and governing multisource heterogeneous data in a standardized way, as well as to ensure health care data security.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>The project to build a big data platform at West China Hospital of Sichuan University was launched in 2017.  The West China Hospital of Sichuan University big data platform has extracted, integrated, and governed data from different departments and sections of the hospital since January 2008. A master–slave mode was implemented to realize the real-time integration of multisource heterogeneous massive data, and an environment that separates heterogeneous characteristic data storage and calculation processes was built. A business-based metadata model was improved for data quality control, and a standardized health care data governance system and scientific closed-loop data security ecology were established.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>After 3 years of design, development, and testing, the West China Hospital of Sichuan University big data platform was formally brought online in November 2020. It has formed a massive multidimensional data resource database, with more than 12.49 million patients, 75.67 million visits, and 8475 data variables. Along with hospital operations data, newly generated data are entered into the platform in real time. Since its launch, the platform has supported more than 20 major projects and provided data service, storage, and computing power support to many scientific teams, facilitating a shift in the data support model—from conventional manual extraction to self-service retrieval (which has reached 8561 retrievals per month).</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The platform can combine operation systems data from all departments and sections in a hospital to form a massive high-dimensional high-quality health care database that allows electronic medical records to be used effectively and taps into the value of data to fully support clinical services, scientific research, and operations management. The West China Hospital of Sichuan University big data platform can successfully generate multisource heterogeneous data storage and computing power. By effectively governing massive multidimensional data gathered from multiple sources, the West China Hospital of Sichuan University big data platform provides highly available data assets and thus has a high application value in the health care field. The West China Hospital of Sichuan University big data platform facilitates simpler and more efficient utilization of electronic medical record data for real-world research.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>big data platform in health care</kwd>
        <kwd>multisource</kwd>
        <kwd>heterogeneous</kwd>
        <kwd>data integration</kwd>
        <kwd>data governance</kwd>
        <kwd>data application</kwd>
        <kwd>data security</kwd>
        <kwd>data quality control</kwd>
        <kwd>big data</kwd>
        <kwd>data science</kwd>
        <kwd>medical informatics</kwd>
        <kwd>health care</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <sec>
        <title>Background</title>
        <p>Emerging technologies, such as big data, the Internet of Things, cloud computing, and artificial intelligence, are profoundly changing medical and health care service models. Health and medical data sets, which are typically large with rapid growth, diverse data structure, multidimensional value density, high requirements of data credibility, and high concerns over data security, are often called health care big data. The term <italic>big data</italic> is used to represent not only a technology but also a resource and a method—a big data platform is a system and a tool that integrates data, tools, apps, and service.</p>
        <p>Driven by national policies, high-income countries in Europe, such as the United Kingdom [<xref ref-type="bibr" rid="ref1">1</xref>], and in North America, such as the United States [<xref ref-type="bibr" rid="ref2">2</xref>], took the lead in building big data platforms for health care [<xref ref-type="bibr" rid="ref3">3</xref>]. For example, Britain’s comprehensive platform integrates and applies data from 12 categories, including health, medical care, transportation, and environment, to support government decision-making [<xref ref-type="bibr" rid="ref3">3</xref>]. The Big Data Analytics Platform built by the Czech Republic meets the data analysis requirements of its national public health service [<xref ref-type="bibr" rid="ref4">4</xref>]. In recent years, China has built a national-level health information platform that can be connected to provincial-level health information platforms for data integration [<xref ref-type="bibr" rid="ref5">5</xref>].</p>
        <p>In addition to national-level big data platforms in health care that are driven by policies, large health care institutions have also built big data platforms to suit their own management needs. At present, a medium-sized health care institution in China generates 1 to 20 TB of health care data, and a large health care institution generates 300 TB to 1 PB of health care data every year. Some hospitals have used big data technology to build hospital-level scientific research platforms—for example, Ninewells Hospital and Medical School in the United Kingdom developed a research data management platform [<xref ref-type="bibr" rid="ref6">6</xref>], Asan Medical Center in South Korea developed a clinical trial management system based on integrated data [<xref ref-type="bibr" rid="ref7">7</xref>], and the People's Hospital of Peking University in China developed a hospital-wide big data platform for clinical research [<xref ref-type="bibr" rid="ref8">8</xref>]—or to build hospital-wide data integration platform—for example, the Third Hospital of Peking University [<xref ref-type="bibr" rid="ref9">9</xref>] and the Second Affiliated Hospital of Guangzhou University of Traditional Chinese Medicine [<xref ref-type="bibr" rid="ref10">10</xref>]. Most hospitals use big data technology in analytics platforms for diseases (eg, for nasopharyngeal carcinoma [<xref ref-type="bibr" rid="ref11">11</xref>]), gastrointestinal conditions [<xref ref-type="bibr" rid="ref12">12</xref>], cancer [<xref ref-type="bibr" rid="ref13">13</xref>], and cardiomyopathies [<xref ref-type="bibr" rid="ref14">14</xref>].</p>
        <p>Meta-analyses [<xref ref-type="bibr" rid="ref15">15</xref>-<xref ref-type="bibr" rid="ref18">18</xref>] have found that big data platforms in health care have had great impacts on have had great impacts on medical technology, medical service quality, and medical costs, but the actual construction process is not easy, with challenges arising in data structurization, security, standardization, storage, processing, and management [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. As a result, the value mined from this type of data is currently limited [<xref ref-type="bibr" rid="ref17">17</xref>], and in China, health care data utilization is still in the early stage [<xref ref-type="bibr" rid="ref18">18</xref>], which necessitates the improvement of health care big data governance.</p>
      </sec>
      <sec>
        <title>Objectives</title>
        <p>Health care data generated in large hospitals include (1) electronic medical records of clinical diagnosis and treatment, which contain diagnoses, prescriptions, surgical treatments, and examination findings; (2) data derived from health management or clinical research activities, including follow-up information, gene sequencing data, and physical examination data; (3) data related to hospital management, including patient wait times, bed turnover rate, medical equipment utilization efficiency, and revenue; and (4) data derived from web-based diagnosis and treatment services [<xref ref-type="bibr" rid="ref19">19</xref>]. To make better use of medical data, the first task is to build a big data platform for data collection and governance to generate high-quality data assets. This will enable in-depth data analysis and mining, as well as the formation of rules of knowledge, allowing big data methods to benefit clinical practice, scientific research, and hospital management.</p>
        <p>In addition to the technical considerations for platform construction, data management in large hospitals must take into account by data service management. Special attention should be paid to patient privacy protection and ethical concerns on data use. A hospital data platform is generally built for a specific purpose, such as scientific research, operations, data integration, or analysis, but large hospitals often require a comprehensive data platform—one that meets needs for medical treatment, education, scientific research, and management.</p>
        <p>The overall objective of this study was to develop and implement a health care big data platform for a large hospital in China, with data governance as the core concept, to solve difficulties related to integration, calculation, storage, standardization, and security for multisource heterogeneous medical data. This platform will integrate the data from all operation systems in a hospital to generate high-quality data assets and form a massive high-dimensional medical database that can comprehensively support the clinical activities, scientific research, and management of the hospital.</p>
        <p>From a technical aspect, construction of a big data platform needs to solve the following problems that are unique to the health care industry: (1) integration of multisource heterogeneous data from multiple independent information systems within the hospital; (2) computing power requirements brought by the development of machine learning and deep learning during data application; (3) difficulties in analyzing and utilizing information data (due to nonuniform data standards, inconsistent use of a master patient index, and the fact that most electronic medical records in China are written in natural language, it is impossible to directly analyze and use existing information data, and as a result, semantic interoperability must be improved with the use of medical terminology) and (4) data security and patient privacy protection.</p>
      </sec>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Overview</title>
        <p>The West China Hospital of Sichuan University (WCH) built a health care big data platform, which is referred to as the WCH-BDP or <italic>the platform</italic> hereafter. WCH is a world-renowned large hospital with more than 4800 beds and approximately 15,000 outpatients on average per day. WCH’s electronic medical record system was built in 2007; therefore, it has been in use for 14 years. The hospital has more than 100 departments and sections, and their clinical activities generate a massive amount of data.</p>
        <p>Traditional information technology can no longer handle massive amounts of data that are continuously growing, causing difficulties in effectively integrating multisource heterogeneous data, the serious problem of isolated data islands, bottlenecks in data storage and calculation, difficulties in structurally utilizing medical records written in Chinese semantics, and high technical barriers in mining data from images, videos, and files. In 2017, WCH launched a hospital-wide health care big data platform project to address these difficulties.</p>
        <p>The project focuses on the design and development of the platform architecture and does not involve any study of clinical data, so ethical declarations are not applicable.</p>
      </sec>
      <sec>
        <title>Project Organization</title>
        <p>The first step of platform construction was organizing a project management team. To ensure the performance of the platform, WCH set up 2 working groups—one for platform construction, and the other for platform management. The construction working group included the chief platform architect, information technology experts, system engineers, and data engineers. The hospital information center was responsible for building the platform. The construction working group focused on the following: (1) the application objectives of the platform, (2) data integration method and scope, (3) master patient index strategy, (4) reference standards for medical terms, (5) scope of the master data, (6) data model structure, and (7) system implementation and training. Project meetings were held weekly and status meetings were held monthly to summarize the progress of the phases until the platform was launched. The discussions in these meetings provided a solid foundation for platform design and development. After the launch of the platform, the construction working group also conducted regular training on system functions, maintenance, and the help manual.</p>
        <p>The management working group included all stakeholders, such as the chief information officer, hospital management users, clinical users, and scientific research users. The management group was the data governance committee responsible for organizing and overseeing all data-related work, including data definitions, data benchmarking, data quality control, and data security, after the launch of the platform. The committee was in charge of formulating related management systems, work collaboration mechanisms, and procedure standardization.</p>
      </sec>
      <sec>
        <title>WCH-BDP Framework Design Strategy</title>
        <p>The convergence of multisource heterogeneous data from all operation systems in the hospital was necessary to ultimately provide data to different medical services (<xref rid="figure1" ref-type="fig">Figure 1</xref>). Therefore, the design strategy was to use computing and storage devices with enough capacity to integrate data into the corresponding physical resources, with separate storage and computing processes based on the characteristics of the modality (eg, clinical data, image data, or genomic data). A data repository was built using data governance methods to meet the needs of different subject fields. The platform had to be able to combine all data service supports, such as data security service, terminology service for data governance, search engine service, virtualization service, and artificial intelligence service—all of which rely on the computing power and storage capacity of physical devices and data resources. Solutions for data integration and governance were core aspects of the construction process. Data governance, which is the core of data management and the basis for standardizing disordered data into highly available data, includes master index data governance, master data governance, metadata governance, data security management, and data quality control management [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>].</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Big data platform architecture.</p>
          </caption>
          <graphic xlink:href="medinform_v10i4e36481_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Storage and Calculation</title>
        <p>Massive data were collectively stored in the storage devices of the WCH-BDP. To better support data analysis, storage and calculation environments were designed and provided according to the characteristics of each data modality. Generally, the amount of data structuration is negatively correlated with storage space and computing power (ie, the greater the data structuration, the lower the requirements for storage space and computing power) (<xref rid="figure2" ref-type="fig">Figure 2</xref>). Hence, data that are poorly structured require more storage space and stronger computing power.</p>
        <p>Highly structured data do not require much storage space. They can be stored on a distributed storage device, and computations can be effectively run by conventional central processing units.</p>
        <p>Semistructured data, such as the records of a patient’s major complaint, disease history, examination findings, and examination conclusions in Chinese electronic medical records do not occupy much storage space and can be stored in distributed storage devices. However, these data require natural language processing for analysis; therefore, both general graphics processing units (GPUs) and central processing units are needed to provide sufficient computing power.</p>
        <p>Unstructured data that are large in total volume but small in individual volume (eg, the original image data in DICOM format generated by thin-layer scanning examinations such as radiology and ultrasound) require a relatively high storage space and must be stored in centralized storage devices (mostly network-attached storage) to save resources. To analyze and mine these data, characteristic modeling is performed mainly with machine learning or deep learning technologies, which requires the support of a large amount of GPU power and private GPU resources.</p>
        <p>Unstructured data with a large individual volume, such as genomic data, are generally stored directly in object-based storage. Genomic sequencing generates not only a large amount of original sequencing data, but also, a large amount of data related to multiple processes in research on biological information. As a result, genomic data sets often have a tremendous size, and the storage space that is required is mostly measured in petabytes. Analysis and mining of the types of data stored in object-based storage require a lot of clustered computing power supplied by multiple high-performance GPUs, which necessitates the deployment of accelerated supercomputing power supported by GPU clusters.</p>
        <p>Traditional big data platforms are planned and implemented in a unified way with storage and computing integration. The design of the WCH-BDP is the realization of storage and computation separation. The WCH-BDP first solves the problem of effective storage and management of massive genomic data files. Second, when researchers use genetic data for analysis, the scheduling software provided by the WCH-BDP loads the analysis data into the supercomputer environment for analysis. After the analysis is completed, the analysis results are retained, and the temporary storage space occupied by the analysis process is released.</p>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>The relationship between the degree of data structuration and storage and computing capability.</p>
          </caption>
          <graphic xlink:href="medinform_v10i4e36481_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Integration</title>
        <p>In China, medical institution operations information database systems mainly include Microsoft SQL Server, Oracle database, MySQL database, Caché database, and MongoDB; other unstructured data are mostly stored in the form of files. The WCH-BDP achieves data integration through both real-time and non–real-time data entries. For real-time data integration, a master–slave database is generated, and the log data of the slave database are parsed and captured in real time. Real-time data integration is suitable for an operations information system with mostly structured data. Parsing the information in the slave database does not consume much physical resources and therefore does not affect the performance of the master database, which ensures the security and stability of data integration. Image data integration and entry can be completed by directly reading image files using the DICOM protocol. Genomic data and other data in the form of files are not integrated in real time and are entered via file transfer protocol.</p>
      </sec>
      <sec>
        <title>Master Index Governance</title>
        <p>The enterprise master patient index is the unique tag of a patient in a health care institution. One patient might have different enterprise master patient indexes in the different operating systems of a hospital because these systems were constructed independently. This necessitated a master patient index governance to standardize the enterprise master patient indexes. The governance of the master index data is achieved through the master index governance system. The governance system included 4 stages: data preparation, standardization strategy, data processing, and tracking or feedback (<xref rid="figure3" ref-type="fig">Figure 3</xref>).</p>
        <p>The data governance strategy of the WCH-BDP mainly focused on 3 key values: ID number, name, and telephone number. The configurations and data processing of these 3 key values are shown in the following table (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <p>Master index data processing cannot rely only on the system for automatic completion. For example, in the fifth row of <xref ref-type="table" rid="table1">Table 1</xref>, both the Name and Telephone number are <italic>Equal</italic>, but the ID card number is <italic>Unequal</italic>, which might be because the same patient used a different ID card for registration. In this case, the last step for standardization of the master index is critical, during which the uniqueness of each master index can be ensured by manual adjustment after log analysis or by referring to the actual operational process.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Flowchart  of master index governance.</p>
          </caption>
          <graphic xlink:href="medinform_v10i4e36481_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Governance strategy of enterprise master patient index.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <col width="250"/>
            <thead>
              <tr valign="top">
                <td>ID number</td>
                <td>Name</td>
                <td>Telephone number</td>
                <td>Result</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Equal</td>
                <td>Equal</td>
                <td>Equal</td>
                <td>Accept</td>
              </tr>
              <tr valign="top">
                <td>Equal</td>
                <td>Equal</td>
                <td>Unequal</td>
                <td>Accept</td>
              </tr>
              <tr valign="top">
                <td>Equal</td>
                <td>Unequal</td>
                <td>Equal</td>
                <td>Accept</td>
              </tr>
              <tr valign="top">
                <td>Equal</td>
                <td>Unequal</td>
                <td>Unequal</td>
                <td>Denied</td>
              </tr>
              <tr valign="top">
                <td>Unequal</td>
                <td>Equal</td>
                <td>Equal</td>
                <td>Accept</td>
              </tr>
              <tr valign="top">
                <td>Unequal</td>
                <td>Equal</td>
                <td>Unequal</td>
                <td>Denied</td>
              </tr>
              <tr valign="top">
                <td>Unequal</td>
                <td>Unequal</td>
                <td>Equal</td>
                <td>Denied</td>
              </tr>
              <tr valign="top">
                <td>Unequal</td>
                <td>Unequal</td>
                <td>Unequal</td>
                <td>Denied</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Master Data Governance</title>
        <p>Master data include all related data items listed in the data dictionary, such as health care institution code, drug code, diagnosis code, and anesthesia method [<xref ref-type="bibr" rid="ref22">22</xref>] (<xref ref-type="table" rid="table2">Table 2</xref>). Master data governance is the aim to map and handle master data discrepancies caused by different system standards. Classification and reference standards for the master data to be processed are determined, and they are used to map relationships between data in the database. The results are published to users for subscription and application.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Example of the WCH-BDP master data reference standard.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="200"/>
            <col width="120"/>
            <col width="680"/>
            <thead>
              <tr valign="top">
                <td>Classification of master data</td>
                <td>Number of reference standards</td>
                <td>Example</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Classification of diseases</td>
                <td>5</td>
                <td> ICD-10GB/<italic>t</italic> 14396-2016 Classification and codes of diseasesGB/<italic>t</italic> 15657-1995 Classification and codes of diseases and ZHENG of traditional Chinese medicine</td>
              </tr>
              <tr valign="top">
                <td>Basic industry information</td>
                <td>6</td>
                <td>GB 11714-1997 Rules of coding for the representation of organizationGB/<italic>t</italic> 13745-2009 Classification and code of disciplinesGB/<italic>t</italic> 2260-2007 Codes for the administrative divisions of the People's Republic of China</td>
              </tr>
              <tr valign="top">
                <td>Health informatics</td>
                <td>20</td>
                <td>GB/<italic>t</italic> 21715-2020 Health informatics—Patient healthcard dataGB/<italic>t</italic> 24465-2009 Health informatics. Health indicators conceptual frameworkGB/<italic>t</italic> 25512-2010 Health informatics-guidelines on data protection to facilitate trans-border flows of personal health informationGB/<italic>t</italic> 30107-2013 Health informatics.HL7 Version 3.Reference information modelGB/Z 24464-2009 Health informatics-Electronic health record-definition, scope and contextGB/Z 28623-2012 Health informatics. Interoperability and compatibility in messaging and communication standards. Key characteristics</td>
              </tr>
              <tr valign="top">
                <td>Personal information</td>
                <td>12</td>
                <td>GB/<italic>t</italic> 2261-2003 Classification and codes of basic personal informationGB/<italic>t</italic> 4658-2006 Codes for record of formal schoolingGB/<italic>t</italic> 4761-2008 Codes for family relationshipGB/<italic>t</italic> 6565-2009 Classification and codes of occupationsGB/<italic>t</italic> 8561-2001 Code of professional technical position</td>
              </tr>
              <tr valign="top">
                <td>Information technology</td>
                <td>3</td>
                <td>GB/<italic>t</italic> 34960.1-2017 Information technology service－Governance GB/<italic>t</italic> 39725-2020 Information security technology—Guide for health data security</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Metadata Governance</title>
        <sec>
          <title>Metadata Governance Process</title>
          <p>Metadata are the bridge between the data and the data users. They describe the content (what), coverage (where, when), quality, management method, owner (who), and provision method (how) of data. The metadata governance approach used by the WCH-BDP is shown in <xref rid="figure4" ref-type="fig">Figure 4</xref>.</p>
          <p>In the WCH-BDP, a unified metadata model for identifying the registered original data was designed and constructed based on the standards of the Common Warehouse Metamodel of the Object Management Group. Based on the metadata directory, the relationship for data mapping is configured to initiate data extraction. The mapping results are saved in terms of the configured relationship and compared with the standard terminology and tags in the metadata management system. All extracted data are stored in the platform’s data repository, which provides data services to the application layer using standardized metadata, terminology, and tags.</p>
          <fig id="figure4" position="float">
            <label>Figure 4</label>
            <caption>
              <p>Metadata governance architecture.</p>
            </caption>
            <graphic xlink:href="medinform_v10i4e36481_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
          </fig>
        </sec>
        <sec>
          <title>Terminology Standardization</title>
          <p>Terminology standardization is an important step in metadata governance. The WCH-BDP uses medical terminology from the Chinese Open Medical and Healthcare Alliance to standardize the terminology in the metadata system.</p>
        </sec>
        <sec>
          <title>Governance of Tag Data</title>
          <p>Tagging is also one of the more effective methods used for data governance. Unlike terminology synonyms, the <italic>tag</italic> is an attribute that reflects the application of data [<xref ref-type="bibr" rid="ref23">23</xref>]. Tag data are more suitable for the preprocessing scenario of comparing or calculating a large amount of data, such as the change in the value of a test result before versus after surgery, or the range of patient blood pressure change before and after taking a medication. The governance of tag data should consider the app objectives and continuously track and maintain tag data.</p>
        </sec>
        <sec>
          <title>Natural Language Processing Governance</title>
          <p>Many medical records and reports with descriptions written in Chinese are difficult to process due to the unique characteristics of the Chinese language. Currently, in China, one mainstream post–structured data processing method is the use of machine learning technology combined with health care terminology to segment words and refine concepts from Chinese text [<xref ref-type="bibr" rid="ref11">11</xref>]. It is common practice to optimize the word segmentation algorithm model by comparing the word segmentation results with standard terms and aggregating the comparison results, through which a comprehensive corpus and a more accurate word segmentation algorithm can be developed. The algorithm model and the content of the corpus may depend on disease type, regional culture, and even writing habits; therefore, these factors had to be considered during construction.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Security Management</title>
        <sec>
          <title>Overview</title>
          <p>Data utilization and security are contradictory. To ensure proper and secure data use, all countries have issued laws and regulations on the security of health and medical data. Referring to relevant international and domestic laws and regulations on security protection, the WCH-BDP uses a <italic>5S</italic> (ie, data security, app security, use security, management security, and ownership security) control system for data storage, access, use, and transformation of scientific and technological achievements.</p>
        </sec>
        <sec>
          <title>Data Security</title>
          <p>Data security refers to data classification and hierarchical management security. Scholars from Harvard University have proposed that a data classification system should be established to ensure data security according to the laws and regulations of Health Insurance Portability and Accountability Act and related ethical regulations on scientific research [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>]. In the WCH-BDP, data security has 5 levels, with 3 dimensions: affected object, degree of impact, and scope of impact. The data access interface with corresponding restrictions is provided to each level accordingly (<xref ref-type="table" rid="table3">Table 3</xref>).</p>
          <table-wrap position="float" id="table3">
            <label>Table 3</label>
            <caption>
              <p>Data security strategy of the big data platform.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="100"/>
              <col width="130"/>
              <col width="280"/>
              <col width="320"/>
              <col width="170"/>
              <thead>
                <tr valign="top">
                  <td>Security classification</td>
                  <td>Security level</td>
                  <td>Descriptions</td>
                  <td>Examples</td>
                  <td>Precautions</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Level 1</td>
                  <td>Most confidential</td>
                  <td>Hypersensitive information</td>
                  <td>Financial data, personal authentication data</td>
                  <td>A specified environment for a specified single individual to use</td>
                </tr>
                <tr valign="top">
                  <td>Level 2</td>
                  <td>Confidential</td>
                  <td>Highly sensitive information</td>
                  <td>Credit data, personal health privacy data</td>
                  <td>A specified environment for a specified single role to use</td>
                </tr>
                <tr valign="top">
                  <td>Level 3</td>
                  <td>Secret</td>
                  <td>General sensitive information</td>
                  <td>Personal information during diagnosis and treatment, contract information, employee management data of employees</td>
                  <td>Use after the role group is authorized</td>
                </tr>
                <tr valign="top">
                  <td>Level 4</td>
                  <td>Internal use only</td>
                  <td>Information that is not publicly disclosed</td>
                  <td>Organizational structure, basic information of employees, general data after desensitization</td>
                  <td>Use after internal authorization</td>
                </tr>
                <tr valign="top">
                  <td>Level 5</td>
                  <td>Open to the public</td>
                  <td>Data that can be publicly disclosed</td>
                  <td>Summarized results obtained by statistical analysis</td>
                  <td>Public access or use</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>App Security</title>
          <p>App security refers to the data app security management of a system during its processes. In the WCH-BDP, a unified master data authentication service is provided for user authentication so that each app system manages only role and app permissions required by the system itself. When an actual role user uses an app, data desensitization and encryption are completed through the unified platform service interface to ensure the security of the data app.</p>
        </sec>
        <sec>
          <title>Use Security</title>
          <p>Use security refers to the security management during the processes of data processing, use, and analysis. The National Institutes of Health has emphasized that special attention should be paid to privacy protection in data apps [<xref ref-type="bibr" rid="ref26">26</xref>]. Patient information that needs to be desensitized generally includes all of the information that can be directly and indirectly linked to or used to locate the patient, including name, ID, telephone number, address, contact information, information related to infectious disease [<xref ref-type="bibr" rid="ref27">27</xref>]. The WCH-BDP ensures patient privacy protection through desensitization, encryption (<xref ref-type="table" rid="table4">Table 4</xref>), and multiparty computation.</p>
          <p>Multiparty computation is a controllable and measurable method proposed by a Turing Award winner, Qizhi Yao, to solve the problem of data abuse [<xref ref-type="bibr" rid="ref28">28</xref>]. Before statistical analysis of massive data, the multiparty computation service gateways in the WCH-BDP are deployed to complete all data calculations in the security domain and provide the final calculation results to users through the platform service. This process can effectively manage data use security.</p>
          <table-wrap position="float" id="table4">
            <label>Table 4</label>
            <caption>
              <p>Data desensitization and encryption policies of big data platform.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="210"/>
              <col width="290"/>
              <col width="500"/>
              <thead>
                <tr valign="top">
                  <td>Name of strategy</td>
                  <td>Scope of data involved</td>
                  <td>Design of desensitization and encryption policy</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Digital data</td>
                  <td>Operating revenue, key quantity...</td>
                  <td>Fuzzy rounding method or fuzzy percentage method</td>
                </tr>
                <tr valign="top">
                  <td>Structured data of fixed length</td>
                  <td>Identification card number, telephone number, name...</td>
                  <td>Replace or encrypt from the starting bit to the end of the specified length range</td>
                </tr>
                <tr valign="top">
                  <td>Text data of varying length</td>
                  <td>Address, electronic medical record, descriptive diagnosis (infectious disease)</td>
                  <td>Locating sensitive content, then replace or encrypt sensitive characters</td>
                </tr>
                <tr valign="top">
                  <td>Image data</td>
                  <td>Radiological, ultrasonic and pathological imaging data</td>
                  <td>In image files, encryption algorithm is used for desensitization and watermarking is configured</td>
                </tr>
                <tr valign="top">
                  <td>File data</td>
                  <td>Genomics, molecular protein data</td>
                  <td>Locating sensitive content and rename sensitive characters</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Management Security</title>
          <p>Management security of platform data requires that all platform services, including data services, be completed under secure closed-loop management. In the WCH-BDP, all tasks—data access, management, and governance; data analysis, utilization, and mining; and the transformation and realization of scientific research findings—are completed through platform services for data resources, storage, computing power, and network access. Establishment of the management security system can effectively guarantee the security of the data utilization process.</p>
        </sec>
        <sec>
          <title>Ownership Security</title>
          <p>Currently, most research findings are obtained in a laboratory or scientific research setting but are difficult to apply in an actual production setting, which directly leads to a low transformation rate of research achievements and insufficient recognition of intellectual property rights. In the WCH-BDP, through the integrated service gateway that connects to the real service operation scenario, published research findings can be directly introduced into clinical practice, realizing the translation of scientific research to the clinic. In this process, the design of the integrated service gateway management system can effectively ensure researcher’s ownership security.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Quality Management</title>
        <sec>
          <title>Overview</title>
          <p>Data quality management is a continuous process and an important link in data governance. Health care data quality management in the WCH-BDP involves the following steps: (1) building a data quality standard system; (2) evaluating current data quality; (3) analyzing data quality problems; (4) developing and optimizing the solutions in detail to solve problems; and (5) establishing a data quality control knowledge database for future reference. The steps above are continuously iterated to form a closed-loop system for health care data quality management.</p>
        </sec>
        <sec>
          <title>Standards of Data Quality</title>
          <p>Common data quality problems include data outliers, duplications, data without any clear relationships, orphaned data records, and data that make no logical sense medically. Fully referring to the evaluation and grading standards of electronic medical records issued by the National Health Commission of China and research findings by experts in the field of health care [<xref ref-type="bibr" rid="ref29">29</xref>-<xref ref-type="bibr" rid="ref31">31</xref>], we developed a standard system for data quality control using the dimensions <italic>consistency</italic>, <italic>integrity</italic>, <italic>integrability</italic>, <italic>timeliness</italic>, and <italic>stability</italic> as parameters for evaluation (<xref ref-type="table" rid="table5">Table 5</xref>).</p>
          <table-wrap position="float" id="table5">
            <label>Table 5</label>
            <caption>
              <p>Data quality standard system.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="140"/>
              <col width="450"/>
              <col width="240"/>
              <col width="170"/>
              <thead>
                <tr valign="top">
                  <td>Dimension</td>
                  <td>Content of the dimension</td>
                  <td>Quality indicator</td>
                  <td>Rule</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Consistency</td>
                  <td>Check whether the data value is in the dictionary domain</td>
                  <td>Consistency rate</td>
                  <td>Higher than 90%</td>
                </tr>
                <tr valign="top">
                  <td>Integrality</td>
                  <td>Check the completeness of the required data</td>
                  <td>Percentage of integrality</td>
                  <td>Higher than 80%</td>
                </tr>
                <tr valign="top">
                  <td>Relevance</td>
                  <td>Check the relationship between key data</td>
                  <td>Degree of relevance</td>
                  <td>Higher than 95%</td>
                </tr>
                <tr valign="top">
                  <td>Timeliness</td>
                  <td>Check the logical validity of time-type data</td>
                  <td>Timeliness ratio</td>
                  <td>Higher than 80%</td>
                </tr>
                <tr valign="top">
                  <td>Uniqueness</td>
                  <td>Check whether data duplication exists</td>
                  <td>Repetitive rate</td>
                  <td>Lower than 0.01%</td>
                </tr>
                <tr valign="top">
                  <td>Stability</td>
                  <td>Check whether the fluctuation of data volume is abnormal</td>
                  <td>Fluctuation ratio</td>
                  <td>Lower than 20%</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Process Quality Control</title>
          <p>In addition to data quality control for original data, quality control management of procedures in operations are included [<xref ref-type="bibr" rid="ref21">21</xref>]. Data quality problems reflect problems in operations processes. By formulating a plan that optimized data quality by improving management and operational protocols, the WCH-BDP achieved its goal of controlling the quality of operations to obtain high-quality data outputs. Data quality management is a continuous optimization process that requires the participation of all personnel involved.</p>
        </sec>
      </sec>
      <sec>
        <title>Data Service Support</title>
        <p>The WCH-BDP is an environment that can effectively support data services with voluminous data repositories and strong physical resources for data computation and storage. Under an overall ecology of data security management, the platform can provide support to data services such as computing, storage, and virtualization. Search engine services, terminology services, and artificial intelligence services can be effectively integrated to meet the needs of all health care operations.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>General</title>
        <p>The WCH-BDP was formally launched in November 2020, after 3 years of construction, for demand surveys, platform design, module development, and pilot operation. To date, the platform has formed a massive high-dimensional database with more than 12.49 million patients, 75.67 million visits, and 8475 data variables. The platform has brought hospital informatization to a new level and greatly improves the hospital’s overall big data capabilities.</p>
      </sec>
      <sec>
        <title>Computing Power</title>
        <p>The WCH-BDP has more than 20 PB data storage capacity and runs on a server cluster consisting of 252 physical servers: 117 servers are dedicated to computing and analyzing, and 38 are equipped with more than one GPU card. In the server cluster dedicated to computing, there are 320 CPU cores and 149 GPU cards. In total, the platform has computing powers that exceed 300 TFLOPS for clinic data, 600 TFLOPS for image data, and 1000 TFLOPS for genomic data.</p>
      </sec>
      <sec>
        <title>Scope of Data Integration</title>
        <p>The WCH-BDP integrates diagnosis and treatment data from clinical information systems, clinical research data from science and research information systems, and management activity data from management information systems. Of 134 hospital systems, the platform has integrated the data of 27 systems, including hospital information systems, laboratory information systems, radiology, ultrasound, web-based medical appointments, human resources, equipment and supply management, Internet medical service since January 2008. In addition, all image data in the picture and communication systems and more than 20,000 patients’ genomic data have been entered into the platform.</p>
      </sec>
      <sec>
        <title>Database</title>
        <p>Using Fast Healthcare Interoperability Resources Reference Information Model 3.0 standards, data integrated into the WCH-BDP were reorganized and arranged based on the type of operational activities while considering the characteristics of China’s medical system. Finally, a database that includes 134 data charts for 18 subject fields was developed. The top 5 subject fields that were responsible for the most data in the database are listed in <xref ref-type="table" rid="table6">Table 6</xref>. To date, the database includes 8475 data variables and 6.272 billion rows of data records.</p>
        <table-wrap position="float" id="table6">
          <label>Table 6</label>
          <caption>
            <p>Top-5 subject fields in terms of number of data rows.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="70"/>
            <col width="150"/>
            <col width="80"/>
            <col width="130"/>
            <col width="120"/>
            <col width="450"/>
            <thead>
              <tr valign="top">
                <td>Number</td>
                <td>Subject field</td>
                <td>Tables, n</td>
                <td>Data variables, n</td>
                <td>Rows (10,000×n)</td>
                <td>Systems involved</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Medical record</td>
                <td>10</td>
                <td>476</td>
                <td>369824.53</td>
                <td>Hospital information system, online diagnosis and treatment system</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Medical technology</td>
                <td>6</td>
                <td>502</td>
                <td>115073.35</td>
                <td>Electrocardiogram system, radiology information system, echocardiography system, endoscopic system, dynamic electrocardiogram system, pathology information system, ultrasonic system, laboratory information system, interventional surgical workstation, medical technology reservation information system, outpatient information system, physical examination information system</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Fee</td>
                <td>8</td>
                <td>440</td>
                <td>60855.24</td>
                <td>Hospital information system, physical examination information system, online diagnosis and treatment system</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Medical advice</td>
                <td>3</td>
                <td>395</td>
                <td>21366.64</td>
                <td>Hospital information system, online diagnosis and treatment system</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Staff</td>
                <td>13</td>
                <td>802</td>
                <td>18138.94</td>
                <td>Hospital information system, physical examination information system, electronic data capture, human resource system</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Data Asset Directory</title>
        <p>The platform has constructed a data asset directory for users by further standardizing the data through the governance of master data, metadata, terminology, and natural language processing. To ease the process of inquiry, the directory has a hierarchical tree structure that allows users to select the data items that they need using fuzzy searches. To minimize comprehension difficulties, the directory uses a data variable–naming scheme consistent with the names in the interface of the corresponding operations systems as much as possible; in addition, users can see the information of the data source, content, and range of values.</p>
        <p>The data asset directory covers 13 fields and 1488 data variables (<xref ref-type="table" rid="table7">Table 7</xref>). Of the 13 fields, the original data variables in 9 fields are structured variables, and those in 3 fields (medical records, imaging examinations, and nursing care records) are semistructured text. Semistructured data were converted into poststructured derived variables by using approaches such as word segmentation, entity extraction, and semantic identification. For patient tag information, the app-oriented poststructured derived variables were generated using a data-mining algorithm.</p>
        <table-wrap position="float" id="table7">
          <label>Table 7</label>
          <caption>
            <p>List of data assets.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="70"/>
            <col width="250"/>
            <col width="140"/>
            <col width="140"/>
            <col width="400"/>
            <thead>
              <tr valign="top">
                <td>Number</td>
                <td>Directory field</td>
                <td>Data variable (unit)</td>
                <td>Types of variables</td>
                <td>Example</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>1</td>
                <td>Demographic</td>
                <td>91</td>
                <td>Structured</td>
                <td>Gender, age, occupation, present address, nationality, height, weight, blood type</td>
              </tr>
              <tr valign="top">
                <td>2</td>
                <td>Basic medical information</td>
                <td>410</td>
                <td>Structured</td>
                <td>Appointment date, visit date, clinic department, clinic type, supervising doctor, the department transferred to, admission date, discharge date, discharge state</td>
              </tr>
              <tr valign="top">
                <td>3</td>
                <td>Medical record information</td>
                <td>123</td>
                <td>Unstructured</td>
                <td>Admit note, progress note, discharge record</td>
              </tr>
              <tr valign="top">
                <td>4</td>
                <td>Clinical diagnostic information</td>
                <td>47</td>
                <td>Structured</td>
                <td>Clinic diagnosis, emergency diagnosis, admitting diagnosis, discharge diagnosis, medical insurance diagnosis, pathological diagnosis</td>
              </tr>
              <tr valign="top">
                <td>5</td>
                <td>Surgical and operational information</td>
                <td>138</td>
                <td>Structured</td>
                <td>Name of operation, name of procedure, surgeon, surgical grade, anesthesia grading, incision type, level of healing</td>
              </tr>
              <tr valign="top">
                <td>6</td>
                <td>Diagnosis and treatment information</td>
                <td>166</td>
                <td>Structured</td>
                <td>Type of medical order, drug name, usage, dosage, frequency, execution time of medical order</td>
              </tr>
              <tr valign="top">
                <td>7</td>
                <td>Laboratory test data</td>
                <td>147</td>
                <td>Structured</td>
                <td>White blood cell count, red blood cell count, sodium level, uric acid level, blood glucose level, creatinine level</td>
              </tr>
              <tr valign="top">
                <td>8</td>
                <td>Imaging results</td>
                <td>124</td>
                <td>Unstructured</td>
                <td>Magnetic resonance imaging, computed tomography, x-ray, ultrasound, digital radiography</td>
              </tr>
              <tr valign="top">
                <td>9</td>
                <td>Nursing record information</td>
                <td>53</td>
                <td>Unstructured</td>
                <td>Admission assessment, daily records, nursing records</td>
              </tr>
              <tr valign="top">
                <td>10</td>
                <td>Physiological monitoring data</td>
                <td>50</td>
                <td>Structured</td>
                <td>Vital signs</td>
              </tr>
              <tr valign="top">
                <td>11</td>
                <td>Scale evaluation data</td>
                <td>50</td>
                <td>Structured</td>
                <td>Mood index, pressure ulcer assessment, risk assessment of falling out of bed</td>
              </tr>
              <tr valign="top">
                <td>12</td>
                <td>Medical cost information</td>
                <td>65</td>
                <td>Structured</td>
                <td>Name of charge items, amount of charge items, settlement time</td>
              </tr>
              <tr valign="top">
                <td>13</td>
                <td>Patient label information</td>
                <td>24</td>
                <td>Unstructured</td>
                <td>Patients with lower test results after surgery, patients with higher blood pressure after medication</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
      </sec>
      <sec>
        <title>Assessment of WCH-BDP Performance</title>
        <sec>
          <title>Service Support to Major Projects</title>
          <p>Supported by the data services of the platform, the research teams of WCH have constructed more than 120 disease databases for different research aims, including a number of national-level multicenter disease databases. Since it was launched, the platform has supported more than 20 clinical and hospital management research projects, of which, 3 have won second prize in the State Science and Technology Progress Award of China and first and second prizes in the Sichuan Provincial Science and Technology Progress Award.</p>
          <p>The platform’s support of basic research is exemplified by a project on the mechanisms of allosteric regulation and signal transduction of G protein–coupled receptors conducted by the State Key Laboratory of Sichuan University; using the storage and computing power provided by the WCH-BDP, the research team revealed the microconversions of key amino acids during allosteric regulation, which laid the foundation for the design and screening of G protein–coupled receptor–targeting small molecule allosteric regulators (unpublished, X. Yang, PhD, 2022).</p>
          <p>Another example of the platform’s support of clinical research is a lung cancer research project at WCH. Using the data resources, storage resources, computing power, and exploration environment provided by the platform, the lung cancer research team identified and validated high-sensitivity high-specificity markers for early diagnosis of lung cancer [<xref ref-type="bibr" rid="ref32">32</xref>], and the team further developed the first lung cancer database and artificial intelligence–assisted product for lung nodule diagnosis in China [<xref ref-type="bibr" rid="ref33">33</xref>]; these papers [<xref ref-type="bibr" rid="ref32">32</xref>,<xref ref-type="bibr" rid="ref33">33</xref>] are listed in Essential Science Indicators—published in <italic>Cell</italic> (impact factor 41.582) and <italic>Signal Transduction and Targeted Therapy</italic> (impact factor 18.187). Research results have also been published in internationally renowned academic journals, such as <italic>Medical Image Analysis</italic> (impact factor 11.148) [<xref ref-type="bibr" rid="ref34">34</xref>] and <italic>Nature Biomedical Engineering</italic> (impact factor 25.671) [<xref ref-type="bibr" rid="ref35">35</xref>].</p>
          <p>Artificial intelligence–assisted products for lung nodule diagnosis can detect 3 mm to 5 mm pulmonary nodules with 98.8% accuracy through artificial intelligence technology, which was significantly better than the performance of domestic and foreign specialists (79.9% of doctors with senior experience in Peking Union Medical College, only 40.9% of those with junior experience), and the average reading of each chest computed tomography (CT) can save 3 to 5 minutes [<xref ref-type="bibr" rid="ref33">33</xref>]. In 2020, the system was used in more than 100 hospitals nationwide, including in West China Hospital of Sichuan University. It not only improves the efficiency of chest CT image reading, but also reduces the rate of missed diagnosis of small pulmonary nodules. It also plays an important role in realizing the homogeneity of early diagnosis of lung cancer.</p>
          <p>Using this platform, research on segmentation of adrenal glands from CT images [<xref ref-type="bibr" rid="ref36">36</xref>], in which a novel 2-stage deep neural network for adrenal gland segmentation in an end-to-end fashion was proposed, used data resources, storage resources, computing capabilities, and the exploration environment provided by the WCH-BDP platform. The research data set contained 348 CT volumes acquired from 348 patients, which was used to verify the performance of the new method and show that the new cascaded framework outperformed, with respect to accuracy, state-of-the-art deep learning in segmenting the adrenal gland [<xref ref-type="bibr" rid="ref36">36</xref>].</p>
        </sec>
        <sec>
          <title>Changes in the Conventional Data Service Model</title>
          <p>The launch of the WCH-BDP has led to tremendous changes in the data service model of the hospital (<xref ref-type="table" rid="table8">Table 8</xref>). Users used to rely on information systems personnel for data use, but now they can analyze data by themselves throughout the entire process. Using the search engine service provided by the platform, researchers can quickly retrieve data from the databases to form a disease database suitable for real-world research, which is then introduced into the information exploration environment for data statistical analysis and mining.</p>
          <table-wrap position="float" id="table8">
            <label>Table 8</label>
            <caption>
              <p>Changes between the traditional and the present data service.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="160"/>
              <col width="390"/>
              <col width="450"/>
              <thead>
                <tr valign="top">
                  <td>
                    <break/>
                  </td>
                  <td>Traditional data services</td>
                  <td>Data services base on the platform</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Data visualization</td>
                  <td>Data not visible</td>
                  <td>Users can visually view the available data catalog</td>
                </tr>
                <tr valign="top">
                  <td>Data retrieval</td>
                  <td>Data engineers develop code through experience</td>
                  <td>Users can customize the search format and output format through the search engine and preview the results</td>
                </tr>
                <tr valign="top">
                  <td>Data approval</td>
                  <td>Data are available after ethical review and clinical study program approval</td>
                  <td>Data are available after ethical review and clinical study program approval</td>
                </tr>
                <tr valign="top">
                  <td>Data mining</td>
                  <td>Use your own computer to analyze data</td>
                  <td>Development environment and tools, such as R, SPSS, and Python, can be used on the platform, and computing power provided by the platform can be called by data mining algorithm</td>
                </tr>
                <tr valign="top">
                  <td>Data download and access</td>
                  <td>Download the data which data engineers develop and perform encryption</td>
                  <td>The platform creates accounts with different permissions for registered users. In a network environment after security authentication, authorized users can log in to the big data platform unified portal through virtual desktop infrastructure. The platform provides each authorized user with private storage space of different capacities. Users can directly store their research results in this space, or install the software developed by our college on their personal computers to transfer the research results to personal computers</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
          <p>The launch of the WCH-BDP has substantially improved the capacity of data services (<xref ref-type="table" rid="table9">Table 9</xref>). The scope of usable data in the platform is 3.37 times that of the previous level, an increase from 8 operation systems covered by the previous data warehouse to 27 systems by the big data platform. The dimensions of usable data are 1.8 times those of the previous level, an increase from 803 data variables to 1488 variables. The amount of usable data is 2.4 times the previous level, increasing from 6.8 billion rows of data records to 16.49 billion rows.</p>
          <p>The engineers completed 996 instances of manual data service in the 6 months before the launch of the platform (monthly mean 166). In contrast, 8561 self-service data retrievals were completed each month after the launch of the platform—a 51-fold increase in service efficiency. Each person could complete 2 instances of data services each day before but could complete 65 instances per day after the launch of the platform due to the help offered by the automated search engine—a 37-fold increase. In addition, the platform shortened the average duration of each data service 30-fold, from 4.5 hours to 0.15 hours. The platform substantially improved the volume and efficiency of data services.</p>
          <table-wrap position="float" id="table9">
            <label>Table 9</label>
            <caption>
              <p>Comparison of data service capabilities.</p>
            </caption>
            <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
              <col width="340"/>
              <col width="330"/>
              <col width="330"/>
              <thead>
                <tr valign="top">
                  <td> </td>
                  <td>Before the launch</td>
                  <td>After the launch</td>
                </tr>
              </thead>
              <tbody>
                <tr valign="top">
                  <td>Number of business systems covered</td>
                  <td>8</td>
                  <td>27</td>
                </tr>
                <tr valign="top">
                  <td>Data dimension</td>
                  <td>803</td>
                  <td>1488</td>
                </tr>
                <tr valign="top">
                  <td>Data volume (billion)</td>
                  <td>6.8</td>
                  <td>16.49</td>
                </tr>
                <tr valign="top">
                  <td>Number of monthly services</td>
                  <td>166</td>
                  <td>8561</td>
                </tr>
                <tr valign="top">
                  <td>Time per request (hour)</td>
                  <td>4.5</td>
                  <td>0.15</td>
                </tr>
              </tbody>
            </table>
          </table-wrap>
        </sec>
        <sec>
          <title>Improvement of Data App Security</title>
          <p>Data security is a key focus of the platform. In the past, data security relied mostly on the professional ethics of data engineers. In contrast, in this platform, which automatically manages data and provides data services, data security management is mostly system-based and manually assisted because all operation activities leave footprints in the system. This can prevent the abuse of individual permissions and effectively ensure data security.</p>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <p>The performance of the WCH-BDP has demonstrated that data resources can be effectively converged and governed to form highly usable data assets that have extremely high application value in the field.</p>
      <p>The success of the construction of a big data platform in health care is based on the following: (1) The project is managed with a strong organizational structure that has a top-down data governance committee involving multiple parties. The committee leads and oversees data governance duties. (2) The project is led by an information technology department that can provide technical support. The information technology team should have excellent skills and be familiar with the operations and data connotations of all systems in the hospital. (3) All departments and sections of the hospital should participate in the project, and detailed demand surveys and analyses should be performed. (4) The project requires sufficient scientific knowledge in medical informatics, management, and engineering to ensure smooth integration of medicine, management, and informatics for overall framework design. (5) The ethics office and clinical research management sections of the hospital should participate in the project to ensure patient privacy protection and data security. (6) The construction project needs suppliers who have rich experience and can provide sufficient technical support. (7) A sufficient amount of servers are needed for data storage and computation. (8) The project needs sufficient financial support.</p>
      <p>Similarities between the WCH-BDP and other data platforms [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref14">14</xref>] are that they provide data services through data integration, need to complete data integration, have various medical data, can provide structured data services, and can provide massive data retrieval. However, there are 6 differences: (1) The WCH-BDP integrates all business system data, while most other platforms integrate data on demand. (2) Our platform parses database logs and migrates full business data to the data center in a master–slave database synchronization mode. Some of the platforms use API interfaces to implement data migration. (3) The WCH-BDP accesses data constantly and in real time. Nevertheless, some other data platforms often access data by the day. (4) While most other data platforms only integrate clinical data, the WCH-BDP integrates both clinical data and hospital management data. (5) Most other data platform may not have supercomputing capability. After integrating supercomputing capability, the WCH-BDP can store more than 20 PB and calculate faster than 1900 TFLOPS. (6) Most other platforms can only provide conventional data storage and processing functions by disease type. The WCH-BDP provides an analysis environment equipped with data mining tools, including open-source tools, such as R and Python, and paid apps, such as SAS and SPSS. Researchers can use distributed clusters for data mining.</p>
      <p>The WCH-BDP can be further improved and optimized by (1) connecting more operations systems of the hospital to the platform and continuously optimizing the data governance strategies; (2) further utilizing and mining the data (eg, exploring multimodal artificial intelligence apps in health care); (3) making the platform a multicenter public platform by launching transdisciplinary, cross-hospital, cross-regional collaborations and including more medical information data; and (4) providing the hospital with further full-cycle <italic>standardization + security + service</italic> big data services.</p>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CT</term>
          <def>
            <p>computed tomography</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">GPU</term>
          <def>
            <p>graphics processing unit</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">WCH</term>
          <def>
            <p>West China Hospital of Sichuan University</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">WCH-BDP</term>
          <def>
            <p>West China Hospital of Sichuan University big data platform</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was sponsored by the National Health Commission (Big data integration and application platform construction of West China Hospital of Sichuan University). Thanks are due to Engineering Research Center of Medical Information Technology, West China of Public Medical Information Services Co Ltd, Shanghai ClinBrain Co Ltd, and New H3C Technology Co Ltd for assistance with the development of data integration and data governance. </p>
    </ack>
    <fn-group>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</label>
        <nlm-citation citation-type="web">
          <article-title>Find open data</article-title>
          <source>UK Government Digital Service</source>
          <access-date>2010-10-20</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.data.gov.uk">https://www.data.gov.uk</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="web">
          <source>U.S. Department of Health &#38; Human Services</source>
          <access-date>2010-09-01</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://www.healthdata.gov/">http://www.healthdata.gov/</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhen</surname>
              <given-names>TM</given-names>
            </name>
            <name name-style="western">
              <surname>Gu</surname>
              <given-names>JL</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>YQ</given-names>
            </name>
            <name name-style="western">
              <surname>Mu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Song</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Dou</surname>
              <given-names>WJ</given-names>
            </name>
          </person-group>
          <article-title>Development of health care big data at home and aboard and the application prospect in health decision support</article-title>
          <source>Soft Sci Health</source>
          <year>2019</year>
          <month>02</month>
          <day>17</day>
          <volume>33</volume>
          <issue>2</issue>
          <fpage>76</fpage>
          <lpage>79</lpage>
          <pub-id pub-id-type="doi">10.3969/j. issn. 1003－2800. 2019. 02. 017</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Štufi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bačić</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Stoimenov</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Big data analytics and processing platform in Czech Republic healthcare</article-title>
          <source>Appl Sci (Basel)</source>
          <year>2020</year>
          <month>03</month>
          <day>02</day>
          <volume>10</volume>
          <issue>5</issue>
          <fpage>1705</fpage>
          <lpage>1705.23</lpage>
          <pub-id pub-id-type="doi">10.3390/app10051705</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>G H</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>X D</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X G</given-names>
            </name>
            <name name-style="western">
              <surname>Hu</surname>
              <given-names>J P</given-names>
            </name>
          </person-group>
          <article-title>Design of data governance system based on national health information platform construction</article-title>
          <source>Chin J Health Inform Manag</source>
          <year>2019</year>
          <volume>16</volume>
          <issue>2</issue>
          <fpage>131</fpage>
          <lpage>134</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1672-5166.2019.02.02</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref6">
        <label>6</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Nind</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Galloway</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>McAllister</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Scobbie</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Bonney</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Hall</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Tramma</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Reel</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Groves</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Appleby</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Doney</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Guthrie</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Jefferson</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>The research data management platform (RDMP): a novel, process driven, open-source tool for the management of longitudinal cohorts of clinical data</article-title>
          <source>GigaScience</source>
          <year>2018</year>
          <month>07</month>
          <day>01</day>
          <volume>7</volume>
          <fpage>1</fpage>
          <lpage>12</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://academic.oup.com/gigascience/article-lookup/doi/10.1093/gigascience/giy060"/>
          </comment>
          <pub-id pub-id-type="doi">10.1093/gigascience/giy060</pub-id>
          <pub-id pub-id-type="medline">29790950</pub-id>
          <pub-id pub-id-type="pii">5001426</pub-id>
          <pub-id pub-id-type="pmcid">PMC6041881</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref7">
        <label>7</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Yoon</surname>
              <given-names>YJ</given-names>
            </name>
            <name name-style="western">
              <surname>Koo</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Beck</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Kim</surname>
              <given-names>TW</given-names>
            </name>
          </person-group>
          <article-title>Utilization of a clinical trial management system for the whole clinical trial process as an integrated database: system development</article-title>
          <source>J Med Internet Res</source>
          <year>2018</year>
          <month>04</month>
          <day>24</day>
          <volume>20</volume>
          <issue>4</issue>
          <fpage>e103</fpage>
          <lpage>e103</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2018/4/e103/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/jmir.9312</pub-id>
          <pub-id pub-id-type="medline">29691212</pub-id>
          <pub-id pub-id-type="pii">v20i4e103</pub-id>
          <pub-id pub-id-type="pmcid">PMC5941091</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>MX</given-names>
            </name>
            <name name-style="western">
              <surname>Ding</surname>
              <given-names>YJ</given-names>
            </name>
            <name name-style="western">
              <surname>Dong</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>GW</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>BT</given-names>
            </name>
          </person-group>
          <article-title>Development of a big medical database system for clinical research and practice of medical data governance</article-title>
          <source>Chin J Med Sci Manage</source>
          <year>2021</year>
          <month>04</month>
          <day>21</day>
          <volume>02</volume>
          <issue>34</issue>
          <fpage>81</fpage>
          <lpage>86</lpage>
          <pub-id pub-id-type="doi">10.3760/cma.j.cnl13565-20201012-00320</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ji</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Jia</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Integration platform and data integration application based on big data</article-title>
          <source>Chin J Health Inform Manag</source>
          <year>2017</year>
          <month>08</month>
          <day>20</day>
          <volume>04</volume>
          <issue>14</issue>
          <fpage>525</fpage>
          <lpage>529</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1672-5166.2017.04.01</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>MY</given-names>
            </name>
          </person-group>
          <article-title>Discussion on big data governance and system construction of hospital health care</article-title>
          <source>Chin J Libr Inf Sci Tradit Chin Med</source>
          <year>2019</year>
          <month>06</month>
          <day>15</day>
          <volume>03</volume>
          <issue>43</issue>
          <fpage>1</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.2095-5707.2019.03.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>CF</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>XD</given-names>
            </name>
            <name name-style="western">
              <surname>Lv</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>BY</given-names>
            </name>
            <name name-style="western">
              <surname>Zhu</surname>
              <given-names>BW</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Development and implementation of a dynamically updated big data intelligence platform from electronic health records for nasopharyngeal carcinoma research</article-title>
          <source>Br J Radiol</source>
          <year>2019</year>
          <month>10</month>
          <day>04</day>
          <volume>92</volume>
          <issue>1102</issue>
          <fpage>92:20190255</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31430186"/>
          </comment>
          <pub-id pub-id-type="doi">10.1259/bjr.20190255</pub-id>
          <pub-id pub-id-type="medline">31430186</pub-id>
          <pub-id pub-id-type="pmcid">PMC6774598</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Feng</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Peng</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Data-enabled digestive medicine: a new big data analytics platform</article-title>
          <source>IEEE/ACM Trans Comput Biol and Bioinf</source>
          <year>2021</year>
          <month>5</month>
          <day>1</day>
          <volume>18</volume>
          <issue>3</issue>
          <fpage>922</fpage>
          <lpage>931</lpage>
          <pub-id pub-id-type="doi">10.1109/tcbb.2019.2951555</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cha</surname>
              <given-names>HS</given-names>
            </name>
            <name name-style="western">
              <surname>Jung</surname>
              <given-names>JM</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>SY</given-names>
            </name>
            <name name-style="western">
              <surname>Jang</surname>
              <given-names>YM</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>JW</given-names>
            </name>
            <name name-style="western">
              <surname>Chung</surname>
              <given-names>SH</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>KS</given-names>
            </name>
          </person-group>
          <article-title>The Korea cancer big data platform (K-CBP) for cancer research</article-title>
          <source>Int J Environ Res Public Health</source>
          <year>2019</year>
          <month>06</month>
          <day>28</day>
          <volume>16</volume>
          <issue>13</issue>
          <fpage>16, 2290</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=ijerph16132290"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/ijerph16132290</pub-id>
          <pub-id pub-id-type="medline">31261630</pub-id>
          <pub-id pub-id-type="pii">ijerph16132290</pub-id>
          <pub-id pub-id-type="pmcid">PMC6651426</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sammani</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Jansen</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Linschoten</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Bagheri</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>de Jonge</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Kirkels</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>van Laake</surname>
              <given-names>LW</given-names>
            </name>
            <name name-style="western">
              <surname>Vink</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>van Tintelen</surname>
              <given-names>JP</given-names>
            </name>
            <name name-style="western">
              <surname>Dooijes</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Te Riele</surname>
              <given-names>ASJM</given-names>
            </name>
            <name name-style="western">
              <surname>Harakalova</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Baas</surname>
              <given-names>AF</given-names>
            </name>
            <name name-style="western">
              <surname>Asselbergs</surname>
              <given-names>FW</given-names>
            </name>
          </person-group>
          <article-title>UNRAVEL: big data analytics research data platform to improve care of patients with cardiomyopathies using routine electronic health records and standardised biobanking</article-title>
          <source>Neth Heart J</source>
          <year>2019</year>
          <month>05</month>
          <day>27</day>
          <volume>27</volume>
          <issue>9</issue>
          <fpage>426</fpage>
          <lpage>434</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/31134468"/>
          </comment>
          <pub-id pub-id-type="doi">10.1007/s12471-019-1288-4</pub-id>
          <pub-id pub-id-type="medline">31134468</pub-id>
          <pub-id pub-id-type="pii">10.1007/s12471-019-1288-4</pub-id>
          <pub-id pub-id-type="pmcid">PMC6712144</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Kruse</surname>
              <given-names>CS</given-names>
            </name>
            <name name-style="western">
              <surname>Goswamy</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Raval</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Marawi</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Challenges and opportunities of big data in health care: a systematic review</article-title>
          <source>JMIR Med Inform</source>
          <year>2016</year>
          <month>11</month>
          <day>21</day>
          <volume>4</volume>
          <issue>4</issue>
          <fpage>e38</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2016/4/e38/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.5359</pub-id>
          <pub-id pub-id-type="medline">27872036</pub-id>
          <pub-id pub-id-type="pii">v4i4e38</pub-id>
          <pub-id pub-id-type="pmcid">PMC5138448</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Krishnan</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Big data and clinicians: a review on the state of the science</article-title>
          <source>JMIR Med Inform</source>
          <year>2014</year>
          <month>01</month>
          <day>17</day>
          <volume>2</volume>
          <issue>1</issue>
          <fpage>e1</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2014/1/e1/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.2913</pub-id>
          <pub-id pub-id-type="medline">25600256</pub-id>
          <pub-id pub-id-type="pii">v2i1e1</pub-id>
          <pub-id pub-id-type="pmcid">PMC4288113</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Niu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Scott</surname>
              <given-names>SR</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lan</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Using electronic medical record data for research in a health care information and management systems society (HIMSS) analytics electronic medical record adoption model (EMRAM) stage 7 hospital in Beijing: cross-sectional study</article-title>
          <source>JMIR Med Inform</source>
          <year>2021</year>
          <month>08</month>
          <day>03</day>
          <volume>9</volume>
          <issue>8</issue>
          <fpage>e24405</fpage>
          <lpage>e24405&#124;p.101</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2021/8/e24405/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/24405</pub-id>
          <pub-id pub-id-type="medline">34342589</pub-id>
          <pub-id pub-id-type="pii">v9i8e24405</pub-id>
          <pub-id pub-id-type="pmcid">PMC8371484</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Li</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pollard</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Johnson</surname>
              <given-names>AEW</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Fan</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Xue</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Celi</surname>
              <given-names>LA</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Promoting secondary analysis of electronic medical records in China: summary of the PLAGH-MIT critical data conference and health datathon</article-title>
          <source>JMIR Med Inform</source>
          <year>2017</year>
          <month>11</month>
          <day>14</day>
          <volume>5</volume>
          <issue>4</issue>
          <fpage>e43</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://medinform.jmir.org/2017/4/e43/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/medinform.7380</pub-id>
          <pub-id pub-id-type="medline">29138126</pub-id>
          <pub-id pub-id-type="pii">v5i4e43</pub-id>
          <pub-id pub-id-type="pmcid">PMC5705855</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>ZY</given-names>
            </name>
          </person-group>
          <article-title>Research on the development and application of big data in health care</article-title>
          <source>Smart Healthc. 2020</source>
          <year>2020</year>
          <month>08</month>
          <day>15</day>
          <volume>6</volume>
          <issue>23</issue>
          <fpage>1</fpage>
          <lpage>10</lpage>
          <pub-id pub-id-type="doi">10.19335/j.cnki.2096-1219.2020.23.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Khatri</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>CV</given-names>
            </name>
          </person-group>
          <article-title>Designing data governance</article-title>
          <source>Commun ACM</source>
          <year>2010</year>
          <month>01</month>
          <day>01</day>
          <volume>53</volume>
          <issue>1</issue>
          <fpage>148</fpage>
          <lpage>152</lpage>
          <pub-id pub-id-type="doi">10.1145/1629175.1629210</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Chang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Research on governance methods of health care resources in big data era</article-title>
          <source>China Digit Med</source>
          <year>2016</year>
          <month>09</month>
          <day>15</day>
          <volume>09</volume>
          <issue>11</issue>
          <fpage>2</fpage>
          <lpage>5</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1673-7571.2016.09.001</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Fei</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Huang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>Z</given-names>
            </name>
          </person-group>
          <article-title>Data governance in health care big data application</article-title>
          <source>Chin J Health Inform Manag</source>
          <year>2018</year>
          <month>10</month>
          <day>20</day>
          <volume>15</volume>
          <issue>05</issue>
          <fpage>554</fpage>
          <lpage>558</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1672-5166.2018.05.016</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Y</given-names>
            </name>
          </person-group>
          <article-title>Research on the construction method of the tag system for health care big data</article-title>
          <source>Chin J Health Inform Manag. 2021</source>
          <year>2021</year>
          <month>04</month>
          <day>20</day>
          <volume>02</volume>
          <issue>18</issue>
          <fpage>189</fpage>
          <lpage>193</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1672-5166.2021.02.08</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Du</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Gong</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Fu</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>Research on Harvard datatags system and its inspiration for China</article-title>
          <source>Libr J</source>
          <year>2019</year>
          <month>08</month>
          <day>15</day>
          <volume>38</volume>
          <issue>08</issue>
          <fpage>17</fpage>
          <lpage>26</lpage>
          <pub-id pub-id-type="doi">10.13663/j.cnki.lj.2019.08.002</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bar-Sinai</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sweeney</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Crosas</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Datatags, data handling policy spaces and the Tags Language</article-title>
          <year>2016</year>
          <month>11</month>
          <conf-name>IEEE Security and Privacy Workshops</conf-name>
          <conf-date>May 22-26, 2016</conf-date>
          <conf-loc>San Jose, California</conf-loc>
          <fpage>1</fpage>
          <lpage>8</lpage>
          <pub-id pub-id-type="doi">10.1109/spw.2016.11</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref26">
        <label>26</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>HX</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>HW</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>SC</given-names>
            </name>
          </person-group>
          <article-title>Ethical issues of medical data sharing under the background of big data</article-title>
          <source>Chin J Inf Tradit Chin Med</source>
          <year>2018</year>
          <month>07</month>
          <day>18</day>
          <volume>25</volume>
          <issue>08</issue>
          <fpage>9</fpage>
          <lpage>11</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1005-5304.2018.08.003</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref27">
        <label>27</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xin</surname>
              <given-names>HY</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>GQ</given-names>
            </name>
          </person-group>
          <article-title>Construction and application of medical research big data platform in hospital</article-title>
          <source>Chin J Health Inform Manag</source>
          <year>2019</year>
          <month>04</month>
          <day>20</day>
          <volume>16</volume>
          <issue>02</issue>
          <fpage>206</fpage>
          <lpage>209</lpage>
          <pub-id pub-id-type="doi">10.3969/j.issn.1672-5166.2019.02.019</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="confproc">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Yao</surname>
              <given-names>A C</given-names>
            </name>
          </person-group>
          <article-title>Protocols for secure computations</article-title>
          <year>1982</year>
          <conf-name>23rd Annual Symposium on Foundations of Computer Science</conf-name>
          <conf-date>November 3-5, 1982</conf-date>
          <conf-loc>Chicago, Illinois, USA</conf-loc>
        </nlm-citation>
      </ref>
      <ref id="ref29">
        <label>29</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Stausberg</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Nasseh</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Nonnemacher</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Measuring data quality: a review of the literature between 2005 and 2013</article-title>
          <source>Stud Health Technol Inform</source>
          <year>2015</year>
          <volume>210</volume>
          <fpage>712</fpage>
          <lpage>716</lpage>
          <pub-id pub-id-type="doi">10.3233/978-1-61499-512-8-712</pub-id>
          <pub-id pub-id-type="medline">25991245</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Weiskopf</surname>
              <given-names>NG</given-names>
            </name>
            <name name-style="western">
              <surname>Weng</surname>
              <given-names>CH</given-names>
            </name>
          </person-group>
          <article-title>Methods and dimensions of electronic health record data quality assessment: enabling reuse for clinical research</article-title>
          <source>J Am Med Inform Assoc</source>
          <year>2013</year>
          <month>01</month>
          <day>1</day>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>144</fpage>
          <lpage>151</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://jamia.oxfordjournals.org/cgi/pmidlookup?view=long&#38;pmid=22733976"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/amiajnl-2011-000681</pub-id>
          <pub-id pub-id-type="medline">22733976</pub-id>
          <pub-id pub-id-type="pii">amiajnl-2011-000681</pub-id>
          <pub-id pub-id-type="pmcid">PMC3555312</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Meng</surname>
              <given-names>RG</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>LX</given-names>
            </name>
          </person-group>
          <article-title>Approaches and prospects on data quality assessment of big data in health and medicine</article-title>
          <source>Chin J Health Inform Manag</source>
          <year>2019</year>
          <month>12</month>
          <day>20</day>
          <volume>16</volume>
          <issue>06</issue>
          <fpage>677</fpage>
          <lpage>681</lpage>
          <pub-id pub-id-type="doi">10.1007/978-3-319-77525-8_100271</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
          </person-group>
          <article-title>COVID-19 in early 2021: current status and looking forward</article-title>
          <source>Signal Transduct Target Ther</source>
          <year>2021</year>
          <month>03</month>
          <day>08</day>
          <volume>6</volume>
          <issue>1</issue>
          <fpage>114</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1038/s41392-021-00527-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41392-021-00527-1</pub-id>
          <pub-id pub-id-type="medline">33686059</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41392-021-00527-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7938042</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref33">
        <label>33</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Sang</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Zha</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Z</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Jiang</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Yin</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Deng</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Wei</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>JY</given-names>
            </name>
            <name name-style="western">
              <surname>Fok</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Clinically applicable AI system for accurate diagnosis, quantitative measurements, and prognosis of COVID-19 pneumonia using computed tomography</article-title>
          <source>Cell</source>
          <year>2020</year>
          <month>06</month>
          <day>11</day>
          <volume>181</volume>
          <issue>6</issue>
          <fpage>1423</fpage>
          <lpage>1433.e11</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://linkinghub.elsevier.com/retrieve/pii/S0092-8674(20)30551-1"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.cell.2020.04.045</pub-id>
          <pub-id pub-id-type="medline">32416069</pub-id>
          <pub-id pub-id-type="pii">S0092-8674(20)30551-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7196900</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref34">
        <label>34</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Xiuyuan</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Chengdi</given-names>
            </name>
            <name name-style="western">
              <surname>Guo</surname>
              <given-names>Jixiang</given-names>
            </name>
            <name name-style="western">
              <surname>Gan</surname>
              <given-names>Yuncui</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Jianyong</given-names>
            </name>
            <name name-style="western">
              <surname>Bai</surname>
              <given-names>Hongli</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Lei</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Weimin</given-names>
            </name>
            <name name-style="western">
              <surname>Yi</surname>
              <given-names>Zhang</given-names>
            </name>
          </person-group>
          <article-title>MSCS-DeepLN: Evaluating lung nodule malignancy using multi-scale cost-sensitive neural networks</article-title>
          <source>Med Image Anal</source>
          <year>2020</year>
          <month>10</month>
          <volume>65</volume>
          <fpage>101772</fpage>
          <pub-id pub-id-type="doi">10.1016/j.media.2020.101772</pub-id>
          <pub-id pub-id-type="medline">32674041</pub-id>
          <pub-id pub-id-type="pii">S1361-8415(20)30136-5</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref35">
        <label>35</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Guangyu</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Xiaohong</given-names>
            </name>
            <name name-style="western">
              <surname>Shen</surname>
              <given-names>Jun</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Chengdi</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Zhihuan</given-names>
            </name>
            <name name-style="western">
              <surname>Ye</surname>
              <given-names>Linsen</given-names>
            </name>
            <name name-style="western">
              <surname>Wu</surname>
              <given-names>Xingwang</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Ting</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Kai</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Xuan</given-names>
            </name>
            <name name-style="western">
              <surname>Zhou</surname>
              <given-names>Zhongguo</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Jian</given-names>
            </name>
            <name name-style="western">
              <surname>Sang</surname>
              <given-names>Ye</given-names>
            </name>
            <name name-style="western">
              <surname>Deng</surname>
              <given-names>Ruiyun</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>Wenhua</given-names>
            </name>
            <name name-style="western">
              <surname>Yu</surname>
              <given-names>Tao</given-names>
            </name>
            <name name-style="western">
              <surname>Gao</surname>
              <given-names>Ming</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Jin</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Zehong</given-names>
            </name>
            <name name-style="western">
              <surname>Cai</surname>
              <given-names>Huimin</given-names>
            </name>
            <name name-style="western">
              <surname>Lu</surname>
              <given-names>Guangming</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Lingyan</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Lei</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Wenqin</given-names>
            </name>
            <name name-style="western">
              <surname>Wang</surname>
              <given-names>Winston</given-names>
            </name>
            <name name-style="western">
              <surname>Olvera</surname>
              <given-names>Andrea</given-names>
            </name>
            <name name-style="western">
              <surname>Ziyar</surname>
              <given-names>Ian</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Charlotte</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Oulan</given-names>
            </name>
            <name name-style="western">
              <surname>Liao</surname>
              <given-names>Weihua</given-names>
            </name>
            <name name-style="western">
              <surname>Liu</surname>
              <given-names>Jun</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Wen</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>Wei</given-names>
            </name>
            <name name-style="western">
              <surname>Shi</surname>
              <given-names>Jichan</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>Lianghong</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Longjiang</given-names>
            </name>
            <name name-style="western">
              <surname>Yan</surname>
              <given-names>Zhihan</given-names>
            </name>
            <name name-style="western">
              <surname>Zou</surname>
              <given-names>Xiaoguang</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Guiping</given-names>
            </name>
            <name name-style="western">
              <surname>Cao</surname>
              <given-names>Guiqun</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>Laurance L</given-names>
            </name>
            <name name-style="western">
              <surname>Mo</surname>
              <given-names>Long</given-names>
            </name>
            <name name-style="western">
              <surname>Liang</surname>
              <given-names>Yong</given-names>
            </name>
            <name name-style="western">
              <surname>Roberts</surname>
              <given-names>Michael</given-names>
            </name>
            <name name-style="western">
              <surname>Sala</surname>
              <given-names>Evis</given-names>
            </name>
            <name name-style="western">
              <surname>Schönlieb</surname>
              <given-names>Carola-Bibiane</given-names>
            </name>
            <name name-style="western">
              <surname>Fok</surname>
              <given-names>Manson</given-names>
            </name>
            <name name-style="western">
              <surname>Lau</surname>
              <given-names>Johnson Yiu-Nam</given-names>
            </name>
            <name name-style="western">
              <surname>Xu</surname>
              <given-names>Tao</given-names>
            </name>
            <name name-style="western">
              <surname>He</surname>
              <given-names>Jianxing</given-names>
            </name>
            <name name-style="western">
              <surname>Zhang</surname>
              <given-names>Kang</given-names>
            </name>
            <name name-style="western">
              <surname>Li</surname>
              <given-names>Weimin</given-names>
            </name>
            <name name-style="western">
              <surname>Lin</surname>
              <given-names>Tianxin</given-names>
            </name>
          </person-group>
          <article-title>A deep-learning pipeline for the diagnosis and discrimination of viral, non-viral and COVID-19 pneumonia from chest X-ray images</article-title>
          <source>Nat Biomed Eng</source>
          <year>2021</year>
          <month>06</month>
          <volume>5</volume>
          <issue>6</issue>
          <fpage>509</fpage>
          <lpage>521</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/33859385"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41551-021-00704-1</pub-id>
          <pub-id pub-id-type="medline">33859385</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41551-021-00704-1</pub-id>
          <pub-id pub-id-type="pmcid">PMC7611049</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref36">
        <label>36</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Luo</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Yang</surname>
              <given-names>Q</given-names>
            </name>
            <name name-style="western">
              <surname>Chen</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Zheng</surname>
              <given-names>T</given-names>
            </name>
            <name name-style="western">
              <surname>Xie</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Sun</surname>
              <given-names>H</given-names>
            </name>
          </person-group>
          <article-title>An optimized two-stage cascaded deep neural network for adrenal segmentation on CT images</article-title>
          <source>Comput Biol Med</source>
          <year>2021</year>
          <month>09</month>
          <day>08</day>
          <volume>136</volume>
          <fpage>104749</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1016/j.compbiomed.2021.104749</pub-id>
          <pub-id pub-id-type="medline">34388467</pub-id>
          <pub-id pub-id-type="pii">S0010-4825(21)00543-6</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
