36C77619R0003-021.docx

ATTACHMENT 20

DoD Correlation guidelines based on results of HC IdM’s iEHR IOC UAT When VA adds a new patient, VA will send everything in the PV to DoD (including POB information, PV Address/phone, PV Date of Death). Those last 3 items are not normally synched out when PV is updated but will be shared with DoD whenever a PV has those fields upon adds and updates.

DoD does not store Alias information in this release.

DoD does not accept or store PS SSN Reason.

POB country was added in Inc 9 per DoD request. MVI will populate POB Country when provided by DOD and if any update is received where no POB Country is provided, but a valid POB State is sent and found in the SDS Tables. The value is then sent to DOD.

DoD affiliation is any association or affiliation to the DoD for identity, employment, pay or benefits.

· Basically if the patient is getting a monthly check then he/she is DoD affiliated.

· If the patient is active duty military then he/she is DoD affiliated.

· If the patient is the family member of an active duty military then he/she is DoD affiliated.

· If the patient is retired military then the patient is DoD affiliated because they are getting a monthly check from DoD.

· If the patient does not meet the conditions above then they should not be DoD affiliated, meaning DoD will accept identity updates from MVI.

· If the patient is DoD affiliated then DoD would not accept identity updates from MVI.

Note: The MVI currently has no flag identifying a record as VA or DoD affiliated.

DoD will accept updates (promote the update to the DoD correlation we see on MVI) when the records is VA affiliated with these exceptions:

· When the DoD correlation has a Verified SSN and VA sends an update that does not include a Verified SSN.

· DoD does not accept MBI value of No at this time. If the MBI is No, the MBI field will be null on the DoD correlation. MBI values of Yes will be accepted by DoD. Note: The DoD has an MBO, Multiple Birth Order, field for when the MBI is Yes. Since VA does not have this concept or field yet, expect to see a MBO of 0 when the record is VA affiliated.

· DoD does not accept deletions on Name components meaning, if VA deletes a name component, the 200 DoD correlation will not be updated to reflect the change made in VA PV.

Imprecise DOB values:

· If a DOB of MM/YYYY is sent to DoD, the DoD correlation will reflect MM/01/YYYY.

· DoD will not update the existing DoD data from a precise DOB to an imprecise DOB.

POB values:

If a POB City (no POB State) is sent to DoD, the DoD correlation will not accept the POB City value (for adds or updates).

When the record is DoD affiliated and VA receives an update from DoD, the DoD correlation will be updated to reflect the requested edit. The PV will not be updated unless the DoD correlation is the ONLY correlation on that ICN, in that case the PV would be updated. Note: I do not believe there are any scenarios where a DoD correlation would be the only correlation on an ICN at this time.

DoD remote data in TK:

Fields not available from the DoD service we use for remote data (DoD refers to this service as DRGS):

· SSN Verification status

· Alias

· MBI

· POB City, State, Country

· MMN

Even if those fields are included in the 200 DoD correlation.

Minor defects found in April 2013 iEHR IOC Adds/Updates:

· Home address and Home Phone labels in the TK. Inconsistent field labels across the TK screens. Colleen to enter a CR to have consistent TK labels.

· If there is a TIN on a record, the TIN value will NOT be displayed in the MPI legacy DoD correlation in the Increment 9 release. It should be fixed in the future. The TIN will be displayed in PV (for both MPI and TK) and the TIN will be displayed on the 200 DoD correlation in TK.