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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Healthcare and Life Sciences

ft:clusterId :

    - hcls

bundleId :

    - hcls

workflow :

    - Customer and Industry


---

# EMR Provider Directory Sync

# EMR Provider Directory Sync {#ariaid-title1}

Release version: Australia  
Updated June 16, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The EMR Provider Directory Sync imports HL7 FHIR R4 resources from a FHIR
server into the ServiceNow Healthcare Operations data model on a configurable
schedule.
The Healthcare Operations (HCO) data model depends on accurate organization,
location, and practitioner records. This application ingests four FHIR R4
resources from a FHIR server on a configurable schedule and upserts them into
the corresponding Healthcare Operations tables. Records are identified across
runs by the FHIR resource ID, stored as an external identifier on each
target.

The integration is one-way (FHIR server to ServiceNow), admin-operated, and
scheduled. It builds on the
[HL7 FHIR Spoke](https://www.servicenow.com/docs/access?context=fhir-spoke-landing&version=australia&pubname=australia-integrate-applications&ft:locale=en-US), which provides the
read-only FHIR actions, and owns all FHIR-to-HCLS field mapping, upsert keys,
and dependency ordering.

## Get started {#hco-fhir-landing__hco-fhir-landing-get-started}

* [What EMR Provider Directory Sync
  does](https://www.servicenow.com/docs/t8F2MlSqkOteNd_XfxhaVQ "The EMR Provider Directory Sync imports provider-directory data from a FHIR R4 server into the Healthcare Operations data model on a schedule. Organizations, locations, practitioners, and care-team memberships stay current without manual maintenance.")
* [How the FHIR sync works](https://www.servicenow.com/docs/3X8HYsfOu~WkRt336FozDQ "A scheduled job runs an orchestration subflow that imports the four FHIR resources in dependency order, upserts each into the Healthcare Operations data model — matching primary records on the FHIR resource ID — and records the outcome in the FHIR Sync Log.")
* [Prerequisites for the
  FHIR integration](https://www.servicenow.com/docs/rhx5f0Lg1XvVn7hFhaM5hg "Before you activate the EMR Provider Directory Sync, confirm that its dependent applications are installed and that the HL7 FHIR Spoke connection to your FHIR server is configured.")
* [Activate the FHIR sync
  schedule](https://www.servicenow.com/docs/JyStSZ0WY9sfnC9ThoWB0g "Activate the FHIR Sync — Daily scheduled job so that the EMR Provider Directory Sync imports FHIR provider-directory data on a recurring schedule.")
* [Change the sync
  schedule](https://www.servicenow.com/docs/IsJZebGGHiX0vaIPJqlUPA "Adjust how often the EMR Provider Directory Sync imports data by editing the FHIR Sync — Daily scheduled job directly.")
* [Configure the
  organization classification decision table](https://www.servicenow.com/docs/wDfXYm2miPoPy6zjsib59Q "Edit the decision table that classifies imported FHIR Organizations as internal or external business locations, so that the classification matches how your organization defines internal and external entities.")
* [Run the initial
  load](https://www.servicenow.com/docs/etuI3stQpBSd_1k9E8Mj2Q "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.")
* [Monitor and troubleshoot
  FHIR sync runs](https://www.servicenow.com/docs/ZUvpbcvdFifo4OwS8DKf1Q "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.")
* [Components
  installed with EMR Provider Directory Sync](https://www.servicenow.com/docs/dC~WyhhVksQe0xlAWRwyXA "Several types of components are installed with the EMR Provider Directory Sync. These include a user role, a sync log table, a scheduled job, flows, a business rule, flow actions, and a decision table.")
* [FHIR Sync Log
  fields](https://www.servicenow.com/docs/LvkXaMyfoM2fM1fSoW3cyQ "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.")
* [FHIR-to-HCLS field
  mappings](https://www.servicenow.com/docs/jUH196PWr10Po_hR8xcLRQ "For each of the four FHIR R4 resources, the Healthcare Operations HL7 FHIR Integration maps FHIR fields to Healthcare Operations target tables and upserts records — matching the primary HCLS record on the FHIR resource ID (stored as an external identifier) and related records on their natural keys.")
{#hco-fhir-landing__hco-fhir-landing-nav}

## Helpful resources {#hco-fhir-landing__hco-fhir-landing-helpful-resources}

Some ServiceNow resources that can provide helpful information:

ServiceNow Community
:   Connect with other Healthcare Operations users in the [Healthcare and Life Sciences
    community](https://www.servicenow.com/community/healthcare-life-sciences/ct-p/healthcare-life-sciences).

ServiceNow University
:   Access training and certification resources on [ServiceNow University](https://learning.servicenow.com).