HEALTHCARE CLOUD MIGRATION
Healthcare Cloud Migration, Las Vegas NV

Migrating clinical workloads to the cloud without breaking the controls: sequencing, cutover, evidence continuity, and what must never move in a single step.
What must not move first
Identity, audit and key management move before the workloads, or every subsequent migration inherits an unprovable control.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Cutover sequencing
Migrate in dependency order and keep the old path live until the new one has produced an outcome, not merely a successful health check.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Evidence continuity
Audit trails that stop at the migration date are a finding; plan for continuity before the first byte moves.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Data gravity and residues
Old environments retain copies; the migration is not complete until the source is decommissioned and provably empty.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Performance under clinical load
Clinical traffic is bursty and unforgiving; capacity tested at average load is capacity untested.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Rollback that works
A rollback plan never exercised is a hope with a document attached.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Vendor and BAA alignment
The cloud agreement, the vendor agreements and the internal analysis must describe the same architecture.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Operational handover
Whoever runs it after the migration needs the runbook, the owners and the trace, not a slide deck.
In practice this is where most programmes lose time: the decision is either never made explicitly or made once and never revisited. Naming the owner, the artefact and the review date converts it from an opinion into a control that can be tested.
Test it deliberately before it matters. A control that has never been exercised under adversarial conditions is a hypothesis, and in a regulated estate the difference between the two is discovered at the worst possible moment.
Identity, audit and keys move first
Migrating a workload before its identity provider, audit trail and key management produces a service that works and cannot prove anything about itself. Every subsequent migration then inherits a control that has never been evidenced.
Move in dependency order: directory and federation, then logging and retention, then key custody, then the data stores, then the applications. Each step produces evidence you can hold, and each step is reversible on its own.
Keep the old path live until the new one has produced an outcome rather than a health check. A green endpoint is a claim about a socket, not about a clinician receiving a record.
Residues, copies and the decommission that never happened
Old environments retain copies. The migration is not complete until the source is decommissioned and provably empty, and the proof is a list of what was deleted with dates rather than an assurance that it was.
Test at clinical load, not average load. Clinical traffic is bursty and unforgiving, and capacity measured at the mean is capacity measured in the wrong conditions.
Rehearse the rollback. A rollback plan never exercised is a hope with a document attached, and the moment you need it is the moment you cannot test it.
Parallel running is the cheapest insurance
Run old and new in parallel for a defined window, comparing outcomes rather than checking that both respond. Two systems that both return 200 can disagree about the patient's medication list, and the disagreement is the finding.
Define the exit criteria before the window opens: how many consecutive matching days, which exception categories are tolerated, and who declares that the old path can be retired. Without written criteria the parallel period either never ends or ends on a date nobody chose.
Decommission deliberately. The residue of an old environment is usually the largest unclassified copy of the data in the estate, and it survives because nobody wrote down that it had to go.
What the migration plan has to say about people
Who runs the old system while the new one ramps, who is authorised to declare a cutover complete, and who can call a rollback. Three names, written down before the first move, because the technical work is usually faster than the decision to proceed.
Training is part of the migration. A system that works and a team that does not know where the runbook lives is a migration with an outage scheduled for the first busy week.
And retire the old access paths in the same change. Credentials that still work to the old environment are credentials to a copy of the data that nobody monitors.
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. Las Vegas, Nevada 89101.
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 healthcare cloud migration, las vegas nv — 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
Available for architecture review, conformance work and fractional leadership. Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more.
Talk to Charles
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
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.