DocID®DocID® Documentation
Back to DocID®
  • Overview

    • DocID® Documentation
  • Introduction

    • Introduction
    • How DocID® works
    • Core concepts
  • Getting Started

    • Getting Started
    • Drupal module
    • WordPress plugin
    • Custom website
    • Go-live checklist
  • Features

    • Features
    • Standard Login
    • Access and personalization
    • Analytics
    • Campaigns
  • Licenses

    • Licenses
  • OAuth 2.0

    • OAuth 2.0
    • Configure a client
    • Authorization code flow
    • Scopes and UserInfo
    • Security and environments
  • API

    • API
  • Help

    • Troubleshooting

Introduction

Introduction

Understand what DocID® provides and where it fits into your website.

DocID® is an authentication and marketing platform built for healthcare and pharmaceutical websites. It gives healthcare professionals (HCPs) seamless access to protected medical content on the web and mobile while giving website owners an established alternative to building and operating their own HCP login infrastructure.

Content subject to the German Drug Advertising Act (HWG) or similar European regulations may only be made available to eligible professional audiences. DocID® helps your website authenticate doctors, pharmacists, medical assistants, nurses, and other healthcare professionals and apply the access rules configured for your implementation.

Your visitors use one DocID® account across participating websites. They authenticate on DocID®, complete the required verification and consent steps, and return to your website with the approved identity information needed to establish a local session.

Why teams use DocID®

  • Faster implementation: integrate an established login using the Drupal module, WordPress plugin, or OAuth 2.0 instead of developing a complete authentication and verification system.
  • A smoother HCP journey: reduce lengthy registration and verification flows and give eligible users faster access to protected content.
  • Returning-user convenience: the DocID® mobile experience can reduce repeated credential prompts while the HCP remains securely authenticated.
  • Audience-specific experiences: guide visitors according to attributes such as profession, country, or language when those claims are available to your integration.
  • Controlled user identification: use approved profile claims to recognize authenticated visitors and map them to your own application records.
  • A foundation for measurable marketing: add Analytics or Campaign capabilities when your teams need audience insight, customer-journey analysis, attribution, consent collection, campaign links, or event-promotion tools.

What DocID® provides

  • A hosted login, verification, consent, and account experience for HCPs
  • OAuth 2.0 authorization code integration with PKCE
  • Configurable access rules and profile-based experiences for protected content
  • A free Standard Login plus optional paid Analytics and Campaign modules
  • A Drupal module and WordPress plugin for common content-protection use cases
  • A business API for managing supported DocID® resources

Standard Login and optional modules

The Standard Login covers the authentication foundation. It can protect a website or application, support selected employee or customer access models, and provide the approved claims needed for personalization.

The Analytics module adds reports and dashboards for authenticated audiences, traffic sources, customer journeys, and connected campaign activity. It is a Paid module.

The Campaign module adds campaign attribution, smart campaign links and deep links, consent collection, and tools for promoting events and webinars. It is a Paid module.

Compare licenses and modules

What DocID® does not replace

DocID® does not host your website content or replace your application session. After a successful callback, your website validates the response, exchanges the code on its server, and creates its own secure session.

It also does not decide which content your organization is legally permitted to publish. Your organization remains responsible for legal review, content classification, access policy, privacy notices, and the way DocID® data is used.

Who should read what

RoleStart here
Website owner or product managerFeatures and Licenses
Drupal or WordPress administratorDrupal or WordPress setup
DeveloperCustom website setup and OAuth 2.0
Security or privacy reviewerSecurity and environments
PreviousDocID® DocumentationNextHow DocID® works

On this page

  1. Why teams use DocID®
  2. What DocID® provides
  3. Standard Login and optional modules
  4. What DocID® does not replace
  5. Who should read what