Dmitry [LAST NAME]
[TITLE]
Founding engineer at three telehealth companies. Led the e-prescribing integration at two of them.
One API plus an embeddable prescribing UI. We handle the vendor relationship, so your team doesn't have to.
We were founding engineers at telehealth companies. We built the products from the ground up, more than once.
Every time, prescribing meant a vendor integration. Every time, the same problems came back. The API was never the hard part. The vendor was.
So we started Noga Health to deal with the vendor once.
Some status webhooks didn't exist. Getting a missing event added could take months. Until then, our own status could be wrong. We wrote up one case.
Use-case reviews. Test scripts. Certification calls. A lot of process, and very little of it had anything to do with our code.
Vendor dashboards are built for the vendor's support staff. Not for the team trying to find out why a prescription is stuck.
A reconciler polls the prescriptions under every order that hasn't reached a final state. If a webhook never arrives, the status still catches up.
A deterministic validator checks anything an AI proposes before it transmits. The validator decides. The model doesn't.
You build against the Noga Health API. The vendor's field names and conventions never leak into it.
[TITLE]
Founding engineer at three telehealth companies. Led the e-prescribing integration at two of them.
[TITLE]
Built e-prescribing integration work, including auth and token caching, SSO URL generation, webhook dispatch, and pharmacy search.
Noga Health is pre-launch. The sandbox is coming. Join the waitlist and we'll reach out when it's ready.
Want the details first? Read When the vendor's webhooks skip steps.