KennelFlow Vet

esbuild bundles ( scripts/build-assets.mjs ) produce booking-wizard , admin-calendar , facility-settings into assets/dist/ .

Vite bundles rebuild assets/dist/ai-dictation.*** from **vite.ai-dictation.config.js and assets/dist/dicom-viewer.*** from **vite.dicom.config.js against the JSX sources listed in assets/src/README.txt . Run npm run build:vite to rebuild only the Vite targets, or npm run build / npm run build:all for the full pipeline (esbuild + both Vite configs).

DICOM / Cornerstone3D: npm run build compiles npm packages @cornerstonejs/core and @cornerstonejs/dicom-image-loader (upstream https://github.com/cornerstonejs/cornerstone3D) into assets/dist/dicom-viewer.js and assets/dist/kennelflow-vet-decode-worker.js via Vite — no assets/vendor/ copies and no remote CDNs load imaging libraries at runtime.

Shipped readable sources map to shipped bundles as follows (see assets/src/README.txt for the definitive table):

• assets/dist/booking-wizard.js / booking-wizard.css — TypeScript/React in assets/src/booking-wizard/ (entry main.tsx ), plus booking-wizard.css
• assets/dist/admin-calendar.js / admin-calendar.css — assets/src/admin-calendar/ ( main.tsx ), plus admin-calendar.css
• assets/dist/facility-settings.js / facility-settings.css — assets/src/facility-settings/ ( main.tsx ), plus facility-settings.css
• assets/dist/ai-dictation.js / ai-dictation.css — assets/src/ai-dictation.js + JSX modules (including AIDictation.jsx ) via Vite
• assets/dist/dicom-viewer.js / dicom-viewer.css — assets/src/dicom-viewer-entry.jsx , assets/src/DICOMViewer.jsx , assets/src/cornerstone3d-bootstrap.js , and assets/src/dicom-viewer.css , via Vite (bundles Cornerstone3D)
• assets/dist/kennelflow-vet-decode-worker.js — DICOM decode Web Worker emitted by the same Vite build (URL passed from PHP; ships beside dicom-viewer.js )

Fully regenerate bundles and the DICOM worker from the plugin root ( Node.js current LTS recommended):

1. 01npm ci
2. 02npm run build (alias: npm run build:all — esbuild, then AI dictation Vite, then DICOM Vite)

Incremental development:

• npm run watch — esbuild only (booking-wizard, admin-calendar, facility-settings)
• npm run watch:vite:ai — Vite watch for ai-dictation
• npm run watch:vite:dicom — Vite watch for dicom-viewer and kennelflow-vet-decode-worker.js

Dependency versions remain pinned via package.json / package-lock.json .

Third-party libraries included in the bundled JS/CSS

The bundled UI loads these runtime OSS libraries straight from the emitted JavaScript payloads (matching package.json majors):

• React and React DOM — https://react.dev/
• FullCalendar (core, React adapters, calendars) — https://fullcalendar.io/
• Cornerstone3D ( @cornerstonejs/core , @cornerstonejs/dicom-image-loader ) — https://github.com/cornerstonejs/cornerstone3D — https://www.cornerstonejs.org/
• dicom-parser (transitive dependency of the DICOM image loader) — https://github.com/cornerstonejs/dicomParser/

esbuild, Vite, TypeScript, and @vitejs/plugin-react are build-time-only developer dependencies.

Admin JavaScript (plain, non-compiled)

The following scripts under assets/js/ are plain, human-readable JavaScript — no build step required:

• assets/js/admin-ajax.js — AJAX helpers used across the admin EMR interface
• assets/js/admin-emr-confirm.js — Confirmation dialog for destructive EMR actions
• assets/js/admin-emr-pet-search.js — Pet search autocomplete for EMR admin pages

External Services

This plugin avoids silent network calls beyond what WordPress administrators explicitly configure.

WordPress AI Client (optional SOAP dictation)

Purpose: Clinicians may dictate optional SOAP scaffolding on pet encounter forms. Audio captured in-browser is processed through the WordPress AI Client ( wp_ai_client_prompt() ) built into WordPress 7.0+ — KennelFlow Vet does not call third-party AI HTTP APIs directly.

Administrator opt-in: Default-off until a connector is configured. Site administrators (typically under Settings → Connectors ) choose and authorize an AI provider once at the site level. KennelFlow Vet stores no provider API keys. The plugin screen KennelFlow Vet → AI dictation links to Connectors and shows availability status.

When transmissions occur: Only after WordPress reports AI support ( wp_supports_ai() ) and a permitted user (EMR edit capability) triggers dictation via the REST route. The configured connector/provider handles outbound requests; if AI is unavailable, the route returns an error and no dictation runs.

Data sent: (1) Audio — browser-captured dictation uploaded to your WordPress site, then passed to the AI Client with with_file() for transcription; (2) Transcripts and prompt snippets — plain text plus a fixed SOAP-structuring prompt sent through the same client. No patient identifiers are added by the plugin beyond what clinicians speak; follow clinic policy when dictating.

Third-party providers: Which external service receives data depends entirely on the connector the site owner configures in WordPress (for example OpenAI, Anthropic, or Google). Review that provider’s terms and privacy policy in Connectors documentation alongside your facility’s HIPAA/state privacy workflows.

DICOM imaging viewer

The bundled DICOM tooling uses self-hosted Cornerstone3D JavaScript compiled into assets/dist/dicom-viewer.js (with assets/dist/kennelflow-vet-decode-worker.js for decoding) and does not , by itself, relay patient imaging to third-party viewing platforms.

Laboratory webhook ingest (optional, inbound)

Purpose: Clinic staff may configure diagnostic/lab vendors to POST result JSON to a KennelFlow Vet REST webhook when a shared secret is stored for that provider.

When transmissions occur: Inbound only — external lab systems initiate HTTPS POST requests to your WordPress site at /wp-json/kennelflow-vet/v1/lab-integration/webhook/{provider} when an administrator or integration filter configures a webhook secret for the provider slug. No outbound calls are made to lab vendors by this feature.

Authentication: Requests must present the configured shared secret via X-KF-Vet-Lab-Secret , X-KF-Vet-Lab-Token , or Authorization: Bearer header. Requests without a matching secret are rejected (401). If no secret is configured, the endpoint does not accept data.

Data received: JSON lab result payloads (patient identifiers and result rows as supplied by the vendor/integration). Parsed rows are stored in your WordPress database as EMR lab results for the matched pet. Review vendor agreements and your facility privacy policy before enabling inbound feeds.

Privacy

The plugin stores clinical and booking data in your WordPress database and media library per your configuration. Review your site privacy policy and any other active plugins for how data is shared.

Developer Resources

The uncompiled source code, along with build tools and instructions for this plugin, is publicly available for review, study, and contribution on GitHub: https://github.com/brelandr/kennelflow-vet . Clone the repo, install dependencies with npm ci , then run npm run build so esbuild and Vite (including the Cornerstone3D DICOM bundle) all execute (matching the WordPress.org upload layout).