內容簡介
Dermatriq 是一款專為皮膚科診所設計的全方位管理系統，能夠幫助診所簡化日常運營、提升病人體驗，並在一個平台上管理預約、帳單等所有事務。
【主要功能】
• 統一的角色導向控制台，適用於管理員、醫生、接待員及帳單用戶
• 前端病人註冊、登入及個人資料更新功能
• 預約管理流程，包含狀態生命周期及請求處理
• 發票管理，支持項目化帳單及付款追蹤
• 報告儀表板，提供運營可見性及數據分析
外掛標籤
開發者團隊
② 後台搜尋「Dermatriq – Dermatology Clinic Management System」→ 直接安裝（推薦）
原文外掛簡介
Dermatriq is a powerful all-in-one dermatology clinic management system built for WordPress. It helps clinics streamline operations, improve patient experience, and manage everything from appointments to billing in one place.
Dermatriq helps dermatology clinics manage day-to-day workflows from one WordPress admin panel.
Who Is This Plugin For?
✔ Dermatology clinics
✔ Skin care centers
✔ Aesthetic clinics
✔ Multi-doctor practices
✔ Medical service providers
Why Dermatriq?
✔ Built specifically for dermatology clinics
✔ Easy to use and fully integrated with WordPress
✔ Reduces manual work and improves efficiency
✔ Centralized system for patient, billing, and operations
✔ Scalable for growing clinics
🔥 Pro version coming soon with advanced features, automation, and extended capabilities.
Detailed Features
Unified role-aware dashboard for admins, doctors, receptionists, and billing users
Capability-based module access and protected admin actions
Patient and Frontend Features
Frontend patient registration, login, forgot-password, dashboard, and profile shortcodes
Patient self-profile update with validation and secure request handling
Patient timeline with appointments, prescriptions, invoices, payments, and weight history
Patient ID card preview and print support
Clinical Workflow Features
Appointment create/manage flow with status lifecycle and request handling
Doctors module with profile management and specialization mapping
Treatments module with sessions, interval days, per-session cost, and total-cost logic
Advises and medicines master data modules for reusable prescription items
Prescription management with treatment-session progression support
Billing and Financial Features
Invoice management with itemized billing
Payment recording with paid/due tracking and payment status updates
Deterministic invoice recomputation and discount handling safeguards
Invoice print preview and print-ready output
Reports and Operational Visibility
Reports dashboard with date filters and operational KPIs
CSV export support across key reporting and module screens
System log views for activity and email traceability
Template, Communication, and Admin Controls
Email template management with event-based toggles
Page template management for prescription, invoice, and card layouts
Forms settings for field visibility/required policy controls
Backup export/import with validation and admin-only protection
QR and Verification Features
QR token verification for supported records
Compact public verification output with privacy-aware field limits
External QR image generation service disclosure in this readme
Architecture Overview
Unified admin dashboard with role-aware context views (admin, doctor, receptionist, accountant)
Legacy doctor dashboard route is an alias redirect to unified dashboard doctor view
Frontend patient system: login/registration, patient dashboard tabs, profile edit/view, password change, ID card preview/print
Central mailer service with event registry and template-driven rendering
Email System
Registry-driven templates on Dermatriq -> Email Templates
Per-event ON/OFF toggle is authoritative before send
Send outcomes are logged in dermatriq_email_logs (sent/failed/skipped)
Deduping uses event identity/body hash safeguards in mailer
SMTP or a configured mail transport is required for reliable delivery (wp_mail depends on host mail setup)
Printing Contracts
Invoice and Prescription print use A4 contract via assets/css/dermatriq-print.css
Patient and Doctor ID Card print contract: 3.35in x 2.17in
Template/Preview/Print parity is enforced for invoice, prescription, and ID cards
Database Tables (Dermatriq)
dermatriq_advise_categories
dermatriq_advises
dermatriq_appointments
dermatriq_discounts
dermatriq_doctor_awards
dermatriq_doctor_certifications
dermatriq_doctor_education
dermatriq_doctors
dermatriq_email_logs
dermatriq_invoice_discounts
dermatriq_invoice_items
dermatriq_invoices
dermatriq_logs
dermatriq_medicine_categories
dermatriq_medicine_companies
dermatriq_medicines
dermatriq_patient_treatment_states
dermatriq_patients
dermatriq_payments
dermatriq_prescription_advises
dermatriq_prescription_medicines
dermatriq_prescription_treatments
dermatriq_prescriptions
dermatriq_roles
dermatriq_specializations
dermatriq_treatments
dermatriq_weight_history
Security & Permissions
Capability checks for admin actions
Nonce verification for state-changing requests
Sanitization and escaping across request/output paths
Prepared SQL for dynamic query values
Public QR verification endpoints are token-scoped and intentionally compact
Patient/Doctor QR verify output excludes contact fields (no mobile/email/address output)
Backup (Import/Export)
Export JSON backup from Settings -> Backup
Import JSON backup with overwrite confirmation and admin-only access
Includes Dermatriq options/templates/forms/roles and Dermatriq custom tables
Does not export WordPress core user credentials (wp_users / password hashes)
Optional uninstall cleanup toggle is available in Settings -> General
Developer Hooks
Reports context filters and post-query hooks
Timeline context and built hooks
Invoice recalculation context and completion hooks
Backup export/import hooks for integration plugins
Payment recorded and invoice created action hooks
Appointment status/date change hooks used by notifications/reminders
External services
This plugin uses a third-party service to generate QR codes.
Service: QRServer API (api.qrserver.com)
Purpose: Generate QR code images when QR features are used inside the plugin.
Data sent: The text/URL content to encode in the QR code (tokenized verification URLs), and the requested image size.
When sent: Only when a QR code is generated or viewed.
Terms: https://goqr.me/legal/tos-api.html
Privacy: https://goqr.me/privacy-safety-security/
Documentation: https://goqr.me/api/
Site owners should ensure their own privacy policies disclose this external request behavior.
