Compliance

ProviderConnect NX for contracted providers: admissions, eligibility, and where workflows stall

LA County DMH's ProviderConnect NX is the mandatory interface to the county's Avatar NX record. Here is what contracted Legal Entity providers do in it, the C-Number and MFA access path, and the friction points β€” from HEAT tickets to post-submission corrections.

IssueVol. I Β· No. 80
Navix HealthOperator Notes
FiledCompliance

If you are a contracted Legal Entity provider on the mental health side of Los Angeles County, ProviderConnect NX is where your county revenue cycle lives. It is the mandatory web interface to the county's Avatar NX record, and it is not optional. This post covers what you do in it, how access works, and the friction points that slow teams down. For the full market context, see the LA County DMH guide.

What PCNX is, and what it touches

ProviderConnect NX (PCNX) is a web interface that communicates in real time with Avatar NX, LACDMH's Netsmart electronic health record. Anything submitted through PCNX updates the county record immediately. Contracted providers use it for admissions, financial eligibility, diagnosis, authorizations, and concurrent review. Because the write-through is real-time, PCNX is effectively the county's front door to your claims β€” which is exactly why the accuracy of what you enter matters so much.

Getting access: C-Number and MFA

Access is gated. Contract providers need a Contractor ID β€” a C-Number β€” to reach DMH applications, and access runs through the county's systems access request process with multi-factor authentication. New staff onboarding is a real project: the request, the credential, and the MFA setup all have to be in place before anyone can work a chart. Build that lead time into your hiring, because a clinician who cannot log into PCNX cannot move a client through admission.

The own-EHR path

Contracted providers are not required to abandon their own EHR. A client must have an open admission and financial eligibility in Avatar NX β€” submitted through the provider EHR via Web Services β€” before an authorization can be created in PCNX, and claims follow the LACDMH 837 5010 companion guide. In other words, your own record can feed the county system for admissions, eligibility, and claims, while authorizations and concurrent review happen in PCNX. See dmh.lacounty.gov for the current interface documentation.

Where workflows stall

Three friction points show up on almost every team:

  1. Corrections after submission. Fixing something already submitted generally means a HEAT help-desk ticket. That is a queue, not a keystroke, so errors are expensive in time.
  2. Access onboarding. The C-Number, SAR, and MFA chain delays new staff.
  3. Double entry. Keeping a clinical record in one place and re-entering admissions and eligibility into PCNX is the same parallel-operations tax that county behavioral health imposes everywhere.

How Navix fits

Navix is designed to fit the Avatar NX Web Services and 837 5010 submission workflow, so admissions, financial eligibility, and claims are produced from the same clinical record your team already documents in β€” and CollaborateMD, our RCM partner, processes the claims. ProviderConnect NX remains the county's system for authorizations and concurrent review; Navix reduces the double entry around it and keeps documentation audit-ready. Confirm current integration specifics with the Navix team and against LACDMH's own materials.

Want to see it on your DMH workflow? Schedule a demo, or read the companion post on residential and PHF concurrent review in ProviderConnect NX.

  • #providerconnect nx
  • #lacdmh
  • #avatar nx
  • #specialty mental health
  • #los angeles county
  • #compliance
All essays
Navix Health Β· Operator Notesβ€” 80 β€”2026
Keep reading

More from the desk.