When data is collected by different sites and organizations, it can be difficult to keep visit naming standards consistent. The datasets generated might use many different ways of referring to the same visit. For example, the following list of values might all refer to the same visit:
  • "Month 1"
  • "M 1"
  • "M1"
  • "Day 30"
Instead of editing your datasets to force them to be consistent, you can define visit name aliases that are mapped to sequences numbers/VisitIDs in your study.

When you import a dataset containing the alias values, each alias is resolved to the appropriate sequence number via this mapping.

Multiple alias names can be mapped to a single sequence number, for example "Month 1", "M1", and "Day 30" can all be mapped to the sequence number "30".

Note: Alias/Sequence Number mapping is only available in visit-based studies, not date-based studies.

Create Alias/Sequence Number Mapping

  • Prepare your mappings as a tab separated list with two columns: Name and SequenceNum, like the example below:
NameSequenceNum
Screening0
Week 1 Checkup7
Week 2 Checkup14
Week 3 Checkup21
  • Click Admin -> Manage Study -> Manage Visits -> Visit Import Mapping -> Import Custom Mapping.
  • Copy and paste the tab separated list into the text area.
  • Click Submit.

Importing Data Using Alias Visit Names

Once the mapping is in place, you can import data using the string reference to the visit, instead of the integer value (the SequenceNum). Place the string values/alias in a column named "Visit". On import, the server will convert the string values in the Visit column to integers for internal storage. For example, the following table import physical exam data using string values in the Visit column:

ParticipantIDVisitTemperatureWeight
PT-101Screening3780 
PT-101Week 1 Checkup3781 
PT-101Week 2 Checkup3881 
PT-101Week 3 Checkup3880 

discussion

Discussion

Search 

Pages 

previousnext
 
expand all collapse all