hitrust · control mapping · evidence

Charles Trinh — HITRUST Mapping and Certification Readiness, Las Vegas NV

A service card reading HITRUST Mapping and Certification Readiness — Charles Trinh, technology architect in Las Vegas
Charles Trinh — HITRUST Mapping and Certification Readiness

Mapping your existing controls onto the HITRUST framework, closing the gaps that actually block assessment, and building the evidence set an assessor will ask for.

Why the mapping is not the work

Mapping controls to a framework is clerical; the work is evidencing that each control operates on a stated cadence.

An organisation can be fully mapped and entirely unprepared, because a mapping row is a claim and the assessor wants an artefact.

Start from what you can already prove and let the gap list follow, rather than starting from the framework and inventing evidence.

Scoping honestly

Scope determines cost and timeline more than any control does, and over-scoping is the most common way a first assessment stalls.

Pick the system boundary that matches how the business actually runs, not the boundary that looks most impressive.

Every system in scope adds evidence obligations, so scope deliberately and document the reasoning.

Evidence that an assessor accepts

Dated artefacts, sampled consistently, retrievable in the format requested, and traceable to the control they satisfy.

A screenshot is weak; a configuration export with a timestamp and a named system is strong.

Build the evidence index before the assessment, because assembling it during the assessment is how timelines slip a quarter.

The controls that usually fail

Access review with no evidence of decisions, change management without approvals, and backup without a restore test.

Each is cheap to fix and expensive to fail, because remediation after a finding means re-assessment on your cost.

Run a pre-assessment against those three first; they account for most first-pass gaps in small estates.

Interim and certification paths

The interim assessment buys structure and a shorter evidence window; full certification costs more and lasts longer.

Choose by what the buyer requires, not by what sounds stronger, because a certification nobody asked for is an expensive badge.

Plan the renewal from the day you certify, since the evidence window starts again immediately.

Cost control

The dominant costs are internal time and evidence assembly, not the assessor's fee.

Budget the internal hours explicitly and name the person who owns evidence collection.

Organisations that treat this as an IT side project pay twice, once in the first attempt and once in the redo.

Vendor and subprocessor scope

Third parties holding PHI extend scope and require their own evidence, which they will resist supplying.

Ask for their certification or assessment summary early, because discovering it late resets your timeline.

Carry the dependency in the risk register with the date you last verified it.

What I actually do

I build the control-to-evidence map, run a pre-assessment, and assemble the index an assessor works from.

I do not sell a compliance platform, and I will not sign an attestation I did not test.

The output is a list of controls with owners, artefacts and dates, and an honest statement of which will fail.

Timeline realism

A first assessment on a small estate runs three to six months of preparation, dominated by evidence assembly.

Compressing it means either narrowing scope or accepting findings, and both are decisions rather than accidents.

State the trade-off to the buyer early, because a missed certification date costs more than a narrower scope.

Where to start

Pull the last access review, the last restore test and the last change approval, and see whether each survives inspection.

If any of the three is missing, that is the first project, and it is measured in weeks rather than quarters.

Everything else in the framework is easier once you can evidence those three.

How I do it

Control inheritance, tested rather than assumed

A platform inherits its hypervisor's controls, and the inheritance is only real when the platform can produce the inherited evidence on demand.

Inheritance claims collapse during assessment because the underlying report covers a window that closed before your system existed in its current form.

Ask for the report, the bridge letter and the date the inherited control last operated, and record all three against the inherited control in your matrix.

What sampling actually tests

An assessor samples to see whether the control operates consistently, not whether it exists, so consistency across the window is the whole game.

Three clean months followed by one improvised month is a failed control, because the sample selects the improvised month often enough to matter.

Design controls that survive a bad month: a review with a standard agenda and a recorded decision costs less than one requiring judgement each time.

The first thirty days

Count the controls you can evidence for last month without inventing anything, and treat that count as the starting position rather than a judgement about the team.

The three that usually fail first are access review, change approval and restore testing, because each needs a second person to sign.

Fix those three before tooling, because tooling applied to an unevidenced control produces a dashboard rather than an attestation.

How the assessment is sequenced

The assessor works from the control you claim to the artefact that shows it, so sequencing follows your matrix rather than their checklist.

Put the controls you can evidence first, because early clean answers buy credibility for the ones that will need explanation.

Anything requiring an interview should be scheduled with the person who actually operates the control, not the person who owns the policy.

Where the framework and the business disagree

A control written for an enterprise may not fit an organisation of eight people, and the framework anticipates a reasonable alternative.

Document the alternative, the mechanism you use instead, and the reasoning, and let the assessor judge it rather than silently skipping the control.

Silence reads as absence; a written alternative reads as judgement, and the two are treated differently.

Keeping readiness after certification

The evidence window closes and reopens, and the work between cycles is the work that determines the next result.

Hold a monthly thirty-minute review of the same three failing controls, and record the decision each time.

An organisation that only assembles evidence when an assessor is booked is buying the same work repeatedly at a premium.

What the assessor writes down

The report records, for each control, what was tested, what was sampled and what the sample showed, and that sentence is the one your buyer reads.

Design controls so that sentence is short and dull: the control operated every month, the sample was clean, no exceptions were noted.

Anything you cannot describe in one such sentence is a control you have not finished designing, regardless of the framework rung it sits on.

How a first assessment is scoped in practice

The practical starting point is the system that holds the records a customer cares about, described by the deployable unit rather than by the department that owns it. Write down the components, the interfaces that cross the boundary and the personnel who can reach each one, then ask whether a change in any single component would require re-assessment. If the answer is yes for a component you were about to exclude, the scope was too narrow and it is cheaper to discover that on paper than in the assessment.

The second decision is which rungs to claim. Claiming every available control because it looks thorough multiplies the evidence set without changing the buyer's reading, and every claimed control is one the assessor may sample. Claim the controls that operate, the ones you can show operating across the period, and the ones a customer questionnaire actually asks about. An honest matrix with a shorter list is worth more than a long matrix with three controls that will fail when sampled.

The third is the evidence window. Pick a start date you can defend, which in practice means after the collection habit exists and after the last control you intend to claim has operated at least twice. Starting early to hit a customer date is the single most common reason a first assessment ends with findings that could have been prevented, because the months before the habit formed are months nobody can reconstruct once the assessor asks.

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 — hitrust mapping and certification readiness, las vegas nv — 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh