{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":21210,"path":"integrate-applications/integration-hub/fhir-spoke-activate.md","title":"Activate the HL7 FHIR Spoke","bundle":null,"doc_type":null,"release":"australia","body":"\n# Activate the HL7 FHIR Spoke\n\nInstall the HL7 FHIR Spoke from the ServiceNow Store and verify that the required platform plugins are active so that the eight FHIR actions are available in Workflow Studio.\n\n## Before you begin\n\nRole required: admin\n\nThe following platform plugins must be active before the spoke's stream actions can be added to a flow:\n\n-   Workflow Studio \\(`com.glide.hub`\\)\n-   Flow Designer Action Step — CORE \\(`com.glide.hub.action_step.core`\\)\n-   REST step type \\(`com.glide.hub.action_step.rest`\\)\n-   Integration Hub Action Template — Data Stream \\(`com.glide.hub.action_type.datastream`\\)\n\n## About this task\n\nHL7 FHIR Spoke is distributed as a scoped application in the ServiceNow Store. After you install it, the eight FHIR actions appear in the Workflow Studio action picker under the four FHIR Integration Hub categories.\n\n## Procedure\n\n1.  Request the HL7 FHIR Spoke application from the ServiceNow Store and install it on your instance.\n\n    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/r/store-release-notes/sn-store-release-notes.html).\n\n2.  Navigate to **All** > **System Definition** > **Plugins** and confirm that the four required plugins listed in the prerequisites are active.\n\n3.  In Workflow Studio, create or open a flow, add an action step, and confirm that the FHIR actions appear under the Organization Management, Location Management, Practitioner Management, and PractitionerRole Management categories.\n\n\n## Result\n\nThe HL7 FHIR Spoke is installed and its actions are available to flow authors. Before the actions can read from a FHIR server, configure the connection and credentials. See [Configure the HL7 FHIR connection and credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/fhir-spoke-activate.md).\n\n## Configure the HL7 FHIR connection and credentials\n\nBind the FHIR server URL and OAuth credentials to the shared `HL7 FHIR` Connection & Credential Alias so that all eight spoke actions can authenticate to and read from your FHIR R4 server.\n\n### Before you begin\n\nRole required: admin\n\nYou need the following from your FHIR server administrator: the FHIR R4 server base URL, the OAuth authorization, token, and revoke-token endpoint URLs, and the OAuth client ID and client secret registered for your instance.\n\n### About this task\n\nThe spoke ships a Connection & Credential Alias named `HL7 FHIR` with an attached configuration template named `FHIR Connection Configuration`. The template adds a guided **Add Connection** action to the alias that creates the HTTP connection and an OAuth 2.0 credential in one step. The OAuth client credentials and the FHIR server URL ship empty — you supply them through the guided setup. All eight actions share this single alias.\n\n### Procedure\n\n1.  Navigate to **All** > **Connections & Credentials** > **Connection & Credential Aliases** and open the **HL7 FHIR** alias.\n\n2.  On the alias record, click **Add Connection** to open the guided `FHIR Connection Configuration` setup form.\n\n3.  Enter the connection details: a **Connection Name**, the **Connection URL** \\(your FHIR R4 server base URL — host and protocol only, over HTTPS\\), and the **API version**.\n\n    Leave **API version** at the default `baseR4` unless your FHIR server uses a different R4 URL fragment. This value populates the `api_version` connection attribute that every action appends to the base URL.\n\n4.  Enter the OAuth credential details supplied by your FHIR server administrator: **OAuth Name**, **OAuth Client ID**, **OAuth Client Secret**, and **OAuth Token URL**.\n\n    The guided setup creates an OAuth 2.0 credential \\(`FHIR Spoke Credential`\\) and application registry \\(`FHIR Spoke OAuth`\\) that use the authorization code grant with PKCE \\(`S256`\\).\n\n5.  Save the connection, then complete the OAuth authorization to obtain an access token.\n\n6.  Use the alias **Test Connection** action to verify that the instance can authenticate to and reach the FHIR server.\n\n\n### Result\n\nAll eight HL7 FHIR Spoke actions can now authenticate to your FHIR server through the shared alias. To add a stream action to a flow, see [Add a FHIR stream action to a flow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/fhir-spoke-activate.md).\n\n## Add a FHIR stream action to a flow\n\nAdd an HL7 FHIR Spoke stream action to a flow to search a FHIR resource and process each matching record as it streams in, with pagination handled automatically by the spoke.\n\n### Before you begin\n\nRole required: a Workflow Studio authoring role, such as `flow_designer`.\n\nThe `HL7 FHIR` connection and credentials must be configured. See [Configure the HL7 FHIR connection and credentials](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/fhir-spoke-activate.md).\n\n### About this task\n\nStream actions use the data stream action template, which retrieves results page by page. You process the streamed items inside a \"For Each\" flow logic block so that the flow handles each resource without buffering the entire result set.\n\n### Procedure\n\n1.  In Workflow Studio, open your flow or subflow and add an action step.\n\n2.  Search for the stream action for the resource you want — for example, **Look up Organizations Stream** — and add it to the flow.\n\n3.  Set the required **Page size** input.\n\n    Page size controls how many resources the spoke requests per FHIR page. The spoke continues to request pages until the FHIR server returns no `next` link.\n\n4.  Set any optional FHIR R4 search parameters to filter the results — for example, **name** or **active**.\n\n    For the full set of search parameters per resource, see [HL7 FHIR Spoke actions reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/integration-hub/fhir-spoke-actions.md).\n\n5.  Add a **For Each** flow logic block that iterates over the action's stream output.\n\n6.  Inside the loop, map the resource data pills into your downstream steps — for example, to create or update records in your application.\n\n7.  After the loop, check the action's **status code**, **error code**, and **error message** outputs to detect transport failures.\n\n\n"}}