--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-yokohama-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3ay bundleId : - delta3ay --- # Combined EMR Provider Directory Sync Sync release notes for upgrades from Yokohama to Australia # Combined EMR Provider Directory Sync Sync release notes for upgrades from Yokohama to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Combined EMR Provider Directory Sync Sync release notes for upgrades from Yokohama to Australia This consolidated release notes document assists ServiceNow customers in preparing for an upgrade of the EMR Provider Directory Sync Sync application from the Yokohama release family to the Australia release family. It summarizes key information about new features, changes, removals, deprecations, and activation details related to this upgrade. Show full answer Show less No updates or changes were made to the application in the Yokohama or Zurich releases. The Australia release introduces enhancements and operational improvements without removing or deprecating any features. ## Key Features in Australia Release * **FHIR Sync Process:** Synchronization with a FHIR R4 server occurs via a scheduled job that runs an orchestration subflow. This subflow imports four key FHIR resources---Organization, Location, Practitioner, and PractitionerRole---in dependency order, and upserts them into the Healthcare Operations data model keyed by the FHIR resource ID. * **Initial and Delta Syncs:** An initial full load imports all records, and subsequent syncs use the timestamp of the last successful run as a watermark to import only changed resources, optimizing data updates. * **Monitoring and Troubleshooting:** Each sync run generates a FHIR Sync Log entry per resource type, including status and counts of processed and skipped records, all linked by a shared correlation ID for easy monitoring and troubleshooting by administrators. * **Classification:** Imported organizations are categorized as internal or external business locations through an editable decision table, enabling tailored data management. * **Configurable Scheduling:** Syncs occur on a configurable daily schedule to ensure healthcare operations data remains current without manual intervention. ## Activation and Dependencies * EMR Provider Directory Sync is installed by requesting it from the ServiceNow Store. * The application depends on the HL7 FHIR Spoke and the Healthcare Operations and Healthcare and Life Sciences data-model applications. Customers should verify prerequisites for FHIR integration before upgrading. ## Additional Information No changes were made to browser requirements, accessibility, localization, or other operational considerations in the Australia release. Customers can expect a seamless upgrade experience focused on enhanced FHIR synchronization capabilities. ## What Customers Can Expect * Automated, reliable synchronization of healthcare provider directory data from a FHIR R4 server into ServiceNow's Healthcare Operations data model. * Efficient data updates using delta syncs that reduce processing time after the initial full import. * Comprehensive logging and monitoring tools to track sync performance and quickly identify issues. * Flexible configuration options to classify organizations and schedule sync jobs according to operational needs. Consolidated page of all release notes for EMR Provider Directory Sync Sync from Yokohama to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family EMR Provider Directory Sync Sync release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Yokohama to Australia. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading EMR Provider Directory Sync Sync to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__2} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for EMR Provider Directory Sync Sync. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__10} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | [How the FHIR sync works](https://www.servicenow.com/docs/access?context=hco-fhir-how-it-works&family=australia&ft:locale=en-US) : A scheduled job runs an orchestration subflow that imports the four FHIR resources in dependency order and upserts them into the Healthcare Operations data model, keyed on the FHIR resource ID. [Run the initial load](https://www.servicenow.com/docs/access?context=hco-fhir-run-initial-load&family=australia&ft:locale=en-US) : After the initial full load, each run uses the previous successful run's timestamp as a watermark to import only resources changed since then. [Monitor and troubleshoot FHIR sync runs](https://www.servicenow.com/docs/access?context=hco-fhir-monitor-sync&family=australia&ft:locale=en-US) : Each run records one FHIR Sync Log row per resource type, with status, processed and skipped counts, and a shared correlation ID, so admins can monitor and troubleshoot syncs. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing EMR Provider Directory Sync Sync features. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__18} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Removed Between your current release family and Australia, some EMR Provider Directory Sync Sync features or functionality were removed. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__26} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some EMR Provider Directory Sync Sync features or functionality were deprecated. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__34} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Activation information Review information on how to activate EMR Provider Directory Sync Sync. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__42} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | Install EMR Provider Directory Sync by requesting it from the ServiceNow Store. Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/access?context=sn-store-release-notes&family=australia&ft:locale=en-US). This application depends on the HL7 FHIR Spoke and on the Healthcare Operations and Healthcare and Life Sciences data-model applications. For the full list, see [Prerequisites for the FHIR integration](https://www.servicenow.com/docs/access?context=hco-fhir-prerequisites&family=australia&ft:locale=en-US). | [ ] ## Additional requirements If any additional requirements were introduced or changed for EMR Provider Directory Sync Sync we have noted them here. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__50} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for EMR Provider Directory Sync Sync we have noted them here. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__58} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for EMR Provider Directory Sync Sync, such as specific requirements or compliance levels. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__66} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for EMR Provider Directory Sync Sync we have noted them here. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__74} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for EMR Provider Directory Sync Sync we have noted them here. {#dfrn3-emrproviderdirectorysyncsync-summary__entry__82} | Release | Release notes | |-|-| | Yokohama | No updates for this release. | | Zurich | No updates for this release. | | Australia | * Keep Healthcare Operations organizations, business locations, practitioners, and care-team memberships in sync with a FHIR R4 server without manual maintenance. * Import FHIR Organization, Location, Practitioner, and PractitionerRole resources on a configurable daily schedule, with delta syncs after the first full load. * Track every sync run in a FHIR Sync Log, with per-resource status and record counts correlated by run. * Classify imported organizations as internal or external business locations using an editable decision table. See [EMR Provider Directory Sync](https://www.servicenow.com/docs/access?context=hco-fhir-landing&family=australia&ft:locale=en-US) for more information. | [ ]