---
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


---

# Monitor and troubleshoot FHIR sync runs

# Monitor and troubleshoot FHIR sync runs {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
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.

## Before you begin

Role required: `sn_hco_intg_fhir.admin`.

## About this task

Each sync run records one FHIR Sync Log row per resource type. The four rows
for a single run share a correlation ID. The status and record counts on each
row tell you whether the run succeeded and how much data it moved. For the
meaning of each field, see
[FHIR Sync Log
fields](https://www.servicenow.com/docs/tiCRyjI9~qEQTfH3QCGOlQ "The FHIR Sync Log table (sn_hco_intg_fhir_sync_log) records one row per resource type per sync run. Use these fields to monitor sync health and trace skipped or failed records.").

## Procedure

1. Navigate to AllEMR Provider Directory SyncSync Log.
2. Review the most recent rows, which are sorted by start time.  
   Each run produces four rows --- one each for Organization, Location,
   Practitioner, and PractitionerRole --- that share a
   Correlation ID.
3. Interpret the Status on each row:  
   * Completed --- all records for the resource upserted successfully.
   * Completed with errors --- some records were skipped; check the Records skipped count.
   * Failed --- a transport, authentication, or system error stopped the import; check the Error message field.
4. To investigate skipped records, copy the run's Correlation ID and open the platform system log.  
   Filter the system log for entries that contain the correlation ID. Each
   skipped record is logged with its resource type, FHIR ID, and a reason,
   in the form `[FHIR Sync] cid=<id> type=<resource>
   fhir_id=<id> skipped reason=<reason>`.

## Result

You can confirm sync health at a glance and trace any skipped or failed
records to their cause.

## What to do next

Common situations:

* If the run stops after the Organization import, the Organization row is likely Failed. Verify that the FHIR server and the HL7 FHIR Spoke connection are reachable, then rerun with Execute Now.
* If locations import but some organization associations are missing, those locations referenced an organization that could not be resolved; the locations still upsert. Rerun after the missing organizations are imported.
* If imported practitioners cannot sign in, set their password or configure SSO --- the integration enables login but does not set credentials.

*[\>]: and then