imedicalxc-doctor-perf-analysis-engineer

Name: imedicalxc-doctor-perf-analysis-engineer
Availability: InStock
Author: skylercook

Analyze trace IDs and optimize database calls for HIS doctor station interfaces.

Updated Jun 4, 2026

Search Tags:#performance analysis #database optimization #HIS #interface optimization #slow API identification

Ready to run

npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-perf-analysis-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: imedicalxc-doctor-perf-analysis-engineer
Source: https://github.com/SkylerCook/imedical.agents/tree/main/plugins/imedicalxc-doctor-perf-analysis-engineer/skills/imedicalxc-doctor-perf-analysis-engineer
Command: npx skills add https://github.com/SkylerCook/imedical.agents --skill imedicalxc-doctor-perf-analysis-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill analyzes and optimizes the performance of HIS doctor station interfaces, identifying slow APIs, tracing trace IDs, and optimizing database calls and frontend loading performance.

Core Features & Use Cases

Performance Analysis: Full chain tracking (Controller → BLH → Service → Mapper), N+1 query and batch call optimization, Graylog log analysis, performance report output.
Slow API Identification: Identify slow interfaces by analyzing trace IDs and optimizing database calls and frontend loading performance.
Use Case: Imagine you have a large number of HIS doctor station interfaces and you want to improve their performance. Use this Skill to analyze the interfaces, identify the bottlenecks, and optimize them accordingly.

Quick Start

Run the 'imedicalxc-doctor-perf-analysis-engineer' skill and provide the trace ID or interface name you want to analyze.

Frequently Asked Questions about imedicalxc-doctor-perf-analysis-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify slow APIs in an HIS doctor station interface?▼

Identify slow APIs in HIS doctor station interfaces by analyzing trace IDs to track the full execution chain from Controller to Mapper, isolating N+1 queries and frontend loading bottlenecks.

What is full chain tracking for HIS performance analysis?▼

Full chain tracking for HIS performance analysis monitors execution paths from Controller through BLH and Service to Mapper, exposing N+1 query inefficiencies to optimize database calls.

How do I optimize database calls causing N+1 queries in HIS systems?▼

Optimize database calls causing N+1 queries by analyzing trace IDs and Graylog logs to detect batch call inefficiencies, then refactoring the query logic within the HIS doctor station interface.

Can I use Graylog logs to troubleshoot HIS doctor station interface performance?▼

Yes, you can use Graylog log analysis to troubleshoot HIS doctor station interface performance by parsing trace IDs to locate slow database calls and frontend loading delays across the request chain.

Do I need prerequisite knowledge before analyzing HIS doctor station performance?▼

Yes, you need prerequisite knowledge of using superpowers before analyzing HIS doctor station performance to effectively trace IDs, optimize database calls, and generate performance reports.

What is the best way to troubleshoot slow HIS doctor station interfaces?▼

The best way to troubleshoot slow HIS doctor station interfaces is running a performance analysis that traces IDs across the Controller-to-Mapper chain, analyzes Graylog logs, and outputs a performance report.