![]() |
VOOZH | about |
This guide explains everything you need to get started with the CData SSIS Components for FHIR. You'll learn how to install the components, activate your license, configure your first SSIS connection manager, and build a data flow task to move and transform FHIR data in your SQL Server Integration Services workflows.
If you are using Visual Studio 2022, the SQL Server Integration Services Projects extension must be installed.
During installation, you are prompted to activate the SSIS Component license. If you need to update or change activation:
The installer automatically prompts you to add your license. During installation, you can choose to:
To activate a full subscription license, contact the CData Orders Team and request your product key at [email protected].
Enter the license key in the installer when prompted. Once activated, the components will be licensed and ready to use inside Visual Studio without any additional steps.
When deploying SSIS packages, a Runtime Key (RTK) can also be used:
Can I use my license on multiple machines?
Yes, depending on your subscription tier. Contact [email protected] for details.
I lost my license key. How do I retrieve it?
Email [email protected] with your order number, and we'll resend your license key.
How do I transfer my license to another machine?
Yes. When transferring the license to a different machine, you will need to submit a License Transfer Request on our site linked below:
https://www.cdata.com/lic/transfer/After the License Transfer Request is submitted and successfully processed, an activation will be added to your Product Key and you will be able to activate the full license on the other machine. Once this process is finished, the license on the previous machine will be invalid.
You may also view and upgrade licenses in the self-service portal at portal.cdata.com.
Once the components are installed and licensed, you can configure a connection to FHIR using an SSIS Connection Manager. This Connection Manager stores all authentication and connection properties used by the Source and Destination components.
Set URL to the Service Base URL of the FHIR server. This is the address where the resources are defined in the FHIR server you would like to connect to. Set ConnectionType to a supported connection type. Set ContentType to the format of your documents. Set AuthScheme based on the authentication requirements for your FHIR server.
Generic, Azure-based, AWS-based, and Google-based FHIR server implementations are supported.
The product supports connections to custom instances of FHIR. Authentication to custom FHIR servers is handled via OAuth (read more about OAuth in the Help documentation. Before you can connect to custom FHIR instances, you must set ConnectionType to Generic.
With a Connection Manager created, you can now pull data from FHIR or push data into it using SSIS data flow tasks.
Solution: Verify OAuth settings, client IDs, secrets, or token permissions for your FHIR. Contact [email protected] for OAuth troubleshooting.
Solution: Check firewall, proxy, and VPN configurations. Contact [email protected] for specific port requirements.
Solution: Confirm you selected the correct schema or database when querying FHIR.
Now that you have installed, licensed, and configured the SSIS Components, here are scenarios you can use to explore our SSIS tools:
| SSIS Component | Article Title |
|---|---|
| BIML | Use Biml to Build SSIS Tasks to Replicate FHIR to SQL Server |
| SSIS Import | Import FHIR Data into SQL Server using SSIS |
If you need assistance at any point:
Be prepared to securely upload the log file upon request when reaching out to [email protected] for troubleshooting analysis.
For questions not covered in this FAQ, contact [email protected].
Download a free trial of the FHIR SSIS Component to get started:
Download NowLearn more:
π FHIR IconPowerful SSIS Source & Destination Components that allows you to easily connect SQL Server with FHIR through SSIS Workflows.
Use the FHIR Data Flow Components to synchronize with FHIR 0, and more. Perfect for data synchronization, local back-ups, workflow automation, and more!