Skip to content

PUERTO RICO

Credentialing in Puerto Rico: no CAQH, and what that changes.

Most credentialing software is built around an assumption that does not hold here — that the provider already has a maintained national profile the plans will accept.

On the mainland, a large share of credentialing effort has been displaced into a shared profile that the provider maintains once and many plans consume. That arrangement shapes the tooling, the timelines and the vendor pitch. In Puerto Rico it does not exist, and the differences compound.

No shared profile means your file is the only file

Without a central profile, each packet is assembled from your records and submitted per plan. Three practical consequences follow:

  • Packet completeness stops being clerical. It determines the submission date, and the submission date determines the effective date. The gap between “we have everything” and “we can prove we have everything” is where weeks go.
  • Nobody else is maintaining currency for you. An expired document does not get flagged by a third party; it gets discovered by a rejection.
  • The same information is submitted repeatedly. Which makes internal consistency a real risk: three plans receiving three slightly different versions of the same work history is a discrepancy waiting to be found.

Licenses verify against ORCPS

Professional licenses in Puerto Rico are issued and registered through the examining boards under ORCPS, which publishes an online verification returning the professional's name, specialty, license number, municipality of practice, issue date, expiration date and current status.

Two operational notes matter more than they appear. First, no national aggregator covers this, so any product claiming universal license verification is either excluding Puerto Rico or doing it manually. Second, ORCPS processes license renewals on a three-year cycle — which means a renewal horizon that is easy to lose track of precisely because it is infrequent enough that nobody develops a habit around it.

PEP is a prerequisite, not a step

The Puerto Rico Medicaid Program requires providers and facilities to be enrolled through the Provider Enrollment Portal (PEP). Treat it as a gate rather than one task among many: work that depends on it does not fail immediately when the registration is missing or lapsed — it fails after the wait, which is the most expensive way for anything to fail.

One concrete trap: an incomplete PEP application expires after 30 days without activity, and an expired application must be started again rather than resumed. An application left half-finished while someone chases a document is not paused; it is on a countdown. Anyone who has restarted one knows the cost; the point of writing it down is that the first time is avoidable.

What this means for how you organize the work

  • Track PEP status as a field on the provider and the facility, with its own date, not as a note. It gates everything downstream.
  • Assume packet assembly is on your critical path, because it is. Start it at offer, not at hire.
  • Verify licenses on a schedule tied to the three-year cycle, and record the verification response — not just the expiration date you typed in.
  • Keep one source for the provider's history so the version that goes to the third plan matches the one that went to the first.
  • Do not assume Medicare enrollment rules carry over. The federal retroactive window described in Medicare retroactive billing is a Medicare rule; Puerto Rico Medicaid and commercial plans set their own terms.

None of this is exotic. It is ordinary credentialing discipline applied to an environment where the shortcuts most tools assume are absent — which is why a platform built inside these constraints, rather than adapted to them afterward, tends to fit better. That is the argument behind provider credentialing and payer enrollment in RIEL, and it is worth judging against your own workflow rather than against a feature list.

Primary sources

Every regulatory statement above traces to one of these. Read them for their exact terms — this page is a summary, not a substitute, and nothing here is legal or regulatory advice.

Is PEP status a field in your system, or a thing people remember?

It gates everything downstream, and it fails after the wait rather than before it. That is the one worth fixing first.