SYNTHETIC DEMO DATA
Every operational figure on this page — census, monitoring days, cart counts, callback hours and time-to-start — comes from a fictional department fixture. None of it is a measurement of your service, an industry benchmark or a validated average. For a real department these are NEEDS INPUT until your own census, inventory and callback records are supplied.
Readiness
Active monitoring studies
1 pending start · 1 pending stop
Median time to start
From order to recording, synthetic demo data.
Callback hours this month
14 after-hours activations
Readiness by domain
A readiness view, never an accreditation determination. Each domain names the question the program has to answer and who owns the answer.
| Domain | The question | State | Where it stands | Owner |
|---|---|---|---|---|
| Staffing model | Who applies, maintains, monitors and reviews, in every hour the service claims to cover? | gap | Application and maintenance covered weekdays; after 18:00 relies on callback. | Manager |
| Competency mix | Which technologists hold verified LTM / critical-care competencies? | partial | Two technologists at supervised stage; one independent; no preceptor-capable depth. | Technical lead |
| Medical coverage | Who reads, how often, and what is the escalation path overnight? | partial | Twice-daily review defined; overnight escalation path unwritten. | Medical director |
| Equipment & consumables | Carts, amplifiers, electrodes, spares and turnaround. | partial | Two carts; no spare amplifier; consumable par levels informal. | Technical lead |
| Network & storage | Bandwidth, remote review, retention and archive. | gap | Remote review possible from two workstations only; retention policy not documented. | IT partner |
| Activation & escalation | Who may start a study, in what timeframe, and what triggers a call? | partial | Criteria written; target response time not measured. | Medical director |
| Quality assurance | Technical QA, impedance standards, artefact review, record audit. | gap | No scheduled technical record audit. | Technical lead |
| Financial case | Cost of coverage vs avoided transfers and length-of-stay assumptions. | not assessed | Not modelled yet; run the Core financial model with cEEG volumes. | Administrative director |
Financial case and roadmap
What a launch costs, and in what order it happens.
Cost drivers
- • Technologist hours for application and daily maintenance (1.4 hrs per monitoring day, model default)
- • Coverage of hours that previously ran on callback
- • Carts, amplifiers, spares and consumable par levels
- • Network bandwidth, remote review workstations, storage and retention
- • Competency development and preceptor time
Implementation roadmap
- 1. Agree the coverage promise: which hours the service actually claims.
- 2. Write activation criteria, target response time and the overnight escalation path.
- 3. Build competency depth to at least two independent technologists per covered shift.
- 4. Confirm storage, retention and remote review with the IT partner.
- 5. Start with a defined unit and indication set, then widen.
- 6. Measure time to start, maintenance intervals and callback burden from day one.
Administrative draft — not clinical authority
This output is operations and administration software. It does not interpret EEG, does not provide diagnostic decision support, and carries no clinical authority. Clinical criteria and local policy require review and approval by your physician and medical leadership.