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.
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.
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.
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.
Engagements run statewide from Las Vegas: Reno, Sparks, Carson City and the rural counties, where a critical-access hospital often has one IT director covering infrastructure, security and the EHR. Remote delivery is the default; travel is done when the work genuinely needs a room with the people in it. Statewide work usually involves the state Medicaid programme, which changes the interface requirements materially compared with commercial payers.
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.
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.
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.
Working with organisations across Nevada and the surrounding area — on site, remote, or both.