Skip to content
Install MCP

Technology

Medidata DCT

Last fetched

Medidata DCT is a technology in WhisperGraph's PredictLeads-derived TECHNOLOGY corpus, categorized under data quality management, with a published adopter count of 2 hostnames.

Profile

Category
data quality management
Broader grouping
data management, human resources
Published adopter count
2
Vendor
medidata.com

Medidata DCT is a technology solution designed to support decentralized clinical trials (DCT), facilitating patient participation and data collection remotely. This system integrates various tools, processes, and methodologies to enable flexible, hybrid clinical trials focused on improving patient engagement, data quality, and operational efficiency. The Medidata DCT program aims to streamline clinical trial management and enhance the overall research experience for all stakeholders involved.

Vendor site: https://www.medidata.com/en/life-science-resources/medidata-blog/decentralized-clinical-trials-case-study-collection

Sample adopters

2 hostnames WhisperGraph observed running Medidata DCT, a sample of the 2 published adopters.

Hosting concentration

The networks announcing the IP addresses of a sample of 2 Medidata DCT adopters, not of all 2 published adopters. A hostname counts once per network.

Related pages

Pivot from Medidata DCT into its category and the vendor behind it.

Queries

Resolves the slug's technology-name candidate(s) and projects the winner's fields.


MATCH (t:TECHNOLOGY)
WHERE t.name =~ $pattern
WITH t ORDER BY t.adopterCount DESC, t.name ASC
WITH collect(t)[0] AS winner, count(t) AS candidates
RETURN winner.name AS name,
       winner.description AS description,
       winner.category AS category,
       winner.parentCategories AS parentCategories,
       winner.adopterCount AS adopterCount,
       winner.url AS url,
       winner.vendorApex AS vendorApex,
       candidates
Run yourself →

Reads a 20-host adopter sample and the ASNs announcing its IP addresses.


MATCH (:TECHNOLOGY {name: $name})<-[:RUNS_TECHNOLOGY]-(h:HOSTNAME)
WITH h LIMIT 20
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
RETURN h.name AS host, a.name AS asn
LIMIT 200
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.