Skip to main content
phealth

Why Signal

The engine — not the platform, the pipe, or the library.

Signal is the intelligence layer between a generic messaging pipe and a free federal content library: sequencing, an audience-safety verdict, and a receptivity read, delivered as a self-serve API.

Display mode never touches PHI — no BAA to start. Federally sourced, not medical advice.

Where Signal fits

Four neighbors, one gap.

Nobody else sells a self-serve, federally-sourced, adaptive health-messaging API. What exists are three adjacent categories, each owning one piece of the job — and a gap in the middle that none of them fill.

Adopt wholesale

Adaptive care platforms

Two-way care messaging you adopt wholesale — sales-led, EHR-integrated, a rip-and-replace project. Powerful inside their world, but not something a developer can try this afternoon, and not built to drop into yours.

Generic transport

Messaging pipes

The transport layer — they send the SMS, email, or push reliably, at scale. But they decide nothing about what to send, whether it is safe, or when it will land. You build the content, the safety layer, and the timing yourself.

The library

Free content APIs

Federal health content, free to pull — the same libraries Signal sources from. Static facts, lists, and tips, with no sequencing, no audience-safety verdict, and nothing that decides what comes next.

Each owns one column. Signal sits in the gap none of them fill — the engine between the pipe and the library: it decides what to send next, proves it is audience-safe, and reads receptivity, on a federally-sourced library, self-serve.

At a glance

The same job, four different stopping points.

Skim the columns — each neighbor stops somewhere Signal keeps going. Where Signal stops is deliberate: it is the engine, not the platform.

Adaptive care platforms

Adopt wholesale

Messaging pipes

Generic transport

Free content APIs

The library

Signal

The engine

Adaptive sequencing — next message on each reply
Yes, inside the platform
No — you build it
No — static content
Yes — on every reply
Receptivity read — whether and when to send
Limited
No
No
Yes — on every reply
Audience-safety verdict + federal provenance
Partial
No
Provenance only
Yes — by default
Developer self-serve — keyless try, API, SDKs, MCP
No — sales-led
Yes
Yes
Yes — keyless to try
Federally-sourced library included
Their own content
No
Yes
Yes — facts, lists, and tips
Delivery, EHR, managed service
Yes
Delivery only
No
By design, no — you keep your stack
What Signal is not

Signal is not a managed care platform, it does not integrate with your EHR, and by default it does not send on your behalf — Display mode renders inside your own product, with no PHI and no BAA to start. That asymmetry is deliberate: Signal is the engine, not the platform.

It is federally sourced — CDC, NIH, USPSTF, SAMHSA — with provenance on every message. It is not independently clinician-authored, and it is not medical advice. The value is sequencing, an audience-safety verdict, and a receptivity read on a library you do not have to build or keep current yourself.

Evaluating Signal? Let Claude or ChatGPT do the vendor legwork — paste one prompt.

See how →