Customer 360 for Healthcare > Predefined Customer 360 for Healthcare assets > Batch jobs
  

Batch jobs

Use batch jobs to ingress the source system records to Customer 360. After you import the records to Customer 360, you can process the imported records in Customer 360. Use batch jobs to export the processed records from Customer 360 to the source system.

Batch jobs of the Associate business entity

Use batch jobs to integrate data from source systems to Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with Customer 360 business entity fields.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress FHIR R4 standard-compliant records:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360hc_ingress_associate_inbound
infac360hc_tf_associate_inbound
  • - infac360hc_mt_associate_root_inbound
  • - infac360hc_mt_associate_social_handle_inbound
  • - infac360hc_mt_associate_phone_inbound
  • - infac360hc_mt_associate_email_inbound
  • - infac360hc_mt_associate_address_inbound
  • - infac360hc_m_associate_root_inbound
  • - infac360hc_m_associate_social_handle_inbound
  • - infac360hc_m_associate_phone_inbound
  • - infac360hc_m_associate_email_inbound
  • - infac360hc_m_associate_address_inbound
Imports data from the FHIR file to the Associate business entity.

Batch jobs of HCO business entity

Use batch jobs to integrate data from source systems to Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with Customer 360 business entity fields.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress data from NPPES:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_ingress_nppes_hco_inbound
infac360ls_tf_nppes_hco_inbound
  • - infac360ls_mt_nppes_hco_inbound_legalName
  • - infac360ls_mt_nppes_hco_inbound_license
  • - infac360ls_mt_nppes_hco_inbound_identifier
  • - infac360ls_mt_nppes_hco_inbound_keyPeople
  • - infac360ls_mt_nppes_hco_inbound_phone
  • - infac360ls_mt_nppes_hco_inbound_address
  • - infac360ls_mt_nppes_hco_inbound_alternateName
  • - infac360ls_mt_nppes_hco_inbound_specialty
  • - infac360ls_m_nppes_hco_inbound_legalName
  • - infac360ls_m_nppes_hco_inbound_license
  • - infac360ls_m_nppes_hco_inbound_identifier
  • - infac360ls_m_nppes_hco_inbound_keyPeople
  • - infac360ls_m_nppes_hco_inbound_phone
  • - infac360ls_m_nppes_hco_inbound_address
  • - infac360ls_m_nppes_hco_inbound_alternateName
  • - infac360ls_m_nppes_hco_inbound_specialty
Imports data from the NPPES file to the HCO business entity.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress data from MedPro Systems:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_trigger_ingress_medpro_HCO_HCP
infac360ls_tf_medpro_trigger_inbound_job
  • - infac360ls_mt_medpro_hco_inbound_root
  • - infac360ls_mt_medpro_hco_inbound_specialty
  • - infac360ls_mt_medpro_hco_inbound_alternateName
  • - infac360ls_mt_medpro_hco_inbound_certification
  • - infac360ls_mt_medpro_hco_inbound_phone
  • - infac360ls_mt_medpro_hco_inbound_address
  • - infac360ls_mt_medpro_hco_inbound_license
  • - infac360ls_mt_medpro_hco_inbound_sampleability
  • - infac360ls_mt_medpro_hco_inbound_identifier
  • - infac360ls_m_medpro_hco_inbound_root
  • - infac360ls_m_medpro_hco_inbound_specialty
  • - infac360ls_m_medpro_hco_inbound_alternateName
  • - infac360ls_m_medpro_hco_inbound_certification
  • - infac360ls_m_medpro_hco_inbound_phone
  • - infac360ls_m_medpro_hco_inbound_address
  • - infac360ls_m_medpro_hco_inbound_license
  • - infac360ls_m_medpro_hco_inbound_sampleability
  • - infac360ls_m_medpro_hco_inbound_identifier
Imports data from the MedPro Systems response file to the HCO business entity.
infac360ls_egress_medpro_hco_outbound
infac360ls_tf_medPro_hco_outbound
infac360ls_mt_medPro_hco_outbound
infac360ls_m_medPro_hco_outbound
Exports data from the HCO business entity to a MedPro Systems request file.

Batch jobs of HCP business entity

Use batch jobs to integrate data from source systems to Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with Customer 360 business entity fields.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress data from NPPES:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_ingress_nppes_hcp_inbound
infac360ls_tf_nppes_hcp_inbound
  • - infac360ls_mt_nppes_hcp_inbound_legalName
  • - infac360ls_mt_nppes_hcp_inbound_license
  • - infac360ls_mt_nppes_hcp_inbound_identifier
  • - infac360ls_mt_nppes_hcp_inbound_phone
  • - infac360ls_mt_nppes_hcp_inbound_address
  • - infac360ls_mt_nppes_hcp_inbound_alternateName
  • - infac360ls_mt_nppes_hcp_inbound_specialty
  • - infac360ls_m_nppes_hcp_inbound_legalName
  • - infac360ls_m_nppes_hcp_inbound_license
  • - infac360ls_m_nppes_hcp_inbound_identifier
  • - infac360ls_m_nppes_hcp_inbound_phone
  • - infac360ls_m_nppes_hcp_inbound_address
  • - infac360ls_m_nppes_hcp_inbound_alternateName
  • - infac360ls_m_nppes_hcp_inbound_specialty
Imports data from the NPPES file to the HCP business entity.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress data from MedPro Systems:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360ls_trigger_ingress_medpro_HCO_HCP
infac360ls_tf_medpro_trigger_inbound_job
  • - infac360ls_mt_medpro_hcp_inbound_root
  • - infac360ls_mt_medpro_hcp_inbound_specialty
  • - infac360ls_mt_medpro_hcp_inbound_dea
  • - infac360ls_mt_medpro_hcp_inbound_status
  • - infac360ls_mt_medpro_hcp_inbound_phone
  • - infac360ls_mt_medpro_hcp_inbound_address
  • - infac360ls_mt_medpro_hcp_inbound_license
  • - infac360ls_mt_medpro_hcp_inbound_taxonomy
  • - infac360ls_mt_medpro_hcp_inbound_sampleability
  • - infac360ls_mt_medpro_hcp_inbound_enrichmentStatus
  • - infac360ls_mt_medpro_hcp_inbound_identifier
  • - infac360ls_m_medpro_hcp_inbound_root
  • - infac360ls_m_medpro_hcp_inbound_specialty
  • - infac360ls_m_medpro_hcp_inbound_dea
  • - infac360ls_m_medpro_hcp_inbound_status
  • - infac360ls_m_medpro_hcp_inbound_phone
  • - infac360ls_m_medpro_hcp_inbound_address
  • - infac360ls_m_medpro_hcp_inbound_license
  • - infac360ls_m_medpro_hcp_inbound_taxonomy
  • - infac360ls_m_medpro_hcp_inbound_sampleability
  • - infac360ls_m_medpro_hcp_inbound_enrichmentStatus
  • - infac360ls_m_medpro_hcp_inbound_identifier
Imports data from the MedPro Systems to the HCP business entity.
infac360ls_egress_medpro_hcp_outbound
infac360ls_tf_medPro_hcp_outbound
infac360ls_mt_medPro_hcp_outbound
infac360ls_m_medPro_hcp_outbound
Exports data from the HCP business entity to a MedPro Systems request file.

Batch jobs of the Organization business entity

Use batch jobs to integrate data from source systems to Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with Customer 360 business entity fields.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress FHIR R4 standard-compliant records:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360hc_ingress_organization_inbound
infac360hc_tf_organization_inbound
  • - infac360hc_mt_organization_root_inbound
  • - infac360hc_mt_organization_status_inbound
  • - infac360hc_mt_organization_associate_rel_inbound
  • - infac360hc_mt_organization_social_handle_inbound
  • - infac360hc_mt_organization_phone_inbound
  • - infac360hc_mt_organization_identifier_inbound
  • - infac360hc_mt_organization_email_inbound
  • - infac360hc_mt_organization_alternatename_inbound
  • - infac360hc_mt_organization_address_inbound
  • - infac360hc_m_organization_root_inbound
  • - infac360hc_m_organization_status_inbound
  • - infac360hc_m_organization_associate_rel_inbound
  • - infac360hc_m_organization_social_handle_inbound
  • - infac360hc_m_organization_phone_inbound
  • - infac360hc_m_organization_identifier_inbound
  • - infac360hc_m_organization_email_inbound
  • - infac360hc_m_organization_alternatename_inbound
  • - infac360hc_m_organization_address_inbound
Imports data from the FHIR file to the Organization business entity.

Batch jobs of the Practitioner business entity

Use batch jobs to integrate data from source systems to Customer 360.
Each job uses a taskflow to run a mapping task. Each mapping task includes a mapping that maps source system fields with Customer 360 business entity fields.
The following table lists the sample jobs and their related taskflow, mapping task, and mapping to ingress FHIR R4 standard-compliant records:
Job Name
Taskflow
Mapping Task
Mapping
Description
infac360hc_ingress_practitioner_inbound
infac360hc_tf_practitioner_inbound
  • - infac360hc_mt_practitioner_root_inbound
  • - infac360hc_mt_practitioner_education_inbound
  • - infac360hc_mt_practitioner_license_inbound
  • - infac360hc_mt_practitioner_phone_inbound
  • - infac360hc_mt_practitioner_address_inbound
  • - infac360hc_mt_practitioner_alternatename_inbound
  • - infac360hc_mt_practitioner_email_inbound
  • - infac360hc_mt_practitioner_social_handle_inbound
  • - infac360hc_mt_practitioner_language_inbound
  • - infac360hc_mt_practitioner_identifier_inbound
  • - infac360hc_mt_practitioner_status_inbound
  • - infac360hc_m_practitioner_root_inbound
  • - infac360hc_m_practitioner_education_inbound
  • - infac360hc_m_practitioner_license_inbound
  • - infac360hc_m_practitioner_phone_inbound
  • - infac360hc_m_practitioner_address_inbound
  • - infac360hc_m_practitioner_alternatename_inbound
  • - infac360hc_m_practitioner_email_inbound
  • - infac360hc_m_practitioner_social_handle_inbound
  • - infac360hc_m_practitioner_language_inbound
  • - infac360hc_m_practitioner_identifier_inbound
  • - infac360hc_m_practitioner_status_inbound
Imports data from the FHIR file to the Practitioner business entity.