Migration begins with source-system reconstruction
Arctic Health uses the existing vendor export or spreadsheet to enumerate providers, entities, payer relationships, documents, and open work. Current status is then reconstructed from CAQH profiles, live payer portals, licensing boards, provider documents, and the organization’s EHR or billing system.
Exports from MedTrainer, Modio, Medallion, symplr, Compliance Watchdog, or another vendor remain part of the audit trail. They do not automatically determine whether an application is open, a provider is active under the correct TIN, or an expirable is current. Each status is reconciled against the system that controls it.
CAQH profiles supply provider-entered professional and practice information, payer authorizations, attestations, and supporting documents. Payer portals remain necessary because a CAQH profile does not establish the live status of every payer application or enrollment. CAQH provider user guide.
| Stage | Arctic Health action | Customer input | Result |
|---|---|---|---|
| 1. Capture the legacy inventory | Collects available exports, spreadsheets, document folders, shared inbox records, portal access, submission receipts, reference numbers, and open issue notes. | Provides available files and organization-controlled access. A clean export is not required. | One inventory of known providers, entities, locations, payers, documents, and pending work. |
| 2. Rebuild the organization map | Maps each provider to the correct NPI, TIN, legal entity, service location, specialty, payer, and group relationship. | Names one decision-maker to resolve provider, TIN, location, and entity discrepancies. | A confirmed structure for credentialing, contracting, roster maintenance, and reporting. |
| 3. Reconstruct open payer cases | Checks live payer portals, correspondence, confirmation numbers, deficiencies, effective dates, and follow-up history. Stale labels from the legacy system are replaced with the current payer stage. | Escalates access issues or confirms business decisions when a payer record conflicts with the organization map. | Every active case has a verified stage, blocker, next action, and accountable owner. |
| 4. Revalidate expirables | Matches licenses, malpractice coverage, certifications, and other expiring credentials to the underlying document and issuing source. | Supplies provider-controlled documents or signatures requested through the migration queue. | Each expirable has a confirmed date, supporting evidence, provider relationship, and renewal workflow. |
| 5. Configure the operating workflow | Builds custom automations around the organization’s TINs, locations, payer mix, approval rules, follow-up steps, and status destinations. | Confirms who receives requests, who approves structural changes, and where status should appear. | A credentialing workflow mapped to the organization rather than copied from the previous vendor’s template. |
| 6. Cut over active work | Moves verified cases into Arctic Health’s operating queue, continues payer follow-up, and starts new submissions from the reconstructed record. | Responds to the remaining decision or document requests through the agreed channel. | Legacy cases continue from their confirmed stage while new work follows the configured process. |
The reconstructed record has four linked layers
A provider name alone is not enough to establish enrollment status. Arctic Health connects the provider to the organization, payer case, and supporting credentials that govern whether the provider can participate and bill under a specific arrangement.
| Record layer | What Arctic Health records | How it is reconciled |
|---|---|---|
| Provider | Identity, NPI, specialty, CAQH profile, licenses, coverage, documents, and provider-controlled actions. | CAQH data, provider documents, licensing boards, and internal systems are compared for conflicts. |
| Organization | Legal entities, TINs, locations, billing relationships, group affiliations, and responsible decision-makers. | The customer’s confirmed structure is compared with payer portals, EHR records, billing records, and legacy data. |
| Payer case | Payer, product, provider, TIN, location, submission stage, reference number, deficiency, next action, contract status, and effective date. | Live portal status and payer correspondence establish the operating stage. |
| Expirable | Credential type, number, jurisdiction, issue date, expiration date, evidence, renewal status, and affected payer relationships. | The document is checked against the issuing source before the renewed date is propagated to dependent records. |
Responsibilities during the handoff
Arctic Health owns the operational reconciliation and portal work. The customer appoints one decision-maker because disagreements about a provider’s location, TIN, group affiliation, or entity structure require an organizational decision before payer records can be corrected.
| Party | Responsibility | Decision authority |
|---|---|---|
| Arctic Health migration team | Imports available records, operates payer portals, reconciles CAQH and source documents, rebuilds open cases, revalidates expirables, and configures automations. | Determines the operational status supported by source-system evidence and identifies discrepancies requiring customer resolution. |
| Customer decision-maker | Resolves provider, TIN, entity, location, ownership, and internal system conflicts through one consolidated discrepancy queue. | Confirms the organization’s intended legal and operating structure. |
| Providers and internal stakeholders | Complete requested attestations, signatures, access actions, or document requests assigned through the configured workflow. | Control information or approvals that must come from the provider, authorized official, finance team, or practice leadership. |
| Outgoing vendor or former coordinator | Supplies any available export, inbox history, submission confirmations, access inventory, and unresolved work notes. | No ongoing decision role is required after organization-controlled access and records are transferred. |
How execution changes after cutover
The same reconstructed record supports managed credentialing and an in-house platform deployment. The difference is who operates the recurring payer queue after migration.
| Operating area | Managed credentialing service | In-house platform deployment |
|---|---|---|
| Migration reconciliation | Arctic Health rebuilds records and operates source portals. | Arctic Health rebuilds records and configures the platform before the internal team takes over the operating queue. |
| New payer work | Arctic Health prepares, reviews, submits, and follows each application. | The internal team operates the configured workflow, automations, document requests, and submission queue. |
| Ongoing maintenance | Arctic Health manages CAQH maintenance, expirables, recredentialing, payer follow-up, and roster updates. | The internal team manages maintenance through the configured alerts, queues, and automations. |
| Exceptions | Arctic Health leads payer deficiencies, escalations, rejections, ownership changes, and non-routine portal work. | Exceptions remain visible in the platform for internal handling or can be assigned to Arctic Health support. |
Under the managed service, complete new payer applications are submitted within two business days after all required information is available. Each application receives specialist review before submission. Arctic Health credentialing services.
Where credentialing status appears
The Arctic Health platform holds the detailed operating record, including application stage, blocker, next action, effective date, expirable status, and the provider, payer, TIN, and location attached to each case.
- Arctic Health platform: The complete credentialing and payer-operations queue, including source evidence and exception history.
- Existing EHR or billing system: Agreed provider, enrollment, effective-date, and outstanding-item fields can be returned through a configured integration.
- Slack or Microsoft Teams: Document requests, discrepancies, blockers, and operating updates can be routed into the customer’s existing communication workflow.
Custom integrations define the exact source field, destination field, update trigger, and system of record instead of relying on a general data export. See how Arctic Health connects to EHR, practice management, and billing systems.
Illustrative scenario: the credentialing coordinator has left
An 18-provider organization has two TINs, four service locations, seven payer relationships, and a spreadsheet listing 23 pending items. The former coordinator maintained payer status through personal notes, email, and portal logins, so the spreadsheet cannot establish which cases remain active.
- Preserve the starting evidence. Arctic Health collects the spreadsheet, shared inbox, document folders, available credentials, payer messages, submission receipts, and reference numbers.
- Reconstruct the roster. Each of the 18 providers is mapped to the correct TINs, locations, specialties, CAQH profile, and payer relationships.
- Check all 23 pending items. Live payer records establish which cases were submitted, which require a response, which were closed, and which never reached a complete submission.
- Resolve structural conflicts. The customer’s decision-maker answers a consolidated set of questions covering outdated locations, conflicting TINs, and unclear group affiliations.
- Revalidate documents. Licenses, insurance records, and other expirables are matched to current documents and issuing sources before renewal tasks are created.
- Configure future work. Provider requests, payer follow-up, expirable alerts, escalation rules, and status updates are mapped to the organization’s EHR, billing system, Slack, Teams, or Arctic Health platform.
- Resume submissions. Legacy cases continue from their confirmed payer stage. Under managed service, each new application is submitted within two business days after its information is complete.
Related platform comparisons
Frequently asked questions
Do we need a clean export from our current credentialing vendor?
No. Arctic Health can start with a partial export, spreadsheet, document folder, shared inbox, or list of providers and payers. Available legacy data establishes the inventory, while CAQH profiles, payer portals, licensing boards, provider documents, and internal systems establish current status. A complete vendor export reduces discovery work, but the migration process does not treat export quality as proof that a case or credential is current.
What happens if our credentialing coordinator quit and everything was in her head?
Arctic Health reconstructs the operation from the records that still exist and the systems that control the work. The starting set includes provider and entity lists, CAQH access, payer portals, shared email, document storage, the EHR or billing system, and submission reference numbers. Arctic Health then creates a discrepancy queue for the organization’s decision-maker rather than asking multiple employees to reconstruct the former coordinator’s undocumented process.
Who resolves conflicts between CAQH, payer portals, and our internal records?
Arctic Health identifies and documents each conflict, and the customer’s named decision-maker resolves questions about the intended provider, TIN, legal entity, location, or group relationship. Arctic Health then updates the operating record and performs the required portal or workflow action. This split keeps payer reconciliation with the credentialing team while reserving organizational decisions for an authorized customer representative.
What happens to historical records that cannot establish current status?
Historical records remain attached to the migration audit trail, but they do not control the active status field. A legacy note can show that someone intended to submit an application, while a payer confirmation number or live portal record establishes whether submission occurred. The same rule applies to expirables: an old certificate remains part of the file, while the current document and issuing source determine the active expiration date.
Can Arctic Health keep credentialing updates inside our existing systems?
Yes. Arctic Health can place agreed status fields and requests in an existing EHR, practice management system, billing system, Slack workspace, or Microsoft Teams environment. The configured workflow identifies which system owns each field, which events trigger an update, and where failures or discrepancies are routed. Arctic Health’s platform continues to hold the detailed credentialing record behind those operating views.
Does switching require us to outsource credentialing permanently?
No. Arctic Health supports a managed credentialing service and an AI-enabled platform for internal teams. Arctic Health performs the migration reconciliation and custom workflow setup in either model. After cutover, the managed service keeps payer execution with Arctic Health, while an in-house deployment gives the configured submission, follow-up, expirable, and reporting queues to the customer’s credentialing team.