When you integrate MDM SaaS with MedPro systems, you can synchronize the records of MedPro Systems with MDM SaaS and enrich the MDM SaaS records.
You can synchronize the records of Healthcare Organization and Healthcare Practitioner in MedPro Systems with MDM SaaS records.
To enrich the MDM SaaS records using MedPro Systems, perform the following tasks:
1Egress data. Run the predefined egress jobs to export data from the HCO and HCP business entities of Customer 360 to the request files of MedPro Systems. The egress job generates the HCO and HCP request files and places them in the SFTP inbound directory.
2Ingress data. Run the predefined ingress jobs to import data from the MedPro Systems response files to the Customer 360 business entities and update the original records. You can choose to run the predefined ingress jobs automatically or manually.
Egress data
When you egress data from Customer 360 to MedPro Systems, the egress job generates a flat file in the .csv format. The flat file contains the records to be processed from Customer 360 and places the file in the inbound directory of MedPro SFTP location. To keep track of the files in the inbound directory, a copy of the flat file is added to the following local directory of the Secure Agent system:
MedproIntegration\Outbound
You can specify the export job types to select the records to be processed. The Cloud Data Integration taskflow logs the status of the processed records in the RunStatus-Outbound flat file. When a new flat file is placed in the inbound directory of MedPro Systems SFTP location, MedPro Systems detects the file, searches for matching records, and generates an enriched records file. MedPro Systems adds the enriched records file to the outbound directory of the MedPro Systems SFTP location.
For more details about egress jobs, see Batch jobs.
The following image shows the data flow from Customer 360 to MedPro Systems:
Ingress data
The ingress job uses Cloud Application Integration processes to read the file that contains enriched records in the outbound directory of the MedPro Systems SFTP location.
You can run the ingress job automatically or manually. After you import the assets, both the trigger process are enabled by default. To run the ingress job automatically, disable the manual trigger process. To run the ingress job manually, disable the automated trigger process. To disable the process, see Unpublishing a process.
The following table lists the triggers to run the ingress job and Cloud Application Integration processes:
The process renames the file that contains enriched records to add the done suffix. The process also triggers the infac360ls_tf_medpro_read_write_Filename_local Cloud Data Integration taskflow. The Cloud Data Integration taskflow updates the file in the file list in the following directory:
MedproIntegration\Inbound
The process then creates a copy of the file with a header structure in the following local directory of the Secure Agent system:
MedproIntegration\HeaderFiles
Cloud Data Integration uses the infac360ls_tf_medpro_read_write_Filename_local taskflow to generate a header file.
When you run the ingress job automatically or manually, Cloud Data Integration uses the infac360ls_tf_medpro_trigger_inbound_job taskflow to trigger the ingress job.
You can also manually schedule the ingress job to import the file with enriched records.
For more details about ingress jobs, see Batch jobs.
The following image shows the data flow from MedPro Systems to Customer 360:
Enriching Customer 360 records with MedPro Systems records in real time
When you create a record in Customer 360, you can search for matching records in MedPro Systems. You can then enrich Customer 360 records with data from MedPro Systems in real time.
Customer 360 for Healthcare extension uses Cloud Application Integration processes to search for similar records and to import the records into Customer 360.
The following image shows the process to search for matching records before you create a record in Customer 360:
