audit · artefacts · traceability

Charles Trinh — Audit Evidence Pack, Las Vegas NV

A service card reading Audit Evidence Pack — Charles Trinh, technology architect in Las Vegas
Charles Trinh — Audit Evidence Pack

Assembling the evidence set an examiner or auditor asks for before they ask: control narratives, artefacts by period, and a traceability index that survives sampling.

What a reviewer actually reads

Not the narrative first: they ask for a specific artefact for a specific period and watch how long it takes to produce.

Speed and consistency are the signals, because both indicate a repository rather than a scramble.

Organise by control and period, not by system, so the answer to a sample is one lookup.

The artefacts that carry weight

Dated exports, signed approvals, log queries with results, restore test records, and access reviews showing decisions rather than attendance.

A screenshot is an assertion with a border; a timestamped export from a named system is evidence.

Keep the raw file, because a re-rendered summary invites a follow-up.

Traceability index

One table: control, claim, artefact, location, period covered and owner.

The index is what lets a stranger navigate without you, which is the actual test of readiness.

Keep it current, because an index that lags the repository is worse than none.

Gaps stated, not hidden

Every repository has gaps; state them with a date and a remediation owner.

An acknowledged gap with a plan is survivable; a discovered gap with an excuse is a finding.

Reviewers respond well to candour and badly to surprise.

Period discipline

Evidence must cover the window being examined, not the last clean month.

If collection starts mid-window, say which months are partial rather than presenting them as complete.

Missing months cannot be reconstructed, only explained.

Access during the review

Give reviewers read access to the repository rather than answering requests one at a time.

Batch the requests where the tooling allows it, and log what was provided.

The log of what you handed over is your own defence if the conclusion is challenged.

Common defects

Policies reviewed annually but not versioned, approvals in email, and evidence that lives in a personal drive.

Each is cheap to fix before the review and expensive to explain inside one.

A shared repository with an owner solves all three.

What I build

The index, the artefact taxonomy and the collection cadence, then I run a mock sample against it.

I do not write your policies; I make the claim and the evidence line up.

The deliverable is a repository a stranger can navigate.

Running the mock sample

Pick ten controls at random, request the artefact for a random month, and time how long production takes.

Anything above an hour per control indicates an index problem rather than an evidence problem.

Repeat after remediation and compare the two timings.

Where to start

List the last five artefacts you actually produced for a real question, and see where they live.

That list is the seed of the repository and it usually reveals two systems nobody indexed.

Everything else is filing with better names.

How I do it

Version control for evidence

Evidence that cannot be traced to a version is a screenshot with a story attached, and reviewers know the difference.

Store artefacts with a hash or a signed export, and record the system and the query that produced them.

When a control changes mid-window, both versions stay in the repository, because the change itself is evidence that change management operates.

The reviewer's clock

A reviewer with a fixed budget samples until confidence is reached, and every slow answer spends that budget.

Time the production of ten artefacts without warning, and treat anything above an hour as an indexing problem.

Fast, boring answers are the goal; the review should end early because nothing interesting was found.

Evidence for controls you cannot see

Some controls operate inside a vendor's boundary, and the evidence is their report rather than your configuration.

Keep the vendor report, its exceptions and the date you last read it, filed against the control it supports.

An inherited control with no artefact is a claim, and the reviewer will ask for it in exactly the case where it matters.

Naming and filing

Artefacts should be findable by control and period without opening them, because the reviewer searches before reading.

A file name that carries the control, the system and the month removes the largest single source of delay.

Agree the convention once and enforce it at collection, not at review time.

The narrative that sits above the artefacts

A short control description explains what operates, who owns it and what evidence it leaves, in a paragraph rather than a document.

Where the narrative and the artefact disagree, the artefact wins, and the disagreement is the finding.

Rewrite the narrative when the process changes, because a stale description is worse than a missing one.

Handling requests for more

A reviewer asking for more is usually asking because the first artefact did not answer the question it appeared to address.

Ask what would settle it, then provide exactly that rather than a larger bundle.

Volume is not persuasion, and a large unindexed bundle slows the review and invites further sampling.

Retention and the end of the review

Evidence outlives the review, and the retention period should be set by the longest obligation rather than by disk space.

Archive the pack at closure with the report, the sample list and the correspondence, so a later question can be answered from the same set.

Organisations that discard the working papers buy the same understanding twice at increasing cost.

Naming the owner of the pack

One person owns the repository, its index and its completeness, and that person must have the authority to chase a missing artefact.

Distribute collection to the control owners but keep the index central, because a distributed index becomes five indexes.

The owner reports completeness monthly, and the report is short because it names only what is missing.

What a pack looks like when it is finished

A finished pack has three layers and each has one job. The index answers where the artefact is, the artefact answers what happened, and the narrative answers why the control is designed this way. Reviewers move down that list in that order, and any layer missing slows the next one to the speed of a conversation. The common failure is a strong narrative with a weak index, which looks organised until the first sample request and then stalls on a search across four systems.

The index should be generated where possible, from the repository rather than maintained by hand, because a hand-maintained index drifts within a quarter. If generation is impossible, keep the index to six columns and review it monthly against the folder structure. The test of a good index is that a person who has never seen the estate can locate any artefact from a control name and a month without asking a question, and that test takes ten minutes to run and reveals most problems immediately.

Finally, the pack should state its own gaps. A page at the front listing the controls with partial evidence, the months that are incomplete and the owner of each remediation converts a series of unpleasant discoveries into a manageable list. Reviewers respond to that with questions about the plan rather than about the gap, and the difference in the shape of the review is worth the discomfort of writing the page, which is usually the last thing anyone wants to do and the first thing that changes the outcome.

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 — audit evidence pack, 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