Procella Helpdesk- The provider network batch process allows the user to create/update/modify the provider networks within a PBM.
- For more details on that batch file layout, refer to Provider Network Batch Load Layout
How to Run Provider Network Batch
- This process is similar to any other batch load process in the system.
- Provider Network Batch configuration should be created and activated in order to load a batch file.
- To create a Provider Network Batch configuration, Navigate to Administration / Data Management. Click on the Add icon and select Provider Network in the Job type
- Enter the data in the job configuration. Save and activate it.
- Once the job configuration is activated, the prepared batch file needs to be placed in the respective S3 folder to load. Refer to this article for more details on how to initiate and view the stats once the loading is completed.
About Provider Network Error File
- The Provider Network stats can be viewed in the Job Execution Details screen. The status would look like this,
- In the status, You can see that a total of 6 provider network records were in the batch file, out of which 5 have been successfully processed and 1 has failed due to some reason.
- The failure reason can be viewed in the Error file. Error file will have details of all the failed records and the error message explaining the reason for failure.
- The error file can be found in S3 bucket. The error file path will be shared in the Job notification email.
Error Code / Error Message
| Error Code | Error Message | Scenario |
| VAL_<FIELD_NAME>_ SHOULD_NOT_BE_NULL | Field name should not be blank. | When any of the mandatory fields are left blank. |
VAL_<FIELD_NAME>_ | Field name cannot exceed <maximum length> characters. | When any field exceeds the maximum allowed length |
VAL_ACTION_CODE_ | Action code must be on of the following values: A, U, M | When the given action code is anything other than A,U,M |
VAL_EFFECTIVE_END_DATE_
| The effective end date should be after effective start date.
| When the effective end date is less than the effective start date |
VAL_STATUS_ID_
| Status ID must be on of the following values A, D
| When the given status ID is anything other than A or D |
VAL_PROVIDER_NETWORK_ID_
| Provider network was not found. Provider network ID: <providerNetworkId>
| For Update (U)/ Modify (M) action code, if the given provider network id is not found in the PBM |
VAL_PROVIDER_NETWORK_ID_ | Provider network information was not found. Provider network ID: {providerNetworkId}
| For Update (U)/ Modify (M) action, an active provider network version should exist in the system. This error shows up, if provider network exist but in draft version. |
VAL_PROVIDER_NETWORK
| Provider network already exists, this record will be skipped. Provider network ID: <providerNetworkId>
| For Add (A) action, if the given provider network id already exists in the PBM |
VAL_PROVIDER_NETWORK_
| Provider network name should be unique. Provider network name: <providerNetworName>
| Provider Network Name has to be unique within a PBM. If the given provider network name is not unique then this error will appear in the error file |
VAL_PAYMENT_GROUP_ID
| Payment group was not found. Payment group ID: <paymentGroupId>
| When the given payment group ID is not found within the PBM |
VAL_REMITTANCE_GROUP_ID
| Remittance group was not found. Remittance group ID: <remittanceGroupId>
| When the given remittance group ID is not found within the PBM |
VAL_ANY_WILLING_PROVIDER
| The Any willing provider field cannot be 'Y' if any providers are sent.
| This error shows up when Any willing provider is 'Y' and also PR,PG or PP records are present within a provider network record |
VAL_SERVICE_PROVIDER_ID_AND
| No provider found for Service Provider ID: <serviceProviderIdValue> and Service Provider ID Qualifier: <serviceProviderIdQualifier>
| When the provider cannot be identified in the PBM with the given service provider ID and service provider ID qualifier |
VAL_PROVIDER_GROUP_ID
| No provider group found for Provider Group ID: <providerGroupId>
| When the provider group cannot be identified in the PBM with the given provider group ID |
VAL_PROVIDER_PARENT_ID
| No provider group found for Provider Group ID:<providerParentId>
| When the provider parent cannot be identified in the PBM with the given provider parent ID |
VAL_NE_METADATA_ID
| No metadata found for Metadata ID <Edit ID>
| When the given Edit ID in the provider network record is not valid/does not exist in the PBM |
VAL_NB_METADATA_CATEGORY_ID VAL_NE_METADATA_CATEGORY_ID
| <Metadata Category name> edit category is not allowed to use. Metadata ID: <Metadata ID>
| When the given Edit ID is anything other than the allowed Edits. Allowed edits in NB and NE records are
|
VAL_NB_METADATA_CATEGORY_ID VAL_NE_METADATA_CATEGORY_ID
| <MetadataCategoryName> edit is already in the record. Metadata ID: <Metadata ID>
| If the edits category is repeated in NB or NE records within a single provider network record |
VAL_NB_CRITERIA_ID
| No criteria found for Criteria ID: {criteriaId}
| If the given Criteria ID is NOT found in the PBM or the given criteria is not in active status |
PROC_ITEM_ERROR
| Unknown exception occurred
| If an error occurred when creating/updating /modifying provider network records. Dev team support may be required to analyse this further. Write to support@procellahealth.zendesk.com for help |