System Structure
A structure for placing any activity in an emergency system precisely, so that two people talking about "the system" are talking about the same thing.
It uses two tools: a decomposition into subsystems (systems thinking) and a value chain applied inside each subsystem (Porter, Competitive Advantage, 1985). Together they say where an activity lives and who controls it.
The subsystems#
An emergency system has five subsystems. Each subsystem depends on the ones around it (see Integration and anti-fragmentation).
- Public Recognizes the emergency, intervenes, and activates the system Readiness Response
- Communications Answers the call, triages it, instructs the caller, and dispatches Readiness Response
- First response Rapid assessment and intervention in life threats Readiness Response
- Patient transport Moves the patient to definitive care Readiness Response
- Definitive care Prepares for, accepts, and treats the patient Readiness Response
The patient passes from one subsystem to the next
| Subsystem | What it covers |
|---|---|
| Public | The public's ability to recognize an emergency, intervene (bystander CPR/AED), and activate the system (911 access). |
| Communications | Turning a call into a response: answering it, determining what is wrong and how urgent, instructing the caller until help arrives, and sending the right resources. |
| First response | Rapid assessment and intervention in life threats: turnout, arrival, stabilizing the patient, and transfer of care to the ambulance, which frees the responders for the next time-sensitive call. |
| Patient transport | Moving the patient to definitive care: out-of-chute, on-scene, conveyance to a capability-matched destination, and return to service. |
| Definitive care | The receiving facility preparing for, accepting, and treating the patient. |
A cross-cutting layer sits across all of them: system-wide medical direction, data and quality improvement (aligned to NIMS, NEMSIS, and NEMSQA), interagency coordination, and disaster/MCI response.
The three parties#
Three roles are in play in the subsystems where readiness is bought (communications, first response, patient transport, and definitive care): the regulator, the procuring entity, and the producer. One body may hold more than one of them and the same body may hold different roles in different subsystems.
- The regulator
- The oversight function, whatever body performs it in a given system: a county EMS agency, a state EMS office, a regional council, or a public-utility board.
- The procuring entity
- The party that decides how much readiness to buy, pays for it, and answers for the result against the standard.
- The producer
- The party that produces the readiness the procuring entity buys, accountable only for what it controls.
For example, in a system with an exclusive private transport producer:
| Subsystem | Regulator | Procuring entity | Producer |
|---|---|---|---|
| Communications | The county EMS agency (dispatch protocols, medical direction for pre-arrival instructions) | The city, county, or joint powers authority that funds the dispatch center | The dispatch center |
| First response | The county EMS agency (credentials the responders, sets protocols) | The city that funds its fire department | The fire department |
| Patient transport | The county EMS agency | The private ambulance company, which decides how much readiness to field, holds the deployment plan, and bills | The same private ambulance company |
In this example the private ambulance company is both the procuring entity and the producer: it buys its own readiness, produces it, and answers to the regulator for the result. In patient transport the procuring entity is also the provider of record that bills for transports, which is why it carries the transport-revenue risk.
The regulator#
The regulator plans, coordinates, and evaluates the whole system and integrates the subsystems under unified medical direction.
Under every delivery model the regulator sets standards and operational response-time allotments, defines zones and coverage, holds medical direction, sets protocols, credentials producers, evaluates the system, and adjudicates exemptions. The procuring entity pays for the readiness, answers to the regulator for meeting the standard, and bears any penalty for missing it. The procuring entity may be the same body as the regulator, but need not be.
The regulator holds the procuring entity to the response-time standard, because the procuring entity controls the readiness and deployment plan that produce it. The procuring entity holds each producer to the metrics within its scope of control.
The regulator may also be the procuring entity, provided that whenever it sets or changes the standard it is judged by, that act is explicit and on the record.
The value chain, applied inside each subsystem#
A value chain (Porter, Competitive Advantage, 1985) treats an organization's work as a sequence of activities, each of which adds value on the way to the customer. Separating them lets each activity's cost and contribution be seen on its own instead of treating the organization as a black box. Five primary activities carry the service to the patient; four support activities make the primary ones possible.
| Activity | In an emergency system |
|---|---|
| Inbound logistics | Bringing in what production needs: people, vehicles, equipment, supplies, and information |
| Operations | Producing the service: readiness and response |
| Outbound logistics | Warehousing and distribution: storing the finished product and moving it to the patient. Not applicable; readiness cannot be stored. |
| Marketing and sales | The public knowing the service exists and when to use it |
| Service | What follows the call: records, billing, and feedback |
| Infrastructure | Governance, management, finance, and legal |
| Human resources | Recruiting, training, credentialing, and scheduling |
| Technology | Computers, networks, phones, radios, printers, and the software that runs on them |
| Procurement | Purchasing what the other activities need |
ODS applies the chain inside each subsystem, not to the system as a whole, so every activity has one home and one party that controls it. Communications, first response, and patient transport each have their own operations, their own people, their own technology. When one party serves several subsystems, the support activities can be shared across them: one procurement function, one technology stack, one human resources office. That sharing is one of the benefits of integration and it is available only to a party that spans the subsystems.
Two adaptations are load-bearing and unique to emergency response:
- Operations decomposes into readiness and response, measured separately. Everything a subsystem does operationally is either producing the capacity to act (readiness) or acting when a call comes (response). (See Measurement & the Score.)
- Outbound logistics is not applicable because readiness has no shelf life. In a firm that makes goods, outbound logistics is how the finished product is stored and shipped. An emergency system's product is availability, which cannot be stored: a unit hour not used at 2 p.m. is gone. That removes a value-creation lever other industries have and makes creating value in emergency services structurally harder than in industries with tangible goods.
Marketing and sales, in an emergency system, is not advertising and it is not a relabeling of the public subsystem. Awareness is a genuine link in the value chain: capacity nobody knows how to reach produces nothing. The field has largely informed the public how to activate an emergency response, with 911 on every fire truck, billboard, and phone, and spends little on when the public should activate the system, which is the decision that actually has to be made.
Integration and anti-fragmentation#
The subsystems depend on one another. A patient passes from one to the next and each one needs the next to be ready. An integrated system is one where those handoffs work.
Integration is how much of the patient's path sits under unified control. Every boundary between organizations is a place where the party on one side does not control what happens on the other, so the fewer of them a patient crosses, the more integrated the system. Clinically, unified medical direction has largely solved this and operations can do the same.
The value chain shows a second benefit. Every subsystem needs the same support activities: infrastructure, technology, human resources, and procurement. When the subsystems belong to different organizations, each runs its own isolated payroll, purchasing office, and records systems. When one party serves several subsystems it becomes possible to share those resources.
A fire department that provides communications and first response holds most of that path before it transports anyone and runs one set of support activities under all three, which is why fire-based transport can reach a depth of integration a stand-alone producer cannot.
However, the same depth can be reached another way, even with multiple transport producers: unified procurement of readiness, a unified deployment plan, and unified accountability integrate readiness and response operations, which is what the readiness market builds.
Unified accountability means every party answers for what it controls and every metric that matters has an owner. A producer answers for its scope of control: the intervals its crews control, from turnout or out-of-chute through return to service. Operational response time is one of several metrics that assess readiness and the deployment plan. The party that answers for it is also responsible for unit-hour procurement, the deployment plan, and billing. The rule is stated in What travels together.
One subsystem can degrade another's readiness#
When a downstream subsystem is slow, the upstream one cannot return to a ready state:
- At the hospital (definitive care to patient transport): when the emergency department cannot move a patient off the stretcher and into a bed, the ambulance crew waits with the patient in the hallway, two crew members to one patient. The crew is utilized with excessive task time, resulting in lost unit hours.
- On scene (patient transport to first response): when the transport unit is slow to arrive, the first responders continue care on scene until it arrives and cannot return to service until it does. They too are utilized with excessive task time.
- On the phone (first response to communications): when first response is slow, the call taker stays on the line giving pre-arrival instructions and cannot timely answer the next call.
ODS attributes the loss to the party that caused the delay, not to the subsystem that absorbed it. Measurement & the Score shows how.
What travels together#
Unit-hour procurement (quantity), the deployment plan (location), response-time accountability, and billing travel together.
One body holds all four: the procuring entity. Money in sets the readiness that can be bought and the readiness bought dictates the deployment. Split the four and the party judged on the measured clock has no reason to pay for the readiness nobody measures.
The four always live in patient transport. Which body is the procuring entity depends on the delivery model. The regulator is the same in every case; the two roles that move differ by model:
- Procuring entity
- Producer
| Delivery model | Arrangement | Procuring entity | Producer |
|---|---|---|---|
| Private, exclusive contract | Exclusive | The private ambulance company | The same company |
| Fire-based | Exclusive | The fire department | The same department |
| Third-service | Exclusive | The EMS department | The same department |
| Hospital-based | Exclusive | The hospital | The same hospital |
| Volunteer or combination | Exclusive | The volunteer service | The same service |
| Public procurement (alliance model) | Exclusive | A public body: a city, a fire department, a county EMS agency, or a joint powers authority | A private, fire, hospital, or volunteer producer selling unit hours to it |
| Public procurement (readiness market) | Non-exclusive | A public body: a city, a fire department, a county EMS agency, or a joint powers authority | Any combination of private, fire, hospital, and volunteer producers selling unit hours to it |
In every model the regulator holds the procuring entity to the response-time standard and the procuring entity holds each producer to the metrics within its scope of control.
In the first five models the procuring entity and the producer are one body. In public procurement they are different parties and the procuring entity buys readiness from producers it does not own: from one producer in the alliance model and from any combination of producers in the readiness market, which is ODS's design for public procurement (see The Readiness Market). In a volunteer system the same functions run, paid in engagement and appreciation rather than salary, which is still not free.
This gives any community one precise question to ask of any proposed model: who is the procuring entity?