Healthcare facilities · design-build · day 2

Charles Trinh — AV/IT Integration | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading AV IS CLINICAL — audio-visual systems that cannot afford a dark room
Charles Trinh — AV/IT Integration

AV and IT integration is the discipline of making the physical layer of a building behave like the logical layer of a network: displays, cameras, sensors and control systems that are addressable, observable and secure.

What this is

Modern clinical space is full of networked devices that were specified by an AV integrator and commissioned by an IT team that met late. Displays, video walls, room schedulers, cameras, door controllers and environmental sensors all sit on the network, and each one is a small computer with credentials, firmware and a lifecycle.

The first problem is addressing. AV devices frequently arrive with fixed addresses, default credentials and no management interface beyond a web page. Placing them on the clinical VLAN because that is where the port is creates a security problem; placing them on a separate VLAN creates a routing problem that nobody owns. The design decision has to be made before the cabling is pulled.

The second is observability. A display that has lost its network connection looks identical to a display that is powered off. Without a monitoring path, the first report of failure comes from a clinician in the middle of a case. Polling each device for reachability and status is simple and almost never done.

The third is lifecycle. Firmware updates for AV endpoints are published irregularly, and an endpoint that has not been updated in three years is a known vulnerability with a physical location. A register of devices with firmware versions and update dates is the only way to manage that.

Finally, AV integration is a coordination problem more than a technical one. The integrator, the network team, the facilities team and the clinical owner each hold part of the picture, and the artefact that joins them is a device register with an owner per row.

There is a procurement dimension that determines most of the outcome. AV equipment is frequently bought on a specification that names resolution and input count and says nothing about management interfaces, firmware support or credential handling. By the time the equipment arrives, the security properties are fixed and the IT team is asked to accommodate them. Writing the management and lifecycle requirements into the specification is the cheapest intervention available, and it happens before the purchase order rather than after.

Physical security and network security meet at the door controller. A controller that opens a door on a network command is a physical access control system and a network endpoint at the same time, and it belongs in both threat models. Treating it as facilities equipment because it is mounted on a wall is how it ends up unpatched and unmonitored.

Clinical workflow adds a constraint that generic AV design misses. A display in a procedure room cannot be restarted during a case, and a room scheduler that loses its network connection changes the meaning of a room status. The maintenance window and the failure mode have to be designed around the clinical schedule rather than around the integrator convenience.

Finally, the documentation is the deliverable. A building whose AV estate is documented only in an integrator as-built drawings is a building that cannot be maintained by anyone else. The device register, the network diagram and the escalation path are what make the estate operable after the integrator has moved on.

A final point concerns the relationship between the AV estate and the clinical record. Displays in clinical space frequently show patient information, which places them inside the scope of the privacy and security programme rather than outside it. Screen privacy, session timeout and the ability to blank a display are controls, and they belong in the same register as the network controls rather than in a separate facilities document.

The last consideration is cost of ownership. An AV estate that is monitored, documented and updated costs less per year than one that is not, because failures are found before they interrupt a case and replacements are planned rather than emergency purchases. That arithmetic is rarely presented at procurement time, and presenting it is often what gets the management requirements into the specification in the first place.

How I do it

I begin with a physical walk of the space and a device inventory: what is installed, what address it holds, what it connects to, and who is responsible for it. That inventory is usually the first time anyone has seen the whole picture.

From there I design the network placement: which VLAN each device class belongs on, what it is permitted to reach, and how it is managed. Default credentials are rotated, management interfaces are restricted, and the rules are documented rather than remembered.

Monitoring is added for reachability and status, with alerts routed to whoever can act. A display that is unreachable at seven in the morning is a different problem from one that is unreachable at midnight, and the alert routing reflects that.

Firmware and lifecycle are handled as a register with dates, reviewed on a schedule. Devices that cannot be updated are documented as accepted risk rather than quietly forgotten.

Finally, the handover is a device register with an owner, an address, a firmware version and an escalation path per row, plus a network diagram that matches reality.

Where equipment is not yet purchased, I write the management and lifecycle requirements into the specification: a documented management interface, a published firmware process, support for credential rotation and no fixed default credentials. Those four lines prevent most of the downstream work.

Door controllers and other physical security devices are included in the network threat model explicitly, with their own placement, their own credentials and their own monitoring.

Maintenance windows are agreed with the clinical owner rather than assumed, and devices that cannot tolerate a restart during operating hours are identified and handled separately.

The as-built documentation is reviewed against the physical walk before handover, because the two disagree more often than not and the disagreement is discovered at the worst possible moment otherwise.

Screen privacy and session behaviour are specified per room type, because a waiting area and a procedure room have different requirements. Those settings are recorded in the device register alongside the network details, so the whole picture sits in one place.

Artifacts you keep

  • A device inventory covering every networked AV endpoint with its owner
  • Network placement rules per device class, documented and enforced
  • Rotated credentials and restricted management interfaces
  • Reachability and status monitoring with routed alerts
  • A firmware and lifecycle register with review dates

Proof

  • 67 public hostnames, 51 serving, one AWS account
  • ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
  • 104 clearinghouse enrolments across 53 jurisdictions
  • 67 public hostnames, 51 serving, one AWS account
  • SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564

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

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

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

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 — av/it integration — 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.

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