a. How the Before the deployment of HAIMS on January 1, 2014, when a service RMC Stores department transferred a former service member’s STRs to the RMC, it sent STRs the STRs in either a single or multiple STR jackets. Each jacket bore the former service member’s name and SSN. The RMC leaves the STRs in the jackets in which they arrived and files them in sequential order by SSN. If a former service member has STR jackets, and the RMC receives multiple a request for transfer of his/her STRs to an RO, the RMC is responsible for sending of the former service member’s STR jackets to the RO. all If an RO requests STRs for a Veteran who has an eFolder in Exception: VBMS, the RMC does send the STRs to the RO. Instead, it sends the not STRs to a vendor for scanning and to upload into the Veteran’s eFolder. For more information about HAIMS, see M21-1, Part III, Subpart Reference: iii, 2.A.5.c. b. SMRTS Prior to the deployment of HAIMS, the RMC received STRs from service departments and recorded their receipt in the Service Medical Records Tracking System (SMRTS). The RMC continues to Note: receive STRs from the Coast Guard, Public Health Service (PHS), and National Oceanic and Atmospheric Administration (NOAA), and record the receipt of STRs from these Federal entities in SMRTS. SMRTS interfaces with Share and continues to provide the RMC with a uniform method for managing and tracking the movement of STRs into and out of the RMC. c. Interaction The table below contains a description of the interaction between SMRTS, Between Share, and the Control of Veterans Records System (COVERS). SMRTS, Share, and COVERS When And if the former service Then … … member had/has … the RMC a VA claims folder that the RMC transferred/transfers the received a former service was/is in an RO’s STRs to the RO. This action member’s STRs from possession triggered/triggers an update to the his/her service department fields on the BIRLS FOLDER (prior to the deployment LOCATION tab in Share to show of HAIMS), or the STRs were/are in transit.
a. How the RMC Stores STRs Before the deployment of HAIMS on January 1, 2014, when a service department transferred a former service member’s STRs to the RMC, it sent the STRs in either a single or multiple STR jackets. Each jacket bore the former service member’s name and SSN. The RMC leaves the STRs in the jackets in which they arrived and files them in sequential order by SSN. If a former service member has multiple STR jackets, and the RMC receives a request for transfer of his/her STRs to an RO, the RMC is responsible for sending all of the former service member’s STR jackets to the RO. Exception: If an RO requests STRs for a Veteran who has an eFolder in VBMS, the RMC does not send the STRs to the RO. Instead, it sends the STRs to a vendor for scanning and to upload into the Veteran’s eFolder. Reference: For more information about HAIMS, see M21-1, Part III, Subpart iii, 2.A.5.c. b. SMRTS Prior to the deployment of HAIMS, the RMC received STRs from service departments and recorded their receipt in the Service Medical Records Tracking System (SMRTS). Note: The RMC continues to receive STRs from the Coast Guard, Public Health Service (PHS), and National Oceanic and Atmospheric Administration (NOAA), and record the receipt of STRs from these Federal entities in SMRTS. SMRTS interfaces with Share and continues to provide the RMC with a uniform method for managing and tracking the movement of STRs into and out of the RMC. c. Interaction Between SMRTS, Share, and COVERS The table below contains a description of the interaction between SMRTS, Share, and the Control of Veterans Records System (COVERS). When … And if the former service member had/has … Then … the RMC received a former service member’s STRs from his/her service department (prior to the deployment of HAIMS), or a VA claims folder that was/is in an RO’s possession the RMC transferred/transfers the STRs to the RO. This action triggered/triggers an update to the fields on the BIRLS FOLDER LOCATION tab in Share to show the STRs were/are in transit.
1-22-16_Key%20Changes_M21-1III_iii_2_SecA.docx