The eKlotho EMR is where clinicians chart, prescribe, order and bill — built on the same patient record the health plan and the IPA already manage. Inbox, charting, e-prescribing, labs, imaging, referrals, an AI ambient scribe, telehealth workflow, encounter billing, reports and practice settings, with coverage, care gaps and risk context in the chart.
Most EMRs stop at the clinic wall. Payers, delegation, authorizations and quality live somewhere else, reconciled by interface engines, fax and phone. The eKlotho EMR is the clinical surface of a network platform: it shares the Nexus patient record and entity graph, so the patient in the chart is the same patient the plan covers and the IPA reports on. There is no second copy and no nightly sync. A clinician opens the inbox, sees today's patients, documents the visit — often from an AI-drafted note — sends the prescription, orders the labs and signs, and the signed encounter is already visible to billing, quality and the network.
That does not make it only for network clinics. A standalone practice gets a complete EMR: an inbox-driven workflow, full coded charting, vendor-connected e-prescribing, lab and imaging orders, referrals, an ambient scribe, telehealth workflow, encounter billing, portal administration, reports and practice settings. A clinic inside an IPA additionally gets what no clinic-only EMR can offer — a referral that opens the IPA's own prior-authorization queue under the delegation contract, care gaps and RAF/HCC (risk-adjustment) context in the chart, and cross-clinic continuity on one record when a patient moves between sites.
The chart is organized the way clinicians think: demographics and insurance preloaded from the shared record, a problem list coded in ICD-10, medications in RxNorm, allergies, immunizations, vitals, assessments and screenings, labs with LOINC codes, imaging, referrals, prescriptions, documents, consent and billing history, with RPM and CCM (remote monitoring and chronic care management) context and PACE sections where they apply. Signed notes lock and change only by addendum; patient timelines, merges and the per-chart access log are append-only, so the record can always answer what changed, when, and who did it.
Needs · To finish the note before the next patient, with results and refills that need a decision in one list, and the prior auth handled without a fax.
Gets · An inbox of abnormal and pending labs, open imaging, open referrals and refill requests; an AI-drafted note to review and sign; care gaps and HCC suggestions on the same page; and a referral that opens the IPA's authorization workflow from the chart.
Needs · To chart and prescribe independently while supervised notes reach the attending without sticky notes.
Gets · Full charting and vendor-connected e-prescribing, and a co-sign workflow where the signed note sits in the attending's queue until counter-signed.
Needs · Vitals, screenings and immunizations captured quickly, and callbacks tracked so nothing waits on memory.
Gets · Encounter vitals and screening entry, immunization and procedure history, a tasks list with patient, priority and due date, and critical-result callback tracking with SLA.
Needs · A day's schedule, check-in that opens the encounter, and a coverage answer before the patient sits down.
Gets · Provider availability and booking, check-in that creates the encounter, coverage status from the patient's enrolled insurance records, and portal invitations and appointment requests to triage.
Needs · Charges captured on the encounter, not re-keyed from the note, and denials in one place.
Gets · Billing items built on signature with a suggested E&M level and bundling edits, the superbill and draft claim, a claim worklist by status with appeals, and per-patient statements and payment history.
Needs · Users, rosters, payer enrollments, branding and legal text administered in one place, with a record of who touched which chart.
Gets · Account pages for practice info, billing entity, payer enrollments, provider roster with NPI verification and delegated scopes; MFA and passkeys; the practice's quality reports; and a per-patient access log with CSV export.
| Area | Today | With EMR Solution |
|---|---|---|
| Results follow-up | Results arrive by fax or interface and sit in a folder until someone opens each chart. | Results land in the inbox flagged abnormal or critical; critical values open a callback item, and signing clears the row. |
| Prior authorization | The MA prints a cover sheet, faxes the plan, waits days, and re-keys the auth number when it comes back by phone. | The referral reads the delegation contract, opens the auth in the IPA's own queue or auto-approves it, and the number appears on the referral row. |
| Documentation | The clinician types the note after hours, or pays a separate scribe service that knows nothing about the payer. | The ambient scribe drafts the note and proposes HCC codes and gap closures; the clinician edits, signs and remains the author of record. |
| Prescribing | Controlled substances are printed or handled in a separate vendor portal with its own login. | Prescriptions go through the practice's configured vendor from inside the chart, with interaction and allergy checks against the chart and a controlled-substance log. |
| Coverage, quality and risk | Coverage is confirmed by phone; HEDIS gaps come from a payer spreadsheet; RAF is a surprise after year end. | Coverage reads from enrolled insurance records, care gaps sit in the chart on the IPA's record, and HCC is recomputed when the encounter is signed. |
| Changing clinics inside the network | A patient seen at a second site becomes a second record, with history re-entered or faxed over. | The same patient row opens at the second site; the chart, authorizations and gaps travel with the patient. |
11 modules, each describing what is built today.
The first screen of the day: everything that needs the clinician's decision, organized into queues, with the top header's patient search, AI assistant, user guide, internal chat, notifications and account tools on every page.
Problem-oriented charting with structured, coded data and a note workflow that locks on signature, supports co-signature, and fans out downstream when the encounter closes.
Electronic prescribing through the practice's configured vendor (DoseSpot or Photon Health), with drug-safety checks run against the chart, refill and change-request queues, and controlled-substance support through the vendor.
Order, route and review results without leaving the chart. The order and the result are the same row: pending, then resulted, then signed.
Imaging orders with modality, body region and clinical indication, routed to a facility from the practice's directory, with report ingestion, critical-finding acknowledgment and ABN generation for Medicare patients.
Outgoing referrals tracked to closure — and, for clinics inside an IPA, the referral itself opens the prior-authorization workflow under the delegation contract.
With patient consent, the visit is transcribed and a draft note is produced for the clinician to review, edit and sign. The scribe also proposes HCC codes and care-gap closures that the clinician accepts or rejects.
Telehealth visits scheduled and run from the same chart window, with licensure checks, recording consent and place-of-service handling. The video layer connects to a vendor under the practice's agreement (vendor selection pending).
Charge capture on the encounter builds the superbill and the claim, which is worked in the same claims engine the IPA uses — no parallel billing system.
Clinician-side controls for the patient portal — accounts, invitations, proxy access, result release and secure threads — plus internal provider-to-provider chat scoped to the organization. The patient-facing site is a separate deployment.
Quality and productivity reports computed by the Nexus engine and scoped to the clinician's panel, FHIR bulk export, and the per-user Settings and org-level Account pages a practice needs to run itself.
The first rule is hard isolation between organizations. Every session token names the user's organization and the exact set of entities it may reach, and every chart request is resolved against the patient's entity through those grants. A clinician at one IPA cannot open another IPA's chart — not hidden, but unreachable: the query returns nothing, because access is computed from the entity graph rather than checked against a list someone maintains.
Inside an organization, access is a posture the practice chooses, not one hard-coded rule. A small clinic where everyone covers for everyone can run an open chart. A larger group scopes each provider's patient list to their panel through care-team membership — so cross-coverage works by adding a clinician to the care team, not by opening every record to everyone.
Writing is tighter than reading. An encounter note belongs to its attending: the attending and the care team can edit; other clinicians can read but not change it. Supervised clinicians' signed notes wait in the co-sign queue until the attending counter-signs, so accountability for the clinical record always has one name on it. And every chart open is written to the per-patient access log, exportable the day compliance asks who touched a record.
Every encounter moves through five phases — schedule and intake, document, order, close and code, follow-up — and every phase reads and writes the same shared record. Booking creates the encounter; check-in confirms coverage from the patient's enrolled insurance; the medical assistant records vitals; and the provider opens a chart whose demographics, history and medication list are already loaded, because they were never anywhere else.
Documenting and ordering happen on the same page. The ambient scribe drafts the note while problems, screenings and care gaps sit alongside it; prescriptions, lab and imaging orders and referrals go out coded, and a referral reads the delegation contract on its way out. Signing closes the phase: the note locks, a level of service is suggested from what was documented, and the superbill becomes the draft claim.
Follow-up runs back through the inbox — results return flagged, the patient gets a letter, follow-up tasks are created, and the problem list and medications are already current for the next visit. The two questions every EMR evaluation asks — how does charting reach billing, and where does the data live — share one answer here: they are rows on the same patient.
Signature is the pivot of the whole system, so it is engineered to never fail from the clinician's chair. The moment a note is signed it locks — from then on it changes only by visible addendum — and three downstream jobs dispatch: render and file the after-visit summary PDF, build the draft claim from the documented codes and diagnoses, and recompute the patient's HCC risk summary from the updated problem list.
The fan-out runs through an outbox with one row per encounter and effect, so each job is tracked individually. If any step fails — a render error, a busy queue, a service briefly down — the signature still succeeds for the clinician, and a scheduled job retries the failed effect until it lands. Nothing downstream ever depends on the clinician waiting at the screen, and nothing is silently skipped.
Because the encounter is a row on the shared record, the signed visit is visible to billing, quality and the network's reporting the moment it closes — no export, no interface run, no nightly batch to reconcile the clinical and business views of the same care. That is the difference between an EMR that talks to the network and one that lives inside it.
The EMR never talks to the national pharmacy network directly. Prescriptions route through the practice's configured vendor — DoseSpot or Photon Health — and every vendor sits behind one gateway interface inside the EMR, so the rest of the system never learns which vendor is on the wire. Which vendor a practice uses is per-practice configuration: two practices on the same platform can run different vendors at the same time, and the clinician's screen is identical either way.
The chart, not the vendor, owns the truth. Drug-interaction and allergy checks run against the chart's own medication and allergy lists rather than the vendor's view of the patient; vendor responses are transformed into the chart's medication records; and inbound events — a refill request, a pharmacy's change proposal, a transmit failure — are normalized so the eRx queues look the same regardless of which vendor sent them.
Controlled substances go through the vendor's identity proofing and two-factor signing, with the EMR triggering the flow and keeping its own controlled-substance audit log as the practice's permanent record of every controlled prescription. Because the vendor holds the network certification and the chart holds the clinical truth, switching vendors is a configuration change — not a chart migration, not a data export, and not a new workflow for the clinician to relearn.
A chart is only as useful as its coding, and most EMRs make the practice pay for coding twice — in license fees, and in coupling to a vendor's proprietary catalog. This chart draws its core vocabularies from public national sources: RxNorm and LOINC from the National Library of Medicine, ICD-10, HCPCS and the HCC risk model from CMS, drug packaging from the FDA's NDC directory, and provider identity from the NPPES NPI registry.
Each lookup is cached in local database tables, so drug and diagnosis autocomplete stays fast in the exam room, public rate limits are never in the clinical path, and the chart keeps working if a national service is briefly unavailable — the cache answers and refreshes later. Catalogs update from the authoritative source on the platform's schedule, not through a middleman contract with its own renewal cycle.
The one deliberate exception is the procedure vocabulary that requires a commercial license: those codes come through the practice's own licensed catalog rather than being bundled into the platform and re-billed at a markup. The practical effect is that the code sets doing the heavy lifting — quality measurement, risk adjustment, prescribing safety and interoperability — carry no per-seat terminology fee at all.
Switching EMRs usually costs months because the new system has nowhere to put coded data. Here the terminology catalogs and a reconciliation key already exist in the schema, so migration is mapping into targets that exist rather than building them. Intake accepts, in order of richness, C-CDA and FHIR exports, HL7 v2 feeds, CSV or database dumps, and scanned PDF as a last resort.
Nothing writes to a live table directly. Extracts land in a staging area; codes are normalized against the live catalogs — diagnoses, medications, allergies, labs, immunizations; identities are matched and deduplicated, with conflicts routed to a human review queue rather than auto-merged; and every staged row is stamped with its legacy key for traceability and rollback. Anything that cannot be coded is quarantined for manual review, never silently dropped.
The load commits only when staged counts reconcile against the source manifest, with every variance itemized — sign-off is on numbers, not a demo. Risk scores are then recomputed from the loaded diagnoses rather than copied, which routinely surfaces documentation the old system missed. Practices choose the cutover: phased by domain, a short parallel run, a single-weekend switch for small clean panels, or an active-patients load with the older history attached as a searchable archive.
Abnormal and pending labs, open imaging and referrals, refill requests, tasks and co-signs are queued per user; the clinician works the queue instead of hunting through charts.
Check-in opens the encounter with demographics, insurance and history already on the shared record; vitals and screenings are captured; the ambient scribe drafts the note while problems, medications and care gaps sit on the same page.
Labs, imaging and prescriptions go out coded through the configured vendors and facilities; a referral reads the delegation contract and opens the authorization where the IPA owns it. Results route back to the inbox.
Signing locks the note, files the after-visit summary, builds the draft claim and recomputes the patient's HCC summary; the superbill is reviewed and the claim handed to the network's claims engine.
Results and consult notes come back to the same queues; the patient gets a result letter, follow-up tasks are created, and a service that closes a care gap credits the measure on the shared record.
Coverage status, care gaps, RPM and CCM data and quality measures are the same rows the IPA works from — nothing is exported, mapped or re-keyed.
Every promise on this page maps to something the software actually enforces.
No. Standalone and non-network clinics get the full EMR. Network affiliation adds the delegation-aware referral workflow, care gaps from the shared record and cross-clinic continuity; it is never assumed.
The referral is created immediately. If the clinic is inside an IPA, a hook reads the IPA's delegation with the patient's plan: the auth is auto-approved under the contract's rules, opened for review in the IPA's UM queue, recorded as plan-owned, or marked not required. The result and any authorization number appear on the referral row.
No. Ambient drafting, HCC suggestions and care-gap detection are built in. Every draft and suggestion is reviewed and signed by the clinician; nothing is filed automatically, and every decision is audit-logged.
Through the practice's configured vendor — DoseSpot or Photon Health — behind one gateway interface. Drug-interaction and allergy checks run against the chart. Controlled-substance prescribing uses the vendor's identity proofing, and the EMR keeps a controlled-substance audit log.
The telehealth workflow — lobby, licensure check, recording consent, place-of-service handling and the encounter — exists today. Live video connects through a vendor under the practice's agreement, and that vendor selection is pending.
The EMR manages portal accounts, invitations, proxy access, result release and secure threads from the clinician side. The patient-facing website is a separate deployment configured per practice.
Through an extract, stage, reconcile and load process that accepts C-CDA, FHIR, HL7 v2, CSV or PDF, normalizes codes against the catalogs already in the database, keeps the legacy key on every loaded row for rollback, and quarantines anything that cannot be matched rather than dropping it.
That is a posture the practice chooses. Access never crosses organizations — that isolation is absolute. Within one, a small clinic can run an open chart for full coverage; a larger group scopes patient lists to each provider's care-team panel, note writing is gated to the attending and care team, supervised notes wait for co-sign, and every chart open lands in the per-patient access log.
Diagnoses in ICD-10, medications in RxNorm, labs in LOINC, procedures in HCPCS and risk in the CMS-HCC model — all drawn from public NLM, CMS and FDA sources and cached locally, so there is no per-seat terminology fee. The one exception is the commercially licensed procedure vocabulary, which comes through the practice's own licensed catalog.
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.
