<?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">v8i4e14710</article-id>
      <article-id pub-id-type="pmid">32329738</article-id>
      <article-id pub-id-type="doi">10.2196/14710</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>Next-Generation Sequencing–Based Cancer Panel Data Conversion Using International Standards to Implement a Clinical Next-Generation Sequencing Research System: Single-Institution Study</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Eysenbach</surname>
            <given-names>Gunther</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Park</surname>
            <given-names>Yu Rang</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Pradeep</surname>
            <given-names>K</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Park</surname>
            <given-names>Phillip</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-8769-6383</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author" equal-contrib="yes">
          <name name-style="western">
            <surname>Shin</surname>
            <given-names>Soo-Yong</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <xref rid="aff3" ref-type="aff">3</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2410-6120</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Park</surname>
            <given-names>Seog Yun</given-names>
          </name>
          <degrees>MD</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-5704-646X</ext-link>
        </contrib>
        <contrib id="contrib4" contrib-type="author">
          <name name-style="western">
            <surname>Yun</surname>
            <given-names>Jeonghee</given-names>
          </name>
          <degrees>ABT</degrees>
          <xref rid="aff4" ref-type="aff">4</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-3192-6044</ext-link>
        </contrib>
        <contrib id="contrib5" contrib-type="author">
          <name name-style="western">
            <surname>Shin</surname>
            <given-names>Chulmin</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-7131-5902</ext-link>
        </contrib>
        <contrib id="contrib6" contrib-type="author">
          <name name-style="western">
            <surname>Jung</surname>
            <given-names>Jipmin</given-names>
          </name>
          <degrees>MS</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-2901-9333</ext-link>
        </contrib>
        <contrib id="contrib7" contrib-type="author">
          <name name-style="western">
            <surname>Choi</surname>
            <given-names>Kui Son</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-5336-3874</ext-link>
        </contrib>
        <contrib id="contrib8" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Cha</surname>
            <given-names>Hyo Soung</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution>Cancer Data Center</institution>
            <institution>National Cancer Center</institution>
            <addr-line>323 Ilsan-ro, Ilsandong-gu, Goyang</addr-line>
            <addr-line>Goyang, 10408</addr-line>
            <country>Republic of Korea</country>
            <phone>82 1073502088</phone>
            <email>kkido@ncc.re.kr</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0003-0537-8355</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Cancer Data Center</institution>
        <institution>National Cancer Center</institution>
        <addr-line>Goyang</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Department of Digital Health</institution>
        <institution>Samsung Advanced Institute for Health Sciences and Technology</institution>
        <institution>Sungkyunkwan University</institution>
        <addr-line>Seoul</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <aff id="aff3">
        <label>3</label>
        <institution>Big Data Research Center</institution>
        <institution>Samsung Medical Center</institution>
        <addr-line>Seoul</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <aff id="aff4">
        <label>4</label>
        <institution>Department of Pathology</institution>
        <institution>National Cancer Center</institution>
        <addr-line>Goyang</addr-line>
        <country>Republic of Korea</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Hyo Soung Cha <email>kkido@ncc.re.kr</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <month>4</month>
        <year>2020</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>24</day>
        <month>4</month>
        <year>2020</year>
      </pub-date>
      <volume>8</volume>
      <issue>4</issue>
      <elocation-id>e14710</elocation-id>
      <history>
        <date date-type="received">
          <day>15</day>
          <month>5</month>
          <year>2019</year>
        </date>
        <date date-type="rev-request">
          <day>3</day>
          <month>10</month>
          <year>2019</year>
        </date>
        <date date-type="rev-recd">
          <day>19</day>
          <month>11</month>
          <year>2019</year>
        </date>
        <date date-type="accepted">
          <day>7</day>
          <month>2</month>
          <year>2020</year>
        </date>
      </history>
      <copyright-statement>©Phillip Park, Soo-Yong Shin, Seog Yun Park, Jeonghee Yun, Chulmin Shin, Jipmin Jung, Kui Son Choi, Hyo Soung Cha. Originally published in JMIR Medical Informatics (http://medinform.jmir.org), 24.04.2020.</copyright-statement>
      <copyright-year>2020</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 http://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="http://medinform.jmir.org/2020/4/e14710/" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>The analytical capacity and speed of next-generation sequencing (NGS) technology have been improved. Many genetic variants associated with various diseases have been discovered using NGS. Therefore, applying NGS to clinical practice results in precision or personalized medicine. However, as clinical sequencing reports in electronic health records (EHRs) are not structured according to recommended standards, clinical decision support systems have not been fully utilized. In addition, integrating genomic data with clinical data for translational research remains a great challenge.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>To apply international standards to clinical sequencing reports and to develop a clinical research information system to integrate standardized genomic data with clinical data.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>We applied the recently published ISO/TS 20428 standard to 367 clinical sequencing reports generated by panel (91 genes) sequencing in EHRs and implemented a clinical NGS research system by extending the clinical data warehouse to integrate the necessary clinical data for each patient. We also developed a user interface with a clinical research portal and an NGS result viewer.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>A single clinical sequencing report with 28 items was restructured into four database tables and 49 entities. As a result, 367 patients’ clinical sequencing data were connected with clinical data in EHRs, such as diagnosis, surgery, and death information. This system can support the development of cohort or case-control datasets as well.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>The standardized clinical sequencing data are not only for clinical practice and could be further applied to translational research.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>data standardization</kwd>
        <kwd>clinical sequencing data</kwd>
        <kwd>next-generation sequencing</kwd>
        <kwd>translational research information system</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Much research has been conducted to find new biological markers for diagnosis or treatment as next-generation sequencing (NGS) technologies have improved [<xref ref-type="bibr" rid="ref1">1</xref>]. Recently, as the price and turn-around time of NGS have dramatically reduced, sequencing of patient samples using NGS has been applied in clinical practice [<xref ref-type="bibr" rid="ref2">2</xref>]. For example, clinical sequencing was mainly applied in cancer patients to determine appropriate treatment by genotyping cancers [<xref ref-type="bibr" rid="ref3">3</xref>]. Government agencies and private insurance companies in various countries have started to reimburse for clinical sequencing tests. For example, in the United States, if a sequencing laboratory is certified by Clinical Laboratory Improvement Amendments, the sequencing test could be reimbursed [<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref5">5</xref>]. Similarly, based on the 100,000 Genomes Project, the National Health Service in the United Kingdom launched a service to provide access to the latest NGS technologies in genomic testing and management [<xref ref-type="bibr" rid="ref6">6</xref>]. Further, the Korean National Insurance Agency started to reimburse for several panel sequencing tests, including those for cancer and rare diseases, in the beginning of March 2017 [<xref ref-type="bibr" rid="ref7">7</xref>]. Much additional clinical sequencing has been performed worldwide in clinical practice.</p>
      <p>Essentially, clinical sequencing results can be used for diagnosis or to identify appropriate treatment. However, since most of the current clinical sequencing results are not standardized, all clinical sequencing reports are stored in text or pdf format. Therefore, clinical decision support systems cannot utilize the clinical sequencing data through electronic health records (EHRs). In addition, clinical sequencing reports are not interoperable among hospitals owing to the lack of standard adoption. This means that extensive manual manipulation is required for interpretation or use of clinical sequencing reports. Based on the large amount of raw sequencing data and the complicated NGS pipeline from raw data to report generation, clinical sequencing requires well-established standard operating procedures and highly-trained experts to ensure data quality [<xref ref-type="bibr" rid="ref8">8</xref>]. To resolve this issue, diverse efforts have been made by standard development organizations. ISO/TC 215 focused on clinical genomics by establishing a subcommittee on genome informatics in 2019. It also published two genomics standards [<xref ref-type="bibr" rid="ref9">9</xref>,<xref ref-type="bibr" rid="ref10">10</xref>] and developed six genomics standards [<xref ref-type="bibr" rid="ref11">11</xref>-<xref ref-type="bibr" rid="ref16">16</xref>]. The HL7 clinical genomics working group also developed diverse clinical genomics standards [<xref ref-type="bibr" rid="ref17">17</xref>-<xref ref-type="bibr" rid="ref23">23</xref>].</p>
      <p>Given the research problem mentioned above, this study aimed to develop a system to standardize clinical sequencing data and to provide services suitable for researchers to utilize the data. In this study, we extended a clinical NGS research system (CNRS) in a clinical research data warehouse (CRDW) that structures and standardizes clinical sequencing results by mapping standard terminology from current unstructured text reports.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>System Architecture and Data Flow</title>
        <p><xref rid="figure1" ref-type="fig">Figure 1</xref> depicts the data flow of the CNRS. The clinical sequencing report is stored as a part of the pathology report in EHRs. The stored clinical sequencing reports are transferred to the operational data store (ODS). In ODS, the data are structured and standardized, and the sequencing information is saved in the CRDW. Through a key management server, the clinical data in the CRDW and the NGS result data in pathology reports are mapped to patient alternative numbers and not patient numbers. In addition, NGS result data in the CRDW are extracted and stored in the NGS viewer database (DB). Researchers can access the necessary deidentified specific genetic variation cohort in the clinical research portal and inspect NGS result data in the NGS result viewer.</p>
        <p>The detailed information of each component is presented in subsequent sections.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Data flow of the clinical next-generation sequencing (NGS) research system. This system was built for the unified management of the clinical information of each patient and clinical NGS test results. CNRS: clinical next-generation sequencing research system; CRDW: clinical research data warehouse; DB: database; e-CRF: electronic-case report form; EMR: electronic medical record; ODS: operational data store.</p>
          </caption>
          <graphic xlink:href="medinform_v8i4e14710_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Data Collection of Clinical Sequencing Results</title>
        <p>The Health Insurance Review &#38; Assessment Service in Korea reimburses laboratory-developed panel sequencing tests that include about 100 genes with 14 mandatory genes. As an example, <xref ref-type="table" rid="table1">Table 1</xref> shows the panel genes that are used in the National Cancer Center (NCC), Korea.</p>
        <p>The current clinical sequencing report of the NCC is illustrated in <xref rid="figure2" ref-type="fig">Figure 2</xref>. Currently, clinical sequencing reports are stored in a single table with 28 attributes in the EHR DB. This table is copied to the ODS on a weekly basis.</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>List of panel genes (n=91) used in the National Cancer Center, Korea.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="250"/>
            <col width="750"/>
            <thead>
              <tr valign="top">
                <td>Category</td>
                <td>Genes</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Mandatory genes (n=14)</td>
                <td><italic>ALK</italic>, <italic>BRAF</italic>, <italic>BRCA1</italic>, <italic>BRCA2</italic>, <italic>EGFR</italic>, <italic>HER2</italic>, <italic>IDH1</italic>, <italic>IDH2</italic>, <italic>KIT</italic>, <italic>KRAS</italic>, <italic>MYC</italic>, <italic>MYCN</italic>, <italic>NRAS</italic>, and <italic>PDGFRA</italic></td>
              </tr>
              <tr valign="top">
                <td>Additional genes (n=74)</td>
                <td><italic>ABL1</italic>, <italic>AKT1</italic>, <italic>AKT3</italic>, <italic>APC</italic>, <italic>AR</italic>, <italic>ATM</italic>, <italic>AXL</italic>, <italic>CCND1</italic>, <italic>CDH1</italic>, <italic>CDK4</italic>, <italic>CDK6</italic>, <italic>CDKN2A</italic>, <italic>CEBPA</italic>, <italic>CSF1R</italic>, <italic>CTNNB1</italic>, <italic>DDR2</italic>, <italic>ERBB2</italic>, <italic>ERBB3</italic>, <italic>ERBB4</italic>, <italic>ERG</italic>, <italic>ESR1</italic>, <italic>ETV1</italic>, <italic>ETV4</italic>, <italic>ETV5</italic>, <italic>EZH2</italic>, <italic>FANCA</italic>, <italic>FANCC</italic>, <italic>FANCF</italic>, <italic>FANCG</italic>, <italic>FBXW7</italic>, <italic>FGFR1</italic>, <italic>FGFR2</italic>, <italic>FGFR3</italic>, <italic>FGFR4</italic>, <italic>FLT3</italic>, <italic>FOXL2</italic>, <italic>GNA11</italic>, <italic>GNAQ</italic>, <italic>GNAS</italic>, <italic>HNF1A</italic>, <italic>JAK1</italic>, <italic>JAK2</italic>, <italic>JAK3</italic>, <italic>KDR</italic>, <italic>MAP2K1</italic>, <italic>MAP2K2</italic>, <italic>MAP2K4</italic>, <italic>MET</italic>, <italic>MLH1</italic>, <italic>MTOR</italic>, <italic>NOTCH1</italic>, <italic>NPM1</italic>, <italic>NTRK1</italic>, <italic>NTRK2</italic>, <italic>NTRK3</italic>, <italic>PIK3CA</italic>, <italic>PIKR1</italic>, <italic>PPARG</italic>, <italic>PTEN</italic>, <italic>PTPN11</italic>, <italic>RAF1</italic>, <italic>RB1</italic>, <italic>RET</italic>, <italic>ROS1</italic>, <italic>RUNX1</italic>, <italic>SMAD4</italic>, <italic>SMARCB1</italic>, <italic>SMO</italic>, <italic>SRC</italic>, <italic>STK11</italic>, <italic>TP53</italic>, <italic>VHL</italic>, <italic>WT1</italic>, and <italic>NRG1</italic></td>
              </tr>
              <tr valign="bottom">
                <td>Additional fusion genes<sup>a</sup> (n=3)</td>
                <td><italic>ALK</italic>, <italic>ROS1</italic>, and <italic>RET</italic></td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>Genes in the fusion category are duplicated in the mandatory gene list.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <fig id="figure2" position="float">
          <label>Figure 2</label>
          <caption>
            <p>Input template of the clinical sequencing report of the National Cancer Center. All boxes are text boxes for free text entry.</p>
          </caption>
          <graphic xlink:href="medinform_v8i4e14710_fig2.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Structuring/Standardization Process</title>
        <p><xref rid="figure3" ref-type="fig">Figure 3</xref> demonstrates the data structuring process. All data are structured and standardized according to ISO/TS 20428 during the extract transform and load process [<xref ref-type="bibr" rid="ref10">10</xref>]. The ISO/TS 20428 standard defines the required and optional fields for sequencing reports, along with the metadata for each field. The required fields include the following 10 categories: clinical sequencing orders, information on the subject of care, information on the legally authorized person ordering clinical sequencing, performing laboratory, associated diseases and phenotypes, biomaterial information, genetic variations, classification of variants, recommended treatment, and addendum. The optional fields include the following seven categories: medical history, family history, reference genome version, racial genomic information, genetic variation, detailed sequencing information, and references.</p>
        <fig id="figure3" position="float">
          <label>Figure 3</label>
          <caption>
            <p>Structure of the next-generation sequencing (NGS) test results. (A) Clinical NGS result summary of the electronic health record database (DB). (B) Variant summary table in the NGS DB. (C) Gene fusion table in the NGS DB. (D) Copy number variation table in the NGS DB.</p>
          </caption>
          <graphic xlink:href="medinform_v8i4e14710_fig3.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
        <p><xref rid="figure3" ref-type="fig">Figure 3</xref> shows that the clinical sequencing data are structured and loaded from the replicated ODS into pathologic and laboratory information, variant summary, fusion variant, and copy number variation (CNV) variant tables. Pathologic and laboratory information has the following nine attributes: identifiers, test order date, quality control results, sample type, report generation date, report generator information, sequencer type, recommended treatment, and references. Variant summary has the following nine attributes: gene name, exon ID, DNA change, protein change, variant information, allele frequency, effects of variants, pathogeny, and clinical relevance. Fusion variant has the following 11 attributes: gene name, chromosome, cytoband, break, transcript part, locus, gene strand, span read, split read, total read, and distance. CNV has the following nine attributes: gene name, locus, <italic>P</italic> value, gain region, total region, region ratio, gene count, region count, and significant region count.</p>
      </sec>
      <sec>
        <title>Combination With Clinical Data</title>
        <p><xref rid="figure4" ref-type="fig">Figure 4</xref> shows that the NCC has deidentified the clinical data warehouse as well. The ODS receives clinical data from the table with the primary key as the patient ID and NGS result data from the table with the primary key as pathology ID from EHRs. The key management system receives the pathology ID and patient ID from EHRs and generates an alternative ID. It then sends the ID to the ODS. The ODS deletes the patient ID and pathology ID and sends the data to the CRDW with the alternative ID. By using an alternative ID, which is a pseudonym for the patient ID, the necessary deidentified clinical data can be combined with the sequencing result data.</p>
        <fig id="figure4" position="float">
          <label>Figure 4</label>
          <caption>
            <p>Overview of the combination with clinical data. CRDW: clinical research data warehouse; DB: database; EMR: electronic medical record; NGS: next-generation sequencing; ODS: operational data store.</p>
          </caption>
          <graphic xlink:href="medinform_v8i4e14710_fig4.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>User Services</title>
        <p>Users can access the necessary information using a clinical research portal and NGS result viewer. The clinical research portal is a user interface to query or extract clinical and genomic data by changing search options. The NGS result viewer provides functionality to create a structured or standardized clinical sequencing report by converting an original unstructured pathology report using ISO/TS 20428.</p>
        <p>This study was approved by the institutional review board (IRB) of the NCC in Korea (NCC2019-0535).</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <p>From April 2017 to February 2019, the CNRS included 367 clinical sequencing results, which consisted of 249 lung cancer cases, 70 ovarian cancer cases, eight breast cancer cases, seven malignant melanoma cases, seven colon cancer cases, seven stomach cancer cases, six liver cancer cases, five thyroid cancer cases, five kidney cancer cases, two brain cancer cases, and one prostate cancer case. In detail, 51 variants were found and stored among a total of 88 genes. <xref rid="figure5" ref-type="fig">Figure 5</xref> shows the distribution of point mutations by cancer type. Across all cancer types, <italic>TP53</italic> (167/367, 45.5%), <italic>EGRF</italic> (56/367, 15.3%), <italic>KRAS</italic> (34/337, 9.3%), and <italic>BRAC1</italic> (21/337, 5.7%) mutations were common. According to each cancer type, <italic>TP53</italic> (120/249, 48.2%), <italic>EGFR</italic> (51/249, 20.5%), and <italic>KRAS</italic> (27/249, 10.8%) mutations were common in lung cancer; <italic>TP53</italic> (39/70, 55.7%), <italic>BRCA1</italic> (9/70, 12.9%), and <italic>PIK3CA</italic> (5/70, 7.1%) mutations were common in ovarian cancer; and <italic>TP53</italic> (3/8, 37.5%), <italic>BRCA2</italic> (3/8, 37.5%), and <italic>PIK3CA</italic> (3/8, 37.5%) mutations were common in breast cancer. The rates of pathogenic, likely pathogenic, and uncertain significance variants were 55.1%, 34.7%, and 42.9%, respectively.</p>
      <fig id="figure5" position="float">
        <label>Figure 5</label>
        <caption>
          <p>Distribution of point mutations by cancer type in 367 patients. The top 12 genes by frequency are displayed.</p>
        </caption>
        <graphic xlink:href="medinform_v8i4e14710_fig5.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p><xref rid="figure6" ref-type="fig">Figure 6</xref> presents the user interface of the clinical research portal. As explained in the previous section, the clinical research portal supports an integrated view of the NGS results and the corresponding clinical data in EHRs. <xref rid="figure6" ref-type="fig">Figure 6</xref> shows the category of the CRDW, which contains clinical data, such as diagnosis, laboratory data, medication, surgery, chemotherapy, follow-up data, and patient demographic data. Users can choose the appropriate category and then choose desired detailed variables by clicking on them. The NGS results can be visualized (ie, variant summary, CNV, and fusion genes), as illustrated in <xref rid="figure7" ref-type="fig">Figure 7</xref>.</p>
      <fig id="figure6" position="float">
        <label>Figure 6</label>
        <caption>
          <p>Interface of the clinical research search portal. The main page of the clinical research search portal comprises two domains. The red rectangle indicates searchable items. The blue rectangle indicates the area where the researcher can select items through drag and drop.</p>
        </caption>
        <graphic xlink:href="medinform_v8i4e14710_fig6.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <fig id="figure7" position="float">
        <label>Figure 7</label>
        <caption>
          <p>Example of next-generation sequencing results in the clinical research portal.</p>
        </caption>
        <graphic xlink:href="medinform_v8i4e14710_fig7.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
      <p>The NGS result viewer can show the detailed clinical sequencing report of each patient in a structured way, whereas the clinical research portal supports the analysis of aggregated sequencing results. As shown in <xref rid="figure8" ref-type="fig">Figure 8</xref>, the clinical sequencing report is mainly divided into the following three parts: basic test information, sequencing methods and other related information, and variants with reporting results.</p>
      <fig id="figure8" position="float">
        <label>Figure 8</label>
        <caption>
          <p>Example of the next-generation sequencing (NGS) result viewer. The main page of the NGS result viewer is composed of three domains. The first box provides basic test information. The second box explains sequencing methods and other related information. The last box shows mutation data with reporting results.</p>
        </caption>
        <graphic xlink:href="medinform_v8i4e14710_fig8.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
      </fig>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Principal Findings and Implications</title>
        <p>The CNRS converts text-based clinical sequencing reports in EHRs into structured data using international standards. Through the CNRS, the content, as shown in <xref rid="figure5" ref-type="fig">Figure 5</xref>, can be easily organized and data can be managed according to international standards. It also provides standardized data through the clinical research search portal; furthermore, using its functions, researchers can set up cohorts with specific mutations and add clinical data columns as needed. Thus, it can be inferred that the CNRS supports researchers in performing translational research by allowing them to easily extract the desired clinical and genomic data from EHRs. For example, non–small cell lung cancer genotyping requires mutation pattern analysis of <italic>KRAS</italic>, <italic>EGFR</italic>, and <italic>BRAF</italic> [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Similarly, other research requires clinical data such as that on cancer stage, smoking history, and death date for survival analysis [<xref ref-type="bibr" rid="ref25">25</xref>]. These types of translational studies can be easily performed using the developed CNRS, and this has already been proven by researchers at the NCC.</p>
        <p>The CNRS is provided to research projects that have been approved by the IRB. Researchers send data extraction requests to health information managers, and it takes about one to two weeks to review, refine, and provide clinical data from EHRs. The CNRS could retrieve data through the clinical research portal after receiving IRB approval, and it takes about two or three days from review to delivery after a data extraction request is made. In addition, the NCC has built a genomic cohort linking the NGS DB with cancer registries such as those of lung cancer and ovarian cancer.</p>
        <p>There are two unique aspects of the CNRS as developed. One is that the CNRS uses an ISO standard (ISO/TS 20428) to support multicenter research. If other hospitals or research institutes use international standards, the data can be easily integrated into the same format. We also achieved the same results as successfully converting the data and manually cleansing the data previously. The other is that the CNRS can help protect patients’ privacy by deidentifying protected health information. To use the patients’ data for research purposes, researchers must obtain written consent from patients or deidentify the identifiable data. In this era of big data, deidentification is usually used for a number of reasons. However, if we deidentify the data, it is difficult to link the separate DBs. To overcome this issue, the CNRS adopted a key management server to pseudonymize the patient ID. This means that the CNRS works as an honest broker [<xref ref-type="bibr" rid="ref26">26</xref>]. To strengthen the protection level, only authorized developers can access this key management server and users can receive the randomly assigned ID after combing clinical data and sequencing data using the key management system. Therefore, users cannot retrieve real patient IDs in EHRs or pseudonymized IDs in the key management system.</p>
      </sec>
      <sec>
        <title>Limitations</title>
        <p>The main contribution of this study is that, for the first time, the ISO/TS 20428 standard was applied to the CRDW to standardize clinical genomic test results. As a result, we also demonstrated that this approach could enable easy search and analysis with clinical data in EHRs. However, it has limitations. We did not verify this system in multiple centers. We hope our approach will help other hospitals or institutions build their own systems.</p>
      </sec>
      <sec>
        <title>Future Work</title>
        <p>Our continuing objectives are to extend the categories of clinical and sequencing data in the CNRS and consider the standards proposed by the Global Alliance for Genomics and Health, which has developed diverse practical standard application programming interfaces for international genomic research.</p>
      </sec>
      <sec>
        <title>Conclusion</title>
        <p>The CNRS converts the text-based clinical sequencing reports of EHRs into structured data using international standards and provides standardized data. In addition, the CNRS allows researchers to set up cohorts with specific mutations and add clinical data columns as needed. Therefore, it can be inferred that the CNRS enables researchers to conduct translational research by allowing them to easily extract the required clinical and genomic data from EHRs.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group/>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">CNRS</term>
          <def>
            <p>clinical next-generation sequencing research system</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">CNV</term>
          <def>
            <p>copy number variation</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">CRDW</term>
          <def>
            <p>clinical research data warehouse</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">DB</term>
          <def>
            <p>database</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">IRB</term>
          <def>
            <p>institutional review board</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">NCC</term>
          <def>
            <p>National Cancer Center</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">NGS</term>
          <def>
            <p>next-generation sequencing</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">ODS</term>
          <def>
            <p>operational data store</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>This study was supported by a grant from the National Cancer Center (grant no. 1810871-2), the National R&#38;D Program for Cancer Control funded by the Ministry of Health and Welfare, Republic of Korea (grant no. 1631180), and the Technology Innovation Program funded by the Ministry of Trade, Industry &#38; Energy, Republic of Korea (grant no. 20004632).</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="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Tan</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>W</given-names>
            </name>
            <name name-style="western">
              <surname>Lim</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>An extracellular matrix-related prognostic and predictive indicator for early-stage non-small cell lung cancer</article-title>
          <source>Nat Commun</source>
          <year>2017</year>
          <month>11</month>
          <day>23</day>
          <volume>8</volume>
          <issue>1</issue>
          <fpage>1734</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/29170406"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/s41467-017-01430-6</pub-id>
          <pub-id pub-id-type="medline">29170406</pub-id>
          <pub-id pub-id-type="pii">10.1038/s41467-017-01430-6</pub-id>
          <pub-id pub-id-type="pmcid">PMC5700969</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref2">
        <label>2</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Simon</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Roychowdhury</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Implementing personalized cancer genomics in clinical trials</article-title>
          <source>Nat Rev Drug Discov</source>
          <year>2013</year>
          <month>05</month>
          <volume>12</volume>
          <issue>5</issue>
          <fpage>358</fpage>
          <lpage>69</lpage>
          <pub-id pub-id-type="doi">10.1038/nrd3979</pub-id>
          <pub-id pub-id-type="medline">23629504</pub-id>
          <pub-id pub-id-type="pii">nrd3979</pub-id>
        </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>Katsanis</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Katsanis</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Molecular genetic testing and the future of clinical genomics</article-title>
          <source>Nat Rev Genet</source>
          <year>2013</year>
          <month>06</month>
          <volume>14</volume>
          <issue>6</issue>
          <fpage>415</fpage>
          <lpage>26</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/23681062"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/nrg3493</pub-id>
          <pub-id pub-id-type="medline">23681062</pub-id>
          <pub-id pub-id-type="pii">nrg3493</pub-id>
          <pub-id pub-id-type="pmcid">PMC4461364</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>Mauer</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Pirzadeh-Miller</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Euhus</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The integration of next-generation sequencing panels in the clinical cancer genetics practice: an institutional experience</article-title>
          <source>Genet Med</source>
          <year>2014</year>
          <month>05</month>
          <volume>16</volume>
          <issue>5</issue>
          <fpage>407</fpage>
          <lpage>12</lpage>
          <pub-id pub-id-type="doi">10.1038/gim.2013.160</pub-id>
          <pub-id pub-id-type="medline">24113346</pub-id>
          <pub-id pub-id-type="pii">gim2013160</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>Hehir-Kwa</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Claustres</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hastings</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>van Ravenswaaij-Arts</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Christenhusz</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Genuardi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Melegh</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Cambon-Thomsen</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Patsalis</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Vermeesch</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Cornel</surname>
              <given-names>MC</given-names>
            </name>
            <name name-style="western">
              <surname>Searle</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Palotie</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Capoluongo</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Peterlin</surname>
              <given-names>B</given-names>
            </name>
            <name name-style="western">
              <surname>Estivill</surname>
              <given-names>X</given-names>
            </name>
            <name name-style="western">
              <surname>Robinson</surname>
              <given-names>PN</given-names>
            </name>
          </person-group>
          <article-title>Towards a European consensus for reporting incidental findings during clinical NGS testing</article-title>
          <source>Eur J Hum Genet</source>
          <year>2015</year>
          <month>12</month>
          <volume>23</volume>
          <issue>12</issue>
          <fpage>1601</fpage>
          <lpage>6</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://dx.doi.org/10.1038/ejhg.2015.111"/>
          </comment>
          <pub-id pub-id-type="doi">10.1038/ejhg.2015.111</pub-id>
          <pub-id pub-id-type="medline">26036857</pub-id>
          <pub-id pub-id-type="pii">ejhg2015111</pub-id>
          <pub-id pub-id-type="pmcid">PMC4795187</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>Ratner</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Next-generation sequencing tests to become routine</article-title>
          <source>Nat Biotechnol</source>
          <year>2018</year>
          <month>06</month>
          <day>06</day>
          <volume>36</volume>
          <issue>6</issue>
          <fpage>484</fpage>
          <pub-id pub-id-type="doi">10.1038/nbt0618-484</pub-id>
          <pub-id pub-id-type="medline">29874203</pub-id>
          <pub-id pub-id-type="pii">nbt0618-484</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>Lee</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>MS26.01 Translation of Clinical Data to Real World - Asia</article-title>
          <source>Journal of Thoracic Oncology</source>
          <year>2018</year>
          <month>10</month>
          <volume>13</volume>
          <issue>10</issue>
          <fpage>S296</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1016/j.jtho.2018.08.189"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jtho.2018.08.189</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>Park</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Status and Direction of Healthcare Data in Korea for Artificial Intelligence</article-title>
          <source>Hanyang Med Rev</source>
          <year>2017</year>
          <volume>37</volume>
          <issue>2</issue>
          <fpage>86</fpage>
          <lpage>92</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.7599/hmr.2017.37.2.86"/>
          </comment>
          <pub-id pub-id-type="doi">10.7599/hmr.2017.37.2.86</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO 25720:2009 Genomic Sequence Variation Markup Language (GSVML)<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/43182.html">https://www.iso.org/standard/43182.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref10">
        <label>10</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/TS 20428:2017 Data elements and their metadata for describing structured clinical genomic sequence information in electronic health records<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/67981.html">https://www.iso.org/standard/67981.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/CD TS 22692.2 Genomics Informatics— Quality control metrics for DNA sequencing<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/73693.html">https://www.iso.org/standard/73693.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/DIS 21393 Genomics Informatics — Omics Markup Language (OML)<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/70855.html">https://www.iso.org/standard/70855.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref13">
        <label>13</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/WD TS 23357 Clinical genomics data sharing specification for next generation sequencing<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/75310.html">https://www.iso.org/standard/75310.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref14">
        <label>14</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/CD TR 21394.2 Genomics Informatics — Whole Genomics Sequence Markup Language (WGML)<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/75956.html">https://www.iso.org/standard/75956.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/WD TS 22693 Health Informatics — Structured clinical gene fusion report in electronic health records<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/73694.html">https://www.iso.org/standard/73694.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <source>ISO</source>
          <access-date>2020-03-10</access-date>
          <comment>ISO/WD TS 22690 Health Informatics — Reliability assessment criteria for high-throughput gene-expression data<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.iso.org/standard/73691.html">https://www.iso.org/standard/73691.html</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Version 2 Implementation Guide: Clinical Genomics; Fully LOINC-Qualified Genetic Variation Model (US Realm)<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=23">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=23</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref18">
        <label>18</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Version 3 Implementation Guide: Family History/Pedigree Interoperability, Release 1<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=301">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=301</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref19">
        <label>19</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Version 2 Implementation Guide: Clinical Genomics; fully LOINC-Qualified Cytogenetic Model, Release 1 - US Realm<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=364">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=364</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref20">
        <label>20</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Implementation Guide for CDA® Release 2: Genetic Testing Reports, Release 1<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=292">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=292</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref21">
        <label>21</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Domain Analysis Model: Clinical Sequencing, Release 1<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=446">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=446</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref22">
        <label>22</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Version 3 Standard: Clinical Genomics; Pedigree, Release 1<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=8">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=8</ext-link>
                                                </comment>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="web">
          <source>Health Level Seven International</source>
          <access-date>2020-03-10</access-date>
          <comment>HL7 Domain Analysis Model: Clinical Genomics, Release1<ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.hl7.org/implement/standards/product_brief.cfm?product_id=479">https://www.hl7.org/implement/standards/product_brief.cfm?product_id=479</ext-link>
                                                </comment>
        </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>Hagemann</surname>
              <given-names>IS</given-names>
            </name>
            <name name-style="western">
              <surname>Devarakonda</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lockwood</surname>
              <given-names>CM</given-names>
            </name>
            <name name-style="western">
              <surname>Spencer</surname>
              <given-names>DH</given-names>
            </name>
            <name name-style="western">
              <surname>Guebert</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Bredemeyer</surname>
              <given-names>AJ</given-names>
            </name>
            <name name-style="western">
              <surname>Al-Kateb</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Nguyen</surname>
              <given-names>TT</given-names>
            </name>
            <name name-style="western">
              <surname>Duncavage</surname>
              <given-names>EJ</given-names>
            </name>
            <name name-style="western">
              <surname>Cottrell</surname>
              <given-names>CE</given-names>
            </name>
            <name name-style="western">
              <surname>Kulkarni</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Nagarajan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Seibert</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Baggstrom</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Waqar</surname>
              <given-names>SN</given-names>
            </name>
            <name name-style="western">
              <surname>Pfeifer</surname>
              <given-names>JD</given-names>
            </name>
            <name name-style="western">
              <surname>Morgensztern</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Govindan</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Clinical next-generation sequencing in patients with non-small cell lung cancer</article-title>
          <source>Cancer</source>
          <year>2015</year>
          <month>02</month>
          <day>15</day>
          <volume>121</volume>
          <issue>4</issue>
          <fpage>631</fpage>
          <lpage>9</lpage>
          <pub-id pub-id-type="doi">10.1002/cncr.29089</pub-id>
          <pub-id pub-id-type="medline">25345567</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Rossi</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rasi</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Fabbri</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Spina</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Fangazio</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Forconi</surname>
              <given-names>F</given-names>
            </name>
            <name name-style="western">
              <surname>Marasca</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Laurenti</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bruscaggin</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Cerri</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Monti</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Cresta</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Famà</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>De Paoli</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Bulian</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Gattei</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Guarini</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Deaglio</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Capello</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Rabadan</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pasqualucci</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Dalla-Favera</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Foà</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Gaidano</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Mutations of NOTCH1 are an independent predictor of survival in chronic lymphocytic leukemia</article-title>
          <source>Blood</source>
          <year>2012</year>
          <month>01</month>
          <day>12</day>
          <volume>119</volume>
          <issue>2</issue>
          <fpage>521</fpage>
          <lpage>9</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://europepmc.org/abstract/MED/22077063"/>
          </comment>
          <pub-id pub-id-type="doi">10.1182/blood-2011-09-379966</pub-id>
          <pub-id pub-id-type="medline">22077063</pub-id>
          <pub-id pub-id-type="pii">blood-2011-09-379966</pub-id>
          <pub-id pub-id-type="pmcid">PMC3257017</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>Choi</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Choi</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Shin</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Lyu</surname>
              <given-names>Y</given-names>
            </name>
            <name name-style="western">
              <surname>Park</surname>
              <given-names>YR</given-names>
            </name>
            <name name-style="western">
              <surname>Yoo</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Establishing the role of honest broker: bridging the gap between protecting personal health data and clinical research efficiency</article-title>
          <source>Peer J</source>
          <year>2015</year>
          <volume>3</volume>
          <fpage>e1506</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.7717/peerj.1506"/>
          </comment>
          <pub-id pub-id-type="doi">10.7717/peerj.1506</pub-id>
          <pub-id pub-id-type="medline">26713253</pub-id>
          <pub-id pub-id-type="pii">1506</pub-id>
          <pub-id pub-id-type="pmcid">PMC4690386</pub-id>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
