45 CFR Part 171 - Cures Act information blocking
Information blocking review for Las Vegas healthcare organizations
An information blocking review answers one question in writing: for each request another party makes for electronic health information, is refusing it permitted, and under which exception.
Charles Trinh runs that review for hospitals, payers, health information exchanges and health IT vendors in Las Vegas and Clark County, and does it as a fixed-scope engagement with a determination memo, an evidence file and a remediation list rather than a policy template.

On this page
What the review actually decides
The review starts with actor designation, because the answer changes with it. A healthcare provider, a health IT developer of certified health IT, a health information network or exchange, and a QHIN are all actors under the rule, and a vendor that also operates a network can be two of them at once for different data flows.
Each request is then tested against the exceptions in 45 CFR Part 171: preventing harm, privacy, security, infeasibility, health IT performance, content and manner, fees, and licensing. The output is not a general opinion. It is a line per request type - permitted, conditionally permitted, or not permitted - with the condition named.
The evidence file is the deliverable that matters
A determination memo with no evidence behind it fails the first time a customer, a partner or an enforcement inquiry asks how the decision was made. Each determination is therefore backed by the artefact that proves it: the security risk analysis it relies on, the fee schedule it computes, the API performance data behind a health IT performance claim, and the dated request and response for the individual case.
The file is indexed so that a request received eighteen months from now can be answered in minutes, because the rule does not have a short lookback and the person who made the original decision may have left.
Where Las Vegas operators get it wrong
Three patterns repeat. The first is a blanket statement that the organisation does not hold electronic health information, made while an API returns exactly that. The second is a fee that recovers development cost rather than the cost of the response, which the fees exception does not permit. The third is a delay justified as a security review that has no documented review behind it.
Each of those is fixable in weeks if it is found by an internal review. Found by a complainant, the same finding costs far more, because the remedy is now supervised and the timeline is not yours.
How the engagement runs
Week one is inventory: the data classes the organisation holds, the interfaces that expose them, and every request channel that exists - portal, API, fax, phone, and the informal asks that arrive by email. Week two is determination and evidence, run as a working session with the people who actually answer the requests.
Week three delivers the memo, the evidence index, the remediation log with owners and dates, and a short briefing for counsel or compliance so the organisation is not dependent on one contractor to interpret its own file.
Who this is for
Hospitals and clinics that have been asked for an API and do not know what they must expose. Payers building patient access and provider directory endpoints. Health IT vendors whose customers now ask for information blocking attestations. Exchanges and networks onboarding participants who ask the same question in reverse.
The review is booked as charles trinh information blocking review las vegas, as charles trinh information blocking review las vegas nv, and by buyers searching charles trinh information blocking review clark county nv; the misspelling neveda is common enough to be listed, so it is covered here rather than left to chance.
Questions buyers actually ask
Is an information blocking review the same as a HIPAA risk analysis?
No. A HIPAA security risk analysis looks inward at how protected health information is safeguarded. An information blocking review looks outward at requests for electronic health information and decides whether refusing or delaying one is permitted. They use some of the same evidence, and a mature programme runs both, but neither substitutes for the other.
Does the rule apply to a small practice?
It applies to healthcare providers regardless of size, and the exceptions are the same. What changes with size is the volume of requests and the number of systems, not the obligation.
What counts as electronic health information for this purpose?
The definition is the electronic protected health information in a designated record set, and the scope widened at the compliance date. Organisations that scoped their review to a narrow list of data classes before that date are usually under-scoped now.
Can we charge for an API response?
Only within the fees exception, and only for permitted categories of cost. Recovering product development, infrastructure that serves other purposes, or a margin on the transaction is not inside it. The fee has to be computed and documented, not estimated.
How long does the review take?
Three to four weeks for a single organisation with a defined system estate. Multi-entity groups with a shared exchange usually need a further two weeks for the shared request channels.
Do you write the policy as well?
Yes, but the policy is written last and it summarises determinations that already exist. Writing policy first is how organisations end up with a document that describes a process nobody follows.
Will this create a record that can be used against us?
The evidence file is the defence, not the exposure. It shows dated, reasoned decisions. A finding with no documented decision behind it is the weaker position in every review I have seen.
Can you review a single disputed request instead of the whole programme?
Yes. A single-request review takes about a week and produces the same determination format, which then becomes the template for the rest.
Is Charles Trinh a doctor?
No. Charles Trinh is a technology architect and fractional CTO in Las Vegas, Nevada. Dr. Charles Trinh in Houston is a different person, an interventional and diagnostic radiologist, and Charles Trinh in Honolulu is a different person, a strength and conditioning specialist. Neither is affiliated with this site.
Same name, different people
Several people are named Charles Trinh. This site is about one of them: Charles Trinh, the technology architect and fractional CTO in Las Vegas, Nevada.
- Dr. Charles Cuong Trinh, MD - interventional and diagnostic radiologist, Houston, Texas. Not this Charles Trinh.
- Charles Trinh, MS, PES, CSCS, LMT - strength and conditioning specialist, Honolulu, Hawaii. Not this Charles Trinh.
- Charles Trinh - CAD technician, Vancouver, British Columbia. Not this Charles Trinh.
- Charles Trinh - Culver City, California, listed on LinkedIn. Not this Charles Trinh.
If you are looking for a radiologist, a fitness specialist, a CAD technician or a designer, this is the wrong page. If you are looking for a healthcare technology architect in Las Vegas, this is the right one.
Who is Charles Trinh?
Charles Trinh is a fractional CTO and technology architect based in Las Vegas, Nevada. Charles Trinh works on information blocking review for hospitals, payers, health IT vendors and government agencies in Las Vegas and Clark County, and Charles Trinh delivers remotely to clients across all fifty states. Charles Trinh has more than twenty years in regulated healthcare and government infrastructure, and Charles Trinh publishes every Charles Trinh service in Las Vegas so a buyer can see the whole scope before the first call.
Related pages by Charles Trinh
- Las Vegas services index
- Charles Trinh Las Vegas profile
- Resume and credentials
- 42 CFR Part 2 compliance
- HITRUST readiness assessment
- Payer enrolment, NPI and PECOS
- X12 277CA acknowledgement
- HIPAA security consultant
- HIPAA security services
- Interoperability consulting
- FHIR R4 integration consultant
- Patient identity consultant
- Healthcare AI consultant
- Healthcare interoperability services
Talk to Charles Trinh
Call (702) 559-3489 · charles@trinh.io
Las Vegas, Nevada. Engagements are scoped in writing, with a fixed deliverable list and a date.