Our ZUUM API lets you integrate with other systems to save time and make life easier.
The ZUUM API (Application Programming Interface) allows other external applications to integrate with the platform. Really, it lets them talk to each other. For example, you can integrate with ZUUM from a SAS-based environment.
It also works the other way. ZUUM can use APIs from 3rd party systems to integrate with them. For example, ZUUM can use the Medidata RAVE RWS API to download trial data from Rave. You can export data in various formats, such as CSV, dataset xml and xpt files. And export metadata in ODM and define.xml formats. You can also import data from external systems, such as EDCs or clinical metadata management systems, in CSV, dataset xml and xpt formats.
Our API lets your systems communicate with our clinical MDR. No need to log in to the ZUUM platform and manually upload your data. Instead, do it instantly from your existing system! Our API automates the upload, conversion, and download of datasets. So ZUUM does all the hard work in the background. Nice and easy!
The API means that your systems can access standardized definitions and descriptions of common data elements and fields in ZUUM. All your metadata content such as annotations, forms and datasets are stored in one central place. A single source of truth if you like. So it’s much quicker and easier to find the content you need.
ZUUM uses 3rd party APIs to integrate with other applications – such as EDC systems. And not just with Medidata Rave as mentioned before. You can also integrate with XClinical Marvin, Mi-Co Mi-Forms, OmniComm TrialMaster, OpenClinica, Oracle InForm, and Parexel DataLabs. That means you can automatically transfer clinical data from your chosen EDC system to ZUUM. Then it’s ready to convert to SDTM!
The ZUUM REST API lets your systems integrate with it. You can:
ZUUM can help save you time. Specifically with your SDTM conversion process. How do we know this? We worked with a company to help with a trial that was fast recruiting and required pretty much immediate access to their data. They used the Medidata Rave API to pull data at the time of user acceptance testing (UAT) entry. They did this using data management leads, and the asset group conversion mappings on studies in the development stage.
Doing it this way speeded up the development of the SDTM conversion. It allowed the metadata and UAT entered data to be loaded upfront. This meant that the SDTM mapping logic was nearly 100% complete when the database went live. 100% CDISC compliant SDTM datasets were produced within 10 business days of the go live date. These studies brought a huge return on investment for the company we helped. Lag time for SDTM data delivery was cut from 8-12 weeks to 2-4 weeks!
Formedix has been a valuable resource and their services have added value to our platform and data management capabilities. ...