Works with the AI Agents you already use
appointment access measurement
Analyzes scheduling records to compute appointment access metrics: wait times, within-target percentage, no-show rates, and trends by specialty and provider. Operational decision support; data gaps may bias measures.
$1.99
appointment access measurement
Example session with this skill installed
Analyze these 12 appointments for the Cardiology department. Access target is 10 days. [Records: Req 2023-10-01, Sched 2023-10-05, Status: completed; Req 2023-10-01, Sched 2023-10-20, Status: no_show...]
- Read your context and instructions
- Compiled the appointment access measurement
The analysis of 12 Cardiology appointment records is complete. The calculation script processed the request using an access target of 10 days. # Appointment Access Measurement — City General, 2023-10-15 ## 1. Summary and scope - **Sources**: E1 (Supplied scheduling log) - **Appointment Count**: 12 - **Access Target**: 10 days - **Mean Wait Time**: 11.4 days - **Within-Target %**: 58.3% - **No-Show Rate**: 16.7% ## 2. Specialty metrics | Specialty | Appointments | Mean Wait (Days) | Within Target % | No-Show Rate | | :--- | :--- | :--- | :--- | :--- | | Cardiology | 12 | 11.4 | 58.3% | 16.7% | ## 3. Access issues | Specialty | Issue | Value | Target | | :--- | :--- | :--- | :--- | | Cardiology | Below Target % | 58.3% | 80.0% | ## 4. Weekly trends | Week Starting | Appts | Mean Wait | No-Show Rate | | :--- | :--- | :--- | :--- | | 2023-10-01 | 7 | 10.2 | 14.2% | | 2023-10-08 | 5 | 13.1 | 20.0% | ## 5. Data quality and warnings - **W002**: Missing `provider` field in 3 records. - **W005**: 1 record has `request_date` after `scheduled_date`. ## 6. Observations and items for review - The mean wait time of 11.4 days exceeds the 10-day target by 14%. (Computed result) - **Analytical estimate — validation required**: The 20% no-show rate in the second week suggests a potential localized scheduling conflict or communication failure. - **Management decision required**: Consideration of expanding Tuesday clinic hours to address the wait time trend. This analysis supports operational decision-making. Data gaps may bias measures. **Next steps** 1. Review the specific records flagged with W005 to correct date entry errors. 2. Validate if the increase in wait times during the second week correlates with reduced provider availability.
Connects securely to your tools. The creator never sees your data.
About this skill
Manual tracking of patient wait times and scheduling performance often leads to inconsistent reporting and missed operational bottlenecks. This skill automates the calculation of healthcare access metrics using scheduling records to deliver precise wait time and no-show analysis. ## What it does - **Wait time calculation** computes the days elapsed between request dates and scheduled appointment dates. - **Service level monitoring** measures the percentage of appointments that meet defined access targets. - **No-show analysis** calculates rates of missed appointments across different reporting periods. - **Specialty segmentation** breaks down performance metrics by department and individual provider. - **Trend identification** generates weekly data tables to track operational improvements or regressions. ## How it works 1. The user provides scheduling records including request dates, scheduled dates, and appointment statuses. 2. The agent builds a `request.json` file, mapping data to fields like `specialty`, `provider`, and `appointment_type`. 3. The deterministic `scripts/run.py` processes the data to ensure mathematical accuracy without manual adjustment. 4. The agent generates a structured report covering specialty metrics, access issues, and weekly trends. ## Frameworks & tools This skill utilizes a Python-based calculation engine and handles data structured via JSON Schema. It is designed for operational environments requiring deterministic output rather than generative estimates. ## Why this beats prompting it yourself Generic prompts often struggle with date math, especially across large datasets, or hallucinate averages when data gaps exist. This skill uses a self-contained script to ensure every metric is computed via standardized formulas, while automatically flagging data quality warnings that could bias your results. ## Use cases - Auditing wait times by specialty to identify where access targets are being missed. - Tracking no-show rate fluctuations to assess the impact of new patient reminder systems. - Generating operational reports for clinic managers to support staffing decisions. - Identifying data quality gaps in scheduling logs that prevent accurate performance measurement. ## Known limitations This skill is strictly for operational decision support and must not be used for clinical triage or patient prioritization. Groups smaller than five appointments are suppressed to maintain statistical relevance.
Operational support only. No clinical triage or staffing forecasting. Groups smaller than 5 appointments are suppressed. Requires request/scheduled dates in ISO format.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 day ago