CONTAINERISATION HEALTHCARE
Containerisation and CI Release Gates, Las Vegas NV

Release gates that catch the defects which reach patients: image provenance, validation in the pipeline, and the evidence each gate leaves behind.
Gates that matter
A gate that can be bypassed under pressure will be; make bypass require a recorded decision.
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.
Image provenance
Know what is in the image and where it came from; an unpinned base image is an unreviewed dependency.
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.
Validation in the pipeline
FHIR validation, schema checks and conformance run per commit rather than per quarter.
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.
Secrets and configuration
Secrets belong in a managed store with rotation, not in an environment file copied between hosts.
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.
Test data
Production data in a test environment is a breach waiting for a classification; synthetic data is the only durable answer.
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.
Deployment evidence
Who deployed what, when, and what changed; the record is the release note an auditor reads.
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 as a gate
A release that cannot be rolled back should require a different approval than one that can.
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.
Pipeline observability
A pipeline nobody monitors fails silently on a Friday and is discovered on Monday.
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.
A gate is only a gate when bypass costs something
Every pipeline has a bypass. The question is whether the bypass is a command anyone can run under pressure, or a decision that has to be recorded with a reason and a name. The first is theatre; the second is a control.
The gates that catch defects which reach patients are few: conformance validation on every commit, schema validation against real fixtures, a dependency and image provenance check, and a rollback that has been executed at least once in staging.
Everything else is useful and none of it is a gate. Organisations confuse a dashboard of advisories with a gate, and then discover that the one thing which needed to block a release was advisory.
Provenance and the unpinned base image
Know what is in the image and where it came from. An unpinned base image is an unreviewed dependency that changes without a commit, and a build that pulls latest is a release nobody described.
Pin digests, scan on build rather than on a schedule, and record the scan result with the deployment. When an incident asks which hosts run the affected package, the answer should be a query rather than an investigation.
Secrets belong in a managed store with rotation and an owner. A secret in an environment file copied between hosts is a secret that will be found in a backup before it is found in an audit.
Test data is a gate too
Production data in a test environment is a breach waiting for its classification. Synthetic data is the only durable answer, and the fixtures should cover the difficult cases: a patient with a hyphenated name, one with no address, one with a revoked consent.
A gate that checks the deployment but not the data it runs against is checking half the release. Conformance failures caused by data are as blocking as failures caused by code, and they are more likely to reach a clinician because no test asserted them.
Record the release: who deployed, what changed, which gates passed and which were bypassed with a reason. That record is what an auditor reads, and it is the difference between a release and an event.
The rollback is the gate everyone skips
A release that cannot be rolled back should need a different approval than one that can, and most pipelines do not distinguish them. Make rollback a required step in the release record, exercised in staging at least once per quarter.
Version the artefact, not the branch. A deployment identified by a tag that changed underneath is a deployment nobody can reproduce, and reproducing it is the first thing an incident asks for.
Monitor the pipeline itself: queue time, failure rate by stage, and the age of the oldest blocked build. A pipeline nobody watches fails silently on a Friday and is discovered on Monday.
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 containerisation and ci release gates, 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.