---
sourceDocument: Brazil Healthcare and Life Sciences
sourceDocumentLink: https://www.servicenow.com/docs/r/healthcare-life-sciences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# Run the initial load

# Run the initial load {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Run the FHIR import on demand to perform the first full load of
Organization, Location, Practitioner, and PractitionerRole data into the
Healthcare Operations data model.

## Before you begin

Role required: `sn_hco_intg_fhir.admin`.

The FHIR Sync --- Daily job must be configured. See
[Activate the FHIR sync schedule](https://www.servicenow.com/docs/et9h7YJsKOU7g53Bm3V7uQ "Activate the FHIR Sync — Daily scheduled job so that the EMR Provider Directory Sync imports FHIR provider-directory data on a recurring schedule.").

## About this task

The first time the sync runs, it performs a full load of all four FHIR
resources because there is no previous run watermark. You can wait for the
scheduled run or trigger the load immediately to validate your
configuration.

## Procedure

1. Navigate to AllSystem DefinitionScheduled Jobs and open the FHIR Sync --- Daily record.
2. Click Execute Now.  
   The orchestration subflow runs the four imports in order: Organizations,
   Locations, Practitioners, and then PractitionerRoles. A large initial load
   can take several minutes.
3. Verify the results in the FHIR Sync Log.  
   See [Monitor and troubleshoot FHIR
   sync runs](https://www.servicenow.com/docs/ELFiF7lu0qzOi1Dnv0A7aw "Review the FHIR Sync Log to confirm that sync runs complete and see how many records each run processed or skipped. Trace skipped records and failures to their cause.").

## Result

The Healthcare Operations data model is populated with the imported FHIR
data. Subsequent scheduled runs import only resources changed since the last
successful run.  
Note:  
Imported practitioners are created as active platform users, but login is not enabled automatically. An administrator provisions each practitioner's password or SSO out of band before they can sign in.

*[\>]: and then