DOCID®
DocID® compatibility with REEID Translate
DocID® compatibility with REEID Translate is being evaluated from available plugin evidence. 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 visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for DocID®.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
DocID® is documented in the Security category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How DocID® compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
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.
CONTENT BOUNDARY
DocID® capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
DocID® and REEID Translate FAQ.
What does DocID® do according to the available plugin evidence?
DocID® has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for DocID®?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for DocID®?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate DocID® in a multilingual WordPress workflow.
REEID documents DocID® functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.