power · cooling · cabling

Charles Trinh — Server Room and Rack Design, Las Vegas NV

Charles Trinh — Server Room and Rack Design, Las Vegas NV
Charles Trinh — Server Room and Rack Design

Server rooms and racks that survive a fault: power redundancy that is real, cooling that matches the load, structured cabling, and physical security that is actually enforced.

Power: redundancy versus reality

A UPS protects against the short event and the generator against the long one; without a generator, a UPS buys you time to shut down, not uptime.

Two feeds on the same panel is not redundancy; verify upstream diversity including the utility feed.

Monitor UPS battery age and test transfer under load; an untested UPS is a battery with a display.

Cooling and airflow

Cooling capacity must cover the actual heat load with margin, and airflow must match the rack layout rather than the room's history.

Avoid mixing hot and cold aisles in a small room; blanking panels and correct orientation buy more than a bigger unit.

Monitor temperature at the top of the hottest rack, not at the wall thermostat.

Structured cabling

Standardise on one cabling scheme, label both ends, and keep a port map that matches reality.

Cable management is not cosmetic; it is the difference between a twenty-minute change and a two-hour outage.

Test and certify new runs, and record the results.

Physical security

Card access with logging, no shared keys, and environmental sensors on the room rather than on the corridor.

Camera coverage of the door and the racks, retained long enough to be useful.

Control who has access by named individual, and review quarterly.

Fire suppression and water

Understand what the suppression system does to equipment and to people; agent systems require egress planning.

Keep water detection where there is any risk of overhead leaks, because the most common server-room flood is a bathroom above it.

Rehearse the shutdown procedure with the people who would have to perform it.

Documentation and change

One drawing, one rack elevation, one power schedule and one cabling schedule, each with a review date.

Any change updates the drawing in the same ticket, or the drawing is fictional within a month.

Photograph the rack after every change; it is the fastest way to reconstruct what happened.

How I do it

One trace of a real case with timestamps at every hop, before any document is written.

A findings list naming the defect, the system, the owner and the date, reviewed monthly.

No attestation I did not test, and no template sold as an assessment.

What the room is actually for

A server room in a clinic is often the room that was available, and the design follows from a legacy of decisions nobody recorded. Before specifying anything, establish the heat load, the growth expectation, the network entry points and the physical access requirement, because those four determine whether the room can be made to work or needs to be replaced. A room that cannot be cooled at the current load will not be fixed by a bigger unit if the airflow path and the door louvres are wrong, and the cost of discovering that after a rack is full is a second room.

Where the room is marginal, decide explicitly what stays and what moves. The usual sensible split keeps the network core and the clinical systems local, and moves anything that can tolerate a cloud dependency out of the room entirely. That decision reduces the heat load, the UPS requirement and the physical security scope in one step, and it is almost always cheaper than upgrading the room to carry a load it was never designed for.

The physical security that is actually enforced

A locked door with a key held by six people is not access control; a card reader with a shared PIN is barely better. Named individuals, logged entry, a quarterly review of who holds access, and no shared credentials are the minimum. The room should also be covered by environmental detection that reports to somebody, because a temperature alarm that nobody receives is a sensor rather than a control, and the difference is discovered when the room is found at forty degrees on a Monday.

Where the room is in a shared building, the building management has its own keys, and the design has to assume they will enter without notice. Put the racks themselves behind a second lock with different access, keep the sensitive equipment in the middle of the room rather than against the wall, and record the building's access separately. This is not distrust of the landlord so much as acknowledgement that two access regimes exist and the equipment should survive both.

Documentation, photographs and the next person

The most valuable document in a server room is a photograph of the back of the rack taken after the last change, with a note of the date and what changed. Cabling schedules and rack elevations are useful and they are always slightly out of date; a photograph is what somebody reaches for at two in the morning when a cable has been pulled and nobody knows where it went. Keep them in the same place as the rack elevation, and take a new one every time the rack changes, even for a small change.

Keep the power schedule with the rack elevation, because the mapping from circuit to rack to device is the thing that must be right during a power event. Label both ends of every cable and both ends of every power lead, and test the labelling on a spare device once a year by removing a cable and confirming the other end matches. The exercise takes an hour and it is the only way to know whether the documentation is current or merely confident, which is the distinction that matters when the room is under pressure.

Small rooms, real constraints

A clinic's server room is often a converted cupboard with a door that opens inward, a single air-conditioning unit and no room for a second rack. Designing within constraints like that is a different discipline from designing a data centre, and the honest options are usually three: reduce the load by moving workloads out, improve the room within its limits, or build a new room. Presenting those three with their costs is more useful than specifying equipment that will not fit the airflow, and the decision belongs to the people who own the clinical service rather than to the IT team alone.

Where the decision is to stay, the cheapest improvements are almost always the physical ones: seal the ceiling void, add blanking panels, move the rack away from the door and the wall, and put a temperature sensor at the top of the rack rather than on the wall. Those changes cost little and they often recover several degrees of headroom. Record the before and after measurements, because the improvement is the argument for the next set of changes, and the measurements are also what tells you when the room has reached its limit rather than merely feeling warm.

The decommissioning backlog

Server rooms accumulate equipment that is powered off but still racked, because nobody wants to be the person who removes a machine that might still matter. A quarterly decommissioning exercise, with a written list of what will be removed and a date, keeps the rack, the power and the documentation aligned with reality. The electrical savings are modest; the value is the physical space, the removed ambiguity about what is running and the reduced surface for anyone who gains access to the room.

Proof

  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 67 public hostnames, 51 serving, one AWS account
  • 104 clearinghouse enrolments across 53 jurisdictions
  • USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
  • AWS Business Associate Addendum active since 18 August 2026

Where this work is delivered

Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.

How an engagement runs

1. Trace one real case

Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.

2. Written findings

A findings list naming the defect, the system, the owner and the date.

3. Monthly review

Review the list monthly and check whether the dates held.

Frequently asked

What is this service?

This page describes charles trinh — server room and rack design, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AV and IT Infrastructure category at trinh.io.

Where is the work delivered?

Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.

What does it cost?

Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.

Who is Charles Trinh?

A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.

How does an engagement start?

With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.

Engagement

Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io

Talk to Charles

Record

Profile

Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.

Selected engineering scale

  • Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
  • FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
  • Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
  • X12 005010 pipelines across eight transaction sets.
  • Designed, built, deployed and operated end to end by one person.

Credentials and standards work

  • Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
  • USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.

Technical environment

AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh