Research Subject Mapper is a tool designed to serve the needs of multi-center studies to prevent exposure of medical record identifiers to the data coordination center while allowing the data coordination center to specify data collection periods for the research subjects. The intended usage of this tool is to combine authoritative data from a research subject data store with identifiable data at a data collection site to generate inputs for queries of an Electronic Health Record (EHR).

To successfully run the Research Subject Mapper tool on the target machine please install the software below before going any further.

Run sudo apt-get install python2.7 on target machine

sudo apt-get install python-setuptools (to install setuptools package)

sudo apt-get install python-dev (to install python-dev packages)

sudo apt-get install libxml2 (to install libxml2 package)

sudo apt-get install libxslt1-dev (to install libxslt1-dev package)

Research Subject Mapper Executable can be downloaded from the http://ctsit.github.io/research-subject-mapper

To install research subject mapper run sudo easy_install rsm_X.X.X.egg where X's represent version number

Check for config-example-gsm and config-example-gsm-input directories in the rsm installation directory on the target machine and prepare custom config directories with your implementations on the target machine.

The files that need to be modified with your implementation details in config directory are site-catalog.xml and source_data_schema.xml.

This xml file follows below structure

<sites_list>
	<site type="data_source">
        <site_URI>sftp.source_site.edu</site_URI>
        <site_uname>source_user</site_uname>
        <site_password>source_password</site_password>
        <site_remotepath>ftp/smi.xml</site_remotepath>
        <site_contact_email>contact@source_site.edu</site_contact_email>
    </site>
    <site type="data_destination">
        <site_URI>sftp.destination_site.edu:50022</site_URI>
        <site_uname>destination_user</site_uname>
        <site_password>destination_password</site_password>
        <site_remotepath>/output.csv</site_remotepath>
        <site_contact_email>contact@destination_site.edu</site_contact_email>
    </site>
</sites_list>

This xml file follows below structure

<source>
	<redcap_uri>Your_RedCap_Instance_URI</redcap_uri>
	<apitoken>API_TOKEN</apitoken>
	<fields>
		<field>Field_Name</field>
		<field>Field_Name</field>
		<field>Field_Name</field>
	</fields>
</source>

1. Edit the source_data_schema.xml file to specify the Person Index fields before running gsm. You will need to specify the study subject number, a field to verify the study subject (typically year of birth), and the subject's corresponding Medical Record Number (MRN).

2. If this tool is being run on the central site you need to run the gsmi tool as shown below and put the generated files in the ftp of the site. Client sites typically only need to run the generate_subject_mapper tool.

Run gsmi -c <FULL_PATH_TO_CONFIG_DIRECTORY> --keep (if a directory named config is already setup in the parent directory of generate_subject_map_input.py, one need not provide the path to config directory in -c option)

If this tool is being run at the site, one can just provide site ftp details in the site-catalog.xml use the gsm tool.

Run gsm -c <FULL_PATH_TO_CONFIG_DIRECTORY> --keep (if a directory named config is already setup in the parent directory of generate_subject_map_input.py, one need not provide the path to config directory in -c option)

Following parameters are required to have a value in settings.ini:

• site_catalog
• source_data_schema_file
• sender_email

The program terminates if they are missing or do not have a value in settings.ini. A message about this is displayed to the user before the program terminates. The same is also written to the log file.

To specify a log file, use the --logfile command-line switch.

Following parameters are required to have a value in settings.ini:

• site_catalog
• source_data_schema_file
• sender_email
• xml_formatting_transform_xsl

The program terminates if they are missing or do not have a value in settings.ini. A message about this is displayed to the user before the program terminates. The same is also written to the log file.

To specify a log file, use the --logfile command-line switch.