Some significant examples of collaborations and direct deployment of EVS resources and services are briefly outlined here for NCI, caBIG, NIH, other Federal, and other partnerships. Illustrative case studies are then described more fully in the Example Case Studies section below.
|Table of Contents|
NCI Division of Cancer Treatment and Diagnosis (DCTD)
Cancer Therapy Evaluation Program (CTEP)
The Cancer Therapy Evaluation Program (CTEP) has had many and sustained collaborations with EVS from 1999 onwards, including:
- Harmonization and use of NCIt drug and molecular target information in CTEP systems.
- Harmonization and integration of CTEP disease classification with NCIt, PDQ and MedDRA in NCIm.
- Joint development, together with other partners, of the redesigned Common Terminology Criteria for Adverse Events (CTCAE) v.4, which has been widely adopted since its release in 2010. (See the detailed description in the Example Case Studies section below.)
The Cancer Diagnosis Program (CDP) - Diagnostics Evaluation Branch
- EVS is supporting gene nomenclature used in a new CDP Biomarker project, including updating HUGO in the EVS servers so it is accessible to CDP curators.
- In an extension to this project, EVS will be creating gene and protein sequence variations in the NCIt, according to HGVS guidelines, for genes/proteins of therapeutic interest as requested by CDP. The initial request is 150 genes (in progress), with about 180 protein variants, 300 gene variants, 300 fusion genes, and 300 fusion proteins.
- This work is to support creation of an application to retrieve content from the NIH Clinical Trial Database into the NCI Clinical Trials Reporting Program (CTRP), and is being done jointly with DCTD, NCI/OCE, NCI/CCR and NIH/NLM.
NCI DCTD and Division of Cancer Prevention (DCP)
EVS staff provides terminology support for the Community Clinical Oncology Program (CCOP), including concepts for use in coding four (4) major clinical trials involving 85,000 patients. An estimated total of 500 studies use NCI Thesaurus terminology.
NCI Division of Cancer Prevention (DCP)
DCP has used EVS, and worked consistently with EVS, since 2002, including the following collaborations and uses:
- Use of NCIt agent information in DCP systems.
- Joint work on improved coverage of nutritional and other preventive agents.
- Joint work in wider working groups and other initiatives to harmonize broader NCI agent coding practices.
CI Office of Communications and Education (OCE)
OCE has been a partner in EVS since 1999, providing much of the seed terminology and development effort for NCIt, and contributing to and using EVS in many ways, including:
- NCIt drug information used in the PDQ clinical trials database.
- NCI Drug Dictionary: NCI Thesaurus provides original definitions for the drugs presented in this tool, with about 40,000 visitors monthly (see section 3).
- NCIt terminology for cancers and related conditions, procedures, and chemotherapy regimens, involving many years of development and harmonization between PDQ and NCIt terminology.
- NCI Glossary includes lay definitions for key cancer terms, and is incorporated into NCI Thesaurus.
NCI Division of Cancer Control and Population Sciences (DCCPS)
DCCPS collaboration includes several terminology projects related to cancer classification, drugs, chemotherapy regimens, and statistics. DCCPS is currently launching a new initiative on standardized terminology for population health data collection.
NCI Division of Extramural Activities (DEA)
DEA is supported by EVS, which helps collect, develop and map grant-related terminology, including representing NCI in the NIH Research, Condition and Disease Categorization (RCDC) effort.
NCI Supported Cooperative Human Tissue Bank (CHTB): EVS has supported terminology creation and editing for this network of research institutions, which host NCI funded tissue facilities and services providing remnant human tissue and fluids from routine procedures to investigators (NCI, Vanderbilt, U. Penn, UAB School of Medicine, Nationwide Children's Hospital, Ohio State, University of Virginia) There is active use by 14 academic and research organizations and eight (8) commercial organizations. EVS staff assisted with matching up terminology used by these groups to NCIt terminology, creating new NCIt concepts and definitions as needed.
Cancer Central Clinical Database (C3D): EVS provides support for C3D, largely through providing the new and updated terminology and definitions for case report forms. C3D currently supports electronic submission of clinical trials data to the NCI Clinical Data System (CDS) and the Clinical Trials Monitoring Service (CTMS/Theradex).
OPEN (Oncology Patient Enrollment Network): This web-based registration system for patient enrollments onto NCI-sponsored Cooperative Group clinical trials is a highly active project; most terminology supplied for this is standard demographic terminology.
PMA-DCCPS Grant Coding: EVS has worked with DCCPS for a number of years to include in NCIt more than 1,500 concepts for grant coding for DCCPS's Portfolio Management Application. PMA terms are also inserted and appear in the NCI Metathesaurus as a separate terminology.
Common Terminology Criteria for Adverse Events (CTCAE): CTCAE is used throughout the entire oncology community as the standard classification and severity grading scale for adverse events in cancer therapy clinical trials and other oncology settings. It is also used in a number of non-oncology trials and settings.
Version 4, released in May 2009, is a major update based on extensive international participation by stakeholders and experts. It is harmonized with MedDRA at the Adverse Event (AE) level, includes revised AE terms and severity indicators to reflect clinical effects identified with current oncology interventions, and is a caBIG® vocabulary standard. This version is used by more than 50 academic and research organizations, as well as many commercial and non-profit organizations. Five different Apple applications utilize the NCI Thesaurus version of the CTCAE data, and cite NCIt as the source.
CTCAE is designed to integrate into information networks for safety data exchange, and is expected to have a significant impact in data management for AE data collection, analysis, and patient outcomes associated with cancer research and care. EVS played a central role in designing and managing this effort, working closely with CTEP, DCP, VCDE, the Vocabulary Knowledge Center, and many participants from the broader community. The revision was developed and deployed using various EVS tools including the BiomedGT Wiki, Protégé editing tools, LexEVS terminology server, NCI Term Browser, and the EVS ftp site .
This database, which predates caBIG®, provides curated information for animal models of human cancers. caMOD annotates information with NCIt terminology, and uses the LexEVS API directly to generate anatomy and diagnosis tree hierarchies. 400 concepts were added or updated for caMOD in the past six months.
ICR (Integrative Cancer Research) Nanotechnology Working Group
caNanoLab has a goal of semantic interoperability across centers performing nanoparticle characterization studies. caNanoLab is based on an information model representing nanoparticles and their physical and in vitro characterization.
EVS provides assistance in curating concept definitions with the community, making them available in NCIt; a glossary of these terms also is provided within the caNanoLab application. (Funding for additional development was recently lost, but caNanoLab continues to be used.) The Nanotechnology Working Group includes about 60 people representing approximately 40 agencies, universities and institutes, a few from Europe. caNanolab is heavily used, representing substantial use of EVS effort. It currently contains 886 samples, 72 sample sources, 3,329 characterizations, and 41 protocols, and identifies 1,073 publications. The caNanoLab homepage shows 141,668 visitors since June 3, 2010. (See also additional nanotechnology-related detail below.)
Georgetown uses LexEVS and other EVS resources for its cancer Bench-to-Bedside (caB2B) project and other activities. A local LexEVS installation, and NCI's production LexEVS servers, provide terminology support for this project. This is an example of how terminology services are being incorporated into other tools as primary components in support of translational medicine.
Washington University uses LexEVS and EVS terminology content in its clinical data warehouse project (CIDER). Washington University deployed LexEVS in 2008 as the terminology server for CIDER. The terminologies are used to code data and for information retrieval. This is an example of an academic medical center adopting NCI EVS technology to support research and clinical enterprise infrastructure.
Ohio State University Medical Center
Ohio State is using LexEVS, NCIt, and NCIm, notably for openMDR. Ohio State University launched openMDR (open metadata repository) in 2009, using local instances of LexEVS, BioPortal, and caDSR. This is an example of an academic research group adopting several open source components of NCI's EVS and semantic infrastructure, and integrating them to create a novel tool for metadata management.
University of Pittsburgh
Pittsburgh uses the NCI Thesaurus cancer, anatomy, and pathology findings terminologies for their research and informatics projects. The ODIE project is used by the University of Pittsburgh, University of California, San Diego, and Children's Hospital, Boston. This collaboration has resulted in the publication of two papers in peer-reviewed journals so far:
- Tobias J, Chilukuri R, Komatsoulis GA, Mohantry S, Sioutos N, et al: The CAP Cancer Protocols-A Case Study of caCORE Based Data Standards Implementation to Integrate with the Cancer Biomedical Informatics Grid. BMC Medical Informatics Decision Making, 20; 6:25, 2006.
- Liu K, Chapman WW, Savova G, Chute CG, Sioutos N, Crowley RS:Effectiveness of Lexico-syntactic Pattern Matching for Ontology Enrichment with Clinical Documents. Methods Inf Med. 2010: 8;49(6).
Human Studies Database (HSDB) Consortium
HSDB is using LexEVS as a core component of its collaborative, distributed, clinical research systems. The OCRe Terminology is served through an NCBO site, which uses LexEVS. This is an example of a consortium of institutions leveraging LexEVS terminology services at the core of a new workflow for the collection of human studies data.
Common Biorepository Model (CBM)
EVS has provided about 1,300 concepts for this model through support for caDSR. CBM is used in many domains including clinical trials management, ICR, in vivo imaging, and tissue banks and pathology tools.
National Library of Medicine (NLM)
Since its inception, EVS has worked with NLM on a variety of terminology content and technology efforts. EVS licenses content from and harmonizes with NLM's Unified Medical Language System (UMLS), building NCIm by modifying and extending a subset of the UMLS Metathesaurus and using NLM editing software.
NCI is also a contributor to the UMLS, for example, providing monthly builds of NCIt for inclusion in UMLS. (UMLS only publishes twice yearly; they pull whichever build is most current at the time they begin processing.) EVS also worked with NLM and other federal partners to develop the Federal Medication Terminologies framework for harmonized medication coding (see below). EVS staff provided startup phrase dictionaries and search criteria for the PubMed Cancer Subset, and jointly maintains this content with NLM on an ongoing basis.
NLM's DailyMed gets over 10 million hits each month, and each of the SPL files in DailyMed uses terminology that is maintained by NCI. There are over 27,000 SPL files on DailyMed, and another 5,000 SPL files that are not on DailyMed. Each of these SPL files requires NCIt codes.
NCI and National Human Genome Research Institute (NHGRI)
The Cancer Genome Atlas (TCGA) is a joint effort between NCI and NHGRI, developing a database of the changes that occur in the genome, associated with a specific cancer type. TCGA creates a national network of research and technology teams, and provides a mechanism for pooling results; data are publically available. 25 Studies are associated with this data, and data are being actively submitted or used by 16 academic and research organizations, 27 commercial organizations, and 17 non-profit organizations. EVS supports terminology for annotating the CDEs for tagging information and samples, mainly cell and specimen type, with information about tumor size, anatomic location, sample preparation, and patient demographics.
National Heart, Lung, and Blood Institute (NHLBI)
Since 2005, NHLBI and EVS have jointly developed terminology in NCIt for various projects including bone marrow transplant clinical trials and the Family Blood Pressure Program. Duke, through an NIH Roadmap project, the American College of Cardiology, and CDISC, have also collaborated with EVS to produce several cardiovascular data standard sets now in use at NHLBI, with a portion incorporated into CDISC SDTM.
National Institute of Child Health and Human Development (NICHD)
Since 2009, NICHD and EVS have jointly developed terminology in NCIt for pediatric terminology, including standardizing data for newborn screening forms, through the Pediatric Terminology Harmonization Initiative, developed to assist Pediatric clinical researchers. This is associated with 848 NICHD Clinical Trials, and is being used by 52 different academic and research organizations.
National Institute of Dental and Craniofacial Research (NIDCR)_*
Since 2008, NIDCR and EVS have jointly developed terminology in NCIt for dental treatments and medical procedures.
NIH Biomedical Translational Research Information System (BTRIS)
Collaboration includes planned EVS publication of the BTRIS Research Entities Dictionary (RED) in support of NIH researchers' coding, retrieval, and analysis of clinical research data stored in BTRIS. RED began with NCIt as a foundation.
NCIt is one of four NIH-approved terminologies for grant coding, and EVS has helped develop the Research, Condition and Disease Categorization (RCDC) grant coding system.
EVS Partnerships and External Adoption
NCI EVS has extensive external partnerships to develop terminology standards, content, technology, and operational support, greatly broadening the base of adoption and having a major impact on the wider biomedical community.
U.S. Food and Drug Administration (FDA)
FDA has worked with EVS since 2001, with formal Memoranda of Understanding starting in 2004, to develop and harmonize terminology content, standards and systems in areas of mutual interest such as drugs, devices, patient safety, and clinical trials. FDA has chosen EVS and NCIt for developing and publishing many important terminology sets; some 15,000 FDA terms in over 20 defined subsets are now maintained in NCIt and required for regulatory reporting and other purposes. These include:
- Structured Product Labeling (SPL): Standard terminology for Drug Establishment Registration (Regulated Product Submission), Drug Listing and the Content of Labels. 16 NCIt subsets used for submission of proposed labeling by all manufacturers using electronic formats. There are 9,466 establishments from over 100 countries that use the SPL terminology in order to comply with federal regulations to list their products. There are approximately 40,000 subscribers to the FDA's SPL listserv, and this is one of the primary mechanisms to inform users of changes to the SPL terminology that is maintained by NCI. FDA does not track the number of hits against http://www.fda.gov/ForIndustry/DataStandards/default.htm and its sub pages, but they suspect that the number of hits is very high; when firms do not select the correct NCIt code, their submitted SPL file will not pass validation.
- CDRH Device Event Problem Codes: NCIt subsets used for the reporting of medical device problems to FDA. CDRH is responsible for ensuring the safety and effectiveness of medical devices and eliminating unnecessary human exposure to man-made radiation from medical, occupational and consumer products. Approximately 200 organizations from some 3,000 different reporting locations report to the CDRH using NCI Thesaurus terminology. CDRH receives approximately 35,000 submissions per month that are based on NCI Thesaurus terminology.
- Individual Case Safety Report (ICSR): NCIt subsets used for adverse event reporting. Proposed regulations for electronic submissions will create similar levels of use for these subsets.
- eCTD (electronic Common Technical Documents): Standard terminology for regulatory forms required by the Center for Drug Evaluation and Research (CDER).
- Drug Submissions: Beginning June 1, 2009, FDA no longer accepts paper submissions for drug establishment registration and listing unless a waiver is granted. Moving from a paper-based format to an electronic system will improve the timeliness and accuracy of the submissions. This is not possible without the terminology provided by NCI Thesaurus. Of 22,246 New Drug related Submissions from October 2009 - September 2010, (63%) were in electronic format submissions that required terminology from NCI Thesaurus.
- Stability: NCIt provides terminology for FDA and HL7 Stability Data Standards, including human pharmaceuticals, animal drugs and medical devices that are in regulatory submissions, amendments, supplements and annual reports.
(For more information, visit the NCI website.
Clinical Data Interchange Standards Consortium (CDISC)
All CDISC controlled terminology – more than 9,800 terms – is maintained and published as NCIt subsets, as part of a partnership started in 2002 to develop and support global data standards for medical research. This includes four main terminology efforts:
- Study Data Tabulation Model (SDTM): An approved standard for FDA submissions, SDTM has been downloaded more than 14,000 times in over 60 countries, primarily for institutional use. More than 270 commercial organizations use SDTM, as do numerous academic, non-profit and research organizations.
- Clinical Data Acquisition Standards Harmonization (CDASH) is developing clinical research study content standards in collaboration with sixteen partner organizations including NCI.
- Analysis Data Model (ADaM) supports efficient generation, replication, review and submission of analysis results from clinical trial data.
- Standard for Exchange of Non-Clinical Data (SEND) extends Study Data Tabulation Model (SDTM) for non-clinical studies and now includes some 1,900 additional terms.
(For more information, visit the NCI website.)
The CDISC Shared Health and Research Electronic Library (SHARE) project is also building a collaborative authoring platform for harmonizing data elements from multiple organizations, using LexWiki for its initial prototype. CDISC has created a data element curation process, including terminology linking, using the LexWiki and LexGrid technologies; this process provides a collaborative framework and platform for representation and harmonization of clinical study data elements. CDISC will use open tools created by NCI as the basis for developing SHARE.
National Council of Prescription Drug Providers (NCPDP)
NCPDP is a not-for-profit, ANSI-accredited, Standards Development Organization with over 1,600 members representing virtually every sector of the pharmacy services industry. NCPDP creates and promotes the transfer of data related to medications, supplies, and services within the healthcare system through the development of standards and industry guidance. In 2009, NCPDP decided to partner with EVS to use NCIt subsets to support two of those standards, employed by some 200 vendors serving approximately 15,000 pharmacies nationwide:
- NCPDP SCRIPT Standard supports messages for new prescriptions, prescription changes, refill requests, prescription fill status notification, prescription cancellation, medication history, and transactions for long term care environments. Many large providers such as First DataBank and Surescripts, the nation's largest e-prescriber, use this standard. Surescripts alone connects thousands of pharmacies across the US, and is connected to the largest network of payers and Medicaid Fee for Service payers nationwide.
- NCPDP Telecommunication Standard supports the electronic communication of claims and other transactions between pharmacy providers, insurance carriers, third party administrators, and other responsible parties.
(For more information, visit the NCI website.)
Federal Medication Terminologies (FMT)
Work started in 2002 as an interagency collaboration between NCI EVS, FDA, VHA, and NLM – joined later by AHRQ, CMS, DoD, and EPA – to improve the exchange and public availability of medication information with coordinated development of terminology standards. The initial FMT terminology set has been endorsed by U.S. Federal standards efforts including the National Committee on Vital and Health Statistics (NCVHS), Consolidated Health Informatics (CHI), the Healthcare Information Technology Standards Panel (HITSP), and the Office of the National Coordinator for Health Information Technology (ONC) within the Department of Health and Human Services (HHS). (For more information, visit the NCI website.)
Veterans Health Administration (VHA)
VHA has worked closely with EVS since 2002. Under an ongoing Memorandum of Understanding, VHA works with EVS on collaborative terminology policy and products, including content collaboration and publication of the VA's National Drug File Reference Terminology (NDF-RT), used by both agencies as a drug information reference resource.
The VHA also performed a thorough comparison of the functional capabilities of LexEVS to those of other terminology servers. The VA provided the results to the VKC, which transformed the matrix into a document that can be used by potential adopters of LexEVS as they evaluate the capabilities of the system. This is an example of a valuable contribution from the community that is not code-based; in an open source model, contributions of documentation can be as important as contributions of code.
Health Level 7 (HL7)
EVS supports terminology content for the Regulated Clinical Research Information Management (RCRIM) committee of HL7, and for other committees as appropriate including Patient Safety, Pharmacy, Clinical Genomics, and the Clinical Interoperability Council.
World Health Organization (WHO)
WHO requested in June, 2009, a Classification Markup Language (ClaML) LexEVS data processing program that could be used to render ICD-10 in preparation for, and as the foundation of, ICD-11. This is an example of an international standards organization using NCI's open source tooling to support the development of a new version of a major international terminology standard.
WHO work on ICD-11 is also using NCI Thesaurus as an important source of cancer terminology and definitions.
Stanford/National Center for Biomedical Ontology (NCBO)
NCBO bases its BioPortal terminology services on LexEVS. NCIt is generally at or near the top of the NCBO ontology use chart (see section 2 above). NCBO and EVS maintain ongoing coordination and harmonization efforts through both caBIG® and other channels. For example, NCBO participates in the VCDE working group on Representing Terminology Metadata, which is adapting work begun by NCBO in this area for use by NCI and NCRI. NCBO also makes its terminologies available through caGrid.
NCBO built its NCBO BioPortal ontology services on top of LexEVS, supporting a very wide collection of ontologies that are actively used in biomedicine. This is an example of how two federally-funded groups are working together on the development of resources that will benefit the biomedical terminology community.
Open Biomedical Ontologies (OBO)
EVS has worked with the OBO Foundry group since around 2005 to develop shared principles for open ontologies. NCI Thesaurus is designated as an Application ontology, since it uses and references domain ontologies within the OBO Foundry group. EVS makes several of the OBO Foundry ontologies available through LexEVS for caBIG® use. (For more information, visit the OBO Foundry website http://www.obofoundry.org/ .)
The Taiwan Cancer Registry, a population-based cancer registry founded in 1979, uses NCI Thesaurus terminology. Hospitals with greater than 50-bed capacity that provide outpatient and hospitalized cancer care are recruited to participate in reporting all newly diagnosed malignant neoplasms to this registry.
Other Sample Case Studies
Nanotechnology, and more specifically nanomedicine, has become important in the development of reagents for cancer detection and treatment. NCI established Cancer Centers of Nanotechnology Excellence (CCNE) to support translational nanomedical research. The NCI CCNE office became a partner with CBIIT in 2006 to develop a data sharing platform called caNanoLab.
NCI Thesaurus (NCIt) has been supporting concept curation for development of caNanoLab since its inception. NCIt editors have worked with the developers and users of caNanoLab from the CCNEs and other academic institutions to define concepts for data curation and to expand the object model to include data submission for both characterizations of experimental nanomaterials and translational research studies. (See additional details above.)
caBIG® has also established a Nanotechnology Working Group as part of its Integrative Cancer Research Workspace (ICR Nano WG) with a mission to federate nanotechnology databases. One requirement of this group has been to develop data and vocabulary standards to facilitate federation and increase data accessibility. The EVS is contributing to this effort as active participants in the working group. Part of the working group effort is the continuing development of the Nanoparticle Ontology (NPO) from Washington University in St. Louis. EVS has supported this effort in several areas: giving feedback on ontology structure and terminology best practices, supporting NPO curation using the NCI Protégé platform, loading and hosting NPO on LexEVS, preparing NPO for integration into the NCI Metathesaurus (NCIm), and planning for future editing of NPO in the BiomedGT Wiki collaborative editing environment.
NPO (NanoParticle Ontology): This terminology is loaded in NCI Metathesaurus, on LexEVS, and on the NCI Term Browser. NPO curators use the NCI Protégé curation tool and they use NCI Thesaurus as a cross-reference and a source for some of their definitions.
NanoTAB: Developed by CBIIT, Oregon State University, PNNL, Washington University St. Louis, Stanford, Jackson Labs, Pennsylvania BioNano Systems, NIOSH, NCI Frederick NCL, Emory/Georgia Tech. This tool is used by all members of the ICR Nano Working Group. Despite recent loss of caNanoLab funding, NanoTAB continues to be used heavily.
Imaging standards development requires the support of multiple products made available through EVS, including publication of Radlex terminology, developed through a collaboration of the Radiological Society of North America (RSNA), which convened experts in imaging informatics and radiological subspecialties to create this resource, now made freely available. RadLex has developed into a rich, structured radiology-specific ontology, which currently includes more than 30,000 terms and to which EVS provides content as well as publication support. EVS incorporates RadLex into the NCI Metathesaurus, and also supports imaging terminology in the NCI Thesaurus as needed by the imaging community.
MedDRA (Medical Dictionary for Regulatory Activities) is an ICH standard for regulatory reporting. EVS contributes to updates of the cancer domain for this widely employed international terminology. The NCI Thesaurus is used as the basis to update MedDRA neoplastic terminology. MedDRA is translated into 11 languages, with approximately 3,000 institutional subscribers from 60 countries.
Use of LexEVS
MD Anderson is using a local LexEVS server as part of their enterprise infrastructure. Special resources were dedicated to resolving initial software compatibility and other issues, ensuring a successful deployment. NCI EVS terminology browsers have also been deployed, as have NCIt and other EVS terminology resources. This is an example of leveraging a wide range of EVS resources and services in support of the research and clinical enterprise infrastructure of a leading cancer center.
Emory University is using LexEVS to develop and host local ontologies. Uses include terminology support for an analytic data warehouse, which incorporates custom patient classes defined using ICD-9 codes. This is an example of an academic medical center deploying and extending EVS components.
GE is developing a platform called Qualibria, which includes LexEVS as a terminology server. VKC has been working with GE since 2008. As part of the collaboration, GE created an extension to the LexEVS 5.1 API based on the Common Terminology Services specification. GE provided the code for that extension, which is now available to the community via the VKC web site. This is an example of NCI open source technology being bundled into a commercial healthcare product.
Mayo Health Solutions Global Products and Solutions is in the process of deploying LexEVS for terminology hosting and management. The project will eventually migrate to the GE Qualibria platform, which also uses LexEVS. This is an example of industry partners engaged in the development and commercialization of NCI open source tooling.
The Biomedical Knowledge Engineering (BiKE) lab at Seoul National University, Korea, adopted the 2005 version of the LexGrid model and over the last several years created an entire terminology-based application suite on that model. The VKC is currently working with BiKE to finalize an agreement under which they would provide to us the source code for a terminology mapping UI that was developed as part of their project. This would be a potentially significant contribution, as it would add a new tool in an area with a known gap in the current functionality of LexEVS.
McGill University Health Center, Canada, is connected to the TRANSFoRm project for European health care reform. LexEVS was chosen as the terminology server for the project, but a new loader is required in support of the ATC terminology. The VKC is currently working with them on the development of the ATC loader, which includes requirements gathering, coding, testing, and documentation. This represents an example where a project-specific use case provided by a customer is used as the basis for collaborative development of an open source contribution.