Status of AI documentation

[Aleida Lanza]

I have many questions:

Why is there no status as to AI documentation in bluebutton?

Will EOBs ever disclose use of A.I. Scribe in creation of clinical notes?

How will patients know when A.I. is accessing their records?

Where does Bluebutton provide transparency in A.I. assisted claims generation?

If EOB does not track this, why not? 

How does a patient detect when claims are submitted using AI Agents and / or AI scribes?

If patients are having claims generated by AI, and claims denied by AI, how does a patient distinguish human vs AI claims generation?

How will CMS know what part of its budget is going to pay for AI generated vs provider generated documentation?  

How does a patient detect claims that are hallucinations if they can’t get IMMEDIATE access to the clinical note to verify the CLAIM is not hallucinated?

If courts don’t allow AI generated pleadings, why are they allowed in AI generated claims to CMS without distinguishing AI originator?

Asking for 350 million friends.

A

On Mar 16, 2026, at 8:04 PM, Developer Group for CMS Blue Button API <developer-group-for...@googlegroups.com> wrote:



Hi Sameer,

Thanks for your interest in Blue Button v3! It is currently under development and we plan to launch this spring. As we get close to general availability we will be sending out announcements about it, so stay tuned.

If you are in the process of having your application approved with the Blue Button API, you can still get approved and use v2 of the API until it is available.

We are also actively taking feedback, so if there is something you’d like us to to address in v3, or features you are looking forward to, please let us know.

Best,
-The Blue Button API Team

On Monday, March 16, 2026 at 1:59:13 PM UTC-7 sameer...@gmail.com wrote:

Hi -- was curious about the current development status/expected launch date of 2.0 v3. The most recent info I can find on this is from the August 2025 office hours slides, which don't specify a timeline. Thanks!

--
You received this message because you are subscribed to the Google Groups "Developer Group for CMS Blue Button API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developer-group-for-cms-b...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/developer-group-for-cms-blue-button-api/1cd39496-ddd0-40b6-b499-efbd989c3773n%40googlegroups.com.

[Developer Group for CMS Blue Button API]

Hello,

Thank you for your thoughtful questions. We understand there is growing interest in how AI may be used across the healthcare ecosystem.

To clarify the role of the Blue Button API: it provides access to Medicare claims data as it is made available from CMS systems. Blue Button does not generate, adjudicate, or modify claims content. Its primary function is to make this data accessible in a standardized FHIR format.

Because of this, Blue Button does not have visibility into, nor does it track, whether AI tools may have been used upstream in the creation of clinical documentation or claims submitted by providers. Questions related to provider documentation practices, claims generation, or adjudication processes are outside the scope of the Blue Button API.

For more information on the data that is available through Blue Button, including field-level details, please see:
https://bluebutton.cms.gov/data/understanding-the-data/

Additionally, the Blue Button API and Beneficiary FHIR Data (BFD) model are open source, which may be helpful if you are looking for further transparency into how the data is structured and delivered.

We appreciate your engagement and feedback.

Best,
-The Blue Button API Team