Notes by Charles Trinh

Writing on interoperability, identity, regulation and enterprise AV/IT

Most of what is here comes out of live work: CMS-0057-F API readiness across the five APIs the rule names — the Prior Authorization API, the Patient Access API, the Provider Access API, the Payer-to-Payer API and the Provider Directory API — plus the identity layer that makes exchange safe to operate, TEFCA IAS, and the fractional healthcare interoperability architect engagements that keep the work funded.

FHIR patient access is not a portal — what the difference costs — cover card
Interoperability

FHIR patient access is not a portal — what the difference costs

CMS Blue Button 2.0 and VA Lighthouse return data; a patient-controlled record is what makes it usable. Where portals stop and interoperability starts.

X12 005010 is only real when it works in both directions — cover card
Claims

X12 005010 is only real when it works in both directions

Composing a 270 is the easy half. Accepting a 271 with dependent loops, parsing a 277CA rejection and returning it to the record is where a claims pipeline earns its name.

A consent checkbox is not a consent record — cover card
Identity

A consent checkbox is not a consent record

Grant, refusal and revocation have to be events with a time, an author and an immutable history — otherwise revocation is a promise the system cannot keep.

The HIPAA Security Rule, read as an engineering backlog — cover card
Regulation

The HIPAA Security Rule, read as an engineering backlog

Access control, audit controls, integrity, transmission security and person authentication are testable. Here is what each one looks like as a running system.

Never promote an interface without a sandbox result — cover card
Delivery

Never promote an interface without a sandbox result

Every integration is a claim until a vendor environment returns a real message. The discipline is a gate, not a document.

Self-host the parts a vendor cannot be exited from — cover card
Platforms

Self-host the parts a vendor cannot be exited from

Email, DNS, search, model routing — the layers where an outage or a price change takes the business with it are the ones worth running yourself.

From capability statement to a four-volume response — cover card
Procurement

From capability statement to a four-volume response

Federal evaluators score against the rubric they published. Writing to that rubric — with UEI and CAGE in place — is a different craft from marketing.

What a hiring manager needs on one page — cover card
Careers

What a hiring manager needs on one page

Lead with the discipline, prove it with numbers, and put the document one click away. The rest is noise.

An architect is judged by what survives production — cover card
Practice

An architect is judged by what survives production

Specification, vendor validation and evidence gates matter more than a clean diff when the system has to answer a payer and an auditor.

One gate for every model, with the guardrails defined first — cover card
AI

One gate for every model, with the guardrails defined first

Multiple foundation models behind a single controlled gateway: routing, tool boundaries, evaluation and limits decided before the first prompt.

Patient matching is the quiet failure in every HIE — cover card
Identity

Patient matching is the quiet failure in every HIE

Wrong-person merges are expensive to reverse and invisible until they are not. Identity resolution deserves the same rigour as the transaction itself.

Prior authorisation is a data problem wearing a form — cover card
RCM

Prior authorisation is a data problem wearing a form

A 278 exchange is not a fax alternative. It is a structured request with a decision attached, and it can be tracked like any other transaction.

What the CMS Interoperability and Patient Access rule actually obliges — cover card
Regulation

What the CMS Interoperability and Patient Access rule actually obliges

Seven policy areas, one patient right: the record travels with the person. The engineering is in the API surfaces, not the policy statement.

AWS for regulated workloads: the controls, not the logos — cover card
Platforms

AWS for regulated workloads: the controls, not the logos

BAA, encryption at rest and in transit, least-privilege identity and an audit trail that survives a rebuild. A checklist of service names is not a control set.

A claims engine without a test suite is a rumour — cover card
Delivery

A claims engine without a test suite is a rumour

Golden files, real payer responses and a gate that refuses to ship: the three things that make an X12 implementation trustworthy.

On-call when the platform is one person deep — cover card
Operations

On-call when the platform is one person deep

A runbook, a page that names the failing component, and a recovery path tested before it is needed. Scale is not a prerequisite for discipline.

HL7 v2 still runs the world, and it is not going anywhere — cover card
Interoperability

HL7 v2 still runs the world, and it is not going anywhere

Pipe-delimited messages carry most hospital traffic. The skill is knowing where the standard is weak and defending that boundary.

Provider identity is harder than patient identity — cover card
Identity

Provider identity is harder than patient identity

Credentialing, NPI, taxonomy and directory accuracy: a provider record that is wrong stops claims before it stops care.

What HIPAA does not require — and why that matters to engineers — cover card
Regulation

What HIPAA does not require — and why that matters to engineers

The Security Rule is technology-neutral and outcome-based. That is freedom to design, and a burden to justify.

An implementation guide is a contract, not a suggestion — cover card
Interoperability

An implementation guide is a contract, not a suggestion

US Core and the Da Vinci guides specify what a resource must carry. Reading them narrowly is how an integration passes conformance and fails the workflow.

Revocation is a promise the system must keep downstream — cover card
Identity

Revocation is a promise the system must keep downstream

A patient withdrawing consent is easy to record and hard to honour. The work is deleting or invalidating every copy the grant authorised.

Clearinghouse or direct payer: the trade nobody prices — cover card
Claims

Clearinghouse or direct payer: the trade nobody prices

A clearinghouse buys you onboarding and a rejection format; a direct connection buys you latency and control. Most teams choose on price alone.

Most agents die in production; the survivors share three traits — cover card
AI

Most agents die in production; the survivors share three traits

Tool boundaries, a fixed evaluation set, and a reason to be decommissioned. Agents without those are demos with a budget.

Integrating with an EHR you cannot change — cover card
Interoperability

Integrating with an EHR you cannot change

The vendor owns the roadmap and the interface. Your job is to make your side survive their next release.

A 999 is not an error message, it is a work queue — cover card
Claims

A 999 is not an error message, it is a work queue

The acknowledgement says what the envelope rejected. Turning it into per-claim work is the difference between a pipeline and a black hole.

A BAA is a contract, not a control — cover card
Regulation

A BAA is a contract, not a control

Signing one with a cloud provider does not make the workload compliant. The safeguards are still yours to design and prove.

How to read a regulator without guessing — cover card
Regulation

How to read a regulator without guessing

Primary text first: the rule, the preamble, the FAQ. Everything else is someone's interpretation, including yours.

What a fractional architect actually does in a week — cover card
Practice

What a fractional architect actually does in a week

Not slides. Decisions, vendor conversations and the two or three choices that would be expensive to reverse.

Mapping HL7 v2 to FHIR without losing the meaning — cover card
Interoperability

Mapping HL7 v2 to FHIR without losing the meaning

Segments map cleanly; intent does not. The mapping is where a hospital's local conventions become somebody else's data quality problem.

Rework is the number nobody puts in the business case — cover card
RCM

Rework is the number nobody puts in the business case

Every rejection that needs a human is a cost the vendor quote never shows. Instrument it before optimising it.

Design-build is a procurement model, not a promise — cover card
AV Integration

Design-build is a procurement model, not a promise

What an enterprise buyer actually pays for when the integrator owns drawings, engineering, installation and commissioning — and where responsibility stops.

AV over IP put the AV system on the network team's budget — cover card
AV Integration

AV over IP put the AV system on the network team's budget

Once audio, video and control ride the LAN, the AV integrator and the network engineer are designing one system. The handoff is where projects fail.

Teams Rooms and Zoom Rooms turned the conference room into a managed endpoint — cover card
Collaboration

Teams Rooms and Zoom Rooms turned the conference room into a managed endpoint

The platform chooses the hardware compatibility list, the update cadence and the management console. Procurement should follow the platform decision, not the reverse.

Digital signage fails at scale, not at install — cover card
AV Integration

Digital signage fails at scale, not at install

One screen is a purchase. Fifty screens is a content pipeline, a player fleet, a network policy and a support model. Most signage programs fund only the first.

A command center is an operations design, not a video wall — cover card
AV Integration

A command center is an operations design, not a video wall

The wall is the least interesting part. Sightlines, console ergonomics, source switching, redundancy and the operator's decision loop decide whether the room works.

AV in a hospital is clinical infrastructure — cover card
Healthcare AV

AV in a hospital is clinical infrastructure

Patient-room televisions, education systems, nurse-call integration and clinical communications share a network and a maintenance window. Treating them as consumer electronics is how they fail.

AV managed services: what day 2 actually costs — cover card
Managed Services

AV managed services: what day 2 actually costs

Monitoring, dispatch, spares and firmware are the recurring bill. A support contract priced without a device inventory is a guess on both sides.

Converged cabling: one plant, two owners — cover card
Infrastructure

Converged cabling: one plant, two owners

When AV, security and IT share the same cable plant, the responsibility matrix decides who fixes it at 2 a.m. Most projects never write that page.

Writing an AV RFP a real integrator can price — cover card
Procurement

Writing an AV RFP a real integrator can price

Scope by outcome and room type, demand the engineered documents, and separate equipment, labour and service so bids can be compared at all.

Casino and hospitality AV: rooms that cannot go dark — cover card
AV Integration

Casino and hospitality AV: rooms that cannot go dark

In a casino, a dark display is lost revenue and a broken experience at the same moment. Redundancy, spares and maintenance windows are revenue protection.

Venue AV: the scoreboard is the smallest system — cover card
AV Integration

Venue AV: the scoreboard is the smallest system

Stadium and speedway AV is a control room, a signal transport layer, a public-address system, a display network and a game-day operations team.

AV-as-a-Service is a financing structure, not a service — cover card
Managed Services

AV-as-a-Service is a financing structure, not a service

The label bundles equipment, installation and support into a subscription. What changes is the balance sheet and the exit — not the engineering.

Control system lock-in is a lifecycle decision — cover card
AV Integration

Control system lock-in is a lifecycle decision

The control platform outlives the room. Choosing it decides who can service the room, what a future change costs, and how portable the design is.

Why AV projects fail inside IT governance — cover card
IT Integration

Why AV projects fail inside IT governance

AV arrives as a capital project and leaves as an operations burden. If it never enters the asset, patch and support model, it fails quietly for years.

AV design in a healthcare building is a clinical decision — cover card
AV

AV design in a healthcare building is a clinical decision

A conference room is easy; a procedure room, a nurse station and a command centre are not. The difference is who is in the room when the system fails.

One conference-room standard, or twenty rooms nobody can use — cover card
AV

One conference-room standard, or twenty rooms nobody can use

Every room built to its own spec becomes its own support ticket. A standard room kit is an operational decision disguised as a design one.

A command centre is an AV system with a consequence — cover card
AV

A command centre is an AV system with a consequence

Video walls, consoles and control-room ergonomics are one system. When it fails, the failure is operational, not cosmetic.

Put AV on its own VLAN, then test what still works — cover card
AV

Put AV on its own VLAN, then test what still works

AV over IP shares the wire with everything else. Segmentation is a design choice that protects both the clinic network and the room.

Buying AV as a service changes who owns the failure — cover card
AV

Buying AV as a service changes who owns the failure

AVaaS moves capital to operating cost and moves the upgrade decision to the contract. Read the exit terms before the first room opens.

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