ADVISORY
Charles Trinh — Legacy System Modernisation | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Modernisation is a sequence of small replacements under a running system, not a rewrite. I map the data the legacy system really owns, sequence the extractions so each one is reversible, and keep the old and new systems answering the same questions until evidence says otherwise.
Find out what the legacy system actually owns
Nobody in the organisation can list every responsibility of a twenty-year-old system, and the documentation is a wish. I start by producing a data ownership map: every table, every interface and every scheduled job, with the business process it serves and the person who would notice if it stopped. I run the system's operation logs through a month and look at what is actually used versus what exists. In most cases between 40 and 60 per cent of the surface is reachable from a screen nobody opens; that is the part that can be frozen before anything else moves.
The map is the input to every later decision. Replacement scope, migration order and rollback windows all depend on knowing which process reads a given table and which one writes it. I build it by reading schema, querying the running system for object access counts, and shadowing the database for a week to see the real query mix. When the legacy system is a vendor product, I ask for the vendor's schema documentation and check it against observation, because vendor docs notoriously lag the deployed version.
The map has an owner in the organisation, usually the operations lead who has lived with the system longest, and it is versioned. When a team finds an interface the map did not capture, the map changes and the team gets the credit for the find. That practice turns the map into a shared asset rather than a consultant deliverable that goes stale on the day it is handed over.
Sequence extraction by risk, not by convenience
The extraction order is the decision that most determines whether a modernisation succeeds. The wrong order is the one that follows the system diagram, because the most entangled parts of the legacy code are usually the core and they take the longest to move. The right order is by risk and by contract stability: start with a capability whose boundary is already well understood, extract it, run it in parallel, then move the next. Each extraction reduces the surface the legacy system owns and provides a working template for the next team.
I score each candidate on four axes: how many processes depend on it, how much data migration it needs, whether the team can define the contract without reading the legacy code, and whether a rollback is possible without a data restore. The first extraction is usually authentication, session or a lookup service rather than a patient record. That is not because it is glamorous, it is because it lets the programme prove the pattern, the tooling and the security model before the stakes rise.
Where the organisation has already taken a platform decision, for example moving toward a cloud platform, the extraction order should match the platform's migration waves. Doing those in parallel lets each wave prove one more piece of the platform and one more piece of the legacy extraction at once. Doing them independently doubles the coordination cost and produces two change calendars that never quite agree.
Parallel run is the evidence, not the reassurance
Every cutover I design runs the new system in parallel with a shadow feed from the legacy system until the new system's answers match the legacy system's useful answers for a defined sample. The sample is agreed with the operational owner: a set of real cases, a set of edge cases, the date range and the definition of acceptable difference. If the acceptance threshold is not written down, the parallel run never ends. A seven-day parallel period with a written threshold and a named sign-off is more useful than a three-month one that nobody is accountable for.
Shadow runs must not write to the production database or send real messages to patients or payers. I route shadow traffic to a test tenant and make the routing visible in the logs so there is no doubt which messages were live. For clinical data, the sample is selected under the data governance process, run only inside the compliant environment and destroyed on a schedule. This is where modernisation meets the HIPAA security programme, and the parallel run should be covered in the same risk assessment as the live system.
The comparison itself is usually a script, and I insist it is kept and re-run at each cutover, not rebuilt by a contractor each time. The script's output is part of the go/no-go pack. Where the legacy answers are themselves wrong (and in a twenty-year-old system they are often wrong in a characteristic way), the comparison script records the discrepancy and the reason rather than pretending the new system must reproduce the error. That distinction needs the operations owner in the room.
The legacy system stays until it is switched off
Running most of the estate on a new platform and a few processes on the legacy system is the normal end state of a modernisation, at least for a while. The risk is that the remaining processes are invisible. I keep a written list of every process still on the legacy system with its owner, its extract date and its switch-off criteria. That list is reviewed monthly with the operations director, and any process past its extract date without a switch-off plan is escalated.
Switch-off is a project in its own right: data retention obligations, archive access, interface decommissioning and the contract with the vendor. In healthcare you cannot just delete a legacy store; you have to retain its contents for the statutory period and keep it accessible for audits and litigation. I plan archive access with the records management lead before the switch-off, and prove a restore from the archive. The cost of skipping that step is a records request years later with no way to answer it.
The programme's success metric is not the number of new services. It is the number of legacy responsibilities retired, with the archive proof on file and the vendor contract closed. That metric is the one I report to the sponsor. The estate I build inside MyRxWallet includes a 337-table clinical store, and every replacement we make there is held to the same rule: the old table is not deleted until the new one has passed its parallel run and the archive has been restored once on purpose.
What to do when the modernisation is already late
Most people call me after a modernisation has already slipped. The symptoms are consistent: the first extraction is behind, the team has grown, the cutover has been re-planned twice, and the sponsor is asking for a date that nobody believes. I start with the data ownership map and the parallel-run criteria, because those are the artefacts that tell me whether the programme is actually stuck or just badly reported. Very often it is the second.
If the programme is stuck, it is usually because the first extraction was chosen for its political visibility rather than its contract stability. The fix is to pause, pick a smaller first extraction, and prove the pattern on that. It costs a month and it changes the trajectory. Where the programme is sound but the team is understaffed in a specific discipline, I bring in the precise role and keep it for the minimum time, rather than adding a general body of people to an already large programme.
I do not recommend a big-bang rewrite from scratch. I have not seen one succeed inside an operating healthcare organisation, and the cost of failure falls on patients and payers as well as the company. The programme that works is the one that retires a capability every few weeks and keeps the running system as the safety net until the last one is gone.
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 — legacy system modernisation — the scope, the failure modes it prevents and how the work is measured. It sits in the Security and Compliance 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
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
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.