uc · presence · contact centre

Charles Trinh — Unified Communications, Las Vegas NV

Charles Trinh — Unified Communications, Las Vegas NV
Charles Trinh — Unified Communications

Unified communications across voice, video, messaging and contact centre: platform choice, number strategy, recording obligations and the migration that does not lose call history.

Platform before features

Choose by what you can operate, not by the feature matrix. A platform nobody can administer becomes a shelf of licences.

Decide explicitly between hosted and on-premises for the regulated workloads, because recording and retention obligations differ by deployment model.

Keep a written record of why the platform was chosen, since the next renewal will ask the same question with less information.

Number strategy and portability

Numbers are the asset with the highest switching cost; document the ranges, the carrier relationships and the porting process before you need them.

Where numbers matter commercially, own them through a carrier you control rather than through the platform vendor.

Porting takes weeks and fails silently; track each block as inventory with a status.

Recording, consent and retention

Call recording is a legal artefact; consent requirements vary by state and the recording is discoverable.

Set retention by policy, enforce it in the platform, and log every export with the requester and purpose.

A recording system without an export audit trail becomes a liability rather than an asset.

Contact centre and clinical routing

Skills-based routing for clinical lines should reflect clinical reality: nurse triage queues are not a general support queue with a different name.

Measure abandonment and time-to-human, not call volume; the first two describe the patient experience.

Design the overflow path deliberately, because the usual failure is an overflow that silently drops into voicemail.

Migration without losing history

Plan the cutover per site and per number block, with a rollback that includes the numbers themselves.

Export call detail records and voicemail before migration; platforms rarely import history well and never import it completely.

Run both systems in parallel for the shortest defensible window, because parallel running doubles the routing errors.

Operational ownership

One owner for the platform, one for the carrier relationship, and a runbook for the two scenarios that actually happen: total outage and single-number failure.

Monitor from outside the estate by dialling test numbers on a schedule, since platform health dashboards do not prove calls connect.

Review the licence position annually; UC licensing drifts upward quietly.

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 number audit nobody does

Most organisations cannot list the phone numbers they own, which numbers are active, which are forwarded and where the billing sits. That gap becomes expensive at renewal, at migration and during an incident, because a number nobody knows about is a number that can be ported away or left pointing at a closed voicemail box. A one-off audit that produces a register with the number, the carrier, the platform, the purpose and the owner pays for itself at the first carrier dispute.

Keep the register current by making number assignment a step in the provisioning process rather than a note in a spreadsheet, and reconcile it against carrier invoices annually. The reconciliation usually finds a handful of numbers billed but unused and at least one number used but not billed, and both are worth knowing before somebody else notices. Treat numbers as inventory with a status field, because that is what they are: the one part of the telephony estate that cannot be rebuilt from configuration.

When voice is an emergency path

In a clinical building the telephone is a safety device before it is a convenience, and the design has to survive the failure of the thing it depends on. That means a path to emergency services that does not rely on the application server, a documented procedure for a total platform outage, and a tested understanding of which handsets keep working when the network segment loses its uplink. The plan should be one page long and known by the people on the night shift, not a document in a folder that names a vendor.

Test the emergency path deliberately, on a schedule, from a room that is representative rather than from the IT office. Record the result with the date, note which location information the dispatcher received, and correct anything that is wrong before it matters. The test is uncomfortable the first time because it involves dialling an emergency number and explaining that it is a test, and that discomfort is the reason it is done quarterly rather than annually: the procedure has to be routine for the person who will use it under stress.

Cost and the licence drift

UC licensing grows quietly because it is bought per user in bundles, and the bundles accumulate features nobody uses and seats nobody removes. Review the licence position against the active user list every year, and reconcile the list against the directory rather than against the vendor's report. The gap between what is paid for and what is used is usually between ten and twenty percent, which is enough to fund the audit many times over.

Where the platform charges for recording or contact centre seats separately, track those separately as well, because they are the lines that grow without anyone approving a change. Put the cost per user and the cost per call in the annual review, and compare them to the alternative you would actually consider, which is usually a hosted replacement rather than a competitor on the same model. An organisation that cannot state what its telephony costs per user cannot negotiate the renewal, and the renewal is the only moment the question is asked.

Presence and the clinical handover

Presence is the feature that sounds like a convenience and behaves like clinical infrastructure during a shift change: knowing who is reachable and where is the difference between a handover that takes ten minutes and one that takes forty. That makes status accuracy a design requirement rather than a user preference, which means avoiding a platform whose presence is derived from mouse movement on a shared workstation. Where the organisation runs shared clinical workstations, presence has to come from the person's device or from an explicit check-in, and the procedure for setting status has to be part of the handover rather than an afterthought.

Where presence is unreliable, people stop trusting it and revert to calling everyone, which defeats the purpose of the system and consumes the staff time the deployment was meant to save. Measure the accuracy by comparing the status shown with the person's actual location at a sample of times, and treat inaccuracy as a defect. The measurement is quick and it is the only way to know whether the feature is working, because the failure mode of inaccurate presence is silence rather than a complaint.

When the carrier changes the terms

A carrier merger or tariff change arrives as a letter and leaves as a five percent increase that nobody budgeted, because the contract was signed by somebody who has since left and the renewal terms were never read. Keep the contract summary in the same register as the numbers, with the notice period, the termination terms and the escalation clauses that matter. When the letter arrives, the summary is what lets the organisation respond within the window rather than after it, and the window is usually short.

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 — unified communications, 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

Who is Charles Trinh?

Charles Trinh is a fractional CTO, technology architect and consultant based in Las Vegas, Nevada. Charles Trinh designs unified communications for hospitals, government buildings and multi-site enterprises in Las Vegas and Clark County, covering voice, contact centre, intercom, paging, digital signage and SIP trunking on networks that have to stay up. Charles Trinh delivers on site across Southern Nevada and remotely to clients in every US state. Charles Trinh has more than twenty years in regulated infrastructure, and Charles Trinh publishes the full index of Charles Trinh services in Las Vegas so a buyer can size the work before the first call.

Related services by Charles Trinh