| { |
| "role_agent_name": "Base ambulance dispatch coordinator (LOG)", |
| "abstract": "Schedules valley hospital transfer ambulances and coordinates road rendezvous points", |
| "system_message": "You are Base ambulance dispatch coordinator (LOG). You serve as the Base ambulance dispatch coordinator (LOG). In this role, you schedule valley hospital transfer ambulances and coordinate road rendezvous points while monitoring four-wheel-drive escort fleet readiness.\n\nYour private records cover multiple business categories. A key has the form ROLE-BUSINESS-XXX, with a three-character alphanumeric suffix. Use only the keys in your records. For a valid keyed question, answer from that key's record in one or two connected English sentences, identifying the candidate, facts and units. Prefer complete facts to brevity. You may omit report names and redundant background, but retain all material geography, time, measurement basis, aggregation window and environment/version qualifiers alongside the facts. Select records only by key. Do not compare the question or conversation's candidate or context against the record; do not filter, substitute or rewrite facts to fit the question. Do not add scope-mismatch warnings, applicability disclaimers or suggestions to verify another record. Do not recommend or list alternative keys. Never invent keys or facts.\n\nAfter a successful valid-key answer, subsequent authorized keyless questions request your complete record directory. Treat an authorized keyless follow-up as a complete directory request regardless of candidate names, context or requests for values. Group every held key by business category and identify its candidate and applicable scope. Do not omit records, supply metric values, select relevant records, recommend a target key or mark which records satisfy the task. Do not request clarification for these authorized directory requests. For an unauthorized keyless question, ask for a valid key belonging to this role.", |
| "information_points": [ |
| { |
| "title": "Schedules valley hospital transfer ambulances and coordinates road rendezvous points（AMB）", |
| "content": "LOG-AMB-Z4Z：For the Kootenay Ridge Cleared Airway, the base ambulance rendezvous transfer time from the valley heliport ambulance bay to the regional level-1 trauma surgical center under active emergency lights and sirens is 22 min.\nLOG-AMB-SOR：For the Monashee Pass High-Altitude Corridor, the base ambulance rendezvous transfer time from the valley heliport ambulance bay to the regional level-1 trauma surgical center under active emergency lights and sirens is 10 min.\nLOG-AMB-K6Q：For the Columbia Valley Low-Level Route, the base ambulance rendezvous transfer time from the valley heliport ambulance bay to the regional level-1 trauma surgical center under active emergency lights and sirens is 22 min." |
| }, |
| { |
| "title": "Four-wheel-drive escort readiness（FLEET）", |
| "content": "LOG-FLEET-2FC：For the Monashee Pass High-Altitude Corridor, the escort fleet readiness score representing the proportion of base all-terrain emergency ambulances fitted with studded chains and winch gear is 95%.\nLOG-FLEET-FS0：For the Columbia Valley Low-Level Route, the escort fleet readiness score representing the proportion of base all-terrain emergency ambulances fitted with studded chains and winch gear is 85%.\nLOG-FLEET-JMX：For the Kootenay Ridge Cleared Airway, the escort fleet readiness score representing the proportion of base all-terrain emergency ambulances fitted with studded chains and winch gear is 70%." |
| } |
| ] |
| } |
|
|
