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


---

# What the EMR Provider Directory Sync does

# What the EMR Provider Directory Sync does {#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 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.

Healthcare Operations workflows in ServiceNow depend on accurate organization
hierarchy, facility, and practitioner data. When that data is maintained
manually, it drifts from the customer's EMR, which is the operational source of
truth. This application closes that gap by importing four FHIR R4
provider-directory resources on a schedule and upserting them into the
Healthcare Operations data model.

## What it imports {#hco-fhir-overview__hco-fhir-overview-resources}

The integration imports four FHIR R4 resources and writes them to the
Healthcare Operations data model:

* FHIR Organizations become Healthcare Organization records and internal or external business locations.
* FHIR Locations become Healthcare Location records and platform location records, optionally associated with a managing organization.
* FHIR Practitioners become user records and Healthcare Practitioner records, each granted the care-team-member role.
* FHIR PractitionerRoles become service organization membership records that place a practitioner on a care team for an organization.

## Relationship to the HL7 FHIR Spoke {#hco-fhir-overview__hco-fhir-overview-boundary}

This application 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). The spoke provides
the read-only FHIR actions and returns raw FHIR field values. This application
owns the EMR-to-HCLS field mapping, the upsert key strategy, and the dependency
ordering. This separation keeps the spoke reusable while concentrating all
Healthcare Operations logic in one place.

## What is out of scope {#hco-fhir-overview__hco-fhir-overview-scope}

The integration is read-only against the FHIR server --- it does not write back
to the EMR. Real-time, event-driven sync (such as CDS Hooks or FHIR
subscriptions) and FHIR resources beyond the four provider-directory resources
are out of scope. There is no user-facing portal; the application is operated
by Healthcare Operations administrators.