Run and Test Integrations for Healthcare Analytics

• The source files must be in comma-separated values (CSV) format. Any other format fails the integrations.
• When input parameters are incorrect, the integration fails.
• When files are missing or fail, the integration fails.
• Integrations cannot run simultaneously but only one at a time.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

   Example: For test runs, it can be helpful to change the filename.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • Each Work Unit Code and Work Unit Name is unique.
   • The Work Unit Code cannot be longer than 50 characters.
   • The Work Unit Name cannot be longer than 256 characters.
   • The organizational path in the work unit configuration must correspond to a path in the business structure.
   • The default Service Line is UNK_SVC_LN.
   • FTE Hours has 6 decimal places or less.
   • Each WFD Pay Rule is defined in the database.
   • Work Group Code is optional even if the Work Unit Type is a work group.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Hyperfinds A search engine that filters and selects groups of employees through queries that specify conditions or locations (criteria). Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Hyperfinds Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Hyperfind Profiles Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Unit Hyperfind Profiles Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Group Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. If the integration run failed , check for errors in the following:
   • Each Work Group Code is unique.
   • Each Work Group Code and Work Group Description is not blank.
   • The maximum length of Work Group Code is 50 characters, and Work Group Description is 256 characters.
   • No records are duplicated.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Work Group Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Job Code Work Group Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • Each combination of Job Name and Work Group Code is unique.
   • A job cannot be mapped to more than one work group.
   • Each Job Name and Work Group Code is not blank.
   • The generic jobs and work groups must be defined in the system.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Job Code Work Group Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Billing Department Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • The work units must be defined in the system.
   • Work Unit Code, Billing Facility Code, and Billing Department Code must be unique, because the system cannot determine which duplicate record is correct.
   • Only Facility, Department, and Custom type work units are supported; Combination type work units are not supported.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Billing Department Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Charge Master Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • Billing Facility Code, Billing Department Code, and Procedure Code must be unique, because the system cannot determine which duplicate record is correct.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Charge Master Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

   Example: If the Effective Date and Weight for the same Procedure Code change, the integration exports two records. Time periods cannot overlap, so a later Effective Date sets an end date for the previous record. Example: An Effective Date of 12/1/2021 on the second record ends the previous record on 11/30/2021.

   Example charge master export

   Billing Facility Code	Billing Department Code	Procedure Code	Procedure Code Description	Weight	Effective Date
   1183140-MedSurg1	1183140-MedSurg1	0011072	X-Ray MedSurge 1	1.000000	1/1/2021
   1183140-MedSurg1	1183140-MedSurg1	0011072	X-Ray MedSurge 1	1.500000	12/1/2021

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Volume Department Copy Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • Billing Facility Code, Billing Department Code, Destination Billing Facility Code, and Destination Billing Department Code must be unique, because the system cannot determine which duplicate record is correct.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Volume Department Copy Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Volume Department Copy Override Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. If the integration run failed , check for errors in the following:
   • Billing Facility Code, Billing Department Code, Destination Billing Facility Code, Destination Billing Department Code, and Procedure Code must be unique, because the system cannot determine which duplicate record is correct.
   • Make sure that the combination of the Billing Facility Code and Billing Department Code in the source file and the destination file is configured in the billing department mapping.
   • Avoid looping logic between the Volume Department Copy and Volume Department Copy Override integrations. Example: Do not import volume departments, override those departments, then import again those same departments.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Volume Department Copy Override Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Department Mapping Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. If the integration run failed , check for errors in the following:
   • Each paycode A category of time or money that employees earn, for example, Regular Hours, Bonus, or Sick. must be unique within the input file.
   • The same Payroll Facility Code, Payroll Department Code, or Payroll Source must not map to multiple work units, unless the Delete Switch for all but one of the work units is 1. The combined payroll facility, department, and source must be unique.
   • Each Delete Switch is 0 or 1.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Department Mapping Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Employment Status Mapping Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Employment Status Mapping Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Job Mapping Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. If the integration run failed , check for errors in the following:
   • The same Labor Category Entry (payroll job) and Payroll Source must not map to multiple Job Names (generic jobs), unless the Delete Switch for all but one of the jobs is 1.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Payroll Job Mapping Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Targets Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. If the integration run failed , check for errors in the following:
   • Fixed and Variable targets are validated.
     • If a validation fails, the target definition is rejected for that combined work unit and metric.
     • Fixed or Variable targets that are empty are excluded from the target definition for a combined work unit, metric, and effective date.
   • Fixed target validations:
     • Each fixed target must have a default value.
     • Targets must be numbers; alphabetic characters are not valid.
     • Maximum length of the target is 10 digits before and 6 digits after the decimal point.
     • The Adjustment Flag applies only to the Productive Hours (daily or pay period) metric.
   • Variable target validations:
     • Each pay-period and daily-ratio target must have a default value. Alternate pay-period values are optional.
     • Targets must be numbers; alphabetic characters are not valid.
     • Maximum length of the target is 10 digits before and 6 digits after the decimal point.
     • If any fixed or variable target has an error, you must submit all of the data again.
     • Group records by Work Unit Code and metric name so that multiple records for the same combined work unit and metric are together and validated for date overlaps.
     • Work units must have pay periods defined in the system before you can import the targets for the pay period end date. Otherwise, these records fail the integration run.
   • Date-overlap validations: The same pay period (same start and end dates) cannot have more than one target definition. Otherwise, the records for that work unit and metric are rejected.
   • The Start Date of a pay period is used as the effective date. The expiration date is forever or is calculated if the same work unit has multiple pay periods. For multiple pay periods, the most recent last date of a pay period has an expiration date of forever, and all other pay period end dates are the respective expiration dates.
   • The possible values for targetType are hca_fixed_target and hca_variable_target.
   • For targetFunctions, the values contain name = PRODUCTIVE_HRS and qualifier = METRIC_SET.
   • All of the required fields are not blank.
   • Each Work Unit Code and Pay Period End Date is unique.
   • The date format is MM/DD/YYYY.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Targets Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

6. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
7. Make sure that the exported data corresponds to the source data:
   1. Open the source (input) and exported (output) files.
   2. Compare the data for accuracy.

1. Make sure that Fiscal Calendar Import is Allowed in your FAP; see Configure Access to Healthcare Analytics.
2. Select Main Menu  > Maintenance > Integrations. 
3. Click Tap Run an Integration . 
4. Select the Fiscal Calendar Import integration. Click Tap Select.
5. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

6. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

7. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
8. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
9. If the integration run failed , check for errors in the following:
   • All dates for this fiscal year are in sequence, and no date is skipped between any first and last entry.
   • FSCL_DAY_OF_YR_NBR starts at 1 and goes up in incremental order.
   • FSCL_WK_OF_YR_NBR starts at 1 and repeats in incremental order.
   • FSCL_MO_OF_YR_NBR starts at 1 and repeats in incremental order.
   • FSCL_QTR_OF_YR_NBR starts at 1 and repeats in incremental order.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

1. Select Main Menu  > Maintenance > Integrations.
2. Click Tap Run an Integration . 
3. Select the Volume Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. Set parameters:

   Select or enter the following parameters or files:

   • Billing Filename
   • Patient Flag
   • Is Billing File Rolling?
   • Manual Filename
   • Is Manual File Rolling?

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. When the import process starts and finishes, notifications go the Control Center and by email.
9. If the integration run failed , check for errors that are common to all integrations; see Check the results > Troubleshooting.
   • Rename the volume exception file and consolidate the exceptions in that file.
   • Move that file to the Inbound folder.
   • Re-run the Volume Import integration to import the rows from the volume exception file.

Volume import use case – new Charge Master

The Volume Import integration creates a new charge master if one is not defined in the database.

Scenario: This integration processes a CSV input file that contains new charge-master records with or without weights.

• The volume feed has records with charges that are already in the charge master: the charges are aggregated and weight is allocated.
• The volume feed has records with charges that are not in the charge master:
  • The integration does not check whether the charges exist for the service date, but it checks only the charges in the database.
  • The charges are added to the database with weight of null and an effective date set to the beginning of time.

    Example volume import for a new charge master

    Field	Charge master in database
    Billing Facility Code	Fac1
    Billing Department Code	Dept
    Procedure Code	Procedure code1
    Procedure Code Description	Procedure code1 description
    WEIGHT	null
    Effective Date	01/01/1753 (Beginning of Time)

    Note:

    • Records that have the unknown charge weight of null are written to an exception file and are not added to the database.
    • When you run the Charge Master Export integration, it exports the entire table and filters out the null weights.
    • Update the weights in the exported SCV file, and re-run the Charge Master Import integration with new weights to replace the charge master exceptions.

Volume import use case – Charge Master updates

If the charge master is in the system already, and you import a volume feed with a new weight for the charge master, the system expires the previous charge master with an effective end date of the day before the day you imported the volume feed (load date — 1). The system creates a new charge master with an effective date of the day you imported the volume feed (load date).

To see the records, run the Charge Master Export integration.

Volume import use case — Aggregation

Volume quantity is aggregated for records in the same file with facility number, department number, billing code, and service date.

Volume import use case — Correction or override

• If the post date and service date are the same for earlier records, new records override VOL_QTY (volume quantity). Example: File2_Record1 replaces the volume quantity from File1_Record1.
• If the post date is different, the volume quantity of the earlier records is aggregated, and the weighted volume for the service date accounts for the aggregated value for productivity metrics Measures and tracks workforce performance by comparing planned with actual workload or coverage, or by showing variances at any organizational level..
• For corrections, a negative volume quantity is supported.

1. Select Main Menu  > Maintenance > Integrations.
2. Click Tap Run an Integration . 
3. Select the Payroll Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. When the import process starts and finishes, notifications go the Control Center and by email.
9. If the integration run failed , check for errors in the following:

   Note: The Payroll import integration processes employee data in batches for a pay period end date. If any records in the batch fail the validations, the integration fails all records for that employee for that pay period end date. This prevents the integration from importing invalid records. Check the error message for details.

   • The payroll data must be only for regular employees and not include data for agency employees.
   • Date formats are MM/DD/YYYY or MM-DD-YYYY.
   • The integration run fails if the following occur:

     Multiple primary job codes for an employee during one pay period

     Multiple employment status for an employee during one pay period

     Multiple standard hours Non-overtime hours that each employee is expected to work. values for an employee during one pay period

     Multiple home departments for an employee during one pay period

     Multiple payroll sources for the same employee during one pay period

   • Each EMP_NBR must be unique across all payroll source files.
   • The following are optional but cannot be blank:

     Caution: If these fields do not apply to a record, enter 0 for the value.

     STD_HRS

     PAY_RATE_AMT

     PAYROLL_PAYCD_HRS

     PAYROLL_PAYCD_AMT

   • The following must contain a distinct value for each combination of employee and pay period:

     HM_DEPT_COD

     STD_HRS

     PAYROLL_EMPLMT_STAT_COD

     PRI_JOB_COD

     SRC_COD: Must be a unique code that identifies the payroll source file and differentiates between payroll systems.

   • If the error indicates a Bad File, do the following:

     Open the source file and replace all values with zero (0).

     Run the integration again with this file that has the hours and amounts zeroed. This overrides the bad records that were imported.

     Find the correct file and run the integration again with that file.

   • Extra part time hours for an employee are calculated based on the paycode and the mapping category for the associated paycode.
   • For errors that are common to all integrations; see Check the results > Troubleshooting.

Payroll import use case — Aggregation

The hours and amounts are aggregated if there are multiple records for an employee for the same pay period that matches the following field values in the file:

• Employee number
• Payroll Home Facility
• Payroll Home Department
• Payroll Worked Facility
• Payroll Worked Department
• Payroll Pay Code
• Job Code (Paid Job)
• Payroll Employment Status Code
• Pay Period End Date
• Payroll Source

Payroll import use case — Correction or override

To correct already imported records, zeroed hours and amounts must be imported with the exact same set of values for the following fields:

• Employee number
• Payroll Home Facility
• Payroll Home Department
• Payroll Worked Facility
• Payroll Worked Department
• Payroll Pay Code
• Job Code (Paid Job)
• Payroll Employment Status Code
• Pay Period End Date
• Payroll Source

The record date of File 2 overrides the record date of File 1.

For an employee for a pay period, these fields cannot have more than one value. To correct the following values, the system must import a correction record that has zeroed hours and amounts:

• Primary job code
• Employment status
• Standard hours
• Home department
• Payroll source

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Agency Export integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.
5. Set parameters:

   Select or enter the following parameters:

   • Reference Date from which to export the transactional punches The entries on a timecard that mark the beginning (in-punch) or end (out-punch) of a work interval, such as the beginning of a shift or transfer. of agency employees. If you do not select a date, the integration exports the past 90 days of punches.
   • Hyperfind: Leave the default Agency Employees or All People hyperfind query selected.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

   Caution: Do not modify the exported CSV file.

7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Agency Import integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.

5. (Not recommended) You can select a different source file. Click Tap Browse and navigate to and select the file.

   Caution:

   • To support scheduled integration runs, do not select a different source file. The default file was generated from the installation kit, and a scheduled integration cannot run without it.
   • (Required) Make sure that only one file with this filename is on the SFTP server at a time. Otherwise, the data can become corrupted.
   • The maximum size of source file is 1 MB. However, you can compress a larger file and select the compressed *.zip file as the source file.
   • The format of the file must be .csv, .zip, .pgp, or .gpg.

6. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.

   See Check the results.

7. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
8. When the import process starts and finishes, notifications go the Control Center and by email.
9. Make sure that the imported data corresponds to the exported (source) data:
   1. Open the source (input) and imported (output) files.
   2. Compare the data for accuracy.

If changes are made to volume or payroll configurations, you can process the historical data again to fit the new configuration.

1. Select Main Menu  > Maintenance > Integrations. 
2. Click Tap Run an Integration . 
3. Select the Recalculate integration. Click Tap Select.
4. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, the default name ends with a date and time stamp.
5. In Domain, select one of the following:
   • All (default): Recalculate payroll and volume data. Both recalculations run independently and do not interfere with each other.
   • Payroll: Recalculate payroll data only.
   • Volume: Recalculate volume data only.
6. Select bothStart Date and End Date, or select neither as follows:
   • Select a Start Date from which to start recalculating the payroll data or raw volume. Set the Start Date to be same as the start date of a pay period.

     Select an End Date to be the last date of the recalculation. Set the End Date to be same as the end date of a pay period.

   • Do not select either start or end dates; then, the integration recalculates for the default date range of today and the 29 previous days.

7. Click Tap Run Integration.

   1. Wait for the confirmation that the integration completed  or failed . Close the panel.
   2. Click Tap Refresh . 
   3. To see details, select the integration run. Select Run Summary.
8. When the integration run starts and when it finishes, notifications go to the Control Center and by email.
9. When the integration runs successfully, the Run Summary shows the execution key for the domain that was recalculated.

   When the recalculate process starts and finishes, notifications go the Control Center and by email.

10. If the integration run failed , check for errors in the Run Summary.

On the Integrations page, each tile A container that provides navigation or action from its summary view. indicates the current status of integration runs as follows:

Status indicators

•  In-Progress: The run of this integration has not yet completed.
•  Completed: The integration ran successfully without errors.
•  Scheduled: This integration is scheduled to run later or repeatedly.
• (Grayed out) Scheduled but Deleted: This integration is scheduled to run, but the integration template has been deleted. When it runs, it will generate an error. To prevent this error, delete the scheduled integration run.
•  Completed with Errors: The integration ran successfully, but one or more records have errors. The integration run is treated as failed. If Abort on Failure is configured in an integration set A sequence of integrations that can be run on-demand or be scheduled., the integration set stops.
•  Failed: The integration run has errors or could not run.
• To troubleshoot and resolve errors, do the following:

  Check the Run Summary for details.

  • To troubleshoot all types of errors, or if the Run Summary shows a large number of errors, click tap Go to Additional Details (if available), or click tap the Source File to open and examine the input source file.
  • (Only for import integrations) To troubleshoot and resubmit integrations that have transactional or data errors, click tap Go to Transaction Assistant Corrects transaction errors in integrations without the need to resubmit entire projects..

Note: Only import integrations can have a status of Partial Failed. Export integrations export all records for the run to complete or no records for the run to fail; export integrations cannot partially succeed.

The Run Summary shows an overview of the results of an integration run.

1. Click Tap the tile for a completed integration run.
2. Click Tap Run Summary to see the results of the integration run.

3. Run Summary details

   • Integration Type: Import or Export
   • Records Processed: Number of records that were processed
   • Records Created: Number of records that were created
   • Errors: Number of records that failed
   • Source Files: For file-based import integrations, click tap the flat file to see the input source for the integration.
   • Output File: For file-based export integrations, click tap the CSV file to see the exported data.
   • Error Files: If the run of a file-based integration has errors, click tap the CSV file. The filename starts with exception_. This file lists the records that have errors, each record to a row, and is kept for 30 days. The Exception Details column in the file provides a detailed message for each error. If a record has multiple errors, each error message is separated by a semi-colon (;). You can edit this file and reload it.

To check the results in more detail and troubleshoot errors, do the following:

1. In Error Files, open the exception file to find the erroneous records and see details.
   • The filename starts with exception_. Example: exception_work_units_*.csv
   • This file lists the records that have errors, each record to a row.
   • The Exception Details column in the file provides a detailed message for each error.
   • If a record has multiple errors, each error message is separated by a semi-colon (;).
   • You can edit this file and reload it.
2. In Source Files, open the generated CSV file and check for the following errors that are common to all integrations in addition to any errors that are specific to an integration:
   • The first row of the file is a header.
   • The headers are correct.
   • All of the required fields are completed and are not blank (null). If these fields do not apply to a record, enter 0 for the value.
   • Formats are correct. Example: Dates are in MM/DD/YYYY or MM-DD-YYYY format.
   • Number fields are right-justified and have no leading zeros.
   • Negative numbers show the minus (—) sign to the left of the number (floating).
   • Field values which must be unique are unique. Example: EMP_NBR must be unique across all payroll source files.
   • If the integration depends on data from previous integrations or external processes, make sure that those integrations or processes finish before this integration starts.

     Example: Payroll Facility and Department Facility Mappings must finish before you can import the payroll records.

     Note: Use integration sets to sequence integration runs; see Configure Integration Sets for Healthcare Analytics.

3. If the source file does not open, navigate to the SFTP server and check the following:
   • The file type is .csv
   • There is only one version of the file. If an integration has multiple files, the system selects one file at random to prevent data corruption.
   • The filename is correct. Example: payroll_*.csv
4. Log into the destination system and make sure that the data has been correctly updated.

   Examples:

   • Check the Work Unit Definitions to see if the integration imported the work units correctly; see Configure Work Units.
   • Check the Target Management to see if the integration imported the targets and thresholds correctly; see Configure Standard Targets.

During day-to-day operations, run the integrations as needed for initial setup and then ongoing updates.

Click Tap Run Integration.

1. Wait for the confirmation that the integration completed  or failed . Close the panel.
2. Click Tap Refresh . 
3. To see details, select the integration run. Select Run Summary.

You can schedule integrations or integration sets to run once later or at a recurring frequency.

1. Click Tap Main Menu  > Maintenance > Integrations. 
2. Click Tap Schedule Processes .

   Note: If you don't see this button, click tap Run Processes to toggle the labels.

3. Click Tap Schedule an Integration . 
4. Select the integration or integration set from the list. Click Tap Select. 
5. (Optional) Enter a unique Integration Run Name to make it easier to identify the run of the integration. Otherwise, you use the default name which ends with a date and time stamp.

   Note: Include "IntegrationSet" in the name for integration sets to make it easier to distinguish integrations from integration sets on the Integrations page.

6. Select or enter any parameters or files that are required. Required and optional parameters, and external files vary by integration.

   Caution: For integration sets, repeat this step for each integration in the integration set.

7. In Schedule, select one of the following:

   Caution: Although integrations run in parallel and independently, if you schedule the same integration or integration set to run repeatedly at short intervals, errors can result. Also frequent runs increase the traffic load on the network. A best practice is to space runs at least 15 minutes apart. Example: If two integrations access and update a file, the first integration must finish the update before the second integration starts to update the same file. If the first integration moves or erases that file before the second can access it, the second integration fails.

   • One-time Scheduled Run

     1. Select a date . 
     2. Click Tap Apply.
     3. Enter the Start Time. 
     4. Click Tap Schedule Integration. 
     5. Close the panel.

   • Recurring Scheduled Run

     Repeat the run on a regular schedule.

     1. Click Tap Recurrence .
     2. From Repeats, select the frequency of runs:

        By Month

        • Select the months.
        • Select the day of the month.

        By Day — Select the number of days between runs.

        By Hour — Select the number of hours between runs.

        By Week

        • Select the number of weeks between runs.
        • Select the day of the week.

        By Minute — Select 5-minute intervals.

     3. Select the Start Date. 
     4. Enter the Start Time. 
     5. Select the End Date. If you select Forever or leave the End Date blank, the schedule recurs indefinitely. 
     6. Click Tap Apply.
     7. Click Tap Schedule Integration Request. 
     8. Close the panel.
     9. Close the panel.