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

Overview

DocID® Documentation

Implement secure healthcare professional access on your website with DocID®.

DocID® gives healthcare and pharmaceutical websites a shared login and verification layer for healthcare professionals (HCPs). Your website remains responsible for its content and user experience; DocID® handles authentication and returns the verified profile data your integration is permitted to use.

This documentation is for website owners, digital teams, agencies, and developers implementing DocID®.

Choose your path

Drupal

Use the DocID® module to authenticate visitors, map verified profile data to Drupal roles, and protect nodes and private media.

Set up the Drupal module

Get the DocID® module from Drupal.org

WordPress

Use the DocID® plugin to protect pages, posts, and media without building an OAuth client from scratch.

Set up the WordPress plugin

Get the DocID® plugin from WordPress.org

Custom website or application

Integrate DocID® through the OAuth 2.0 authorization code flow with PKCE.

Integrate a custom website

Recommended reading order

  1. Read How DocID® works.
  2. Complete the relevant Getting Started path.
  3. Review the features and licenses available for your website.
  4. For a custom integration, implement the OAuth 2.0 flow.
  5. Use the interactive API reference when working with the DocID® business API.

Responsibilities at a glance

DocID®Your website
Authenticates the userStarts the login flow
Applies the configured HCP verification processProtects the requested content
Requests and records the required consentValidates the callback and creates its own session
Returns the approved identity claimsUses claims only for the configured purpose
Operates the DocID® account and identity layerKeeps client credentials and tokens secure

Need help with an implementation? Contact support@docid.pro.

NextIntroduction

On this page

  1. Choose your path
  2. Drupal
  3. WordPress
  4. Custom website or application
  5. Recommended reading order
  6. Responsibilities at a glance