ryze BY SECTOR
- BOOK A DEMO
- FREE TRIAL
Our validation tools help you spot any inaccuracies or inconsistencies, and keep you right with CDISC.
Is your data in good shape? Is it CDISC compliant? ryze carries out systematic checks throughout the design and build process, so you now don’t need to worry about CDISC compliance!
One thing we do is compare what you’re supposed to have against the files you’ve got. This could mean comparing studies against specifications, or against your organizational standards. That way you get to see any differences before approving your study designs.
If you’re working with a CRO, you can check what you get back from them too. ryze eCRF software shows how your form designs will look in your EDC system. Like a preview. So you can compare this with the EDC datasets your CRO passes on, to see if they match up.
What about complying with CDISC standards? ryze is built on CDISC templates, so you’re forced to align with relevant industry standards – including current and previous versions of CDISC SDTM, CDISC ADaM, and CDISC SEND. Even if a CRO does the work for you, use our CDISC validation tools to double check that your datasets comply with standards.
We are using the Formedix platform to design CDASH-compliant, example CRFs for the CDISC eCRF Portal. We can create, visualize, edit and approve eCRFs in the platform, then export them in ODM-XML to use in the CDISC Library and standards packages. Formedix is one of CDISC’s longest standing members. CDISC is keen to work with technology partners that help pharmaceutical organizations to adopt and keep pace with emerging CDISC standards.
Formedix has been a valuable resource and their services have added value to our platform and data management capabilities.
Types of validation
For clinical trials, there are many types of validation to be done. For example:
There are many different steps to consider. Some of these can be included in the design process to build in conformance from the start. When it comes to validating CRFs with clinical oversight, it’s important to be able to quickly review and adjust things. Such as form layout, question wording and controlled terms. A web based system makes this easier, since teams often work in different locations.
Easier validation – work directly in your EDC
If you’re working directly on content in your EDC system – as you can do in ryze – this makes validating CRF system specifications against eCRFs in your EDC system much easier. It’s literally a case of, ‘what you see is what you get’ in the EDC. This is also true for datasets. By producing a specification for each stage of the EDC to SDTM conversion process, you can review and test the design with test data – before the EDC system is live. Once your clinical data is available, by complying with the expected dataset specifications, you know the conversion process will also work as expected.
Easier compliance with CDISC standards
For submission deliverables – such as SDTM datasets – the metadata and data within the datasets (and Define-XML) must conform to the CDISC SDTM-IG standards. In basic terms, this standard dictates the column names, labels and column order of the datasets. Compliance against this standard can be measured if the SDTM specification itself is compliant. ryze cross checks the clinical datasets against the specification for you.
ryze makes SDTM dataset creation far easier, with CDISC SDTM metadata templates. That way you build your datasets in line with CDISC SDTM rules, right from the off. And our CDISC validation tools prompt you about any non-compliance as you go!
The pitfalls of programming validation
Programming validation requires a different approach. The most common cause of problems are human errors. After creating an SDTM compliant specification, this is then divided into separate programming tasks. If each task is then programmed by two different teams, a comparison of the outputs will eliminate most human errors. But you must still compare the output with the specification to ensure compliance.
Rule based templates make SDTM datasets easier
Each SDTM dataset starts as an eCRF specification in the ryze platform. Our dataset design tools contain the CDISC SDTM metadata as templates. So ryze builds your datasets using the CDISC SDTM rules. The templated metadata is then extended using the selected CDISC NCI Controlled terms, and any supplemental qualifiers, value level metadata etc. is added.
Built in SDTM compliance
The FDA and PMDA publish compliance rules for clinical data submissions, including SDTM. The output must ultimately be compared against the rules. And any deviations must be eliminated or fully documented. By building in e.g. SDTM compliance at the start, you maximise compliance throughout the process. Key factors such as correct use of controlled terms must be built into the EDC CRF’s and SDTM conversion process. This includes EDC edit check programming and data management checks programmed to highlight data issues early.
Quicker eCRF design
With ryze metadata management tools, you can quickly build and publish case report forms (eCRFs) for clinical review. As the visual elements (questions, radio buttons, controlled terms) are captured along with the EDC database build specification (variable names, question settings, edit checks etc), an auto-generated specification is used for both the eCRF review and the EDC deployment. So you don’t need to check EDC CRF’s against the eCRF specifications. They’re loaded automatically, so your eCRFs and eCRF specifications are in sync. This also means that any changes can be reflected in the review/build eCRF immediately. There’s no delay. You don’t need to create word specifications, for example, or manually make screenshots in the EDC.
Each SDTM dataset starts as a specification in the ryze platform. Our dataset design tools contain the CDISC SDTM metadata as templates. So ryze builds your datasets using CDISC SDTM rules. The templated metadata is then extended using the selected CDISC NCI controlled terms, and any supplemental qualifiers, value level metadata etc. is added. And our CDISC validator makes checks as you work.
This specification document forms both the guidance for programming teams and also the Define-XML metadata for the dataset deliverable. The dataset specification is saved in ryze, alongside the EDC build documents. This gives a central place for all your study metadata. Once the basic SDTM dataset structure is agreed, additional programmer instructions are added to each variable, domain, etc. within the electronic specification. Any updates or clarifications are immediately captured in ryze, and the software generated programmer specifications (e.g. excel sheets) are automatically updated. And the same metadata is used for the submission Define-XML, which is automatically generated.
The SDTM Define-XML is independent of the clinical datasets (and data programmer). Therefore it can be used as a benchmark to check the dataset content against, to ensure compliance with the CDISC SDTM standard.
Remember, if the Define-XML metadata is extracted from the clinical datasets, this is not suitable for use as a validation specification. Any errors in the datasets will just be recreated in the Define-XML, removing the ability to provide an independent quality check.
How we help you manage study changes
If SDTM conversion is done before first patient enrolment, as a study progresses, inevitably there will be changes. And these changes will need to be made in the EDC system. This can be difficult. The programming team can’t easily track changes within the EDC system. Or easily quantify the impact of a change.
ryze stores the EDC design. So when an update is made, the SDTM programming team can clearly see any changes in ryze – without even going into the EDC system. You can then compare the EDC clinical dataset specification against the updated versions to see the impact on SDTM programming. That means you can make adjustments during the eCRF update process – rather than after EDC deployment when data collection is already underway.
Detect and fix errors early on
As clinical data is entered, there will naturally be errors or incomplete information in the EDC. If SDTM programming is complete, periodic EDC data extracts can be converted into interim SDTM datasets, and SDTM validation can be done using the standard tools for FDA submission. These results can then be fed back to study data managers to correct errors early on. This typically reduces the burden of ‘data cleansing’ query resolution prior to database lock.
From this process, a ‘Reviewers Guide’ document can be created. This documents any deviations from the SDTM/FDA rules in detail as the data is collected. This ensures that all details are recorded for each issue. Check out the PhUSE reviewers guide template and examples.
Our platform validates against the rules for your relevant EDC system – even if you’re using different EDCs for study phases. You can work on content in your EDC system straight from Formedix. This makes validating eCRF specifications against your eCRFs in your EDC much easier. You can do validation checks as you go, or do them all at the end.
ryze lets you build, preview and validate studies for 7 leading EDC systems, including Rave and InForm. Our platform is built on CDISC compliant templates. So when you design eCRFs and build your study in ryze, you automatically comply with the latest CDISC and NCI standards. You can do validation checks as you go, or do them all at the end. Our validation tool tells you where exactly to go to fix your errors. That makes it quick and easy to get your studies compliant.
Yes. You can auto-generate specifications for both the eCRF review and the EDC deployment. You don’t need to check EDC CRF’s against the eCRF specifications. They’re loaded automatically, so your EDC CRFs and eCRF specifications are in sync. Any changes made are reflected in the review/build eCRF straight way. And as an example, you don’t need to create word specifications, or manually make screenshots in the EDC.
Information in the EDC is likely to contain errors or be incomplete as clinical data is entered. EDC data extracts can be converted into interim SDTM datasets if SDTM programming is complete. And SDTM validation can be done. Results can then be fed back to data managers to correct errors early on. From this process, a ‘Reviewers Guide’ document can be created. It shows any deviations from the SDTM/FDA rules as data is collected, as well as ensuring all details are recorded.
You can validate your CRF design against clinical expectations, EDC designs against CRF specifications, EDC clinical datasets against dataset specifications, SDTM dataset designs against CDISC standards (SDTM-IG, NCI Controlled terms etc.), SDTM programming, and SDTM Clinical Data against CDISC (SDTM), NCI standards and FDA or PMDA rules.
ryze uses CDISC SDTM metadata templates that make it much easier to create your SDTM datasets. That means your datasets are built on CDISC SDTM rules right from the start. Our CDISC validation tool highlights any non-compliance as you go.