PARamedic Ops Chief Presentation Guide

Presentation objective

Use the fictional development agency to show how PARamedic Ops gives an EMS chief evidence of readiness, cost, and accountability. The seed represents a 3,000-call annual ALS service with three ambulances, one supply room, four vendors, and six months of history.

The dataset contains 1,500 calls over the prior 182 days: 450 BLS, 825 ALS 1, and 225 ALS 2. That is a 70% ALS mix with 15% of all calls classified as ALS 2. The same period includes 24 vendor orders, 16 inventory items, seven tracked lots, four vehicle storage areas, three narcotic kits, and representative issues.

Prepare the room

1. Reset the complete development dataset.
2. Confirm the DEVELOPMENT ENVIRONMENT banner and use only fictional records.
3. Open Home, Inventory Health, Ordering, Reporting Center, Narcotics Transactions, and Help & Learning.
4. Use Development Ambulance 1 for readiness and Development Ambulance 3 for the narcotics exception.

15-minute chief briefing

Slide 1 — One operational picture

State the scenario: three ALS ambulances draw from Development Supply Room, crews record consumption, inventory staff restore readiness, and administrators purchase from four vendors. Each workflow contributes to one permanent history. Show the Home dashboard and its role-specific operational cards.

Slide 2 — Readiness before the call

Open Inventory Health for Development Ambulance 1. Show Development shortage requiring review for Abdominal Pad 5x9 and explain configured PAR versus actual balance.

Use the seeded storage areas: Airway Cabinet, Driver Side IV Drawer, Passenger Side Medication Drawer, and PPE and Trauma Cabinet.

Leadership point: required quantities, balances, expiration exposure, and unresolved issues are visible before a crew discovers them during a response.

Slide 3 — Work becomes management evidence

Open Reporting Center for the prior six months. Show 1,500 calls and 5,800 inventory-use movements. Explain the mix: 30% BLS, 55% ALS 1, and 15% ALS 2.

Use Alcohol Prep Pads - 10 pack, 10 mL Syringe, IV Catheter 18 gauge, Normal Saline 1000 mL, Aspirin 81 mg tablets, and Adult ECG Electrodes as examples of demand that changes with acuity.

Leadership point: usage, shortages, expirations, and corrections come from operational events instead of month-end reconstruction.

Slide 4 — Purchasing control

Open Ordering and show six rolling monthly cycles for Development Medical Supply, Metro EMS Catalog, Regional Pharmaceutical, and Emergency Care Wholesale.

The newest cycle contains completed, submitted, and draft work. Open the submitted Regional Pharmaceutical order to discuss open-order coverage. Open the Emergency Care Wholesale draft to discuss review before commitment. Identifiers use DEV-PO-YYYYMM-1 through -4 and advance after reset.

Open Compare vendor prices or Smart Recommendations. Explain package size, normalized price, lead time, usable stock, PAR, expiration loss, and already-ordered quantities.

Leadership point: the software recommends from evidence and keeps purchasing approval with agency staff.

Slide 5 — Expiration and lot accountability

Show tracked lots for epinephrine, IV catheters, aspirin, saline, ECG electrodes, albuterol, and the i-gel airway. Epinephrine 1 mg/mL is intentionally nearest expiration; dates roll forward with a reset.

Leadership point: receiving captures the identity used later for expiration response, counting, and traceability.

Slide 6 — Controlled-substance boundary

Open Narcotics Transactions. Show DEV-KIT-001 and DEV-KIT-002 green and DEV-KIT-003 red on Development Ambulance 3.

Leadership point: permissions, seals, custody, discrepancies, and audit history remain in a distinct accountable workflow.

Slide 7 — Implementation and governance

Open Application Configuration and User Management. Explain module licensing, role permissions, notifications, and release stages. Use seeded Voice Count to show that an alpha feature can be limited to beta-enabled users.

Open Help & Learning and show the current User Manual, this guide, the Release Guide, and support tickets. Updated documentation publishes with the software and remains cached for interrupted connectivity.

Leadership point: rollout can be staged by module, role, and maturity with current guidance inside the application.

Decision discussion

1. Confirm annual call volume and ALS mix.
2. Count stations, vehicles, supply locations, and users.
3. Identify vendors and purchasing approvals.
4. Identify truck-check, medication, equipment, and narcotics policies.
5. Define reporting, retention, backup, notification, and support expectations.
6. Select first-phase modules and later-phase modules.

Presentation safeguards

• Never display production records or patient information.
• Do not quote seed totals as projected savings or clinical outcomes.
• Describe alpha and beta functions by their current release stage.
• Do not present general inventory as a substitute for narcotics custody.
• Reset the dataset after presentations that post transactions or change configuration.