ADVISORY
Charles Trinh — Compliant MVP Builds for Healthcare Startups | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A healthcare MVP that handles patient data is not a prototype with a database. I build the smallest product that can be used with real patients, prove its compliance posture honestly, and keep the evidence so the first raise is not the first time the company has to explain itself.
The MVP scope excludes features, never controls
The scope decision for a healthcare MVP is what features the product will not have in the first release. It is not what controls it will skip. The first release with real patient data needs encryption in transit and at rest, access control with named accounts, audit logging of every protected health information access, basic backup and restore, and a BAA with each vendor that touches protected health information. Those are not optional decorations for a later phase; they are conditions of processing data at all, and cutting them turns an MVP into an exposure.
I write the MVP scope with the founder on one page. The page lists seven or eight capabilities, the data each one touches and the control that protects it. The controls are the same for every capability. The features are what can be built in the time available. A capability that requires a new vendor or a new integration goes onto the next phase unless it cannot work without it. The aim is a product that a clinician or patient could use next week and not a demonstration that would make a reviewer wince.
The page also names the scope of data the MVP will hold. A pilot with ten patients and synthetic data only has a much lower bar than a live product with real patients in one state. I ask the founder exactly what data will be used and I plan the compliance controls around that answer, not around the company's ambitions. That distinction saves a startup weeks of work and thousands of pounds of unnecessary assurance.
Prove the posture with evidence, not assertions
Every control in the MVP has an evidence trail from the first week. The encryption is proven by a configuration export, the backup by a restore that was actually run, the access control by a screenshot of the user list and an export of the access log, the audit by a query that shows the events. I assemble the evidence as part of delivery, not as a report at the end. A startup that can show its evidence when asked has a much better position in a diligence conversation than one that has to reconstruct it.
The evidence set is organised to match the security rule and privacy rule requirements that a covered entity or a business associate would look for. I cover the administrative, physical and technical safeguards with the specific items that apply. My delivery record inside MyRxWallet includes an active AWS BAA in place from 18 August 2026 and a documented security posture, and that work was done to exactly this standard of evidence day by day.
The evidence is kept in a versioned location with access control that matches the rest of the product. It is not in a shared folder that any staff member can open. The evidence can be scanned for protected health information because it often contains screenshots of live data; the same de-identification discipline used for test data applies to the evidence screenshots. That discipline stops the evidence itself becoming a data exposure, which is a mistake I have seen more than once.
Designing for the second release from the first
The choices made in an MVP become the architecture the company has to live with. The data model, the identity model, the integration points and the vendor choices are difficult to change after the first customers are live. I design the MVP so that the parts likely to change are isolated from the parts that should not change. For example, the patient record is stored behind an interface that can be connected to a clinical store or a vendor patient record later, rather than being read directly from the database by every feature.
The release process is built from the first deploy, not added later. I set up the CI and release gates from day one, even at small scale, because a healthcare startup's first audit trail is the history of its releases. A deployment pipeline that can promote a known version to production and roll back is the single biggest protection against a failed release stopping patient care, and it is much cheaper to build early than to repair under pressure.
The architecture is documented at the level a new engineer or a diligence reviewer can read. The document names the components, the data flows, the trust boundaries and the vendors. It is updated on every significant change; the revision history shows the company's growth and the controls that accompanied it. A prototype has no such document because it was never meant to be seen by anyone outside the room. The MVP has it from the day it was started.
The honest limits of a young company
I tell a startup plainly what it cannot yet say. It cannot claim that it is HIPAA-certified, because no such certification exists. It cannot claim to be a covered entity unless it is. It cannot claim compliance for a market it has not yet entered or a control it has not yet proven. What it can say is what it has implemented, what evidence it holds and what it has not done yet. Investors and customers respond better to that honesty than to overstatement, because overstatement is what diligence findings are made of.
A small company cannot afford to run every control a large organisation runs, and I do not pretend otherwise. The controls that matter most in the first year are access control, audit logging, encryption, backup and the vendor BAAs. Controls such as role segregation, formal risk assessment renewal and comprehensive business continuity plans come as the company grows. I put them on a written plan with dates so the company can say to a customer or an auditor precisely when each will be in place.
Where the founder intends to serve a market with higher regulatory requirements than the MVP is ready for, I say so at the start rather than discovering it at diligence. The CMS interoperability route, for example, has specific requirements that go well beyond the MVP controls. If the product is heading there in a year, I build that into the second-phase plan so the MVP's choices do not block the path.
What the first raise and first audit need to see
An investor conducting technical diligence on a healthcare startup will look for: a working product, a clear data flow, a vendor register with BAAs, evidence of audit logging, backup restore evidence and a plan for a security programme. I produce all of these as part of the MVP delivery, so the company can answer questions with artefacts rather than descriptions. The technical due diligence review then takes a day instead of a week.
The first audit or enquiry from a customer will ask for the same artefacts plus the specific records that apply to the incident or the customer's requirement. A well-evidenced MVP can answer in hours; an MVP without evidence has to start collecting it under a deadline. That gap is expensive in deal value, not just in time.
The MVP is delivered with the product, the evidence pack and the plan for the next phase. It is not certified by me and it is not a guarantee of compliance; it is an honest starting position and proof that the company has the discipline to go further. That tells an investor more about the team than a polished prototype ever could.
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 — compliant mvp builds for healthcare startups — 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.