Exhibit_3_-_Interface_Specification_-_PIDS-UPdate.pdf

Interface Specification

DMDC PIDS-UPdate Generic Interface Specification

1.0 INTRODUCTION

1.1 Overview

In exceptional cases where a DEERS individual has been inadvertently issued multiple ID cards under multiple DOD_EDI_PN_ID, DMDC has the requirement to reconcile these situations by merging the multiple EDI records through comprehensive Research and Analysis. The process of reconciling these multiple records is known at DMDC as a smoosh case.

In the events leading to a smoosh case, where a population member encounters problems with his/her personal data, the member should first contact the nearest Personnel Center or Rapids Site Operator to resolve the situation. If the situation is determined to be a smoosh case, the process of reconciliation will begin.

Organizations needing periodic EDI smoosh updates can make PIDS-UPdate requests to DEERS on a weekly/daily basis to update any DoD EDI Person Identifiers that have changed within a time period. The Inquiry for EDI updates will be sent as a synchronous real-time transaction. The DOD_EDI crosswalks returned in the PIDS-UPdate response from DEERS will be recorded by the receiving organization for future inquiries. If a specific EDI smoosh case is not found within the returned PIDS-UPdate crosswalk, the receiving organization may contact DMDC with the data quality discrepancy.

1.2 About the DOD_EDI_PN_ID:

EDIs are not recycled at DMDC. If a Web Services customer continues making requests using an old EDI for a reconciled record, the customer will still receive the most current record, along with the additional field DOD_EDI_PN_XR_ID.

The DoD_EDI_PN_XR_ID is the newest person identifier in a situation where there were two previous EDIs for one person and the reconciled new EDI, the DoD_EDI_PN_XR_ID, replaces any old numbers.

Interface Specification

1.2.1 Business Context for PIDS-UPdate

DMDC Customers may make the following PIDS-UPdate request to DEERS on a recurring basis (suggest nightly or weekly) to get a list of all amended DOD_EDI_PN_IDs since the last periodic inquiry.

1.3 Interface Requirements

1.3.1 PIDS-UPdate Inquiry Identifiers

PIDS-UPdate Inquiry

System Name Description Note Type

LST_CHNG_RQST_

DT

Start Date/Time to Present inquiry period.

Required Data/Time

Table 1-1: PIDS-UPdate Request Data Field

1.3.2 PIDS-UPdate Response Data

Synchronous PIDS Update Inquiries will receive the following information with the last change request date (LST_CHNG_RQST_DT) being submitted.

Type DEERS Element Description Notes Data Type

PIDSUpdateRecord (0:N) DOD_EDI_PN_ID Key for matching DoD records

NUMBER(10)

DOD_EDI_PN_XR_ID

The identifier that is used to represent cross-reference between a person’s Department of Defense Electronic Data Interchange identifiers. If the code is invalidated, this is the new DoD EDI PN ID to use instead of the current one

NUMBER(10)

DEPI_CHNG_EFF_DT

The date the DoD DoD EDI Person Identifier change became effective

VARCHAR2(8)

Table 1-2: PIDS Update Acknowledgement Record Layout