MétaCan
Menu
Back to cohort
Record W2998878620 · doi:10.1061/9780784482223.003

Medical Office Building Structural Design Considerations

2019· article· en· W2998878620 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueStructures Congress 2019 · 2019
Typearticle
Languageen
FieldPsychology
TopicFacilities and Workplace Management
Canadian institutionsLockheed Martin (Canada)
Fundersnot available
KeywordsFlexibility (engineering)Health careMedical equipmentComputer scienceEngineeringRisk analysis (engineering)Systems engineeringArchitectural engineeringBusinessMedicine

Abstract

fetched live from OpenAlex

As the population of the United States both grows and ages, the demand for healthcare facilities has grown steadily. Within the healthcare industry, new construction has been trending towards outpatient facilities, like medical office buildings (MOBs) and skilled nursing facilities (SNFs). In this paper, the special structural engineering considerations common to MOB design are discussed. With healthcare buildings, flexibility of future use is an important consideration. MOBs, in particular, are often delivered in two phases. The first phase delivers a core and shell package, and the second addresses tenant improvements (finishes). Strategies for success with this delivery method will be discussed. Additionally, code minimum design loads are often insufficient for heavy imaging equipment. X-rays, CTs, and MRIs can have special requirements for vibration response, structure levelness, and magnetic interference. Final designs require an understanding of the manufacturer’s equipment specifications and specific building criteria. However, those specifications are not always available to the design team during the core and shell design. For that reason, this paper provides appropriate design assumptions and highlights best engineering practices for successful MOB design.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.490
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0650.001

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.

Opus teacher head0.018
GPT teacher head0.303
Teacher spread0.285 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it