DATA

Charles Trinh — Analytics Readiness Assessment | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

Readiness assessment scorecard across data, governance, platform and staffing dimensions
Charles Trinh — Analytics Readiness Assessment

Before you buy an analytics platform, find out whether the data and the team can answer the questions you are about to ask. A readiness assessment does that in four to six weeks.

What the assessment answers

An analytics readiness assessment answers three questions before a purchase or a hiring decision: what questions does the organisation need to answer next year, what data do those questions require, and what is currently blocking the data from answering them. Most platform investments go wrong because the answer to the middle question was assumed rather than measured. The vendor demonstration shows a dashboard on synthetic data; the organisation's own data cannot feed it, and the project stalls in the second month.

I run the assessment in four to six weeks and produce a written report. The report lists the priority questions, maps each to the data and the systems that hold it, and identifies what is missing. It also scores the organisation's readiness in four dimensions: data, governance, platform and staffing. Each score comes with a stated finding and a path forward. The report is a decision document, not a vendor selection.

The assessment is also useful for organisations that already have a platform and are trying to work out why adoption is low. The same four dimensions apply, and the answer is usually that the data layer cannot support the questions the platform is intended to serve. The platform looks fine; the data is the constraint. Distinguishing these is the point of the assessment.

Data readiness: the questions before the platform

Data readiness is about whether the data needed to answer the priority questions exists in a usable form. For each question I trace the required fields to their source systems, and then to the timeliness, completeness and quality of those fields. A question about hospital readmission rates requires encounter data from several systems, admission and discharge timestamps, and diagnosis and procedure codes for the readmission event. If the discharge disposition is unreliable, the readmission rate is unreliable, and that is a data finding, not a platform finding.

The assessment is time-boxed. Priority questions are limited to what the organisation intends to answer within the next twelve months. Coming with the full list of everything the organisation might want is how assessment projects become years. The business owner of each question is the person named in the assessment who will use the answer, and the question is included only when that person has agreed. Without a named user the data finding is speculative.

The output is a per-question data map: what is required, what is available, gaps, blockers and effort. Where the same source supports several questions, the map is consolidated so effort is counted once. Where a question needs new capture from the clinical systems, that is a separate change and not an analytics investment; the assessment makes the distinction so the investment conversation is honest.

Governance readiness

Governance is often the largest gap and the one that most affects the analytics timeline. If the organisation cannot decide whether a patient is attributed to one primary care provider or two, the readmission report and the population health dashboard will disagree about the count and neither can be reconciled. The healthcare data governance work covers the design; the assessment measures whether a workable design exists today.

The governance readiness finding covers: a decision log, named owners for the priority data domains, an access request route that works in under two weeks, and an exceptions process for disputed definitions. Where these exist, I record them and move on. Where they do not, I record the absence as a finding and name the cost in analyst time, in delayed decisions, and in unresolved contradictions between reports.

Governance gaps do not always require a formal structure before analytics gets started. Where the organisation is small enough, a single owner with an explicit list of decisions and a fortnightly review can carry the work for the first year. The assessment records the current state and the minimum structure required for the specific priority questions. The recommendation is sized to what the questions need, not to a template.

Platform readiness and the buy decision

The platform assessment is about fit, not features. Most platforms solve the same core problems; the differences are in the specific queries the organisation needs to run, the data volumes it has, and the way its teams work. I test fit against the priority questions: can the candidate platform answer the readmission question at the organisation's data volume, at the refresh cadence required, within the budget, with the team's existing skills, and with the access model the governance finding describes?

Where a platform already exists, the assessment tests whether its usage matches the priority questions. A platform showing dashboards to executives who look at them once a quarter is not being used as a decision tool. The assessment records the actual usage pattern and the questions the platform has answered in the last year. That record is the honest input to a renewal decision and it is usually more informative than the cost line.

I do not recommend one platform over another in the readiness report. The report states the requirements, the constraints and the fit criteria; the selection is the organisation's decision. I will review shortlisted candidates against the requirements and report fit findings, but the decision itself belongs to the people accountable for the investment. The report makes the trade-offs explicit so the decision can be made without a round of clarification meetings.

Staffing and skills

Analytics is a function, not a tool. The assessment names the skills required for the priority questions in the next twelve months: data engineering, analytics, clinical informatics, governance and data privacy. For each I record whether the skill exists in the team, exists adjacent, is contracted, or is missing. The assessment does not fill the gap; it names it., and the minimum structure is named for each of the priority questions rather than for a template.

The assessment is done through interviews, data profiling and a workshop to agree the priority questions. The interviewing is short: structured conversations with the business owners, the data owners and the technical leads. The substance is profiling: for each priority question I measure the required fields in their sources and record completeness, timeliness and quality with actual numbers. The workshop fixes the priority list and confirms the owners before profiling starts.

The staffing recommendation names the minimum viable team for the priority questions, with a named owner for each question and an escalation route for the questions the team cannot answer. Where the organisation cannot staff fully, the recommendation is to reduce the scope to the questions it can staff. A smaller scope that delivers is better than a wider scope that stalls; the assessment is the place to make that choice with the business, not to discover it in the third month of the project.

Assessment methodology and the report

The assessment is done through interviews, data profiling and a workshop to agree the priority questions. The interviewing is short: a handful of structured conversations with the business owners, the data owners and the technical leads. The data profiling is the substantive work: I profile the sources against the required fields for each priority question and record completeness, timeliness and quality with actual numbers. The workshop sets the priority list and confirms the owners before profiling starts.

The report structure is: executive summary, priority questions and owners, per-question data map, dimension scores with findings, recommended next steps, and an appendix with the profiling method. It is written for a decision maker and the technical detail is in the appendix. Where a finding needs the data to speak for itself, the appendix contains the numbers; where a finding needs judgement, the report states the judgement and who made it.

The assessment is the front end of the analytics programme, not a separate project. When the assessment lands, the organisation has the priority list, the owners and the minimum structure to start. The report deliberately stops there; the next work is the analytics build itself, and the population health analytics or reporting automation work picks up from the recommendation. The assessment's value is that the build starts from an actual data map rather than from an assumption.

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 — analytics readiness assessment — 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