Charles Trinh · Services
Remote engagements

Architecture for healthcare data exchange, identity and regulatory control.

TRINH + whoosh — Charles Trinh, Technology Architect, Las Vegas NV

Each engagement starts with the decisions that are expensive to change later — the exchange profile, where consent is recorded, which vendor is load-bearing — and ends with evidence from a vendor environment, not a slide.

Enterprise AV/IT — AV design, unified communications, digital signage, command centres and network design by Charles Trinh
Enterprise AV/IT — design, integration and support

1. Healthcare interoperability architecture

FHIR R4 patient access, provider directory and payer-to-payer work; HL7 v2 for hospital interfaces; the US Core and Da Vinci profiles that make an API answerable to a trading partner.

Interoperability

2. Claims and eligibility pipeline

X12 005010 end to end — 270/271, 837P/837I/837D, 835, 276/277, 278, 277CA, 999 — with responses parsed back into the record and rejections tracked to closure.

X12 · RCM

2b. Enterprise AV/IT integration

AV design and integration for conference rooms, command centres and venues; unified communications with Teams Rooms, Zoom Rooms and Webex; digital signage, video walls and room scheduling; Crestron, Extron, Q-SYS, Biamp and Dante audio; structured cabling, rack and server-room design; LAN/VLAN segmentation on Fortinet, Palo Alto, Juniper, Cisco and Meraki.

AV · UC · Networks

3. Identity and consent architecture

Patient and provider identity, verifiable credentials, and a consent record that captures grant, refusal and revocation as events rather than a checkbox.

Identity

4. Regulatory control mapping

HIPAA Security Rule, HITECH, HITRUST, SOC 2, the ONC Cures Act and CMS interoperability rules turned into testable controls and the evidence an auditor asks for.

Regulation

5. Cloud and self-hosted platform

AWS architecture under a BAA, Linux hardening, self-hosted mail with SPF/DKIM/DMARC alignment, release gates, and an estate that does not depend on a vendor it cannot exit.

Platform

6. Vendor evaluation and sandbox validation

Clearinghouse, payer and platform vendors evaluated on the response they actually return, with every interface validated in a test environment before production promotion.

Delivery

7. Federal and state proposal support

Capability statements, four-volume responses, UEI and CAGE identifiers, and vendor registrations — written to the evaluator's published rubric.

Federal

8. Architecture review and fractional architect

A standing review of the decisions that are expensive to reverse: identity model, transaction boundaries, where consent lives, which vendor is load-bearing.

Advisory

Deep dives: CMS-0057-F and identity

For teams working to the January 2027 deadlines, the detail lives on its own pages: the CMS-0057-F API readiness assessment, each of the five APIs — Prior Authorization, Patient Access, Provider Access, Payer-to-Payer, Provider Directory — and the identity layer, TEFCA IAS, that ties them together. If the work is ongoing rather than a one-off assessment, the fractional architect engagement is the standing version.

Reference

Browse by category

Ten categories, each with its own index of engagements:

Charles Trinh, by discipline

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

Las Vegas, Nevada · Serving clients worldwide — remote delivery from Las Vegas, Nevada, USA.

Email Charles Trinh