{"id":311211,"date":"2026-06-23T15:07:20","date_gmt":"2026-06-23T15:07:20","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/kennelflow-vet\/"},"modified":"2026-06-23T15:06:43","modified_gmt":"2026-06-23T15:06:43","slug":"kennelflow-vet","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/kennelflow-vet\/","author":12029770,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.1.0","stable_tag":"0.1.0","tested":"7.0","requires":"6.2","requires_php":"7.4","requires_plugins":null,"header_name":"KennelFlow Vet","header_author":"LandTech Web Designs","header_description":"Clinical foundation: patients, rooms, locations, and bookings with availability checks and REST API.","assets_banners_color":"","last_updated":"2026-06-23 15:06:43","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/wordpress.org\/plugins\/kennelflow-vet\/","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":33,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"0.1.0":{"tag":"0.1.0","author":"brelandr","date":"2026-06-23 15:06:43"}},"upgrade_notice":[],"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[7101,43578,2690,268559],"plugin_category":[40],"plugin_contributors":[251791],"plugin_business_model":[],"class_list":["post-311211","plugin","type-plugin","status-publish","hentry","plugin_tags-bookings","plugin_tags-clinic","plugin_tags-pets","plugin_tags-veterinary","plugin_category-calendar-and-events","plugin_contributors-brelandr","plugin_committers-brelandr"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/kennelflow-vet.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n

KennelFlow Vet provides clinical scheduling and record-keeping building blocks that integrate with KennelFlow shared pets and locations. Install KennelFlow Core<\/strong> first, then activate this add-on.<\/p>\n\n

Primary development and listings use the WordPress.org profile @brelandr<\/a>.<\/strong> Optional commercial services are available via LandTech Web Designs<\/strong>.<\/p>\n\n

Human-readable JavaScript\/CSS source (Guideline 4):<\/strong> Every release includes the unminified sources under assets\/src\/<\/strong> (see assets\/src\/README.txt<\/strong> for the dist-to-source map). Built files under assets\/dist\/<\/strong> are generated via npm run build<\/strong> (esbuild + Vite). The DICOM viewer bundles Cornerstone3D<\/strong> into assets\/dist\/dicom-viewer.js<\/strong>. Public source: https:\/\/github.com\/brelandr\/kennelflow-vet \u2014 see Developer notes for rebuild steps.<\/p>\n\n

Developer notes<\/h3>\n\n

Frontend bundles (readable source and rebuild)<\/h4>\n\n

Public source repository:<\/strong> https:\/\/github.com\/brelandr\/kennelflow-vet \u2014 clone with git clone https:\/\/github.com\/brelandr\/kennelflow-vet.git<\/code>, then run npm ci<\/strong> and npm run build<\/strong> to regenerate all bundles from the readable sources in assets\/src\/<\/strong>.<\/p>\n\n

WordPress.org release package:<\/strong> each trunk<\/strong> or tag<\/strong> revision shipped to WordPress.org should include assets\/src\/<\/strong>, vite.*.config.js<\/strong>, scripts\/build-assets.mjs<\/strong>, package.json<\/strong>, package-lock.json<\/strong>, tsconfig.json<\/strong>, and assets\/dist\/<\/strong> (including the Cornerstone3D-powered dicom-viewer.js<\/strong> bundle and kennelflow-vet-decode-worker.js<\/strong>).<\/p>\n\n

Maintainer zip builds:<\/strong> From a git checkout you can run scripts\/build-wordpress-org-zip.sh<\/strong> locally (repo-only tooling); it stages release\/*.zip<\/strong> and verifies assets\/dist\/<\/code><\/strong> artefacts and core source entries. Install Plugin Check<\/strong> from https:\/\/wordpress.org\/plugins\/plugin-check\/ and validate the staged directory before uploading to WordPress.org.<\/p>\n\n

esbuild bundles<\/strong> (scripts\/build-assets.mjs<\/strong>) produce booking-wizard<\/strong>, admin-calendar<\/strong>, facility-settings<\/strong> into assets\/dist\/<\/strong>.<\/p>\n\n

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

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

Shipped readable sources map to shipped bundles as follows (see assets\/src\/README.txt<\/strong> for the definitive table):<\/p>\n\n

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

    Fully regenerate bundles and the DICOM worker from the plugin root (Node.js current LTS<\/strong> recommended):<\/p>\n\n

      \n
    1. npm ci<\/li>\n
    2. npm run build (alias: npm run build:all<\/strong> \u2014 esbuild, then AI dictation Vite, then DICOM Vite)<\/li>\n<\/ol>\n\n

      Incremental development:<\/p>\n\n

        \n
      • npm run watch<\/strong> \u2014 esbuild only (booking-wizard, admin-calendar, facility-settings)<\/li>\n
      • npm run watch:vite:ai<\/strong> \u2014 Vite watch for ai-dictation<\/strong><\/li>\n
      • npm run watch:vite:dicom<\/strong> \u2014 Vite watch for dicom-viewer<\/strong> and kennelflow-vet-decode-worker.js<\/strong><\/li>\n<\/ul>\n\n

        Dependency versions remain pinned via package.json<\/strong> \/ package-lock.json<\/strong>.<\/p>\n\n

        Third-party libraries included in the bundled JS\/CSS<\/h4>\n\n

        The bundled UI loads these runtime OSS libraries straight from the emitted JavaScript payloads (matching package.json<\/strong> majors):<\/p>\n\n

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

          esbuild, Vite, TypeScript, and @vitejs\/plugin-react<\/strong> are build-time-only developer dependencies.<\/p>\n\n

          External Services<\/h3>\n\n

          This plugin avoids silent network calls beyond what WordPress administrators explicitly configure.<\/p>\n\n

          WordPress AI Client (optional SOAP dictation)<\/h4>\n\n

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

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

          When transmissions occur: Only after<\/strong> WordPress reports AI support (wp_supports_ai()<\/code>) and<\/strong> 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.<\/p>\n\n

          Data sent: (1) Audio<\/strong> \u2014 browser-captured dictation uploaded to your WordPress site, then passed to the AI Client with with_file()<\/code> for transcription; (2) Transcripts and prompt snippets<\/strong> \u2014 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.<\/p>\n\n

          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\u2019s terms and privacy policy in Connectors documentation alongside your facility\u2019s HIPAA\/state privacy workflows.<\/p>\n\n

          DICOM imaging viewer<\/h4>\n\n

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

          Laboratory webhook ingest (optional, inbound)<\/h4>\n\n

          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.<\/p>\n\n

          When transmissions occur: Inbound only<\/strong> \u2014 external lab systems initiate HTTPS POST requests to your WordPress site at \/wp-json\/kennelflow-vet\/v1\/lab-integration\/webhook\/{provider}<\/code><\/strong> 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.<\/p>\n\n

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

          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.<\/p>\n\n

          Privacy<\/h3>\n\n

          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.<\/p>\n\n

          Developer Resources<\/h3>\n\n

          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<\/strong>, then run npm run build<\/strong> so esbuild<\/strong> and Vite<\/strong> (including the Cornerstone3D DICOM bundle) all execute (matching the WordPress.org upload layout).<\/p>\n\n\n

            \n
          1. Install and activate KennelFlow Core<\/strong> from WordPress.org.<\/li>\n
          2. Install KennelFlow Vet (upload zip or install from the Plugins screen). The folder name should match the plugin slug \/wp-content\/plugins\/kennelflow-vet\/<\/code>.<\/li>\n
          3. Activate KennelFlow Vet from the Plugins screen.<\/li>\n
          4. Configure rooms, locations, and roles for your clinic.<\/li>\n<\/ol>\n\n\n
            \n

            Does this require another KennelFlow plugin besides Core?<\/h3><\/dt>\n

            KennelFlow Vet requires KennelFlow Core. Other KennelFlow add-ons are optional.<\/p><\/dd>\n

            Does this send data to external services?<\/h3><\/dt>\n

            Clinical and booking data ordinarily stay on your WordPress site. SMTP<\/strong> mail and other unrelated plugins remain outside KennelFlow Vet\u2019s scope. Laboratory ingest<\/strong> integrations do not transmit data externally unless clinic staff explicitly configure webhook or ingest flows that invoke other APIs.<\/p>\n\n

            AI SOAP dictation uses the WordPress AI Client (WordPress 7.0+).<\/strong> KennelFlow Vet does not store provider API keys. Site administrators configure AI connectors under Settings \u2192 Connectors<\/strong>; only then may permitted clinicians trigger dictation, which sends in-browser audio and derived text through the configured provider for transcription and SOAP structuring (see External Services<\/strong>). If no connector is configured, dictation is unavailable.<\/p>\n\n

            The in-browser DICOM viewer<\/strong> uses bundled JavaScript shipped with the plugin; it does not<\/strong> upload medical images to a third\u2011party viewing service by default.<\/p><\/dd>\n

            Where is the non-minified JavaScript and CSS source?<\/h3><\/dt>\n

            Human-readable sources live under assets\/src\/<\/strong> alongside assets\/src\/README.txt<\/strong> (dist-to-entry mapping). The same trees ship in every release alongside assets\/dist\/<\/strong>. Browse or fork from https:\/\/github.com\/brelandr\/kennelflow-vet. Run npm ci<\/strong> then npm run build<\/strong> from the plugin root after edits; see Developer notes for esbuild vs Vite entrypoints and bundled dependencies.<\/p><\/dd>\n\n<\/dl>\n\n\n

            0.1.0<\/h4>\n\n
              \n
            • Initial release on WordPress.org.<\/li>\n<\/ul>","raw_excerpt":"Veterinary foundation: patients, rooms, locations, and bookings with availability checks and REST API. Requires KennelFlow Core.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/311211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=311211"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/brelandr"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=311211"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=311211"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=311211"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=311211"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=311211"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=311211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}