Skip to main content

 

Model N Helpcenter

Transmission of Data from Validata to Formulary Product Master (FPM)

  1. Last updated
  2. Save as PDF

Overview

For the Manufacturer who had procured the Formulary Compliance sub-module license, when the Validation process is initiated for a Non-Coverage Gap Submission in the Validata application, a list of data about the Submission will be transmitted to the Formulary Product Master (FPM) application. The data transmission to FPM will happen only for the Non-Coverage Gap Submission where the ‘Submission receipt date/ postmark date’ value is later than or equal to the F1 effective Start Date (f1Subscriber effectiveStartDate) configured in the Tennant Configuration file.

Note: When the ‘Submission receipt date/ postmark date’ value is before the F1 effective Start Date, data transfer to FPM will not initiated.

Transmission of the data from Validata to the FPM application will be initiated in the below scenarios:

  • When a new Submission is created and validation is initiated.

  • Submission for which data was previously transmitted to FPM but at a later point in time changes have been done in the Submission File tab (new file addition, file level changes, Contract change for Submission, etc…) and the Submission is re-validated.

  • When a new Submission is created or an existing Submission has been updated (new file addition, file level changes, Contract change for Submission, etc…) but the Submission is not Validated, the nightly job CMnFPMRequestScheduler sends the data for the Submission to the FPM application.

Note: Apart from this, no other Submission life cycle status change impacts the triggering of data transmission from Validata to FPM.

The Validata application transmits the following set of data to FPM, during the transmission process:

  • Tenant ID

  • Submission Start Date

  • PBM (ID, Name, and Type) in the Submission

  • Unique Plans IDs and Plan names in the Submission

  • Unique PBM Formulary IDs in the Submission

Submission data will be transmitted to FPM only when the Rx line contains a valid value for the PBM Formulary ID and Plan ID components. When the PBM Formulary ID and Plan ID components contain a NULL value data transmission to FPM will not be processed.

Configuration for Data Transmission

The data transmission process is auto-initiated when the user validates a Submission. When the data transmission to FPM fails for the Submission, the Validata application takes care of the re-transmission process using a nightly job, CMnFPMRequestScheduler. The FPM application to which the data will be sent and the maximum number of retries the CMnFPMRequestScheduler job will attempt are configured in the tenant configuration file. Following are the two new properties added to the tenant configuration file:

  • fpmConfig.fpmURL

  • fpmConfig.fpmMaxRetry

For more information about the newly added configuration properties, see Validata Spring 2024 Installation Guide vd_install.pdf .

Data transmission to FPM Process and Result

In the Validata application, when the user validates a Submission (either using the validation automation or manual validation process), the data transmission process is auto-initiated. Users can verify the status of the data transmission to FPM in the IVD_SUBMISSION table in the SENT_TO_FPM. The SENT_TO_FPM column contains one of the following values:

  • 1: This value indicates the Submission data has been successfully transmitted to the FPM application.

  • 0: This value indicates that for the respective Submission, the data transmission to the FPM application has failed.

  • -1: This value indicates that the respective Submission has been newly created and the validation process is not initiated.

When the data is transmitted to the FPM, the users can view the respective details in the FPM application as below:

FPM Data.png

Handling Submissions with a failed status for data transmission to FPM

When Submission validation is initiated in the Validation PBM Formulary ID data transmission to the FPM application is auto-initiated. When the data transmission to FPM is failed for the Submission (i.e the value for the SENT_TO_FPM column is ‘0'), the Validata application takes care of the re-transmission process using a nightly job CMnFPMRequestScheduler. This job will be executed based on the time value configured in the application.properties file for the com.modeln.fpm.scheduler.cornExpression property. By default, the value for this property is set to Midnight 12.

This nightly job will be triggered to initiate PBM Formulary ID data transmission to the FPM application for Submissions that contain a '0' value for the SENT_TO_FPM column in the IVD_SUBMISSION table. A maximum of 3 retries of job execution will be done with an interval of 5 minutes to transmit the PBM formulary ID data to the FPM application for Submission.

The FPM application to which the data will be sent and the maximum retries will be attempted by the CMnFPMRequestScheduler job is configured in the tenant configuration file. For more information about the tenant file configuration, see Validata Spring 2024 Installation Guide.