PMS
Dentrix
Patient and claim lookup with a dedicated least-privilege user (for example DenialBot). Document Center files attach via Export / Save As PDF or JPEG. Seamless .ZENI access is a later vendor bridge.
Integrations
Works beside the stack you already run.
Phase 1 is dental: Dentrix, Dexis, Eaglesoft, inbox, scanner, and a package you upload in Vyne. Chiropractic and small medical offices are next on the map — same workflow, different backends.
Phase 1 · shipping
Dental practice software
Vendor names describe compatibility. ClaimMend is independent software from Network Specs, not a product of those companies.
Imaging
Dexis 9 and 10
Dexis 9: folder walk on the configured image path. Dexis 10: SQL Server connection with schema discovery, path/blob export, and manual browse fallback.
PMS + imaging
Eaglesoft
Documents and images are open folders. Point ClaimMend at the shares. No API key for the demo path.
Submit path
Vyne (manual)
Phase 1 stores Vyne login for your reference and exports a folder. Staff upload the package in Vyne. There is no Vyne API auto-submit in this release.
Inbox
Gmail, Outlook, IMAP
Polls about every 20 minutes for denial-like mail, de-duplicates, marks handled messages read, and can load the attachment into the workflow.
Paper
Scanner or file upload
Windows TWAIN/WIA when a scanner is present. Otherwise browse for PDF or image. Same analyze → resolve → export path.
What’s next
Same workflow. Swappable backends.
The product was built so scan → analyze → resolve → preview → export stays fixed. PMS, imaging, and procedure codes are the parts that change.
ChiroTouch and chiropractic
Next specialty after dental: small offices, imaging-heavy denials, ChiroTouch-class practice management. Not in the Phase 1 installer today.
Small physician offices
Family practice and other small medical groups are on the later map (CPT/ICD, other PMS). ClaimMend is not an Epic or hospital RCM product in this release.
Other claim sites
The export folder is meant for Vyne or any clearinghouse/claim portal the office already uses. Auto-handoff APIs are Phase 2.
Ask about your stack
If you run something we have not listed, that is a conversation. Phase 1 needs a denial letter plus a way to reach imaging and documents.