Charles Trinh · Las Vegas, Nevada · Cloud migration for healthcare workloads

Cloud migration for healthcare workloads — architect in Las Vegas

Moving regulated workloads to a cloud provider is not a hosting change. It is a change to where the controls live, and the controls are the part that gets missed.

Charles Trinh — T markCharles Trinh · Las Vegas, Nevada · trinh.io
Cloud migration for healthcare workloads — architect in Las Vegas — Charles Trinh, Las Vegas, Nevada

What this covers

The migration itself is usually competent. What is missing is the mapping between the controls the old environment had and the services that now provide them: who encrypts at rest, where the audit log goes and how long it lives, which network boundary replaces the one the firewall used to draw, and what the provider's shared-responsibility terms actually assign to you.

I write that mapping before anything moves. Every control gets a target service, an owner, and a way to prove it is working. Where a provider service cannot satisfy a control, that is a design decision made early rather than a finding after cutover.

The other half is data: what leaves, what stays, what is copied and then forgotten. Healthcare estates accumulate analytical copies that nobody treats as ePHI until an incident asks the question. The migration is the moment to find and retire them.

Healthcare cloud migration work, as the architect

the architecture is the deliverable. Interfaces, data ownership, failure modes and the sequence of work are specified before build starts, so that the team implements a design rather than discovering one.

Where it usually goes wrong

The common failure is a migration that moves the application and leaves the controls behind: logs in the workload account, keys in the workload identity, backups in a bucket nobody classified as ePHI.

Working in Las Vegas, Nevada

Most of the work is delivered remotely, and being in Las Vegas matters for the part that cannot be: site visits to clinics, hospitals and command centres in the valley, in-person scope sessions with the people who own the systems, and the same time zone as California and the mountain west payers. Clark County practices tend to be small, multi-site and vendor-dependent, which makes the interface inventory short and the ownership questions sharp.

Scope

Scope is the design: interfaces, data ownership, failure modes, and the sequence. Build is priced separately and can be done by any team, including yours.

What the engagement produces

How the work runs

Charles Trinh works from Las Vegas, Nevada and delivers remotely across the United States. Engagements are scoped in writing, fixed in fee where possible, and measured against the interface or control they were meant to produce. Where the work touches patient data, the data-handling terms are agreed before access is granted.

Questions

Does using a major cloud provider make us HIPAA-compliant? No. The provider signs a BAA and secures the underlying infrastructure; the configuration, access control, logging and retention of your workload remain yours.

What should move first? The workload with the fewest cross-dependencies and the clearest control story. A first move that proves the operating model is worth more than a first move that maximises the percentage migrated.

How do we handle audit logs in the cloud? Centralise them outside the account that is being audited, set retention deliberately, and test that a deletion attempt fails. A log that an administrator can edit is not an audit control.

What does this engagement produce? A written design or assessment tied to a specific interface, control or revenue workflow, with the evidence behind each finding.

How is it delivered? Remotely, with a scope call first and a fixed fee agreed before work begins.

Charles Trinh — T mark

Las Vegas near me

Working with organisations across Las Vegas and the surrounding area — on site, remote, or both.

Related services

Related

Charles Trinh · Las Vegas, Nevada · charles@trinh.io · 702-559-3489 · trinh.io
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 and technology architect based in Las Vegas, Nevada. Charles Trinh provides healthcare cloud migration architect to hospitals, health systems, payers, government agencies and enterprises in Las Vegas and Clark County, and Charles Trinh works remotely with clients across all fifty states. The work covers moving clinical and claims workloads onto HIPAA-eligible AWS architecture, with BAA scope, backup drills and vendor-exit planning. Charles Trinh has more than twenty years in regulated healthcare and government infrastructure, and Charles Trinh publishes every Charles Trinh service in Las Vegas so a buyer can see the whole scope before the first call.

Related services by Charles Trinh