Attachment 34 - DMS Migration Phases -AMEND 3.pdf
PDF 122 KB Posted
- Attached to
- Surveillance, Epidemiology, and End Results (SEER) Program Federal contract opportunity
- Solicitation number
- 75N91019R00029
About this file
This document outlines the three phases of a Surveillance, Epidemiology, and End Results (SEER) Program data migration from a registry's current central data management system to SEERDMS. Phase 1 involves completing prerequisites for data migration such as identifying a registry transition team, executing legal agreements, and providing database documentation to the contractor. Phase 2 consists of data migration and system configuration through requirements analysis, migration data transfers, and testing. Phase 3 focuses on registry training and testing the data migration through recurring webcasts and a beta-testing plan. The National Cancer Institute intends to solicit for additional cancer registries to join the SEER Program for surveillance research purposes. The contractor will be responsible for migrating registry data to the SEERDMS central data management system in accordance with the three-phased timeline and deliverables described in the document.
View the file
Other files for this federal contract opportunity
Show all 50
Surveillance, Epidemiology, and End Results (SEER) Program has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Attachment 34 – DMS Migration Phases
The SEER*DMS migration consists of three dependent phases – each phase must be completed before the next phase can be started.
Phase Description Estimated Completion Time 1 Complete steps required prior to the transfer of data for migration.
3 months
2 Data migration and system configuration. 12 months 3 Registry training and testing. 3 months
Phase 1 – Prerequisites for Data Migration
The following deliverables will be completed at the end of phase 1:
• Identify the registry transition team. This would be relatively small group with representatives from registry management, IT, and operations.
• Execute legal agreements:
o A legal agreement must be executed between the registry and IMS.
o The registry must provide a data use agreement for individuals. This will be signed by all
IMS staff with access to the data (development, systems, and support teams).
• Provide database documentation to IMS.
o Identify the type of database currently used (PostgreSQL, Microsoft SQL, etc) o Provide a list of all database tables that will be migrated from the current central data management system to SEER*DMS.
o Provide a list of tables that the registry does not expect to migrate; include a brief description that explains why the table does not need to be migrated.
o For all tables that will be migrated, provide detailed field documentation. Provide a spreadsheet for each table that contains each of these fields:
Registry DB Table Name Registry DB Field Name NAACCR Item Number NAACCR Name If it is a NAACCR data item but the registry stores values that differ from the
NAACCR standard then include a description of those differences.
If it is not a NAACCR data item then describe the field and the way it is used.
A column indicating whether the field is collected, derived, or both.
• Work with IMS to define and establish a VPN connection between the registry and IMS. This will be used to transfer data for migration and to provide registry staff with access to the registry’s instance of SEER*DMS.
• Define the file format for registry migration files and confirm these file formats with IMS.
Comma separate values (CSV) format is the most commonly used format for migrations. There would be one file per registry database table.
• Successfully transfer migration files to IMS.
• Establish a repeatable process for creating and transferring migration files.
Phase 2 – Data Migration and System Configuration
• Participate in scheduled calls with IMS for the purpose of requirements analysis.
• Provide timely response to all requests from IMS.
• Periodically, provide new versions of the migration data to IMS upon request. This must be completed using the repeatable process defined in Phase 1.
Phase 3 – Registry Training and Testing
• Work with IMS to define a beta-testing plan for testing the data migration and system.
• Participate in recurring webcasts with IMS staff (one hour sessions conducted 2 to 3 times per week). The purpose of the webcasts will be to train registry staff and to review issues identified by registry staff.
File details come from the government source that posted it. Updated .