The eRx Solution is the prescribing engine inside the eKlotho EMR, exposed as its own module: a prescription composer with RxNorm coding, drug-safety checks run against the chart's own medication and allergy lists, a controlled-substance rulebook with an append-only audit log, and one gateway interface to the practice's configured e-prescribing vendor — DoseSpot or Photon Health — so refills, change requests and transmission status all land in queues the practice actually works.
Most EMRs rent prescribing: a vendor iframe opens over the chart, the vendor owns the workflow, and the chart finds out later — if at all — what was prescribed. The eKlotho eRx module inverts that. The chart owns the truth: drug-interaction and allergy checks run against the chart's own medication and allergy lists rather than a vendor's view of the patient, a signed prescription immediately updates the chart's med list, and inbound events — a refill request, a pharmacy's change proposal, a transmission error — are normalized into queues that look the same regardless of which vendor sent them. The vendor is reduced to what it should be: a certified transmission channel behind one gateway interface.
That gateway is the module's architectural core. Each practice configures its own vendor — DoseSpot over REST or Photon Health over GraphQL — with credentials encrypted per organization; the prescribing screens never change when the vendor does. Every prescription records which vendor carried it, so a cancel or a refill response reaches the right channel even after a practice switches vendors. And when no vendor is configured at all, the platform degrades honestly: a signed prescription lands in a QUEUED status instead of TRANSMITTED, the transmit timestamp stays empty, and the record never claims more than what actually happened — the same graceful-degradation pattern eKlotho applies to every optional integration.
Prescribing safety is enforced at signature, in a fixed order: allergy match, contraindicated-interaction block, quantity ceiling parsed from the sig, and a pediatric age floor — each override-able only with a recorded reason, each override audited. Controlled substances get their own rulebook: schedule classification against a curated catalog, zero refills for Schedule II, a hard block when the prescriber has no active DEA registration, and an append-only controlled-substance log that snapshots the DEA number at signing time and cannot be edited afterwards.
7 modules, each describing what is built today.
A draft-to-signed-to-transmitted state machine with an RxNorm typeahead, sig templates, dispense quantities with a server-derived ceiling, DAW and refill caps.
Interaction, allergy, controlled-substance and quantity checks that run against the chart's own lists, enforced again at signature with audited overrides.
One protocol — authenticate, send, cancel, search pharmacies, check formulary, respond to refills — implemented by a DoseSpot REST client and a Photon Health GraphQL client.
Refill requests, pharmacy change requests and transmission failures as first-class worklists, with a badge count that tells staff what is waiting.
A per-prescription timeline of the message conversation — direction, message type, acknowledgment code, error text — behind a dashboard bucketed by status.
Signing a prescription updates the chart med list by rule, not by copy — and imported medication history is reconciled row by row, never dumped into the chart.
Pharmacy search across the vendor and a local NCPDP-keyed directory, patient pharmacy preferences, and advisory formulary tiers with prior-auth and step-therapy flags.
Runs in fixed order: allergy, contraindicated interaction, quantity ceiling, pediatric age floor.
The chart med list updates immediately; a controlled prescription writes its append-only audit row with the DEA number as of that moment.
Each practice selects DoseSpot or Photon Health once; credentials are encrypted per organization.
Acknowledgments, errors, refill and change requests return as HMAC-verified, replay-safe webhooks and land in the queues.
The practice administrator selects a vendor and enters credentials once; they are encrypted per organization and never displayed again — the config screen only ever confirms that a value is on file.
The prescriber searches RxNorm, picks strength and form, writes the sig from a template or free text, and watches interaction, allergy and controlled-substance checks evaluate live against the chart.
Signature re-runs the safety chain in order — allergy, contraindication, quantity, age floor — updates the chart med list, and, for a controlled drug, writes the append-only audit row with the DEA number as of that moment.
The gateway hands the prescription to the configured vendor and records which vendor carried it; without a configured vendor the prescription is held in QUEUED with its transmit timestamp empty, so the record stays truthful.
Refill requests, change requests and failures arrive in dedicated worklists with badge counts; each decision is one-shot, reasoned and written to the transmission record.
Vocabularies, tiers and matrices drawn from the product documentation — the same terms the software uses.
| Status | Meaning |
|---|---|
| Draft | Being composed; safety checks evaluate live but nothing is committed |
| Queued | Signed with no vendor configured — held honestly, transmit timestamp empty |
| Submitted | Handed to the configured vendor; the carrying vendor is recorded on the prescription |
| Accepted | The pharmacy acknowledged the transmission |
| Failed | The error and acknowledgment code are recorded, and the prescription lands in the failure queue |
| Cancelled / voided | Cancel retracts before transmission; void retracts after it and notifies the pharmacy through the gateway |
| Rule | Enforcement |
|---|---|
| Schedule classification | Every prescription is checked against a curated schedule catalog |
| Schedule II refills | Forced to zero at signature |
| Schedules III–V refills | Capped at five |
| No active DEA registration | Hard block with no override path |
| Audit trail | An append-only log snapshots the DEA number at signing; rows can never be edited afterwards |
| Aspect | DoseSpot | Photon Health |
|---|---|---|
| Transport | REST | GraphQL |
| Authentication | Per-organization credentials, encrypted at rest | OAuth2 client credentials with cached, auto-refreshed tokens |
| What changes on switch | Nothing — screens, queues and records are identical | Nothing — screens, queues and records are identical |
Switching vendors is a credentials change, not a migration.
Every promise on this page maps to something the software actually enforces.
DoseSpot and Photon Health, each behind the same gateway interface. The practice picks one and enters credentials; every prescribing screen, queue and record works identically on either. The vendor holds the pharmacy-network certification and carries the transmission.
The module degrades honestly. A signed prescription lands in a QUEUED status instead of TRANSMITTED and its transmit timestamp stays empty; pharmacy search falls back to the local directory; vendor-dependent lookups return a clear unavailable answer instead of a fake one. Configure credentials and the same records proceed.
From curated rule tables the platform ships and maintains — interaction pairs with severities, a controlled-substance schedule catalog, sig-derived quantity ceilings — with per-network overrides so an organization can tighten the defaults. Checks evaluate against the chart's own medication and allergy lists, and every override requires a recorded reason.
A schedule classification runs on every prescription: Schedule II forces zero refills, Schedules III–V cap at five, and a controlled drug with no active DEA registration on the prescriber is blocked outright with no override. Signing a controlled prescription writes an append-only audit row that snapshots the DEA number at that moment. Identity proofing for electronic controlled-substance prescribing is initiated through the configured vendor.
It is the EMR's prescribing engine, surfaced as its own module. There is no second patient record: the composer reads the chart, signature writes the med list, and the queues live alongside the inbox. A network running the HMO platform sees the same medication data through its own delegated views.
We walk through it with your data and your team — not a canned demo.
Program and billing eligibility are determined by each practice and its payers. Results and alerts do not constitute a medical diagnosis. Third-party names are trademarks of their respective owners and do not imply endorsement.
