content addressing · document integrity · pinning

Charles Trinh — IPFS and Content-Addressed Storage, Las Vegas NV

Charles Trinh — IPFS and Content-Addressed Storage, Las Vegas NV
Charles Trinh — IPFS and Content-Addressed Storage, Las Vegas NV

Content-addressed storage for clinical documents: integrity by construction, pinning that actually persists, gateway strategy, and the boundary between addressing and confidentiality.

What content addressing gives you

A CID is a digest of the content, so the address changes if the bytes change; integrity becomes structural rather than procedural.

That property is genuinely useful for documents that must be provably identical to what was signed or attested.

It is not encryption and not access control; a CID shared with the wrong party is a document shared with the wrong party.

Pinning is the whole operational problem

Content exists while someone pins it; a node going offline without replication is a deletion you did not intend.

Pin to multiple providers and monitor the pin set as an inventory with a verification cadence.

Test retrieval before you rely on it, because a CID that resolves on your laptop and nowhere else is a local file with extra steps.

Gateway strategy

Public gateways are convenient and are not a confidentiality control; anyone with the CID can fetch through them.

Use a private gateway for anything containing PHI, with the same authentication as your application.

Cache at the gateway, because the first fetch after a pin move is slow enough to be visible in a clinical workflow.

Encryption before publishing

Encrypt at the application layer before content leaves your boundary, so the CID refers to ciphertext you control.

Keep key custody separate from the storage provider, or the encryption protects you from nobody.

Document key rotation, because re-encrypting means a new CID and a new anchor.

Where it fits in a clinical estate

Document attestation, consent artifacts and signed disclosures: things that must be provably unaltered.

Not primary records, which need query, update and lawful deletion that content addressing makes awkward by design.

The useful combination is CID in your database plus anchor on a ledger, giving integrity and existence proof together.

Exit and portability

Keep the canonical copy in storage you control and treat IPFS as a distribution and integrity layer.

If a provider disappears, you should lose a gateway, not a record.

Write the exit test down and run it once, before the provider has an incident.

How I do it

One trace of a real case with timestamps at every hop, before any document is written.

A findings list naming the defect, the system, the owner and the date, reviewed monthly.

No attestation I did not test, and no template sold as an assessment.

Addressing is not custody

A CID tells you what the content is, never where it lives or who may read it; custody remains a decision about pinning and keys.

Write down which node holds the canonical copy, which nodes replicate it, and what the retrieval path is when the first one is unavailable.

The design is only complete when somebody can answer that question without consulting the person who built it.

The pin inventory

Treat pinned content as an inventory with an owner, a purpose and a verification date, the same way you would treat a storage volume.

Run a monthly check that a sample of CIDs resolves and returns the expected digest, and correct any that do not.

Unpinned content disappears silently, and silent disappearance in a clinical document store is a records-retention failure.

Integrity without confidentiality

The digest proves the document is unaltered; it says nothing about who should see it, and a public gateway exposes anything whose CID is known.

Encrypt before publishing and keep keys in your own custody, so the gateway serves ciphertext to anyone and plaintext to nobody without a key.

Record the key identifier alongside the CID, because a document whose key cannot be found is a document you cannot produce.

Verification in practice

Verification recomputes the digest of the stored document and compares it with the CID and with any anchor on a ledger.

Put that check in your own tooling with a single button and a printable result, because the person who needs it is usually not an engineer.

A verification method that requires a specialist is a method that will not be used when it matters.

Practical retrieval latency

A cold fetch through a public gateway can take seconds to tens of seconds, and a clinician waiting for a document experiences that as a broken system. The mitigations are caching at your own gateway, pre-warming the content you know will be read, and showing the retrieval state in the interface so that a slow fetch looks like progress rather than failure. None of these fix cold storage; they make the common path fast and the uncommon path comprehensible.

Measure the retrieval path the way you measure any other dependency: p95 by document age and by gateway. Content that has not been requested in months will be slow the first time, and knowing which documents those are lets you warm them deliberately before a workflow that needs them. The alternative is discovering the distribution problem during an audit, when a reviewer asks for a document you have not touched in a year.

Choosing what to address

Content addressing rewards immutable documents and punishes mutable ones, because every change produces a new address and a new key to track. Signing bundles, attested disclosures, finalised reports and consent artifacts fit; working documents, drafts and anything edited in place do not. Drawing that line in the design, rather than leaving it to application developers, keeps the store from filling with thousands of abandoned addresses that nobody can explain.

The practical rule is that the CID should be created when the document becomes final and never before. That gives the CID a meaning, keeps the pin inventory small enough to audit, and makes the verification story simple: every CID refers to a document that someone decided to freeze. Abandoned content is deletable by design, which is a property you want when retention obligations and storage costs both apply.

Working with an anchor

The combination that survives scrutiny is a CID in your database, an encryption key in your custody, and a digest anchor on a ledger. The CID proves integrity, the key controls access, and the anchor proves that the document existed in that form at a time. None of the three substitutes for the others, and a design that has two of them will fail the question the third answers.

When verifying, check all three in a fixed order and record the result: digest recomputes, key produces plaintext, anchor exists at the claimed time. The order matters because each check depends on the previous one, and a partial verification reported as complete is worse than no verification at all. Put the procedure in writing with the commands, since the person running it may be a compliance officer rather than an engineer.

Cost and the shape of the bill

Storage via pinning services is billed by volume and by bandwidth, and a document store with generous retention accumulates both without anyone noticing. Instrument the pin inventory's total size and its monthly growth, and set a review threshold before the growth becomes a budget conversation. Deleting what no longer needs to exist is a designed action with a date, not an afterthought that happens when a bill arrives.

The comparison that decides the architecture is against object storage with server-side integrity checks, which is cheaper for most estates. Content addressing earns its premium when independent verification matters; when it does not, the same integrity guarantee is available from a checksum column and a bucket policy. Being honest about which case you are in keeps the design proportionate to the requirement rather than to the technology's reputation.

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 — ipfs and content-addressed storage, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Data and Ledgers 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