Our validation tools give you the perfect match

Our EDC system validation tools help you spot any inaccuracies or inconsistencies, and keep you right with CDISC

Do EDC system validation & easily validate SDTM, CRFs & datasets

Is your data CDISC compliant? ryze does systematic checks throughout the design and build process, so you 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. So you can compare this with the EDC datasets your CRO passes on.

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.

What can I do with ryze?

How you’re better off with ryze

Improve consistency

ryze makes it easy to see any differences between your original specs, and the datasets you get back. Our built-in rules and processes help you avoid any inaccuracies that could affect your FDA submission.

Effortlessly comply with standards

No need to worry about meeting regulatory standards. The ryze platform is built on CDISC compliant templates. So when you design CRFs and build your study in ryze, you automatically comply with the latest CDISC SDTM, CDISC ADaM, and NCI standards. And if you’re importing existing content into ryze, our CDISC validation tools flag up any issues and help you get them fixed!

Effortless EDC validation

EDC system validation is taken care of with ryze. The platform validates against the rules for your chosen EDC system – even if you’re using different EDCs for study phases. And because you can work on content in your EDC system straight from ryze, it makes validating CRF system specs against your eCRFs in your EDC much easier.

Save time & submit studies faster

Because validation is built in throughout ryze from the start, you save precious time both during and after clinical study build. Now you can submit studies faster, as validation has been done continuously, and not left until submission at the end. 

Organizations using our clinical trial software

moderna logo
UCB logo
vertex logo
University of Alabama logo
cdisc logo
University of Utah logo
argenx logo
idorsia logo
mercator medsystems logo
science37 logo
Catalyst clinical research logo

What people say about us

UAB testimonial of ryze clinical MDR
Testimonial of CDISC for CRF portal
UCB testimonial ryze clinical mdr

Is your data compliant with CDISC?

ryze makes sure of it, with built in rules to automatically validate against non-compliance.

Validate CRF specs against eCRFS in your EDC system

Types of validation
For clinical trials, there are many types of validation to be done. For example:

  • CRF validation – validate the CRF design against clinical expectations
  • EDC system validation – validate the EDC design against CRF specs and the specific rules for your EDC system.
  • Dataset validation – validate the EDC clinical datasets against dataset specs
  • CDISC SDTM validation – validate SDTM dataset designs against CDISC standards (SDTM-IG, NCI Controlled terms etc.)
  • Validation of SDTM programming
  • Validation of SDTM Clinical Data against CDISC (SDTM), NCI standards and FDA or PMDA rules.

Validation steps
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 
EDC system validation is painless with ryze. If you’re working directly on content in your EDC – as you can do in ryze – this makes validating CRF specifications against eCRFs in your EDC much easier. It’s literally a case of, ‘what you see is what you get’ in the EDC. And our EDC system validation also checks against the exact rules for your chosen EDC.

Dataset validation is also easier with ryze. 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.

Effortless SDTM datasets

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!

Maximize compliance - do it from the start

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 eCRF’s against specifications. They’re loaded automatically, so your eCRFs and specs 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. And EDC system validation is also done in unison.

Want EDC system validation?

The ryze platform validates your EDC study, CRFs and SDTM datasets.

A quicker SDTM dataset validation process

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.

Easily manage clinical study changes with ryze

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. EDC system validation is also taken care of in real time with ryze.

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.

FAQs

How does EDC validation work in ryze?

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.

How does the validation tool work?

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.

Can I validate eCRF specifications?

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.

Can I create a Reviewers Guide using ryze?

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.

What types of validation can I do?

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.

How does SDTM dataset validation work in ryze?

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.