Logical Record Position
[Rate this topic]

When creating an edit check using Data Value, Logical Record Position (LRP) eliminates the need for custom functions by comparing data based on the logical order that is specified. Examples include finding a minimum or maximum value, or determining if a value is greater than a previously submitted value (based on date).

 

LRP is independent of the Record Position found on log forms. A check or derivation step that references a data point can be further qualified with a value for LRP.

 

The following table describes the LRP settings in Rave 2014.1.0:

 

Selection

Values

Required

Description

Logical Record Position

None

 

The system bypasses the Logical Record Position.

Min

 

Finds the minimum value for the field in the folder, form, subject

Max

 

Finds the maximum value for the field in the folder, form, subject

First

 

Sorts the data points by the specified order and then takes the data point that is in the first position. This is typically used in conjunction with a date that specifies the observation date of log/form (Record Date), observation date of form (Data Page Date), or observation date of Folder (Instance Date), and observation date of subject (Subject Date) property.

Previous

 

Sorts the data points by the specified order and then takes the data point that is in the previous position. This is typically used in conjunction with a date that specifies the observation date of log/form (Record Date), observation date of form (Data Page Date), or observation date of Folder (Instance Date), and observation date of subject (Subject Date) property.

Next

 

Sorts the data points by the specified order and then takes the data point that is in the next position. This is typically used in conjunction with a date that specifies the observation date of log/form (Record Date), observation date of form (Data Page Date), or observation date of Folder (Instance Date), and observation date of subject (Subject Date) property.

Last

 

Sorts the data points by the specified order and then takes the data point that is in the last position. This is typically used in conjunction with a date that specifies the observation date of log/form (Record Date), observation date of form (Data Page Date), or observation date of Folder (Instance Date), and observation date of subject (Subject Date) property.

Scope

Form

Required only if LRP is Max, Min, First, Next, Previous, Last

Specifies whether LRP should consider only the data points within the form.  

Folder

Required only if LRP is Max, Min, First, Next, Previous, Last

Specifies whether LRP should consider only the forms within the folders.

Subject

Required only if LRP is Max, Min, First, Next, Previous, Last

Specifies whether LRP should consider only the folders for the subject.

Order By

Record Date

Required only if LRP is First, Next, Previous, Last

Specifies whether LRP should be sorted by Record Date.

CRF Location

Required only if LRP is First, Next, Previous, Last

Specifies whether LRP should be sorted by CRF Location.

 

Example:

 

A form Vitals contains the field Visit Date. An edit check is configured to trigger when all Visit Date fields on forms within a folder are not in ascending order. To set up edit check:

 

 

If the Visit Date field in Vitals with LRP Previous/Folder/CRF Location Is Greater Than Or Equal to the Visit Date field in Vitals with LRP None, then the system opens a query to site on the Visit Date in Vitals and displays "Within a folder, all Visit Date fields must be in ascending order."

 

For example:

 

Record Position 1 shows CRF Visit 1, Visit Date 2014/01/2014

Record Position 2 shows CRF Visit 2, Visit Date 2014/02/2014

Record Position 3 shows CRF Visit 3, Visit Date 2014/01/2014

 

An edit check query will trigger on Record Position 3.

 

 

 

 

Copyright © 2014 Medidata Solutions, Inc. All rights reserved.

 



How do you rate this topic?