DOCID®
DocID® translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what DocID® does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
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.
Distinctive features
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.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what DocID® does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
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.
Does the current evidence establish translation scope for DocID®?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.