SERVICES · LAS VEGAS NV

Charles Trinh — Estate Operations | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Charles Trinh — Estate Operations, Las Vegas NV
Charles Trinh — Estate Operations

Operating a multi-hostname regulated estate: one owner per component, restore drills, monitoring from outside, and change control that keeps a small team out of incident.

Every component needs an owner

An owner is a person who can be asked, who knows the first diagnostic step, and who has the authority to change it. Components without owners accumulate until an outage is also an archaeology project.

Keep one page per component: purpose, owner, dependencies, runbook and last verified date. Review it quarterly against the running estate.

Drill the restore

Run a restore drill quarterly and record time to recovery. That number is the only one anyone will care about during an incident, and it is always worse than assumed.

Restore into a different environment sometimes, since restoring in place proves the data but not the process.

Monitor the surface from outside

Synthetic checks against the public surface catch what internal dashboards cannot, because internal telemetry shows the process running while the certificate expired an hour ago.

Alert to a human with an owner and a first action, not to a channel nobody reads.

Change control proportionate to blast radius

Automate the reversible changes and require approval beyond them. A process that treats a DNS record and a database migration identically fails at both ends.

Take a configuration backup before every change and keep it retrievable without the network.

The inventory and its owners

The estate is a list before it is anything else: every hostname, service, certificate, backup and scheduled job, each with an owner and a last-verified date. The list is reviewed quarterly against what is actually running, because the difference between the list and the estate is where the unowned component lives. An outage without an owner is also an archaeology project, and the two costs arrive together.

Keep one page per component: purpose, owner, dependencies, runbook, monitoring and the date it was last verified. That page is what a new engineer reads before touching anything, and it is what makes the estate survivable across staff changes.

Monitoring from outside

Internal telemetry reports the estate's opinion of itself. Synthetic checks against the public surface report what a user experiences, and the difference between the two is always the interesting case: an expired certificate, a DNS change, a proxy rule, a WAF update nobody in the team made. Run one synthetic check per critical journey rather than per endpoint, because the journey is what matters.

Alert to a person with a first action, and record who that person is. An alert to a channel is a notification, and a notification to a channel nobody reads is a log line with ambition.

Backup and restore as different things

Backups are files; recovery is a capability. The only evidence distinguishing them is a drill with a written result: what was restored, into what environment, how long it took and whether the service worked afterwards. Drill quarterly and record the number, because that number is the one quoted during an incident.

Immutability matters more than frequency for the most likely attack, and an offline or object-locked copy is what makes a backup a recovery capability. Retention that keeps thirty daily copies and no immutable monthly is doing less than it appears to.

Change control by blast radius

A process that treats a DNS record and a database migration identically fails at both ends: too slow for the first and too casual for the second. Automate reversible changes, require approval for the rest, and take a configuration backup before every change that is retrievable without the network. The test is whether a rollback can be performed by the person who made the change without a meeting.

Record the change with its rollback and its verification. A change record without a verification step is a description of an intention, and the verification is where the incident is usually caught before a user finds it.

Cost and capacity

Review the estate's cost per hostname and per service annually against growth, because a single-account design drifts upward quietly. The review is short and it produces the two questions that matter: which components could be consolidated and which are growing faster than the business. Both are decisions that are cheap when they are early.

The on-call experience

The estate's quality is visible in what happens at two in the morning: whether the person on call can find the runbook, reach the owner and perform the first diagnostic step without a meeting. Test that deliberately by having somebody who did not write the component follow the runbook on a quiet afternoon, and record where they got stuck. The stuck points are the documentation's real content, and fixing them is cheaper than any monitoring upgrade.

Keep the on-call rotation short and named, with a written handoff at each change of shift. A rotation that exists only in a chat channel is a rotation that fails silently when the person is unreachable, and the failure is discovered during the incident rather than before it.

Review incidents for the process as well as the cause. Most incidents describe a detection that was late or a rollback that was improvised, and both are process defects with cheap fixes.

Documentation the estate needs

Four documents cover the estate: the component inventory, the network diagram with a revision date, the backup and restore record, and the change log with its rollbacks. Everything else is depth for a specific incident. An estate with those four can be reasoned about by somebody new; one without them can only be operated by the person who built it.

Review all four quarterly against the running estate, and record the review. The record is what distinguishes a documented estate from a documented intention.

Budget and renewal calendar

Every component has a renewal date, and the estate's availability depends on renewals nobody has on a calendar: certificates, domains, licences, support contracts and phone numbers. Keep one calendar, owned by one person, with a lead time that fits the slowest renewal. The incident that follows a missed domain renewal is entirely preventable and entirely ordinary.

Review the calendar quarterly against the inventory, because components are added without being added to the calendar, and the gap is the one that expires.

Review the renewals calendar against actual invoices each quarter; a renewal that appears in neither is a component nobody owns.

Keep the incident log with the change log, so a change that caused an incident is visible next to the incident it caused.

Review the log annually for patterns rather than for individual events; the pattern is the thing that gets funded.

Name a deputy for every component owner, because single-owner components are single-person dependencies and the person is the one on holiday.

Keep the deputy list with the inventory and review it at the same time, since it ages faster than the hardware.

Record the last time each runbook was actually used, because a runbook unused for two years describes a system that has changed since.

Record the last date each component was verified and treat a blank as a finding, because an unverified component is an assumption wearing a row.

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 — estate operations — the scope, the failure modes it prevents and how the work is measured. It sits in the Cloud and Operations 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