av design · rooms · integration

Charles Trinh — Enterprise AV Design, Las Vegas NV

Charles Trinh — Enterprise AV Design, Las Vegas NV
Charles Trinh — Enterprise AV Design

Audio-visual design for clinical and corporate spaces: room standards, signal routing, control systems and the documentation that keeps twenty rooms from becoming twenty bespoke installations.

Standardise the room, not the equipment

A handful of room archetypes with fixed kit lists is worth more than perfect rooms chosen individually, because maintenance and training both scale with variety.

Name each archetype by capacity and function: huddle, consult, conference, training, auditorium. Every new space maps to one or a new archetype is justified in writing.

The cost of bespoke rooms is paid later, at every failure, by whoever has to identify a part nobody stocked.

Signal routing and the network

Modern AV is IP: Dante for audio, NDI or SDI for video, and camera control over the same switches that carry clinical traffic.

Put AV on its own VLAN with QoS and bandwidth reservations, because a broadcast storm from a misconfigured matrix should not reach a clinical application.

Document the multicast boundaries; uncontrolled mDNS and multicast are the usual cause of mysterious network instability after an AV install.

Control systems and failure modes

A control panel that fails should leave the room usable, not dark. Design the fallback to be manual and obvious.

Avoid control processors that become single points of failure without a documented bypass. Label the bypass and teach it to the people who use the room daily.

Test power-cycle recovery: a room that needs an engineer after every outage is a room that will be abandoned.

Clinical-specific requirements

Consult rooms and telemedicine spaces have constraints consumer AV ignores: privacy, infection control, sight lines, and audio that must work for a patient with hearing loss.

Specify echo cancellation and beamforming for the clinician side, and test with a real hearing-aid wearer rather than a specification sheet.

Consider acoustic separation before buying a better microphone; no DSP fixes a room where the next patient can hear the consultation.

Documentation and handover

As-built drawings, IP schedules, credential escrow and a plain-language user guide per archetype.

The single most useful artefact is an IP and credentials register, because every future fault starts with finding the device.

Handover without training is a room that gets used as a meeting room with a broken TV.

Lifecycle and cost

AV has a shorter useful life than the building it sits in; plan a refresh cycle and hold spares for the parts that fail.

Keep one spare of each critical component rather than a full spare room; the goal is same-week repair, not redundancy.

Track firmware and end-of-support dates for codecs and DSPs, because vendor discontinuation is the usual reason a working room must be replaced.

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.

Procurement that does not fight the standard

The fastest way to lose a room standard is to let each project buy its own equipment, because the specification is written by whoever has the integrator's ear that quarter. Write the standard as a procurement document with named models, an approved-equal clause and a clear statement of what may vary, then hold it at the purchase order rather than at the design review. Most standardisation programmes fail not because the design was wrong but because procurement was allowed to substitute one component at a time until the rooms no longer matched and nobody could say when it happened.

Review substitutions against the standard rather than in isolation, since a lower-cost display with a different control protocol can require a different processor, and the saving on the display is paid for twice in the control system. Keep the standard short enough that it fits on two pages, because a forty-page standard is read once and then ignored. The document that actually governs is the one an integrator can carry to a site and check against, and that is a list of models, mounts, cable types and cable lengths, not a design philosophy.

Support and the cost of the first failure

The cost of an AV estate is not the install; it is the average time to restore a room, multiplied by the number of times rooms fail. That number is driven almost entirely by how quickly somebody can find the device, identify the fault and swap a component, so the register of IP addresses, credentials and serial numbers is the most valuable document in the programme. Rooms without it are repaired by process of elimination, and the technician who rebuilt the room last year is usually not the one who is called.

Train the people who use the rooms on the three recoveries that solve most faults: reseat the input, power-cycle the processor, and select the fallback source. Those three cover the majority of support tickets and cost an hour of training per archetype. Everything beyond them is an engineer call with a named owner and a response time, and the response time should be written into the support contract because an AV integrator's default is best-effort, which in a clinical corridor means days.

When the room must work during an incident

A training room or a boardroom can be out of service for a week; a consult room or a telemedicine space used for an on-call handover cannot. Classify each room by what happens clinically when it fails, and let that classification drive both the spares held and the support tier. The classification is also the argument for funding redundancy in the few rooms that need it, because a blanket redundancy policy across fifty rooms is unaffordable and a targeted one is not.

For the rooms in the critical class, keep a tested fallback that does not depend on the control system: a direct HDMI path to the display, a phone that can host the conference, a documented manual procedure taped inside the cabinet. Test the fallback quarterly, because an untested fallback is a plan rather than a capability, and the first time anyone discovers it does not work should not be during a clinical call. The test takes ten minutes and it is the cheapest resilience available in an AV estate.

Who to call, and what they are allowed to do

The support model determines the experience of a room more than the equipment does, and the model has to be written down with named roles: the person who resets the room, the technician who swaps a component, and the integrator who handles warranty work. Each has a defined scope and a defined response time, and the boundary between the first two is the one that matters, because a room where every fault escalates to a technician is a room that sits broken for a day over a cable that was never plugged in. Publish the boundary and train the first role to it, then check quarterly whether the tickets actually follow the model or whether everything is escalating upward out of habit.

Warranty and the end of warranty are decisions that should be made before they arrive, because the estate's behaviour at year three is set by choices made at purchase. Record the warranty period per component and per room archetype, and plan the refresh against the point where the call-out charge exceeds the value of the repair. The exercise is unglamorous and it prevents the common outcome where a room is kept alive for years with intermittent faults because nobody has decided to replace it, and the people who use it stop reporting the faults because nothing ever changes.

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 — enterprise av 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