![]() |
VOOZH | about |
This article illustrates using the FHIR ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of FHIR data to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.
In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.
๐ The components used in the data task in this example.In the connection manager, enter the connection details for FHIR data.
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.
๐ Connection properties in the Connection Manager dialog. (Salesforce is shown.)Open the DataReader editor and set the following information:
SELECT Id, [name-use] FROM Patient WHERE [address-city] = 'New York'
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
๐ Input and destination columns in the OLE DB Destination Editor.Download a free trial of the FHIR Data Provider to get started:
Download NowLearn more:
๐ FHIR IconRapidly create and deploy powerful .NET applications that integrate with FHIR.