Glossary

Functional Service Provider (FSP)

Definition

A functional service provider (FSP) is a company that runs specific functions of clinical research, such as data management, biostatistics, clinical monitoring or pharmacovigilance, for a drug or device sponsor. Unlike a full-service CRO that runs entire studies, an FSP supplies dedicated teams for one function across a sponsor's portfolio of trials.

FSPs take on specific functions of clinical research, such as data management or biostatistics, so a sponsor gets specialist teams without handing over the whole study.

What is a functional service provider model?

In the FSP model, a biotech, pharmaceutical or device company outsources particular functions it needs for its trials, such as data management, biostatistics, clinical monitoring, regulatory affairs or pharmacovigilance, rather than an entire trial. The sponsor keeps more control over how the work is done and can scale each function up or down.

How does the FSP model benefit clinical research?

  • Cost: sponsors pay only for the functions they need
  • Flexibility: different providers can handle different functions
  • Control: sponsors keep their own processes and oversight while adding capacity

How does an FSP differ from a traditional CRO?

A full-service contract research organization (CRO) runs entire clinical trials, from setup to final report. An FSP provides staff and expertise for specific functions inside the sponsor's own process. Many large CROs offer both models.

What the FSP model means for teams selling into healthcare

FSP deals are usually decided by the sponsor's clinical operations, data management or biostatistics leaders together with procurement and outsourcing teams. Vendors of trial software and services should map both the sponsor's functional leaders and the FSP partners they already use, because the FSP team often runs the tools day to day.

FSP

See where FSP shows up on the accounts you sell to

Search 7.4M+ HCPs and 11M+ executives at 997K+ sites of care, each placed under its health system and IDN.

  • 30 days free
  • Self-serve
  • No credit card

Cookie settings

Turn each category on or off. Your choice is kept for 12 months and you can change it here at any time.

Necessary

Always on. Sign-in, security, downloads you asked for, your cookie choice, and the page that led to a signup.

View cookies (6)
  • dm_consentDmand AI. Your cookie choices and whether your browser sent a Global Privacy Control signal. 12 months.
  • dm_ft, dm_ltDmand AI. The first and the latest page you arrived on, with the date, so a signup is credited to the page that worked. 90 days, 30 days.
  • dm_fs, dm_lsDmand AI. The first and the latest source of a visit (a search engine, a campaign or the site that linked here). 90 days, 30 days.
  • dm_dl, dm_dl_okDmand AI. After you give an email address for a download, lets you download files without being asked again. 30 days.
  • Session and CSRF cookiesDmand AI (app.dmand.ai). Sign-in and form protection in the application. Session.
  • __cf_bm, cf_clearanceCloudflare. Tells people from automated traffic and keeps the site available. 30 minutes; cf_clearance while a security check is valid.

Analytics

On unless you turn it off. How pages are used, in aggregate, and recordings of how pages are used.

View cookies (6)
  • Google Tag ManagerGoogle. Loads the analytics and marketing tags that are on. Sets no cookie of its own and does not load when both categories are off. n/a.
  • _ga, _ga_<container-id>Google Analytics 4. Visits and page views in aggregate on dmand.ai. 2 years.
  • _clck, _clskMicrosoft Clarity. Recordings and heatmaps of how pages are used, with form fields masked. 1 year, 1 day.
  • CLID, MUID, ANONCHK, MR, SMMicrosoft (clarity.ms). Set by Microsoft when Clarity loads, to recognize a browser across sites that use Clarity. Up to 1 year.
  • None (cookieless)Ahrefs Analytics. Page views in aggregate. n/a.
  • ph_<project>_posthogPostHog. Product usage, errors and performance in app.dmand.ai, used to fix bugs and improve features. 365 days.

Marketing

On unless you turn it off, and always off when your browser sends a Global Privacy Control signal. A visitor identification service tells our sales team which companies and people visit.

View cookies (6)
  • _reb2buid, _reb2butkRB2B. Recognizes a returning browser for visitor identification. 360 days, 1 year.
  • _reb2bgeoRB2B. The location used to decide whether a visit can be identified. 20 days.
  • _reb2brefRB2B. The page or site that referred the visit. 15 days.
  • _reb2bfxf, _reb2btd, _reb2bliRB2B. Links the visit to an identified business profile. 1 month.
  • _reb2bresolveRB2B. Holds a match while it is being resolved. 2 days.
  • _reb2sessionID, _reb2bloadedRB2B. The current visit, and a guard against loading the script twice. 30 minutes, 1 second.

Functional

On unless you turn it off. Remembers choices such as a collapsed section.

View cookies (none today)