DOCID®
DocID® compatibility with REEID Translate
DocID® compatibility with REEID Translate is being reviewed using official plugin documentation. OAuth-based authentication integration with DocID® (requires Client ID/Client Secret and callback URL) to authenticate healthcare professionals and gate access to protected content. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What DocID® does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
DocID® is documented in the Security category with 8 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How DocID® compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- OAuth-based authentication integration with DocID® (requires Client ID/Client Secret and callback URL) to authenticate healthcare professionals and gate access to protected content.
- Technical access restriction controls for WordPress content (posts, pages, custom post types, and media) using DocID® login/session state and authentication-aware navigation/shortcodes.
- Scope-based data minimization for identity/profile attributes: the plugin always requests a stable DocID® identifier and professional access data, while profile/email/phone data are requested only when optional scopes are enabled and only after user authorization.
- Optional native WordPress account provisioning linked to the DocID® account identifier (not by email), with provisioned users unable to use local WordPress passwords/password reset/application passwords; role mapping can assign non-administrative roles based on verified profession/discipline/institution/subject values.
- Role mapping and login destination logic: role mappings can target every DocID® user or match exact attribute values; login destinations can route users to local URLs based on profession/discipline with deterministic precedence rules.
- Developer-facing session inspection API to determine whether a user is logged in and to retrieve normalized identity fields (e.g., stable account ID and, when authorized, profession/discipline and verification flags) without necessarily creating a WordPress user.
- Content visibility shortcodes for authenticated vs.
- logged-out visitors (e.g., [docid-loggedin-content] and [docid-loggedout-content]) and account-navigation/username/profile shortcodes that depend on required scopes and authorization.
TRANSLATION BOUNDARY
DocID® capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
DocID® and REEID Translate FAQ.
What does DocID® do?
DocID® has 8 documented features listed in its official documentation. See the Plugin Information section for details.
Does DocID® have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from DocID®?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate DocID® in a multilingual WordPress workflow.
REEID documents DocID® functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.