wi-fi · clinical roaming · site survey

Charles Trinh — Wireless Network Design, Las Vegas NV

Charles Trinh — Wireless Network Design, Las Vegas NV
Charles Trinh — Wireless Network Design

Wireless for clinical environments: survey-driven coverage, roaming that survives a moving patient monitor, device onboarding at scale, and the security posture clinical Wi-Fi actually needs.

Survey before you buy

Predictive surveys are a starting point; a post-install validation survey with the real devices is the only proof coverage exists where care happens.

Survey with the carts, monitors and scanners that will actually roam, because antenna orientation and body shielding change everything.

Measure at the point of use: patient rooms, corridors, lifts and the supply corridor where nobody thought to check.

Roaming and clinical devices

A monitor that drops association mid-transfer is a clinical event, not a user annoyance; 802.11r and band steering matter more than raw throughput.

Tune power levels so devices make deliberate roaming decisions rather than clinging to a distant access point.

Test roaming with a real device walking a real route, and record where associations fail.

Device onboarding at scale

Clinical devices often support limited authentication options; plan a dedicated SSID with certificate or MAC-based access, and an inventory that matches.

Avoid shared PSKs for anything that matters, because a shared key is a shared identity and revocation becomes a project.

Automate onboarding where the vendor allows, and document the manual path for the ones that do not.

Security posture

Separate clinical, corporate, guest and building-management wireless; apply client isolation on guest and enforce egress rules on clinical.

Detect rogue access points and unauthorised SSIDs, because the shadow network installed by a vendor is a common finding.

Log associations and authentication failures, and review failures weekly, since they are the earliest sign of a device problem.

Capacity and interference

Capacity planning is about client count per radio, not headline throughput. A ward with sixty devices and five access points is a design problem.

Check for interference from building systems and from neighbouring networks during the survey, not during the incident.

Re-survey after any building change, because a new wall or a new imaging suite invalidates the original plan.

Operations

Name access points by physical location, keep a map, and record each device's home location so a fault can be localised.

Monitor from the device's perspective where possible; controller health does not prove a monitor can associate.

Review firmware and end-of-support dates quarterly.

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.

The devices decide the design

Wireless planning for an office is about throughput; for a hospital it is about latency, roaming and the behaviour of devices that were not designed for a shared network. Start from the device inventory: monitors, pumps, scanners, carts, phones and badges, each with its own radio behaviour and its own firmware constraints. The inventory determines the SSIDs, the security model and the access point density, and it is the document that every later design decision references when someone asks why a particular ward has two more access points than its area suggests.

Test with the devices, in the places they are used, moving the way they move. A survey with a laptop walking the corridor proves coverage for a laptop walking the corridor; it says nothing about a monitor being wheeled through two doors and a lift lobby. The validation step is where the gaps appear, and the gaps are almost always in the transitional spaces: stairwells, lifts, utility corridors and the thresholds between departments where several access points disagree about which is nearest.

Guest access is a clinical risk

Guest wireless is a service to patients and visitors and it is also an attack surface, and the two facts together determine its design. Isolate guests from every internal segment, cap bandwidth so a queue of streaming video cannot degrade clinical traffic, and make the onboarding simple enough that staff are not asked to help with it. The failure mode is a guest network that technically exists but is so awkward to join that a department sets up its own access point, which is exactly the shadow infrastructure the policy was written to prevent.

Monitor for unauthorised access points and for SSIDs that look like yours, because both appear regularly in clinical buildings. A vendor installing a device with a default SSID, or a team solving a coverage gap with a consumer router, produces an unmanaged entry point that no inventory contains. Detection is straightforward with the controller and a periodic survey, and the response should be a conversation with the department rather than a disciplinary process, because the underlying cause is usually a gap the official network left open.

Capacity is people, not bandwidth

The capacity question in a clinical area is how many clients associate to each radio and how much of that is latency-sensitive, not what the headline throughput is. A ward with sixty devices spread over five access points and a single high-density access point in the day room are different designs with different failure modes. Plan for the busy hour and for the device mix, and revisit the plan when a new device class is introduced, because the arrival of one new monitor fleet changes the client count per radio more than any change in user behaviour.

Watch the association counts and the retry rates rather than the throughput graphs, because high throughput with high retries is a satisfied-looking dashboard over an unhappy radio. Both numbers should be visible per access point and per band, and the alert should be on the retry trend rather than on a threshold, since the trend tells you about interference before the floor experiences it. The organisation that watches retries fixes coverage problems before the clinicians report them, and the one that watches bandwidth fixes them afterwards.

Interference from the building itself

Hospitals are electrically hostile, and the interference that matters is often not the neighbouring office network but the building itself: imaging suites, electrosurgical equipment, microwave ovens in staff rooms and the lifts whose shafts behave as shielded columns. A survey that does not run during clinical activity misses the interference that only exists when the equipment is in use, so the validation should include a period when the imaging suite is operating. Where interference is unavoidable, the design answer is more access points at lower power and a band plan that avoids the affected channels rather than a louder signal across the floor.

Track retries and channel utilisation per access point over time, because interference shows up as an increase in both long before users report a problem. A sudden change in one area usually correlates with a new piece of equipment or a construction change, and the correlation is much easier to establish from a chart than from a complaint. Feeding that chart into the quarterly review turns wireless from something that is fixed when broken into something that is watched, which is the only state in which a clinical wireless estate stays usable over several years of change.

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 — wireless network 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