About:Pharmacopedia.ext: Difference between revisions

= Pharmacopedia extension specification =

'''Requires:''' MediaWiki ≥ 1.46.0 · PHP ≥ 8.5

'''Author:''' MDElliottMD · '''License:''' GPL-2.0-or-later

The Pharmacopedia extension turns a MediaWiki install into a structured, community-edited medicine reference with rich user-profile and assessment infrastructure. It adds parser tags, special pages, API modules, a chip-picker / autosave UI framework, and a database schema that together support:

* Structured medicine pages via the <code><nowiki>{{MedTemplate}}</nowiki></code> template

* Per-user rating on effects, problems, titration strategies, anecdotes, and drug-drug interactions (continuous 0–100 sliders, ±100 valence; no 0–5 likert anywhere)

* User profile with dimensional personality / autism assessments (CATI, CAT-Q, MBTI, Enneagram, PID-5-BF, OCEAN/BFI-10) and rich auto-generated reports

* Chip-picker / autosave / slider-precise-input UI framework shared across editor surfaces

* Verified-provider role with document-based verification

 

 

 

* '''Backend (PHP):''' <code>includes/</code>, one class per parser tag, store, special page, or API module. Auto-loaded under <code>MediaWiki\Extension\Pharmacopedia\</code>. Assessment classes under <code>includes/Assessments/</code>.

* '''Frontend (JS):''' <code>resources/ext.pharmacopedia.js</code>, single IIFE binding click handlers, modals, chip-pickers, autocomplete, autosave debouncer, slider-precise click-to-type. <code>resources/ext.pharmacopedia.blocksave.js</code> is the autosave infrastructure (debounced AJAX per block, race-safe).

* '''Styles (CSS):''' <code>resources/ext.pharmacopedia.css</code>, shared row layout, per-tag chrome, dark-theme palette (black / dark-grey / purple / white primary; red / green / blue / teal sparingly for semantic distinction).

* '''Datepicker:''' <code>resources/ext.pharmacopedia.datepicker.js</code> + <code>.css</code>, supports single dates, ranges, and possibility-mixed dates (e.g. "1995 or 1996").

* '''Schema:''' <code>sql/</code>, ~20 core tables plus migration patches. Picked up via <code>LoadExtensionSchemaUpdates</code> hook.

Registered via <code>Hooks::onParserFirstCallInit</code>:

| <code>&lt;effect&gt;</code> || Therapeutic or adverse effect; patient + provider perspectives; provider freq slider 0–100; shared valence slider ±100 || <code>EffectTag</code>

| <code>&lt;problem&gt;</code> || A problem (formerly "indication") the medicine addresses; 0–100 efficacy likert slider + "don't know" toggle || <code>ProblemTag</code>

All non-self-closing tags take a <code>slug</code> argument and (where relevant) a <code>title</code>, <code>label</code>, <code>author</code>, <code>ref</code>, or <code>perspective</code>.

<problem slug="depression" title="Major depressive disorder"

   author="MDElliottMD">First-line for moderate to severe MDD.</problem>

| Anecdote || +1 / −1 binary || single (perspective is metadata) || <code>pcp_votes</code>

| Problem (efficacy likert) || 0–100 continuous slider, optional "Don't know" (-1) || single || <code>pcp_likert_reports</code>

| Effect (patient) || experienced ∈ {yes, no, unsure} + valence ±100 slider || patient || <code>pcp_effect_reports</code> (perspective=1)

| Effect (provider) || frequency 0–100 continuous slider + "Don't know" (-1) + valence ±100 slider || provider || <code>pcp_effect_reports</code> (perspective=2)

| Interaction || experience 1–5 + valence ±100 slider + optional note || user + provider, separate aggregates || <code>pcp_interaction_reports</code>

Server-side aggregates: <code>n</code>, mean of the rating field, and (for interactions) <code>severe = (vmean ≤ −83.0)</code> (rescaled from the original ±3-scale −2.5).

| '''Rare''' || ≤ 5, provider vmean > −83 || collapsed

| '''Rare but Severe''' || ≤ 5 and vmean ≤ −83 || '''expanded by default''', red highlight

The vmean ≤ −83 threshold is also the trip-wire for the "severe" red treatment on interaction rows.

== User profile ==

 

 

 

 

 

 

 

 

 

 

 

 

=== Personality / autism assessments ===

Six assessments, all with continuous-slider items, "Not sure" toggle per item, auto-computed subscale + total scores, and a rich auto-generated report at <code>Special:MyAssessment/{key}</code>:

{| class="wikitable"

All assessment items submit raw responses to <code>pcp_user_profile_fields</code> under namespace <code>{key}_raw</code> (e.g. <code>cati_raw</code>); the computed scores live under namespace <code>{key}</code> with keys like <code>subscale_SOC</code>, <code>total</code>, plus a <code>taken_at</code> timestamp. Re-scoring happens automatically on every save (autosave fires `scoreResponses()` on the full raw set, skipping "unsure" rows).

Every block on <code>Special:MyProfile</code> is wrapped in <code>&lt;div data-pcp-save-block="block-name"&gt;</code>. The blocksave.js library:

# Listens for <code>input</code> and <code>change</code> events on every input inside any save-block

# Race-safe: if user keeps typing during an in-flight save, the in-flight save records what it sent; newer changes mark the block dirty again and schedule another save when the response returns

# Diagnosis + medicines "Add a row" slots are exempted from autosave (would create duplicates); they require an explicit + Add button

Slider numbers are also clickable: a single delegated handler on every <code>&lt;output&gt;</code> next to a range slider swaps it for a number input on click, accepts a precise typed value (clamps to the slider's <code>min</code>/<code>max</code>), commits with Enter, cancels with Escape.

Scroll position is preserved across the rare reloads (delete operations on diagnoses / medicines / experience reports, and the auto-reload after a new diagnosis or medicine is added) via <code>sessionStorage</code>.

 

|-

| <code>Special:UserProfile/&lt;name&gt;</code> || Public profile view (filtered by per-field visibility)

| <code>Special:MyAssessment/cati</code>, <code>/catq</code>, <code>/pid5bf</code>, <code>/mbti</code>, <code>/enneagram</code>, <code>/ocean</code> || Rich report per assessment

| <code>Special:SaveProfileBlock</code> || AJAX endpoint for autosave (POST-only, JSON response)

| <code>Special:Problems</code> || Browse the problems repository (165+ entries, 18 categories)

 

 

| <code>pharmacopedialikert</code> || Submit problem-efficacy likert (0–100 + −1 DK)

| <code>pharmacopediaeffect</code> || Submit effect report (patient or provider perspective)

| <code>pharmacopediacomment</code> || Threaded discussion ops (add / edit / delete / reply)

| <code>pharmacopediaexperiencesubmit</code> || Submit experience report (multi-field form)

| <code>pharmacopediaeffectslookup</code>, <code>indicationslookup</code> || Pickers used by the experience-submit form

| <code>pharmacopedialiteratureadd</code>, <code>literaturedelete</code> || Literature attachment ops

 

 

The Interactions section is rendered by placing <code>&lt;pharmaInteractions/&gt;</code> anywhere in the wikitext of a med article ('''NS_MAIN''') or a Category page ('''NS_CATEGORY''').

 

 

* Severe (any of pooled / user / provider vmean ≤ −83.0): red 4 px left border + red-tinted background + "severe" pill + counterparty title in red.

Triggered by the <code>+ Add interaction</code> button at the bottom of the section. Two-stage UX: search → click Use → confirm with Add interaction → POST to <code>pharmacopediainteractionadd</code>. Categories appear in the modal only if tagged with the marker category (default <code>Category:MedCategory</code>, configurable via <code>$wgPharmacopediaInteractionCategoryMarker</code>).

 

 

 

 

 

 

 

 

 

 

* <code>$wgPharmacopediaInteractionCategoryMarker</code> (default <code>Category:MedCategory</code>): only categories tagged with this marker appear in the add-interaction modal

* (Various permission-grant arrays via standard MW <code>$wgGroupPermissions</code>)