Most of the healthcare organizations and staffing firms we work with are not running outdated processes because they do not care about efficiency. They are running them because the processes were built for a workforce that no longer looks the way it did.
When the long-tenured hospital employee was the norm, a single background check at hire made sense. The clinician stayed put. The report sat in a file. Nobody needed to think about it again for years. Travel nurses now move between facilities every thirteen weeks. Per diem clinicians carry active relationships with multiple staffing firms at once. Contract staff return to the same health system two or three times before their first year is up. And each time, large portions of the same screening process start over from scratch.
At Universal Background Screening (UBS), we have been working through this problem directly with healthcare and healthcare staffing clients for over two decades. The picture that keeps emerging is the same: the industry is heading toward a model built around portable, candidate-owned profiles rather than one-time reports. We are not there yet, but the groundwork is being laid now, and organizations that understand the direction will be better positioned when the infrastructure catches up.
Why the Current Model Creates Problems in Healthcare
A travel nurse completes a physical exam, a TB test, an immunization titer series, and a criminal background check for one assignment. Six months later, when she moves to a new facility, many of those credentials are still valid within their defined windows. But because those results live inside a PDF report or a closed platform, the new employer cannot easily act on them. The data is there, technically. Extracting and reusing it cleanly is a different matter.
When systems cannot surface what is current and what has expired, re-running everything becomes the default. That cost distributes across the staffing firm’s margins, the clinician’s time, and the facility’s onboarding calendar.
For healthcare staffing firms running high-volume travel and per diem programs, redundant screening is one of the more consistent sources of cost that never quite makes it onto a line item. A useful diagnostic for your own program: how many times have clinicians in your pipeline completed a TB test, a physical exam, or an immunization titer in the past two years, and of those, how many were actually outside their valid window?
The Idea Behind Candidate-Owned Profiles
A candidate-owned profile changes the fundamental unit of a background check from a packaged report to a set of discrete credentials, each with its own validity window, source record, and reuse logic.
Under this model, a clinician’s identity verification, license and certification status, criminal check history, sanctions screening, occupational health results, and facility-specific requirements all live as structured, portable data tied to the candidate rather than archived in a single employer’s system. With consent, those credentials can be shared across employers, assignments, and hiring programs. Employers run delta checks covering only what has expired or what their specific regulatory context requires, rather than rebuilding the full picture each time.
For the clinician, the practical change is meaningful. Instead of re-entering the same information and waiting through the same process with every new assignment, their verified record updates over time and follows them. For employers and staffing firms, the result is faster time-to-start, lower cumulative screening costs, and better confidence in the accuracy of the data they are relying on.
Why Healthcare Moves First
Clinician mobility in healthcare is structural. The travel nursing market, per diem staffing, and contract models are not anomalies to be managed around. They are how healthcare systems cover demand fluctuations, specialty gaps, and seasonal volume. The workforce is mobile because the work requires it.
Healthcare credentials also happen to be well-suited to a portable, structured model in a way that softer background information is not. Licenses carry defined validity periods and primary source verification pathways. Occupational health results like TB tests and titers have clear windows. Sanctions and exclusions monitoring follows its own ongoing logic. These are verifiable data points with known lifecycles, which makes them considerably more tractable as portable credentials than many other types of background information.
The compliance obligations in healthcare are also what will shape how carefully this model develops. Joint Commission accreditation requirements, OIG exclusion standards, state licensing rules, and HIPAA-aligned data handling practices all have to be accounted for in any portable profile architecture. Movement toward candidate-owned models in healthcare will be deliberate precisely because the regulatory environment demands it, and that deliberateness is likely to produce more durable implementations than faster-moving industries with fewer constraints.
The Technical Foundation: Credential-Centric Architecture
Candidate-owned profiles are not a product that gets switched on but an extension of architectural work that screening providers should already be doing: moving from report-centric to credential-centric design.
At UBS, we have been building in this direction for several years. In practice, that means treating each screening element as a discrete data object rather than a line item in a static report. A TB test result is stored with its completion date, its valid-through window, the collection site details, and the medical review status. A professional license verification is stored with the license number, the issuing board, the expiration date, and the primary source confirmation. A criminal check is stored at the jurisdiction level, with the logic that determines how long it remains usable for a given role or facility type.
Storing credentials this way makes two things possible that the legacy model handles poorly: reuse, when a credential is still valid for a specific use case it can be surfaced and applied rather than re-ordered; and portability, because structured credential data is far easier to include in a candidate-owned profile than a flat PDF.
Our credential-based API integrations with ATS and VMS platforms, including healthcare-specific providers like symplr and LaborEdge, are built around this level of granularity. Credential requests go out individually or in logical groups. Results come back in a structured format that your systems can store and act on. Multiple business units or facilities can reference the same valid credential without triggering a new order.
What the Model Could Look Like in Practice
The specific architecture of candidate-owned profiles will vary by implementation, and the governance structures to support them at scale are still being worked out across the industry. The general shape, though, is becoming clearer.
For candidates, it likely means a secure digital profile, through a trusted platform or consortium, where they can view and manage their credentials, grant or revoke access for specific employers and assignments, and see what is current, what is expiring, and what is missing for a role they want to pursue.
For employers and staffing firms, it means receiving structured, verified credential data from that profile as the starting point for onboarding, then running targeted delta checks to fill gaps or meet program-specific requirements. The API architecture already in place for credential-level integrations is the same infrastructure that would support pulling from a candidate’s portable record.
For a provider like UBS, the role in this model is less about generating a one-time report and more about verifying, refreshing, and expanding candidates’ records over time, maintaining compliance controls and audit trails across the profile lifecycle, and building the integrations that let employers consume portable credential data safely. Human review on sensitive items, including potentially reportable criminal records, stays in place. The rigor has to travel with the credential for the model to work.
The Questions That Still Need Answering
Candidate-owned profiles are a direction of travel with real unresolved questions around them:
Who sets the standards for credential validity and reuse across employers?
How are privacy and consent rights protected when a candidate’s profile is accessed by multiple parties?
Who bears liability if a reused credential is later found to be invalid or outdated?
How do different platforms, employers, and screening providers connect to shared profile infrastructure without creating interoperability problems?
These are the kinds of questions that require collaboration among screening providers, healthcare employers, staffing firms, regulators, and technology partners. The answers will shape how quickly the market is able to move with confidence.
What You Can Do Right Now
The steps that prepare your program for candidate-owned profiles are largely the same steps that improve your current program. Starting there is worth doing regardless of how the portable profile landscape develops.
Internally, it helps to shift how your team thinks about screening results. A background check is a set of discrete credentials with their own lifecycles, not a single report. That framing changes the questions you ask of your vendor and your technology.
- Audit where your program is creating redundancy. If clinicians are regularly completing physicals, TB tests, and titers that are still within valid windows from a prior assignment, that is both an immediate cost problem and a signal that your current architecture is not built for reuse.
- Push your integrations toward credential-level granularity. ATS and VMS connections that receive structured credential data at the component level are the same infrastructure that will eventually connect to portable candidate profiles. Building that now is useful in either scenario.
- Ask your screening provider directly how their architecture handles structured credential storage and reuse, and how they are thinking about more portable, candidate-centric models. The answer is a reasonable indicator of whether they are positioned to be a useful partner as the model matures.
Where This Is Heading
Healthcare employers will always need reliable, compliant, context-specific screening. The underlying requirement does not change. What is changing is how the results of that screening get packaged, stored, and used across a clinician’s career rather than within a single employer relationship.
At UBS, roughly 70% of our business is in healthcare and healthcare staffing. We have worked at this problem long enough to have a clear view of both how carefully the industry needs to move and what the infrastructure investments being made now are actually for. Organizations building toward credential-centric architecture today are not just solving a current efficiency problem. They are positioning themselves to participate in a model that will, over time, change what it means to onboard a clinician you have already worked with before.
Universal Background Screening has been recognized by HRO Today as the number one enterprise background screening firm for 14 consecutive years, the only screening firm to achieve that distinction. To learn more about UBS’s credential-centric approach to healthcare background screening, contact us today.
