Unable to render {include} The included page could not be found.

Version 
Unable to render {include} The included page could not be found.
 (
Unable to render {include} The included page could not be found.
)

Prepared by the 

Unable to render {include} The included page could not be found.

 

Notes to Readers

Unable to render {include} The included page could not be found.

Revision History

Date

Version

Unable to render {include} The included page could not be found.

Unable to render {include} The included page could not be found.
Unable to render {include} The included page could not be found.

 

© 2016 Clinical Data Interchange Standards Consortium, Inc. All rights reserved.  See  Representations and Warranties, Limitations of Liability, and Disclaimers.

Introduction

This Therapeutic Area Data Standards User Guide for _Therapeutic_Area_ (TAUG-_TA_) was developed under the Coalition for Accelerating Standards and Therapies (CFAST) initiative.

Instructions to Developers

Teams: you must customize this page at least a little. Do something to bring some personality to the document! It needs to be a little different for each TA guide, to encourage those who read more than one to not get into the habit of skipping sections.

For instance, if the document was not developed under the CFAST initiative, then of course you will want to change the first sentence above so that it's no longer telling lies. Use that first change as a springboard – and don't be afraid to wander from a fully formal style of writing. The more it feels like boilerplate, the easier it is to skim.

If you have difficulty thinking of how to customize this page, try talking to your clinical experts, other project managers, and the program-level staff. It will probably be a collaborative effort.

The purpose of this TAUG-___ is to describe how to use CDISC standards to represent data pertaining to _therapeutic_area_ studies. This _nth_ version (v#) focuses on ____________________________________________________.

Instructions to Developers

In place of the underscore above, insert a broad description of the scope of the project. Here are some examples to start you off:

  • "clinical trials of drugs to treat asthma in an adult population"
  • "phase 1-3 clinical trials of drugs to treat the chronic infection of hepatitis C genotypes 1-6 in adults in the outpatient setting"
  • "traumatic brain injury in adults"

(This does not count as part of customizing the introduction.)

If you want to expand on what is currently out of scope but might be in scope in later versions, feel free. If you want to link to the project proposal in the appendices, again, feel free.

(This may count as part of customizing the introduction, depending on how common it becomes.)

How to Read this Document

  1. First, read _______________________ to gain some familiarity with _______________________. These standards are available from: http://www.cdisc.org/.
  2. Next, read Introduction to Therapeutic Area Standards (at http://wiki.cdisc.org/x/SSy8AQ) and/or take CDISC's free training module TA001 - Overview of Therapeutic Area User Guides (at https://secure.trainingcampus.net/uas/modules/trees/store/wcatalog.aspx?cat=1015&ci=4&vtype=2&pi=0) to be sure to know what to expect from a therapeutic area user guide such as this document. 
  3. Read this guide all the way through (without skipping any sections) at least once.
  4. Finally, revisit any sections of particular interest.
Instructions to Developers

Completing this section

  • Fill in the blanks in step 1 with (a) the names of the foundational standards upon which this document is based, and (b) what, in general, the reader should already be familiar with before reading this guide (such as the CDISC data models and their general rules for implementation).
  • Fill in the blank in the paragraph below with the tiny link (such as the one to Introduction to Therapeutic Area Standards above) to the Draft Standards of Interest (DSoI) page for the guide; or if there are no draft standards of interest, remove the paragraph.
  • All fill-in-the-blanks must be replaced with actual text before the document can go to internal review.

Expanding on this section

  • The instructions above, and both paragraphs below, are all extensible. They can also be modified slightly, so long as their basic meaning is unaltered.
  • Any additional instructions should not be simply appended to the end of the steps above, but be inserted so that the entire set of instructions reads in approximate chronological order.
  • Any companion documents (or list of such) should be added to the first paragraph below, either before or after the sentence provided depending on whether you think they're more or less important and/or interesting than the DSoIs. More important/interesting companion documents go first.
  • Any additional caveats or disclaimers — assuming they do not simply restate a general caveat already given in Introduction to Therapeutic Area Standards — should be added to the second paragraph below, after the sentence provided.
  • Additions to the steps above should be written in the imperative; to the paragraphs below in the indicative (see also: Grammatical mood at Wikipedia).

Draft standards of interest to this document are listed at: _____________________.

All general caveats for TA standards given in the Introduction to Therapeutic Area Standards (http://wiki.cdisc.org/x/SSy8AQ) apply to this document.

Organization of this Document

This document is divided into the following sections:

  • Section 1, Introduction, provides an overall introduction to the purpose and goals of the _Therapeutic_Area_ project.
  • Section 2, ________________________________________________________________
  • (etc.)
  • Appendices provide additional background material and describe other supplemental material relevant to _therapeutic_area_.
Instructions to Developers

The TAUG Content Guide has some default language for sections, but don't rely too heavily on this if you can avoid it.

Subject and Disease Characteristics

Disease Assessments

Routine Data

Analysis Data

Appendices

Project Proposal

NameofTeam Team

Instructions to Developers

Change the name of this page to reflect the name of the team.

Names are given in natural order (e.g. the given name preceding the family name in Western cultures). With the exception of the team lead(s), team members should be listed in order by surname.

NameInstitution/Organization
_____________, Team Lead 
  
  
  
  
  

Glossary and Abbreviations

Instructions to Developers

This is the preliminary glossary. Add and/or remove entries so that it includes terms used in this standard that readers may wish to look up, and does not include any terms that are not used in the guide.

ADaM

Analysis Data Model

ADaMIG

ADaM Implementation Guide

BRIDG

Biomedical Research Integrated Domain Group

Biomedical ConceptA high-level building block of clinical research and/or healthcare information that encapsulates lower level implementation details like variables and terminologies.

CDASH

Clinical Data Acquisition Standards Harmonization Project

CDISC

Clinical Data Interchange Standards Consortium

CFAST

Coalition for Accelerating Standards and Therapies

Collected

“Collected” refers to information that is recorded and/or transmitted to the sponsor. This includes data entered by the site on CRFs/eCRFs as well as vendor data such as core lab data. This term is a synonym for “captured”.

Controlled Terminology

A finite set of values that represent the only allowed values for a data item. These values may be codes, text, or numeric. A code list is one type of controlled terminology.

CRF

Case report form (sometimes called a case record form). A printed, optical, or electronic document designed to record all required information to be reported to the sponsor for each trial subject.

Domain

A collection of observations with a topic-specific commonality about a subject.

eCRF

Electronic case report form

Foundational Standards

Used to refer to the suite of CDISC standards that describe the clinical study protocol (Protocol), design (Study Design), data collection (CDASH), laboratory work (Lab), analysis (ADaM), and data tabulation (SDTM and SEND). See http://www.cdisc.org/ for more information on each of these clinical data standards.

MedDRA

Medical Dictionary for Regulatory Activities. A global standard medical terminology designed to supersede other terminologies (such as COSTART and ICD9) used in the medical product development process.

NCI EVS

National Cancer Institute (NCI) Enterprise Vocabulary Services

NIH

National Institutes of Health

Patient

A recipient of medical treatment.

PRO

Patient-reported outcome

SDS

Submission Data Standards. Also the name of the team that maintains the SDTM and SDTMIG.

SDTM

Study Data Tabulation Model

SDTMIG

SDTM Implementation Guide (for Human Clinical Trials)

SHARE

Shared Health and Clinical Research Electronic Library. CDISC’s metadata repository.

Subject

A participant in a study.   

UML

Unified Modeling Language

Non-Standard Variables

The following table lists the non-standard variables used in this document, and gives their parent domain and variable-level metadata.

Parent DomainVariableLabelSAS Data TypeXML Data TypeCodelist/Controlled TermsRoleDescriptionNotes
         
(Parenthesis indicates CDISC/NCI codelist)

Instructions to Developers

If no NSVs use a CDISC/NCI codelist, then remove the line in italics under the table.

References

Instructions to Developers

Not every sub-section of this appendix will necessarily apply to any given TA standard. If the section does not apply, remove it.

The sections are given together on this page in the template, but should be split into individual child pages once it's clear which ones will be kept.

Works Cited

  • This list contains the full reference information for works cited within the document. Each item pairs with the inline citation(s) with which it shares its ordinal number.
  • By the time of publication, works should be given in the order of first citation within the document, and use AMA format, but worry about that second. Worry about making sure the list is correct and complete first.
  • The entry given below is an example of AMA format, and should not be retained.

A work is "cited" when it is the source of a direct or indirect quote. The phrase or sentence to which a citation is attached is thereby attributed to the work cited, which both gives credit where it is due and disavows the quoter of necessarily agreeing (or disagreeing) with the quotee.

A work might also be cited when it serves as supporting evidence for a defensible statement, but CDISC standards are generally didactic, so this form of citation is rare.

Figures

  • Each row in this table represents a figure that was not created by CDISC. The first column holds the figure number and caption as given in the current document; and the second column holds the copyright information and means/date of permission to reproduce, if applicable.
  • See the TAUG Content Guide has examples.

Further Reading

  • This list contains the full reference information for any works not actively cited within the document, but which might still be of interest to the reader, or were mentioned or referred to at some point in the document, or even were once cited at an earlier point in in the document's development but are not any more. If you already have a list of potential references, add them here.
  • Works listed here should also use AMA format, but they are listed in alphabetical order by author, or by title if no author is known.

A work is "mentioned" or "referred to" when it is named or otherwise identified within the text, but not as part of an attribution. Referring to a work directs the reader to it, whereas mentioning usually happens when the existence of the work is incidental to the point of discussion and not the point itself.

Works Cited

  1. Wold JD, Wood F. Suggested guidelines for grammar and punctuation. J Abbr. 2016;29(10)6787.

Figures

Figure number
Caption 
Copyright information and means/date of permission to reproduce, if applicable
  
  

See the TAUG Content Guide for examples of how to complete this table.  

Remove this section if there are no figures (which includes tables, when reproduced verbatim from an existing work) in the document. 

 Further Reading

  • List of works that are of interest to the TAUG but were not actively cited within it.

Representations and Warranties, Limitations of Liability, and Disclaimers


CDISC Patent Disclaimers

It is possible that implementation of and compliance with this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any claim or of any patent rights in connection therewith. CDISC, including the CDISC Board of Directors, shall not be responsible for identifying patent claims for which a license may be required in order to implement this standard or for conducting inquiries into the legal validity or scope of those patents or patent claims that are brought to its attention.

Representations and Warranties

“CDISC grants open public use of this User Guide (or Final Standards) under CDISC’s copyright.” 

Each Participant in the development of this standard shall be deemed to represent, warrant, and covenant, at the time of a Contribution by such Participant (or by its Representative), that to the best of its knowledge and ability: (a) it holds or has the right to grant all relevant licenses to any of its Contributions in all jurisdictions or territories in which it holds relevant intellectual property rights; (b) there are no limits to the Participant’s ability to make the grants, acknowledgments, and agreements herein; and (c) the Contribution does not subject any Contribution, Draft Standard, Final Standard, or implementations thereof, in whole or in part, to licensing obligations with additional restrictions or requirements inconsistent with those set forth in this Policy, or that would require any such Contribution, Final Standard, or implementation, in whole or in part, to be either: (i) disclosed or distributed in source code form; (ii) licensed for the purpose of making derivative works (other than as set forth in Section 4.2 of the CDISC Intellectual Property Policy (“the Policy”)); or (iii) distributed at no charge, except as set forth in Sections 3, 5.1, and 4.2 of the Policy. If a Participant has knowledge that a Contribution made by any Participant or any other party may subject any Contribution, Draft Standard, Final Standard, or implementation, in whole or in part, to one or more of the licensing obligations listed in Section 9.3, such Participant shall give prompt notice of the same to the CDISC President who shall promptly notify all Participants.

No Other Warranties/Disclaimers. ALL PARTICIPANTS ACKNOWLEDGE THAT, EXCEPT AS PROVIDED UNDER SECTION 9.3 OF THE CDISC INTELLECTUAL PROPERTY POLICY, ALL DRAFT STANDARDS AND FINAL STANDARDS, AND ALL CONTRIBUTIONS TO FINAL STANDARDS AND DRAFT STANDARDS, ARE PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND THE PARTICIPANTS, REPRESENTATIVES, THE CDISC PRESIDENT, THE CDISC BOARD OF DIRECTORS, AND CDISC EXPRESSLY DISCLAIM ANY WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR OR INTENDED PURPOSE, OR ANY OTHER WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, FINAL STANDARDS OR DRAFT STANDARDS, OR CONTRIBUTION.

Limitation of Liability

IN NO EVENT WILL CDISC OR ANY OF ITS CONSTITUENT PARTS (INCLUDING, BUT NOT LIMITED TO, THE CDISC BOARD OF DIRECTORS, THE CDISC PRESIDENT, CDISC STAFF, AND CDISC MEMBERS) BE LIABLE TO ANY OTHER PERSON OR ENTITY FOR ANY LOSS OF PROFITS, LOSS OF USE, DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, OR SPECIAL DAMAGES, WHETHER UNDER CONTRACT, TORT, WARRANTY, OR OTHERWISE, ARISING IN ANY WAY OUT OF THIS POLICY OR ANY RELATED AGREEMENT, WHETHER OR NOT SUCH PARTY HAD ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.

Note: The CDISC Intellectual Property Policy can be found at: https://www.cdisc.org/sites/default/files/2020-09/cdisc_policy_003_intellectual_property_v2019.pdf

  • No labels