Contact

Start with one question

Email charles@trinh.io with the API you are worried about and the date you are working to. A reply comes the same week, and if an assessment is the right next step it is scoped in that reply rather than a call.

What to include

The payer type and product lines, which of the five APIs is furthest from ready, whether the build is in-house or with a vendor, and what has already been tested. Three sentences is enough to make the first reply useful.

Availability

Assessments start within two weeks. Build sprints are sequenced one API at a time. Remote, from Las Vegas, Nevada.

Call 702-559-3489 · Las Vegas, Nevada · Serving clients worldwide — remote delivery from Las Vegas, Nevada, USA.

Where the work sits

For context before writing, the deadlines and standards are the ones set by CMS and ASTP/ONC, and the implementation guides are published by HL7.

Sources

Last updated

Last updated 2026-11-15

← CMS-0057-F readiness