Customer 360 for Healthcare > Configuring Customer 360 for Healthcare for source system integration > Configuring Customer 360 to import data with FHIR R4 standard in batches
  

Configuring Customer 360 to import data with FHIR R4 standard in batches

Configure Customer 360 to ingress records that comply with the Fast Health Interoperability Resources (FHIR) R4 standard. Import assets related to FHIR into your organization.
Note: Before you import assets related to the FHIR R4 standard, import the data model related to the extension, predefined custom pages, and search result layout components.
To configure Customer 360, perform the following tasks:
    1Import the supplementary data model and pages related to the FHIR R4 standard.
    2Import the Cloud Data Integration assets related to the FHIR R4 standard.
    3Import job assets.
    4Import the supplementary reference data sets related to the FHIR R4 standard.
    5Add the lookup files related to the FHIR R4 standard in the Secure Agent machine.
    6Import parameter files.
    7Configure the flat file connection.
    8Configure the Business 360 FEP connector.

Importing supplementary assets

To import records that are compliant with the FHIR R4 standard, import the supplementary data model assets, pages, and search result layout components.
Before you customize the Customer 360 data model, import the extension assets.
    1In Business 360 Console, click Explore > Import.
    2Navigate to the 1_MDM_Assets.zip file in the following location:
    <Extracted extension package>/Supplementary Assets
    3Click Open.
    4On the Import Assets page, ensure that all the assets are selected, and click Import.
    5On the My Import/Export Logs page, verify whether the import job is successful.

Adding predefined pages and components

You can add predefined pages and search result layout components of the Location, Network, Practitioner Role, and Organization Affiliation business entities to Customer 360. Ensure that you have the Admin user role.
    1In Business 360 Console, click Explore > Customer360.
    2Click the business application.
    3Add the following business entities:
    4Select the fields to display and click Save.
    5On the Pages tab, select Location.
    6On the Create tab, click Add Page.
    A blank row appears.
    7To select a page, click the asset picker.
    8On the Select a page window, select Create Page Location, and click Select.
    The selected page appears in the row.
    9 To assign user roles to the page, from the list of user roles, select one or more user roles.
    For more information about user roles assigned to pages, see Pages.
    10On the View and Edit tab, click Add Page.
    A blank row appears.
    11To select a page, click the asset picker.
    12On the Select a page window, select Edit Page Location, and assign the page to one or more user roles.
    For more information about user roles assigned to pages, see Pages.
    13In the Business Entities section, select the business entity and repeat steps 6 through 12.
    For more information about pages for business entities, see Pages.
    14On the Seach tab, in the Business Entities section, select Location.
    15In the Search Result Layouts: Location section, click Add Search Result Layout.
    A blank row appears.
    16To select a component, click the asset picker.
    17On the Select a Component window, select Search Layout for Location, and assign the component to one or more user roles.
    For more information about user roles assigned to search result layout components, see Search result layout components.
    18In the Business Entities section, select the business entity and repeat steps 15 through 17.
    For more information about search result layout components for business entities, see Search result layout components.
    19Click Save.
For more information about how to assign pages to user roles, see Assign pages to user roles.

Importing Cloud Data Integration assets

Import Cloud Data Integration assets related to FHIR R4 standard, such as predefined taskflows, mapping tasks, and mappings. Create import and export jobs based on the predefined taskflows.
    1In Data Integration, click Explore > Import.
    2Navigate to the following file:
    <Extracted extension package>/2_DI_Assets/FHIR_DI_Assets.zip
    3Click Open.
    4On the Import Assets page, ensure that all the assets are selected, and then select Publish Taskflow(s) after import.
    5Click Import.
    6On the My Import/Export Logs page, verify whether the import job is successful.

Importing job assets

After you import Cloud Data Integration assets, import job assets related to the FHIR R4 standard. Use batch jobs to ingress records that comply with the FHIR R4 standard.
    1In Business 360 Console, click Explore > Import.
    2Navigate to the FHIR_Job_Assets.zip file in the following location:
    <Extracted extension package>/3_MDM_Job_Assets
    3Click Open.
    4On the Import Assets page, ensure that all the assets are selected, and click Import.
    5On the My Import/Export Logs page, verify whether the import job is successful.

Importing reference data

Import reference data code values in bulk from CSV files into reference data assets.
The reference data code values related to Fast Healthcare Interoperability Resources (FHIR) R4 standard records are available in the supplementary assets folder.
The following table describes the file and folder in the extracted reference data directory:
File or Folder Name
Description
Healthcare
Folder that contains the code values folder with the name _1.
LoadReferenceData.py
Python script to import reference data.
The following table lists supplementary reference data assets and their code value file location:
Supplementary Reference Data Asset
Code Value File Location
infa360loc_AddressType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_AddressType
infa360loc_AddressUsageType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_AddressUsageType
infa360loc_Country
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_Country
infa360loc_DaysOfweek
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_DaysOfweek
infa360loc_EndTimeHours
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_EndTimeHours
infa360loc_EndTimeMinutes
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_EndTimeMinutes
infa360loc_EndTimeSeconds
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_EndTimeSeconds
infa360loc_EnrichedIndicator
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_EnrichedIndicator
infa360loc_GeoLocType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_GeoLocType
infa360loc_IdentifierType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_IdentifierType
infa360loc_IdentifierUsageType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_IdentifierUsageType
infa360loc_IndicatorGroup
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_IndicatorGroup
infa360loc_IndicatorType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_IndicatorType
infa360loc_IndicatorValue
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_IndicatorValue
infa360loc_LocationForm
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_LocationForm
infa360loc_LocationType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_LocationType
infa360loc_NameType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_NameType
infa360loc_OwnershipType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_OwnershipType
infa360loc_StandardTimeZone
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StandardTimeZone
infa360loc_StartTimeHours
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StartTimeHours
infa360loc_StartTimeMinutes
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StartTimeMinutes
infa360loc_StartTimeSeconds
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StartTimeSeconds
infa360loc_State
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_State
infa360loc_StatusType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StatusType
infa360loc_StatusValue
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infa360loc_StatusValue
infac360hc_HealthcareServiceCategory
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_HealthcareServiceCategory
infac360hc_HealthcareServiceType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_HealthcareServiceType
infac360hc_IsAcceptingPatients
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_IsAcceptingPatients
infac360hc_NetworkID
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_NetworkID
infac360hc_NetworkType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_NetworkType
infac360hc_OrgAffilRoleName
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_OrgAffilRoleName
infac360hc_OrgAffilRoleSpecialty
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_OrgAffilRoleSpecialty
infac360hc_PractitionerRoleIdentifierType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_PractitionerRoleIdentifierType
infac360hc_PractitionerRoleIdentifierUsageType
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_PractitionerRoleIdentifierUsageType
infac360hc_PractitionerRoleName
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_PractitionerRoleName
infac360hc_PractitionerRoleSpecialty
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_PractitionerRoleSpecialty
infac360hc_PractitionerRoleStatus
<Extracted extension package>/Supplementary Assets/Reference Data/Healthcare/_1/infac360hc_PractitionerRoleStatus
To import code values in bulk from CSV files that are available in the extracted supplementary reference data directory, run the LoadReferenceData.py Python script.

Add lookup files

Add the lookup files related to FHIR in the Secure Agent machine.
    1Navigate to the following directory:
    <Extracted extension package>\Secure Agent Files\Lookup Files\FHIR
    2Copy the EnterpriseSuffixName.csv file to the local directory where you store the flat file connection.

Importing parameter files

Import the list of user-defined parameters and their associated values for Cloud Data Integration mappings.
To import parameter files, save the parameter files in the Secure Agent Installation directory.
Copy the parameter files from the source directory to the target Secure Agent installation directory:
Source: <Extracted extension package>\Secure Agent Files\Parameter Files\FHIR
Target: <Secure Agent Installation Directory>\apps\Data_Integration_Server\data\userparameters
Optionally, if you want to use a configured path for the target location, see Parameter file location.

Using the parameter files

A parameter file is a list of user-defined parameters and their associated values. Use parameter files to define values that you want to update without having to edit the mapping task. The parameter values are applied when the task runs.
The Customer 360 for Healthcare package contains the following parameter files in the Secure Agent files directory for the Cloud Data Integration mappings:
For more information about importing the parameter files, see Importing parameter files.

Configuring the flat file connection

To access flat files from the Secure Agent, configure the flat file connection.
    1In Administrator, click Connections.
    2Click infac360hc_conn_flatfile.
    3Verify the directory to store the flat file.
    Default is C:\ReferenceData.
    4Test the connection, and ensure that the connection is successful.

Configuring Business 360 FEP connection

You can use the Business 360 FEP Connector to write data from the source system into MDM SaaS. If the input values for source system integer fields are null, the Business 360 FEP Connector converts the null values to 0 in MDM SaaS.
    1In Administrator, click Connections.
    2Click infac360hc_conn_customer360.
    3Test the connection.
    The connection might fail with the following error:
    The test connection for infac360hc_conn_customer360 failed. Unable to fetch connector attributes, Ensure adapter ID is valid[com.infa.adapter.mdmflat].
    4If the connection fails, verify and ensure that the connection is successful.
    1. aVerify the license used.
    2. bEnsure that the connector is enabled for the Secure Agent group.
    3. cRestart the Secure Agent.