Pull Services

Pull Services manage the extraction and posting of batched beneficiary data, ensuring efficient and accurate data handling. The process starts with the InfoPump and involves several critical steps to ensure that data is accurately matched and processed.

Overview of Pull Services

Pull Services are centered around data retrieval from InfoNexus, initiated by the InfoPump. This process involves:

  • Customer-Based Module (CBM): The data source from which beneficiary information is extracted.
  • InfoPump: Extracts data from the CBM in batches and sends it to InfoNexus for processing. Key features include batching, logging, and managing restarts if the data connection is lost.
  • InfoNexus: Processes incoming batches, matches them against the DMF, and writes matches back to your local InfoPump database.

InfoPump

InfoPump is responsible for initiating the Pull process by extracting data from the CBM and sending it to InfoNexus. Key features include:

  • Database Compatibility: Supports Oracle, SQL Server, and MySQL (Open Source).
  • Hands-Free Operation: Runs as a Windows Service with minimal user intervention.
  • Log and History: Maintains logs of batches sent and match history.
  • Batch Processing: Utilizes BatchBySSN and BatchByDOB tables for efficient extraction.
  • Restart Capability: Can resume from where it left off if the connection is lost.
  • Duplicate Record Handling: Prevents sending records that have already been matched.
  • Batch Frequency and Notifications: Configurable for frequency and email notifications about service status.
  • High-Speed Bulk Loading: Uses MySQL's bulk loading utility for rapid data processing.

InfoNexus

InfoNexus processes batches received from InfoPump. Key features include:

  • Batch Queue Management: Manages and queues incoming batches for processing.
  • Dynamic BPA Allocation: Adjusts the number of Batch Processing Agents (BPAs) based on queue load.
  • Batch Size and Load Balancing: Distributes batches according to size and balances load for efficient processing.
  • Match Records Against the DMF: Matches records by SSN or Name and Date of Birth (DOB).
  • Name and DOB Matches: For records without SSNs, matches using Date of Birth, Last Name, First Name, and Middle Name; if needed, re-attempts match without Middle Name.
  • Database Updates: Updates the Match History table and batch logs in the InfoPump database.

Configuring InfoPump for Optimal Matching

For the best results in matching beneficiary data with the Decedent Master File (DMF), consider the following:

Preferred Matching Methods

a. Query by SSN

Description: SSN provides the most precise matching method, allowing for a one-to-one match.

Advantages:

  • High Accuracy: Directly retrieves specific records with minimal ambiguity.
  • Efficient: Reduces data processing and investigative effort.

Recommendation: Use SSN whenever available to ensure the highest match quality.

b. Alternative Query Methods

Description: When SSN is not available, queries are based on Date of Birth, Name Fields, and Suffixes.

Required Data:

  • Date of Birth: Essential for all non-SSN queries.
  • Name Fields: Last Name, First Name, Middle Name, and Suffix enhance match accuracy.

Implications:

  • Quality of Match: The more comprehensive the name data, the better the match attempt.
  • Consider the Number of Unique Data Points in the DMF:
    • Date of Birth: 66,000 unique entries
    • Last Name: 2.1 million unique entries
    • First Name: 870,000 unique entries
    • Middle Name: 250,000 unique entries
  • Considerations: Queries with only name and date of birth can result in multiple records, necessitating further investigation.

Impact on Matching Quality and Effort

High-Quality Matches:

Achieved With: SSN or a complete set of name fields and Date of Birth.

Result: Fewer records retrieved, leading to lower effort for investigation.

Lower-Quality Matches:

Achieved With: Incomplete data, such as missing SSN or partial name fields.

Result: More records retrieved, requiring additional effort to verify.

Recommendations for Optimal Setup

  • Collect Comprehensive Data: Gather as much data as possible from the CBM, especially SSNs.
  • Use SSN When Available: Prioritize SSN for precise and efficient matching.
  • Include Accurate Date of Birth: Essential for all non-SSN queries.
  • Enhance Name Data: Collect full name details to improve match quality.

Additional Information

For detailed information about the data elements returned by the match, please refer to the FAQs section. For more details on InfoPump, refer to our Onboarding Process. If you have specific questions, visit our Contact Page.