--- 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 --- # Components installed with the EMR Provider Directory Sync # Components installed with the EMR Provider Directory Sync {#ariaid-title1} Release version: Australia Updated June 16, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Components installed with the EMR Provider Directory Sync The EMR Provider Directory Sync in the Australia release (updated June 16, 2026) installs multiple components designed to synchronize healthcare provider data using FHIR standards. These components collectively enable automated and scheduled imports of healthcare organization, location, practitioner, and practitioner role data into ServiceNow, facilitating accurate provider directory management and integration. Show full answer Show less ## Key Features * **User Role:** `HCO FHIR Integration Admin` role manages the FHIR synchronization process, including triggering sync runs, modifying schedules, configuring organization classification, and accessing sync logs. This role is inherited by users with the `snhco.admin` role. * **Tables:** The main table installed is `FHIR Sync Log`, which records detailed information about each sync run per resource type, such as timing, counts, status, and errors. The application also interacts with other relevant tables for healthcare organizations, locations, practitioners, and service organization members. * **Scheduled Job:** A daily scheduled job named `FHIR Sync --- Daily` initiates the import orchestration subflow by default at 3:00 AM instance time. This job is installed inactive and must be activated before use. It can also be manually triggered by administrators. * **Flows and Subflows:** The import orchestration subflow coordinates sequential imports of Organizations, Locations, Practitioners, and PractitionerRoles, halting on failures. Additional subflows manage logging sync start and end, delta sync watermarking, and detailed record processing. * **Business Rules:** A business rule updates the sync log to mark when a sync run ends by stamping the end timestamp upon status transition. * **Flow Actions:** Includes actions for formatting FHIR last-updated filters for delta synchronization and parsing FHIR references to extract logical IDs. * **Decision Table:** The `FhirOrgTypeToBusinessLocationClass` decision table classifies imported FHIR organizations as internal or external business locations. This table is editable by administrators to tailor classification logic. * **Spoke Integration:** The sync uses read-only actions from the HL7 FHIR Spoke for data retrieval, including lookups for organizations, locations, practitioners, and practitioner roles. All actions authenticate via a shared HL7 FHIR Connection and Credential Alias configured in the spoke. * **System Properties:** None are installed. Sync scheduling and classification are managed directly through the scheduled job record and the decision table respectively. ## Practical Benefits for ServiceNow Customers * Automates synchronization of provider directory data into ServiceNow, ensuring up-to-date healthcare organization and practitioner information. * Provides administrators with control over sync scheduling, classification rules, and detailed logging for audit and troubleshooting. * Leverages native ServiceNow flows and spokes to manage data imports efficiently and securely. * Enables incremental (delta) sync through last-updated filters to optimize performance and data freshness. * Supports customization of organization classification to align with customer-specific business location definitions. 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. ## Roles installed {#hco-fhir-installed-components__hco-fhir-installed-roles} {#hco-fhir-installed-components__hco-fhir-installed-roles__entry__3} | Role title \[name\] | Description | Contains roles | |-|-|-| | HCO FHIR Integration Admin \[`sn_hco_intg_fhir.admin`\] | Operates the FHIR sync: triggers runs, edits the sync schedule and the organization classification decision table, and reads, creates, and updates FHIR Sync Log rows. | Inherited by users with `sn_hco.admin`. | [ ] ## Tables installed {#hco-fhir-installed-components__hco-fhir-installed-tables} {#hco-fhir-installed-components__hco-fhir-installed-tables__entry__2} | Table | Description | |-|-| | FHIR Sync Log \[`sn_hco_intg_fhir_sync_log`\] | Records one row per resource type per sync run, with start and end times, processed and skipped counts, status, correlation ID, and a transport error message. For field details, see [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."). | [ ] The application also writes to tables owned by other applications but does not install them. These include the Healthcare Organization, Location, and Practitioner tables, the business location tables, the user table, and the service organization member tables. See [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."). ## Scheduled jobs installed {#hco-fhir-installed-components__hco-fhir-installed-scheduled-jobs} {#hco-fhir-installed-components__hco-fhir-installed-scheduled-jobs__entry__2} | Scheduled job | Description | |-|-| | FHIR Sync --- Daily | Runs daily (by default at 03:00 instance time) and starts the Import FHIR Resources orchestration subflow. Admins can also run it on demand with Execute Now. Installed inactive. Set Active to true on the job record before first use. | [ ] ## Flows and subflows installed {#hco-fhir-installed-components__hco-fhir-installed-flows} {#hco-fhir-installed-components__hco-fhir-installed-flows__entry__2} | Subflow | Description | |-|-| | Import FHIR Resources | Orchestration subflow that sets a correlation ID and runs the four per-resource imports in dependency order, stopping if any fails. | | Import Organizations | Imports FHIR Organizations into Healthcare Organization records and internal or external business locations. | | Import Locations | Imports FHIR Locations into platform and Healthcare Location records and associates them with a managing organization. | | Import Practitioners | Imports FHIR Practitioners into user and Healthcare Practitioner records and grants the care-team-member role. | | Import PractitionerRoles | Imports FHIR PractitionerRoles into service organization member and responsibility records. | | Start Sync Log Entry / End Sync Log Entry | Shared subflows that open and close a FHIR Sync Log row and provide the delta-sync watermark. | [ ] Each per-resource import decomposes into additional child subflows --- a per-record processor and a shared upsert subflow, plus a one-level parent-recovery subflow for Organizations and Locations. ## Business rules installed {#hco-fhir-installed-components__hco-fhir-installed-business-rules} {#hco-fhir-installed-components__hco-fhir-installed-business-rules__entry__3} | Business rule | Table | Description | |-|-|-| | Stamp ended on status transition | `sn_hco_intg_fhir_sync_log` | Before update --- stamps the `ended` timestamp when a sync log row transitions out of the Running status. | [ ] ## Flow actions installed {#hco-fhir-installed-components__hco-fhir-installed-flow-actions} {#hco-fhir-installed-components__hco-fhir-installed-flow-actions__entry__2} | Action | Description | |-|-| | Format FHIR Last-Updated Filter | Converts the previous run's timestamp into a FHIR `last updated` search filter for delta syncs. | | Parse FHIR Reference | Strips the resource-type prefix from a FHIR reference to return the bare logical ID. | [ ] ## Decision tables installed {#hco-fhir-installed-components__hco-fhir-installed-decision-tables} {#hco-fhir-installed-components__hco-fhir-installed-decision-tables__entry__2} | Decision table | Description | |-|-| | `FhirOrgTypeToBusinessLocationClass` | Classifies an imported FHIR Organization as an internal or external business location based on its organization type. Editable by admins. See [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."). | [ ] ## Spoke components used {#hco-fhir-installed-components__hco-fhir-installed-spoke-components} EMR Provider Directory Sync uses read-only actions from the [HL7 FHIR Spoke](https://www.servicenow.com/docs/access?context=fhir-spoke-landing&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) to fetch provider-directory data. The following FHIR Spoke actions are called by the import subflows: * Look up Organization by ID * Look up Organizations Stream * Look up Location by ID * Look up Locations Stream * Look up Practitioner by ID * Look up Practitioners Stream * Look up PractitionerRole by ID * Look up PractitionerRoles Stream All eight actions authenticate through the shared `HL7 FHIR` Connection \& Credential Alias defined in the HL7 FHIR Spoke. For setup details, see [HL7 FHIR Spoke](https://www.servicenow.com/docs/access?context=fhir-spoke-landing&version=australia&pubname=australia-integrate-applications&ft:locale=en-US). ## System properties installed {#hco-fhir-installed-components__hco-fhir-installed-system-properties} The application installs no system properties. The sync cadence is controlled by the scheduled job record, and the organization classification is controlled by the decision table.