Metadata Needs and Support
The caDSR (Cancer Data Standards Registry and Repository) supports a broad community of users both inside and outside of NCI that have requirements to ensure the longevity and aggregability consistency of biomedical research data. Participants Content owners and end users have included NCI and its partners in clinical trials, academic institutions (including NCI Designated Cancer Centers, SPOREs and Cooperative GroupsNCTN/ETCTN), other NIH institutes (including NICHD, NHLBI and NIDCR), other federal agencies (in particular the FDA), pharmaceutical companies, standards development organizations (e.g. CDISC) and a range of international biomedical organizations. For more information see the caDSR Collaborations and Use.
Requirements from researchers and/or their supporting informatics groups drive the creation of metadata in the caDSR, and not vice versa. Metadata content development usually starts with a request for assistance by a researcher planning a clinical or research data collection. Metadata curators work with the user and EVS to identify an appropriate vocabulary while identifying a mix of new and existing CDE content to support the scientific requirement. Curators always attempt to reuse existing metadata (where that content supports the scientific requirement) as a way to help scientists ensure the compatibility of their data with other data collected across the enterprise.. Because so many groups need metadata content, and to ensure that the recording of metadata does not become a bottleneck in the research process, all caDSR roles are open to individuals in the community upon completion of appropriate training. Training is role based and includes courses on infrastructure, methodologies, and tool usage. Most of the training is managed through self-paced modules, while the actual tool use modules are done through web sessions. More information can be found on the caCORE training wiki., and sometimes researchers request that their content be harmonized with specific existing projects.
The word cloud that follows illustrates the broad variety of collections of data elements that are reposited in the caDSR for various communities and types of studies.
CBIIT’s management of metadata began as part of an effort to support CTEP’s reporting for breast cancer trials, and from a need to develop and disseminate standards that would ensure consistency and accuracy in reporting across the Cooperative GroupsNCI Clinical Trial Network (NCTN/ETCTN) and Lead Protocol Organizations (LPOs). This led to the establishment of a centralized resource and associated web-based tools for creating, clearly documenting, and sharing human- and machine-readable data descriptions. The need to maintain and share data about data, or metadata, became the basis for the NCI’s repository of CDEs, metadata, and data standards, what is now known as the caDSR. A CDE Steering Committee was formed to define what kind of metadata was needed for the repository. Driven by the needs from community to create, share, and manage CDEs over time, a set of metadata attributes was established, which included attributes such as human friendly name(s), text definition(s), valid values, unique identifiers, and workflow status. Consultation with appropriate experts identified ISO 11179, an international standard for data-element metadata registries, as meeting the needs identified by the CDE Steering committee. As time went on, more groups wanted to record their data elements and share them via the caDSR, so additional features were added, including extensions of ISO 11179 to enable storage templates for CRFs that use CDEsof metadata describing Case Report Forms (CRFs) that use CDE metadata as the basis for questions on the CRFs.
As more groups recorded their data elements in caDSR, the difficulty in creating high-quality names and definitions for data elements became recognized as a challenge for data-element curators, as well as a best practice for clarifying the meaning of the data, but also a challenge for data-element curators. Consequently, ISO 11179-5 Naming Principles were used to establish naming conventions that could be applied across groups. The same naming conventions are used in the National Information Exchange Model (NIEM). Since NCI had the EVS terminology services available, this was seen as a reasonable means by which to aid this task by giving curators access to well-formed and NCI-preferred names for concepts that form the name of the CDEs. At present, curators find concepts in EVS based on synonym or concept id searches, and the EVS preferred-term name and definition streamline their task. The challenge of ensuring that duplicate CDEs were not created led to leveraging the parts of the ISO 11179 metamodel along with a preference for the use of NCIt concepts so the system could semi-automatically recognize and promote reuse of existing content. NCIt is a specialized cancer terminology that includes additional knowledge from the literature about these concepts and is modeled as an OWL ontology with relationships were concepts have various types of relationships and mappings defined to other concepts. It also includes mappings to the UMLS where they exist. Therefore, a link to NCIt concepts from caDSR concepts content can help test similarity between CDEs. It Links to NCIt concepts can also provide access to researchers for exploring the meaning of a data that conforms to a given CDE in greater depth.
Although this activity began as a means to support the cooperative groupsCTEPs trials networks, the caDSR now supports a much wider audience. This includes clinical trials run by the NCI intramural program, the Center for Cancer Research (CCR), and Division of Cancer Prevention (DCP); Specialized programs of Research Excellence (SPOREs), Cancer Centers and other academic medical centers, other NIH institutes and centers as well as standards groups such as CDISC and a variety of international partners.
A note on the term “Common Data Element” (CDE). While originally intended to mean a data element that was reused across groups, the term has come to mean any description of a variable and its valid values. In this document, we will use the standard NCI version of this definition, which is to say a variable description (including valid values) described in the caDSR using its implementation of the ISO 11179 variable, regardless of whether the element in question has been used more than once.
Information about caDSR Initiatives and Tools
This is the wiki home page for caDSR. You may edit pages if you are working on them with the authors. You are welcome to leave comments. This wiki includes the following.
- caDSR Content
Focuses on the Metadata Content within the caDSR and is most useful for consumers. The pages include Data Standards, Harmonization, Reuse and Business Rules that establish the capabilities of the caDSR Tools.
- caDSR Database and Tools
Focuses on the features of the Tools from the perspective of users. The pages include descriptions for each tool, Release Notes and reference materials. The information on these pages is specific to the use case implementation of Business Rules recorded in the caDSR Content pagesProvides access to caDSR tools and links to the tool summary page for current user documentation and technical information like release notes.
- caDSR for Application Developers
Focuses on the software interfaces to the caDSR available to programmers and software developers. The pages include details on the caDSR API, XML messages produced and consumed by the caDSR products and the caDSR UML Model.
- caDSR Installation and Implementation
Focuses on Open Source adoption of the caDSR Database and Tools. The pages include ISO 11179 implementation extensions, software implementation architectures and Downloads.
Focuses on specific projects. The pages include projects spanning across tools and products and projects involving inter-metadata registry sharing. For projects related to one specific tool, refer to the caDSR Database and Tools section.
Documentation and FAQs
- Index Page - Release Notes for caCORE
- caDSR 4.x Technical Guide
- Semantic Integration Workbench and UML Model Loader 4.1 User Guide PDF
- caBIG® Compatibility Guidelines
- Documentation Index for caCORE Tools
- Index Page - FAQs for caCORE Tools and Projects and caBIG
- Javadocs Index for caBIG-CBIIT Tools
We continually look at new requirements and have an initiative begun in 2014 to replace the aging software and infrastructure currently supporting caDSR end users. This is an opportunity to link our efforts more broadly with NIH wide CDE and metadata initiatives. Please see the caDSR Requirements pages for more information.
For a complete list of current caDSR Tool user documentation, application guides, release notes, and FAQs, see the caDSR Documentation wiki page.
Email Lists and Forums
Email address or URL
For end user issues regarding the caDSR tools and content
For developer issues regarding the caDSR APIs and use of caDSR Metadata
Archive for content users such as Curators
Archive for developers using caDSR Metadata, such as UML Model owners (subscription required)
Index of all NIH mail lists
How to Cite caDSR
To cite the NCI Semantic Infrastructure, use the following reference.