- New England's Only Dental-Specific IT Provider
- (207) 333-2206
New York Dental Medicaid Billing: IT Configuration Guide
-
Ezra Angelo
- • September 5, 2026
New York dental Medicaid billing depends on technical configuration as much as it depends on billing policy.
Authorized staff need reliable access to eMedNY and ePACES, while provider identifiers, submitter information, claim-status workflows, prior approvals, and electronic attachments stay consistent across the billing environment.
The IT side should protect PHI, support secure access, and keep the escalation path clear when the problem sits in the portal, browser, workstation, PMS, clearinghouse, or network rather than in coding.
Account access, NPI mapping, ETIN setup, submitter information, browser behavior, clearinghouse configuration, or a software integration can all interrupt the Medicaid billing workflow before coding is the real question.
Keep the billing environment aligned with the current rule set
The page starts with the 2026 NYS Dental Policy and Procedure Code Manual, the current fee schedule, and current eMedNY communications as the operating source for billing configuration.
Use the current manual and fee schedule rather than relying on an older authorization or prior-year workflow.
Configure the correct portal access, supported workstation and browser, and documented user permissions.
Keep the identifiers eMedNY expects consistent across the systems that prepare and submit claims.
Four technical handoffs support electronic Medicaid submission
The page treats ePACES as part of a broader workflow that includes account access, enrollment data, identifiers, claim preparation, and secure documentation.
Give the right staff the correct account, workstation, browser access, and documented permissions.
Keep Medicaid provider ID, ETIN, NPI, email address, and submitter information consistent.
Support electronic dental claims, claim-status requests, eligibility checks, and related submission activity.
Document how billing access is replaced or removed when staff roles change.
Treat authorization workflow and PHI protection as part of the same environment
The page separates prior approval from ordinary claim submission while keeping both inside a secure, documented technical workflow.
Know who submits, where supporting documents are stored, how status is checked, and how the authorization returns to the patient record.
Use unique user access, secure endpoints, appropriate permissions, protected transmission, and logging where available.
Run the Medicaid Configuration Handshake
Connect the claim packet to the systems and configuration data it depends on before a technical failure gets mistaken for a policy or coding problem.
One billing workflow, four technical handoffs
Claim data should carry the same provider, patient, and submitter information expected downstream.
Claims, status, eligibility, prior approval, and secure supporting documentation.
Authorized staff need the right account, browser, workstation, credentials, and documented access process.
Provider ID, ETIN, NPI, email address, and submitter information should remain consistent.
Permissions, secure endpoints, protected documents, authorization status, and access changes belong in the same managed path.
Frequently Asked Questions
Ekim IT Solutions supports the IT layer around New York dental Medicaid billing, from provider access and eMedNY tools to eligibility checks, remittance workflows, and staff permissions. We handle the portals, browsers, and software integration so your team can focus on claims.
-
- • September 5, 2026
