CDISC Implementation for Dummies

CDISC (Clinical Data Interchange Standards Consortium) standards have been in development for many years. There have been major structural changes to the recommended standards from version 2 to 3. It is still an evolving process but it has reached a point of critical mass such that organizations are recognizing the benefits of taking the proposed standard data model out of the theoretical realm and putting it into real life applications. The complexity of clinical data coupled with technologies involved can make implementation of a new standard challenging. This paper will explore the pitfalls of the CDISC SDTM (Submission Data Tabulation Model) transformation and present methodologies and technologies that make the transformation of nonstandard data into CDISC efficient and accurate.


There are some tasks within the process that can be applied asynchronously, but the majority of the steps depend on each other and therefore follow a sequence. The process is described below:




It is important to have a clear vision of the processes for the project before you start and to be aware that the effort is resource-intensive. This provides the ability to resource and plan for all the processes and enables adherence to deadlines and budgets. The organization and planning for this undertaking is an essential first step towards an effective implementation.

...


STEP 5: TRANSFORMATION SPECIFICATION – The specification for transforming to CDISC standards is a detailed road map that will be referenced and used by all team members during the transformation implementation and review. There can be different technologies used to perform this task. The following example utilizes tools including MS Excel and Transdata™. Dataset transformation is a process in which a set of source datasets and their variables are changed to meet new standard requirements. The following list describes some of the changes that can occur:

  1. Dataset Name - SAS dataset names must be updated to match SDTM standards, which require them to be no more than 8 characters in length.
  2. Dataset Label - The descriptive labels of SAS datasets must be modified to conform to SDTM standards.
  3. Variable Name - Each variable within a SAS dataset has a unique name. Variable names can be the same across different datasets, but if they share the same name, they are generally expected to possess the same attributes. Variable names are no more than 8 characters in length.
  4. Variable Label - Each variable has an associated label that describes the variable in more detail. Labels are no more than 40 characters in length.
  5. Variable Type - A variable’s type can be either character or numeric.
  6. Variable Length - A character variable can vary in length from 1 to 200 characters.
  7. Format - Variable format will be updated.
  8. Yesno - If the value of the variable is "yes", it will produce a new row with the newly assigned value of the label.
  9. Vertical - Multiple variables can be assigned to one variable that will produce a row if it has a value.
  10. Combine - Combine values of multiple source variables into one destination variable.
  11. Drop - The variable from the source dataset will be dropped when creating the destination data.
  12. Same - The same variable with all of the same attributes will be kept in the destination data.
  13. Value Change - This can have either a recoding of values or a formula change. This will change the actual values of the variable.

There may be other types of transformations, but these are the common transformation types that are usually documented in the specification. The transformation specification is stored in an Excel spreadsheet and is organized by tabs. The first tab named "Tables" contains a list of all the source tables. The subsequent tabs contain the transformation specifications for each source dataset as specified in the initial tables tab.

more details at: CDISC Papers , CDISC Software, Define.xml Software and SAS Outsourcing

Bookmark and Share

Comments

  1. SAS Training IndiaMay 26, 2013 at 10:06 PM

    Clinical trial is a research conducted in human volunteers to assess the protection and effectiveness of the investigational Drug/molecule.Clinical SAS programming. I have included the important models of CDISC:

    i) Operational Data Model (ODM) - it helps the activity of clinical details gathered from several resources to one operational data source. The resources of the details are paper CRF, eCRF, individual journal, etc.

    ii) Analysis Data Model (ADM) - it describes a standard for analysis datasets that are used to generate mathematical reviews for regulating syndication. The dataset should be ready for analysis to be conducted using SAS techniques directly without any further perform on the details.

    iii) Study Data Tabulation Model (SDTM) - it describes a conventional framework for data tabulations that are to be posted as part of a item application to a regulating power such as the FDA. The current edition being used is 3.1.1 SDTMIG.

    iv) Laboratory Study Model (LSM) - it works towards the growth of a conventional model for purchase and interchange of lab details which is the biggest component of the Clinical Trial data.

    ReplyDelete

Post a Comment

Popular posts from this blog

SASGF12 Opening Session with Jim Goodnight starting a technical demo ... nice :) Here is a video of it: http://ping.fm/sn6dY
Read more

Clinical Trials Terminology for SAS Programmers

Image
Introduction The drug development process is a clinical process that has its own language. It is not required that SAS programmers function as a MD or a regulatory expert, but working knowledge of the terminology is important to be effective. This section will walk through the drug development process from discovery to Phase IV. It will explain a wide range of acronyms such as IND, NDA , GCP and MedDRA . It will also describe some of the terminologies used within the process of clinical trials as a drug is developed and submitted to the FDA . This will give SAS programmers a larger perspective and context to their work during the analysis and reporting of clinical trials data. This section will tell a fictitious story about a college graduate named James who is starting a new position at a pharmaceutical company. Each new term James encounters is presented in bold and italicized for emphasis. As he enters a new professional world, he meets many people and learns new processes that...
Read more

SAS iPhone App Architecture

Image
The delivery of SAS data and reports to an iPhone application is unique and requires a different architecture as compared to traditional client server systems. This is similar to web applications in how it is delivered to a browser but in this case, the application replaces the browser. The diagram below illustrates the components of the iPhone SAS application architecture including: the iPhone application , a web server and the BI Flash server. In this example, the iPhone application on the iPhone communicates through standard TCP / IP protocol to a web server. The web server then communicates to an application server which is actually a SAS session processing SAS programs and data. The output resulting from the SAS program is then delivered back to the iPhone in a similar way a web browser would access a web page the serer. The distinction however is that the iPhone application is not a web browser and the SAS session running on the server is more dynamic compare to ...
Read more