How It Works

The work behind the work.

Sherpas has spent more than fifteen years working inside healthcare data. That accumulated knowledge shows up in how we approach every retrieval, every provider relationship, and every client program. This page walks through what actually happens on our end, from the moment a request arrives to the moment a chart is delivered.

01 — THE COPY SERVICE MODEL

What happens when a chart request comes in.

When Sherpas serves as the records service partner for a provider, every chart request, audit, or release of information inquiry that arrives routes directly through us. The provider's staff handles patient care. Sherpas handles the rest.

Risk adjustment, HEDIS, and quality programs

A payer or analytics firm sends an audit list. Sherpas receives it, schedules the retrieval, completes the work, and delivers completed charts back to the requester. The provider's staff is not involved in the process beyond their initial agreement to work with Sherpas.

Types:

HEDIS

MRA

CRA

RAC

RADV

Life, legal, disability, and continuity of care

General ROI / non-audit requests — Supporting life insurance, legal, disability, workers’ compensation, continuity of care, transfer of care, and other non-audit needs.

Individual record requests from law firms, life insurance companies, disability evaluators, and care transition teams. Handled remotely. Sherpas processes the request, retrieves the chart, and transmits it to the requesting party.

Types:

Life insurance

Legal

Disability

Step 01

The request arrives

A requester contacts Sherpas directly, or is directed to us by the provider. Sherpas receives the request via phone, email, fax, or through OneView. The request is logged and assigned.
Step 03

We retrieve the charts

A dedicated Sherpas technician accesses the provider's system, onsite or remotely, and retrieves the requested charts. Every chart is quality checked against a 99% assurance standard before it leaves our hands.
Step 02

We validate and schedule

Sherpas verifies the request is complete and valid. For audit requests, we confirm the patient list, the audit type, and the delivery requirements. A retrieval appointment is scheduled based on the provider's setup and the best service mode for that location.
Step 04

We deliver and report

Charts are transmitted directly to the requester in the required format. A full record of the transmission, date, time, destination, and status, is logged in OneView. For audit projects, weekly communication continues until the list is finalized. Typical project timelines run 14 to 60 days.
Want to see how Sherpas can transform your retrieval program?
02 — SERVICE DELIVERY MODES

How Sherpas accesses your records depends on what works best for you.

Sherpas meets providers where they are today while helping them move toward more efficient retrieval over time. Depending on location, EHR environment, and access preferences, retrieval may happen onsite, remotely, or through ZING automation where supported EHR access or API connectivity is available.

Automated via ZING

For providers with a FHIR-ready EHR system, ZING handles the retrieval automatically. Significantly faster than manual remote access and further reduces the number of people who need to log into the provider's system.

Requires: any FHIR-supported EHR or API access granted by the provider.

Remote

Sherpas accesses the provider's system securely from off-site. No disruption to the provider's physical space or staff workflow. Three remote access configurations are available depending on what the provider has in place.

Access options: dedicated login · generic third-party credentials · temporary login created per retrieval.

On site

A Sherpas technician comes to the provider facility and retrieves records directly. Availability depends on local technician coverage in the provider's area. Best for: providers who prefer in-person access, or who are in an area well covered by Sherpas' technician network.

03 — ZING FULL TECHNICAL EXPLANATION

How Sherpas' proprietary automation technology works.

ZING is the automation layer Sherpas built to accelerate retrieval within our internal Everest infrastructure. Where a provider’s EHR system supports it, ZING can take over the retrieval process, reducing the need for a technician to manually navigate the system record by record.

Proprietary

Built by Sherpas

Introduced 2024

Named after TenZING Norgay

ZING is the automation layer Sherpas built to accelerate retrieval within our internal Everest infrastructure. Where a provider’s EHR system supports it, ZING can take over the retrieval process, reducing the need for a technician to manually navigate the system record by record.

Using FHIR-based connectivity, it locates the relevant chart data and delivers it directly to the requester, with expert-in-the-loop review where needed. Provider staff are not pulled into the process, fewer people need system access, and the work moves faster.

How ZING works, step by step:
01

Sherpas receives the chart list from the requester and loads it into the system.

02

ZING connects to the provider's EHR through a FHIR-compliant integration. Additional supported systems can be added quickly.

03

ZING searches and retrieves the relevant chart information automatically, eliminating manual work that would otherwise be required.

04

Charts are delivered in real time directly to the requester. No manual formatting step. No delay between retrieval and transmission.

05

A full record of every transmission is logged in OneView, including date, time, destination, and delivery confirmation.

Performance:
Up to 50x
faster than manual retrieval processes
20–25
records per minute, consistent throughput at high volume
1,000
patients in ~44 minutes — including file preparation and conversion for delivery
How ZING gets connected:

ZING runs through the provider’s existing EHR, either one already on the supported list, or one where API access can be enabled. Sherpas works with your organization to confirm compatibility before deployment. There are two ways in:

Already integrated

Your EHR is already on the supported list, including Epic and other FHIR-compatible systems. ZING deploys quickly with minimal setup on your end.

Vendor integration

Your team initiates the request for your EHR vendor to enable API access for Sherpas. With that access, our integration team handles the technical coordination and next steps so that any back-and-forth stays on our side, not yours.
04 — THE RETRIEVAL PARTNERSHIP MODEL

How the engagement works

When Sherpas is contracted for bulk retrieval, the engagement is fully managed end to end. No existing provider relationship required. You bring the list. We handle access, retrieval, and delivery.

Step 01

You send the chase list

Patient details, dates of service needed, provider locations, and your submission deadline. Received via secure encrypted transmission.
Step 03

We retrieve and quality check

Charts are retrieved provider by provider, with real-time status visible in OneView throughout the project.
Step 02

Sherpas organizes the chase

We assess each provider on the list, determine the right retrieval approach, and schedule access. Remote where possible. Onsite where necessary.
Step 04

You receive complete data

Charts delivered in the format your team needs, with full reporting on every record in the original list, including any that were ineligible, inaccessible, or not found. No surprises at the end of the project.
05 — ONEVIEW IN THE WORKFLOW

Where the portal fits into everything above.

OneView is woven into the retrieval process and how work gets tracked, communicated, and reported. Every step is visible in real time, whether your team is managing it or ours.

OneView Provider in the workflow

OneView gives providers a simpler way to manage chart requests from start to finish. Teams can upload requests quickly, follow status updates as they happen, and keep a permanent record of each completed release, including when it was sent and confirmed.

OneView Payer in the workflow

Payer program teams track every project, every provider, and every chart in real time. With OneView, payer teams can move away from scattered spreadsheets and work in a centralized workspace. Every project, provider, and chart can be tracked in real time, making it easier to manage progress, spot gaps, and keep work moving.

06 — SECURITY IN PRACTICE

How PHI is handled from request to delivery.

Security at Sherpas is operational practice built into every step of the retrieval process. Here is what that looks like end to end.

Secure handling

Sherpas manages PHI in accordance with HIPAA and applicable BAAs. That means encrypted transmission, controlled access by trained personnel, and audit trails across every step of the workflow. Policies and safeguards are reviewed regularly to stay aligned with current regulatory standards and client expectations.

More automation, fewer touchpoints

ZING reduces manual system navigation and removes unnecessary touchpoints from the retrieval process. Fewer hands on each chart means a more controlled, auditable approach to PHI access.

Every person is screened monthly

All Sherpas personnel undergo monthly OIG and BSA screenings and annual HIPAA compliance training and testing. The compliance framework applies to everyone who touches a retrieval, not just those in client-facing roles.

Transmission is encrypted end to end

AES-256 encryption for all data at rest and in transit, with AES-128 used only where required for compatibility or legacy systems. All activity within OneView is protected by multi-factor authentication.

Want to see how Sherpas fits your organization?

We meet you where you are. Talk to our team and find out what that looks like for you.

Talk to our team