Pediatric Urological Surgery Readiness Condition (PedsUROCON)
Bibliographic record
Abstract
To the editor,
 
 As of March 11th, 2020 the World Health Organization declared Coronavirus disease 2019 (COVID-19) a pandemic and urged countries to implement protocols to contain the virus spread [1]. It was soon realized that the world was ill prepared and too few lessons had been learned from previous infectious outbreaks in 2003 and 2009. [2] As a result, preparation and planning were insufficient to deal with the impact of this strain on the healthcare system.
 To deliver the optimal care despite this pervasive and fast-evolving event, healthcare managers must address and adjust 4 main domains in order to reach optimal surge capacity: maximize use of hospital structure, increase staff capacity, prioritize use of equipment and supplies, and develop an efficient communication system between hospitals [3,4]. Another key factor in pandemic preparedness is the rapid acquisition of information on pathogen epidemiology. All of this knowledge is essential to make adjustments, which can increase the reliability of the current protocol in addition to clarifying existing hospital vulnerabilities. More importantly, it can assist in predicting which further measures might be necessary to accommodate the influx of patients. [3,4].
 It is important to recognize that patient flow plays a primary role in organization of hospital resources [4]. Critically analyzing the needs and requirements of each healthcare component, by identifying a hierarchy of their services, can lead to hospital planning being more efficient, resulting in quicker establishment and mobilization of rapid-response groups. [3,4]. However, accuracy of communication is a major challenge identified when creating a mass protocol as inconsistent terminology or triggers can generate confusion [4]. For this reason, assuring optimal communication and networking between local and regional hospitals aids hospital management by allowing patient tracking, information sharing, and appropriate distribution of patients and supplies [3-5].
 Defense readiness condition (DEFCON) is a system created by the United States military to standardize the level of reaction required for a threat level perceived by the military [6]. DEFCON is graded from 1 to 5, where 5 represents normal peacetime readiness and 1 represents maximum readiness – nuclear war is imminent [6]. Each level is detailed with the expected actions and clearly states the trigger to activate the next level. This system establishes a clear and well-defined approach to assess readiness and could be used as a template in healthcare for crisis management. In order to achieve this, hospital departments should create protocols that prioritize procedures based on hierarchy and formally establish triggers that guide personnel when upgrading or downgrading readiness levels is recommended.
 The concept of using the DEFCON model to create a crisis standard of care was previously suggested by Dr. Thomas Forbes from the Vascular Surgery Department at the University of Toronto when designing the VASCCON [7]. Based on this experience, we propose the pediatric urological surgery readiness condition (PedsUROCON). PedsUROCON includes guidance for different alertness levels ranging from a fully functional hospital capacity (level 5) to when maximal hospital capacity has been reached, and even life/limb threatening surgeries cannot be performed (level 1). The purpose of this decision-making algorithm is to serve as a template for long-term pediatric urology pandemic/emergency preparedness. Figure 1 describes which procedures should be restricted once each level of alertness is reached. 
 PedsUROCON alertness levels should be transitioned (i.e. upgraded or downgraded) once hospital capacity reaches pre-determined thresholds. We suggest 40%, 60%, 80% and 100% of hospital capacity (table 1). Hospital capacity should be determined by hospital administrators when factoring physical space, personnel availability, resources and supplies. Regional communication and networking are paramount for this system to be effective. Constant communication must be maintained throughout the crisis to coordinate the efficient flow of patients, resources and information with the goal of reducing the need to escalate any healthcare institution to the next UROCON level. 
 Each level of PedsUROCON can be implemented on the fast developing COVID-19 outbreak (figure 2). The protocol is based on resources and procedures offered at our institution. We recommend adjusting thresholds for triggers based on regional epidemiological forecasting, hospital programs & specialized care areas, physical capacity and services offered by the local healthcare system. Lastly, for optimizing functionality and readiness, this system should be updated annually, after a major change in clinical care protocols or after major renovations at a hospital; whichever comes first.
 Creating a surge capacity mitigation protocol involves a multilayered level of interconnectivity between local hospitals, regional healthcare services, hospital supplies management and emergency services infrastructure. Current protocols are lacking and inefficient in being able to deal with events such as the COVID-19 outbreak. Establishing the UROCON protocol will allow hospitals and healthcare infrastructures to be forewarned allowing them to be forearmed. 
 
 Summary:
 Purpose:long term pediatric urology pandemic plan for patient flow management. PedsUROCON alertness levels should be transitioned once hospital capacity reaches specific thresholds. Hospital should communicate with the network of regional hospitals to organize patient flow. Alertness on patient flow facilitates prioritization of equipment, structure and services.
 Thresholds for action:UROCON 5: <40% hospital capacity; UROCON 4: 40-59%; UROCON 3: 60-79%; UROCON 2: 80-99% and UROCON 1: ³100% of hospital maximal capacity.
 Maintenance:Based on the current structure of the hospitals and demands, their UROCON should be updated yearly, following a major protocol change or after a major hospital renovation; whichever comes first.
 Goals:i) Organize patient flow in pediatric urology; ii) Standardize communication between hospital departments to optimize resource utilization; ii) Promote communication between hospitals to improve pandemic/emergency planning
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".