Getting Through the Onboarding Wall
OneSource Passport by STn Global is the backbone for a lot of mid-market and enterprise mobility programs. You upload an assignment, it calculates taxes, immigration, compensation adjustments, and generates compliance documentation. That part works well enough. The Health Login portal is a different animal. It lives inside the same platform but serves a separate function, handling medical assessments, insurance verification, and fitness-for-duty documentation for relocating employees across borders. I have managed the login issues for this portal on enough assignments to know exactly where the friction lives. The actual interface is stable once you are in, but getting past authentication is where people spend their time.
Onesource Passport Health Login The Definitive Guide To Global Mobility Management
Accessing the health portal requires credentials separate from the main Passport login. When you log into the primary OneSource Passport system, the health assessment module does not auto-provision access. You have to navigate to the health section, enter your passport case number, and verify your identity through a secondary auth step. That secondary step typically involves either a secure OTP sent to your registered email or a pre-assigned access code from your mobility coordinator. If you are new to this workflow, here is how it actually goes down. First, locate the case number for the relocation file in question. Then go to the designated health login URL provided in your onboarding packet. Enter the case number and your personal identifier as configured in the system. Complete the OTP or access code verification. Once authenticated, you can begin the medical questionnaire, upload vaccination records, and access the insurance portability tools specific to the destination country. The first time I ran into trouble was with a transfer to Singapore. The assignee had the correct case number and OTP, but the health portal kept rejecting the login with a generic error. After about forty minutes of troubleshooting, I discovered the issue was a timestamp mismatch between the session token and the regional server routing the request. The workaround was closing the browser, waiting three minutes, and re-initiating the login through an incognito window instead of the standard session. The stale session token was the problem. Fresh cookie context resolved it immediately. STn support confirmed this was a known edge case with their SaaS instance routing for APAC.
Common problems that are worth knowing about before they waste your afternoon. The most frequent issue I see is people trying to use the same credentials across multiple case numbers. The system ties each health portal session to a single assignment record. If you are managing more than one relocation at a time, you need separate sessions for each case number. Logging out and back in with a different case number will not always clear the previous session cleanly. Clearing your browser cache or switching to a private window between cases usually prevents the confusion. Another issue involves the OTP delivery timing. The codes expire after ten minutes, but the email often arrives with a twenty-minute delay during peak processing hours. I have seen coordinators tell assignees the login is broken when really the OTP just had not arrived yet. Waiting twenty minutes before declaring a problem saves a support ticket and an afternoon of wasted time. The vaccination document upload feature is functional but unforgiving with file formats. The system accepts PDF, JPEG, and PNG, but the maximum file size is five megabytes per document. Scanned passports and vaccination certificates often exceed that limit when done at full resolution. Compressing the files to under five megabytes before uploading prevents the error messages that follow. I usually recommend compressing documents on the source device before even attempting the portal upload.
Get the Full Details
There is a nuance most people miss about how OneSource Passport calculates health insurance portability. The system uses the destination country's social security totalization agreements to determine whether a relocating employee needs local health coverage or can rely on their home-country plan. The algorithm is not perfect. I have seen it incorrectly flag employees from countries with incomplete agreement coverage as requiring local insurance when their home plan actually provided adequate coverage through bilateral arrangements. When that happens, the assignment can be delayed because the mobility team has to manually override the system calculation and provide a written justification for the exception. Getting ahead of this by checking the destination's totalization agreement status before the health login process begins prevents that bottleneck entirely. A second counter-intuitive point is that the health assessment questionnaire adapts dynamically based on the destination country, but the adaptation is not always complete. An employee moving from the US to Germany will see a different set of questions than one moving to Brazil, but both may still encounter questions that are irrelevant to their specific situation. The system does not filter out these irrelevant questions automatically. You have to answer them as N/A rather than skipping them, or the portal will not let you proceed to the next section. Skipping is not an option. Answering N/A is required to move forward. Where the system breaks down and what to do about it. The biggest limitation I deal with is the lack of real-time integrations with many regional healthcare providers. The portal gives you the information about required vaccinations and insurance options, but it does not connect directly to clinics or hospitals in most destination countries. You still need to make appointments and coordinate with providers independently. The system tells you what to do, not how to do it with the actual local infrastructure.
Another significant gap is the support response time. During business hours, you might get a response within a few hours. Outside those hours, which often overlaps with the of assignees in other time zones, you are looking at next-business-day responses at the earliest. If you are on a tight relocation timeline and something breaks in the health portal on a Friday evening, you are essentially waiting until Monday. There is no 24/7 support channel for the health module specifically. If you are dealing with a high-volume relocation program where the health portal friction is affecting your timeline, consider whether STn Global's Professional Services team offers a workaround through direct API integration or a dedicated account manager escalation path. For individual assignees, the workarounds I described above are the best available option. There is no shortcut around the fundamental design constraints of the portal. The actual process for completing a health assessment once you are logged in. After successful authentication, the portal presents a series of sections covering medical history, current medications, vaccination records, and insurance preferences. Each section must be completed before the next becomes accessible. You cannot skip ahead, and you cannot save and return to a partially completed section without losing the data you entered in the current section if your session times out. Sessions typically expire after fifteen minutes of inactivity, which is aggressive for a form that can take thirty to forty-five minutes to complete depending on the complexity of the medical history being reported.
Once all sections are completed, the system generates a summary document and routes it to the designated insurance provider or mobility coordinator for review. The review process usually takes between two and five business days. During that time, the assignee's relocation status will show as pending health clearance. This is normal. Do not resubmit the assessment during the review period because it creates duplicate entries in the queue and further delays processing. The system also provides a tracking dashboard where you can check the status of your submitted assessment. The dashboard updates are not real-time. They typically reflect the current stage of the review process, not an actual timestamp of when the next action occurred. If the status has not changed in three business days, it is usually still being processed. Contacting support before five business days have passed typically results in a hold response while they confirm the assessment is still in queue. A note on data privacy and the health module specifically. The health assessment data is handled differently from general relocation data. Medical information falls under stricter regulatory categories depending on the destination country. The portal encrypts health data in transit and at rest, but the encryption keys and data storage locations vary by region. If your assignment involves a country with specific data sovereignty requirements, such as China or Russia, the health data may be routed through a separate regional server instance. This is not always disclosed in the initial login process and can cause unexpected delays if the data routing does not match the assignee's declared residence. Checking with your mobility coordinator about data routing before completing the health assessment prevents that particular headache.
