There are many common questions people have when creating Define-XML metadata for their datasets. One of these revolves around how to handle data that can come from multiple sources, such as a CRF or eDT. In the simple case you just create a Value List, and specify the Origin on each Value instead of on the Variable.
This latest post in our "Introduction to CDISC" series is all about Define-XML. It's known by many due to it being required in regulatory submissions, but why does it exist and what benefits can it bring you?
In the past sponsors submitting to FDA were required to submit a PDF describing their submission datasets. As we all know PDF is great for viewing on screen or printing, but the information inside it can't be interpreted by a computer in any meaningful way. Enter CDISC's Define-XML model...
Let’s start at the start - what is CDISC? The Clinical Data Interchange Standards Consortium is an organization dedicated to helping improve medical research by driving interoperability through data standardization.
Formedix have been strong advocates for the use of CDISC data standards in clinical and non-clinical research for half my life now, ever since we realised how it could transform our business by enabling the rapid design and build of clinical trials. We quickly focused our company around use of CDISC standards, and are now industry leaders in CDISC software, professional services and training.
Over the next few weeks we’ll be publishing a series of blog posts giving an overview of the various CDISC models. Our aim is to help you understand how you can make the most of these industry standards. If we all work together using the same standards we can optimize our clinical trials by increasing data quality and reducing design and execution time. Ultimately that means getting more products to the market with less cost.
With FDA now regulating for all new studies to use CDISC standards when submitting data, it's vital that our processes are up to date with the latest standards and fit for purpose.
An FDA presentation at the recent PhUSE Computational Science Symposium tried to shed some light on how we're doing as an industry. It analysed all eCTD submissions from January-February 2017 that used standardized data.
You might be surprised how the submissions fared...
The festive period is in full swing, and in the Formedix office, we’re no exception. While we sample festive chocolates, raise a glass over Christmas lunch, or add the star to the top of the office tree, we look back over the year and give a nod to all the great things we’re excited to offer, here at Formedix.
REGULATORY DEADLINE UPDATE: The FDA Data Standards Catalog has recently been updated to state that Define-XML v1.0 cannot be used in studies starting after March 15, 2018 . The Catalog previously stated March 2017, however the update now aligns with the date communicated on the Federal Register Notice.
During the SDTM dataset extraction process, some SAS programmers create the SDTM or ADaM Define-XML directly from the dataset metadata used in the SAS file. This has the perceived advantage of automating the Define-XML creation, but it has a fundamental weakness.
“You’d be surprised how many people in the industry don’t realize that the Study Data Tabulation Model (SDTM) and Define-XML are two separate standards,” said my colleague Ed in a meeting last week.
When submitting clinical data to a regulator in electronic format, you’ll need to include metadata - data about the data - in the form of a Define-XML. This CDISC-format file helps the reviewer who’ll eventually approve or reject your application by describing the format and content of the data submitted.
Ahead of this year's DIA 2015 Annual Meeting, Formedix commissioned a series of three interviews with some of our CDISC standards experts. In the second, our man in Japan Masahiro Hayashi talks about the country's looming CDISC deadline, and what it means for its pharmaceutical companies.