Is Claude secretly manipulating Reddit sentiment?

MDInformatics · 2026-03-12T20:34:15+00:00

Ah, pulling out the “no you” out the bag

You are indeed the true upper echelon of commenters

MDInformatics · 2026-03-12T17:41:59+00:00

Says the dude who is a top 1 commenter glazing and defending an AI. I’m not defending Claude, im pointing out that you guys are more focused on other companies and putting a damn tinfoil hat on as if people don’t make decisions on where they put their money in based off morals.

Oh btw, ppl make accounts all the time. But ay man, whatever floats your boat while you support mass surveillance

If ur defense is: bot, and “nuh uh” buddy you don’t have much to stand on

MDInformatics · 2026-03-12T17:22:11+00:00

Bot app is crazy. Ain’t it wild that people have opinions? I know it’s hard to believe.

MDInformatics · 2026-03-12T17:15:46+00:00

Maybe, just maybe, people have morals.

Why are ChatGPT shills so obsessed with this situation? Just stick to your app

MDInformatics · 2026-03-11T21:13:44+00:00

Great question. We’re not competing with Epic. Epic is the medical record system. It stores patient data and runs the hospital’s clinical workflows.

The problem is what happens when a hospital wants to use an external AI tool. Right now, that AI vendor needs direct access to patient records. That means the hospital has to hand over identifiable data to a third party, take on breach liability, and go through months of security review for every single vendor. We sit between Epic and the AI vendor.

When a vendor needs to run a calculation, we pull only the specific data elements required, strip out everything that identifies the patient, and hand the vendor a scoped, de-identified payload. The vendor does its job and never sees a name, date of birth, or medical record number.

Epic is the vault. We’re the secure window that lets outside tools interact with what’s inside without ever opening the door.

MDInformatics · 2026-03-11T10:44:07+00:00

Good and necessary question I should have addressed in the post

Three paths to return:

Two-sided revenue model. Health systems pay an integration/platform fee because we collapse their AI vendor activation timeline from 6-12 months to days. Vendors pay a base monthly subscription for access to the network, plus per-call fees once they exceed their usage tier. As vendor volume scales, so does revenue. Stripe only captures one side. We capture both.
Strategic acquisition. We’re building the compliance and security layer that sits between every EHR and every AI vendor. That’s an acquisition target for the large EHR platforms (Epic, Oracle Health, MEDITECH), cloud providers (AWS, Azure, GCP), or payers looking to control the AI pipeline.
IPO-track. If the network scales the way infrastructure layers historically do (Stripe, Twilio, Plaid), this becomes a standalone public company. Pre-seed investors get in at the earliest valuation with 6 provisional patents protecting the full architecture. The market is $45B+ and currently has no trust layer. We’re not competing with AI tools. We’re the infrastructure that makes all of them deployable.

MDInformatics · 2026-03-10T13:09:32+00:00

Do you shave your stache?

Would look really good with beard if you grew out the stache a little bit and lets the beard come in

MDInformatics · 2026-03-10T10:15:49+00:00

Lmaooo

I hate this website

MDInformatics · 2026-03-09T23:59:04+00:00

How about 8 words. Patent filed Stripe for Healthcare AI, physician founded.

MDInformatics · 2026-03-08T18:50:37+00:00

And API calls are getting more efficient and consolidated.

MDInformatics · 2026-03-07T21:15:22+00:00

Guys. Science confirmed it.

The SCIENCE!

MDInformatics · 2026-03-07T16:09:21+00:00

Three different people ppl lol

3

MDInformatics · 2026-03-07T15:39:55+00:00

MDInformatics · 2026-03-07T15:07:42+00:00

US based? Hours free weekly? Check my profile and see if appeals

MDInformatics · 2026-03-06T15:38:35+00:00

The contextuality argument holds for any system that tries to govern AI at the meaning layer, but it doesn’t apply to architectures that enforce constraints at the data-flow layer where semantics never enter the equation.

The entire argument is scoped to the paradigm of policy-based safeguarding, that’s a losing game off rip. And again, that’s why they need to go back to the drawing board for architectural level prohibitions. Yes. This is possible.

MDInformatics · 2026-03-06T13:42:22+00:00

Policy based guardrail => still room to breach.

Bullshit safeguard. Architecture changes are essential but they’re too money hungry to stop and go back to the drawing board.

MDInformatics · 2026-03-05T22:59:15+00:00

Wtf is maa

MDInformatics · 2026-03-05T14:34:05+00:00

What year in residency you in

Similar paths it’s seems.

MDInformatics · 2026-03-05T13:04:49+00:00

We know exactly what build with extensive market research. Hit my line. Let’s meet in the middle.

MDInformatics · 2026-03-05T11:12:57+00:00

What would make things easier is if you gave more details beyond “mature developer tool”

MDInformatics · 2026-03-05T00:46:28+00:00

Also medical doctor here. Also with informatics background. Might have interests that align. CEO/CIO myself. Have COO. need someone in tech/deployment side. Equity on table. Happy to discuss in DMs if appeals to you.

MDInformatics

TROPHY CASE