PDex · CRD · DTR · PAS · Plan-Net

Charles Trinh — Da Vinci Implementation Guides | Las Vegas, NV · Las Vegas, Nevada · Henderson · Clark County, Nevada · North Las Vegas, Nevada

A service card reading DA VINCI — CRD, DTR, PAS and PDex adopted in the right order
Charles Trinh — Da Vinci Implementation Guides

The Da Vinci guides are where US payer-provider interoperability is actually specified: coverage discovery, documentation templates, prior authorisation and the exchange of clinical data for payment.

What this is

Da Vinci is a set of implementation guides, not one specification, and the guides compose. Coverage Requirements Discovery answers the question of whether a service needs authorisation before it is scheduled. Documentation Templates and Rules fetches the payer's questionnaire and the rules that decide which questions apply. Prior Authorization Support submits the request and returns the decision. Payer Data Exchange moves the clinical record needed to adjudicate or coordinate care. Plan-Net publishes the provider network.

Each guide constrains FHIR in a specific direction, and the constraints are the interesting part: which profiles are mandatory, which extensions carry the payer's own identifiers, how a questionnaire is packaged so a provider system can render it without knowing the payer's internal logic, and how a prior-authorisation response carries a denial reason that a provider can act on. Reading the guide is necessary; testing against another implementation is what reveals the gaps.

The composition is where programmes fail. A provider that implements Prior Authorization Support without Documentation Templates and Rules will send an authorisation request without the attachments the payer requires, and receive a denial that looks like a clinical decision but is really a payload problem. The guides are designed to be adopted together, and adopting them separately produces a pipeline that is conformant at each step and broken end to end.

I sequence the adoption by the rule deadline: Coverage Requirements Discovery and Documentation Templates and Rules first, because they reduce volume; Prior Authorization Support next, because it is the one with a regulatory clock; Payer Data Exchange and Plan-Net alongside, because they support the other three. The sequencing is as much of the deliverable as the code.

Testing against a counterparty matters more than testing against a spec. The published reference implementations let a payer see its own response read through a provider-side client, and that reading is where the misinterpretations surface: a field the payer believed was optional, a code the provider does not map, an attachment the questionnaire expects and the response omits. A programme that has never done that exercise is conformant on paper and untested in practice.

How I do it

Each guide gets a conformance matrix: the profiles it requires, the operations it mandates, the extensions it defines, and the test that proves each. That matrix is compared against the reference implementations the community publishes, because a spec reading that disagrees with every working implementation is usually a misreading.

Then the integration path. I test payer and provider sides against each other rather than against a mock, using the published reference servers where available and a captured conversation where not. The prior-authorisation flow gets an end-to-end test that starts with a service request and ends with a decision and a reason, including the denial path. A flow that has only been tested on the approval path is a flow that will fail the first time a payer denies a request for a reason the provider can fix.

Version drift is the maintenance burden. The guides publish drafts and updates, and a programme that pins to one version needs a written record of which version it conforms to and what changed in the next one that matters to it. Without that record, the first upgrade is a surprise audit of the whole integration rather than a scoped change with a test list. I keep the pinned version in the repository next to the tests, so the question of what was verified is answered by the code rather than by memory.

Artifacts you keep

  • A per-guide conformance matrix with the proving test for each requirement
  • An adoption sequence tied to the regulatory deadlines
  • An end-to-end prior-authorisation test including the denial path
  • A pinned version record with a documented upgrade path
  • A comparison against the published reference implementations

What the guides are for

Da Vinci implementation guides are not a general interoperability framework. Each addresses a named clinical or administrative workflow between payer and provider, and each is worth adopting only if you run that workflow at volume.

Read them as specifications for specific friction: coverage requirements discovered too late, documentation collected twice, authorisations submitted through a channel that cannot return a structured answer. The guides remove those specific frictions and nothing else.

That framing matters because organisations adopt a guide, pass conformance, and see no operational change. The guide was never the outcome; the workflow cycle time was.

CRD: timing is the entire value

Coverage Requirements Discovery asks, at order entry, whether documentation requirements apply. The same requirement surfaced during order entry is actionable; surfaced three weeks later it is a work item in a queue.

The engineering constraint is latency inside the ordering workflow. A clinician will tolerate a second; they will not tolerate a spinner while a payer's API thinks. Cache requirements by service category and plan, and fail open with a logged fallback rather than blocking the order.

Measure it in cycle time: from order entered to requirement known. That number is the case for the whole programme.

DTR: the mapping work nobody assigned

Documentation Templates and Rules has the payer supply the questionnaire and the rules that determine which questions apply, and the provider's system populate what it already knows. This is where most implementations stall.

Populating what you already know requires mapping your clinical data to payer-defined questions, and no vendor sells that mapping for your data. It is unglamorous, it is per-payer, and it is the difference between a form that arrives half-filled and one that arrives complete.

Scope it by questionnaire rather than by payer. The same questionnaire appears across several plans, so the mapping effort amortises where the questions are common and repeats only where they are not.

PAS: the denial has to carry a reason

Prior Authorisation Support returns the decision as a resource, including the reason. A denial with a structured reason is appealable at volume; a denial with a PDF is a phone call, and phone calls do not scale past the first hundred cases.

The value is entirely in the reason code being specific enough to drive an action. A generic denial reason converts a structured exchange into a structured notification, which is progress in formatting and nothing else.

Test it by taking a denial and asking what your system does differently because of the reason. If the answer is nothing, the structure is decorative.

PDex: the guide with the least upside and most exposure

Payer Data Exchange defines how claims and clinical data move between plans when a member changes coverage. It is peer-to-peer, so your counterparty's quality becomes your defect rate.

The failure to plan for is a beautiful request flow and a responder that returns an empty bundle because the member match silently found nothing. Log match failures — they are the only evidence available when a member says their history did not transfer.

Build the responder first. Every plan builds the requester because it is the visible half, and the programme stalls on the half nobody demonstrated.

Adoption discipline

Pick one workflow, one counterparty, and measure cycle time before and after. A guide adopted as a checkbox produces conformance and no operational change; a guide adopted against a measured workflow produces fewer denials and a shorter authorisation cycle.

Ask your vendor which guides, which versions, and for a live demonstration against a test counterparty. A roadmap slide is not evidence. The question that separates vendors is whether they can show a denial with a structured reason that came back through PAS.

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

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

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 — da vinci implementation guides — the scope, the failure modes it prevents and how the work is measured. It sits in the Interoperability 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.

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