Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For the TIG Product Impact on Individual Health use case, applicants may collect free text data on a CRF to supplement a standard field. A common example is collection using a list of choices with a field to collect "Other, specify". In such cases, collected free text will be populated in the domain based on the scope or role of the variable used to represent data from the standard collection field.

  • Grouping Qualifier for variables which are used to group together a collection of observations within the same domain.
  • Result Qualifier for variables which describe the specific results associated with the topic variable in a Findings dataset.
  • Synonym Qualifier for variables which specify an alternative name for a particular variable in an observation.
  • Record Qualifier for variables which define additional attributes of the observation record as a whole, rather than describing a particular variable within a record
  • Variable qualifiers for variables which are used to further modify or describe a specific variable within an observation and are only meaningful in the context of the variable they qualify. 


Metadataspec
NumVariable PopulationImplementation
1

When Data from a Standard Field standard field is Represented represented in a Variable variable with Rolerole:

  • Grouping Qualifier,qualifier
  • Synonym Qualifier,qualifier
  • Record Qualifier; orqualifier
  • Variable Qualifierqualifier
When free text is collected to supplement a standard non-result qualifier field, the free text value will be represented in the SUPP-- dataset.
2

When Data from a Standard Field standard field is a Result Represented result represented in --ORRES.

When free text is collected to supplement a result, representation of the value will depend on the applicant's coding practice and analysis requirements.

  • To maintain controlled terminology pre-specified prespecified on the CRF, free text will be represented in --ORRES and controlled terminology will be represented in --STRESC.
    • Example:
    For example, if eye color is collected as a subject characteristic and "blueish gray" is collected for "Other, specify", then free text may be represented in SCORRES and controlled terminology may be represented in SCSTRESC. 
  • Blask
  • Blue
  • Green
  • Other specify:
    • SCTEST = Eye Color
    • SCORRES = BLUEISH GRAY
    • SCSTRESC = OTHER
    •   
    CRFRepresentation

    Eye Color:

    Brown

    ,

    Eye Color

    An investigator has selected "OTHER" and specified "BLUEISH GRAY". As in the preceding discussion for non-result qualifier values, the sponsor has several options for submission:

    If the sponsor wishes to maintain controlled terminology in the standard result field and limit the terminology to the 5 prespecified choices, then the free text is placed in --ORRES and the controlled terminology in --STRESC.

    Black, Blue, Green, Other, Specify:

    SCTEST

    SCORRES

    SCSTRESC

    Eye Color

    BLUEISH GRAY

    OTHER

    If the sponsor wishes to maintain controlled terminology in the standard result field, but will expand the
    • To expand terminology based on values

    seen in the
    • collected from "Other, specify"

    field
    • ,

    then the free text is placed
    • free text will be represented in --ORRES and the value of --STRESC will reflect the

    sponsor
    • applicant's coding decision.

    CRFRepresentation

    Eye Color:

    Brown, Black, Blue, Green, Other, Specify:

    SCTEST

    SCORRES

    SCSTRESC

    Eye Color

    BLUEISH GRAY

    GRAY

    • If the
    sponsor
    • applicant does not require that controlled terminology
    be
    • is maintained, then the verbatim value will also be
    copied to
    • represented in --STRESC..
    CRFRepresentation

    Eye Color:

    Brown, Black, Blue, Green, Other, Specify:

    SCTEST

    SCORRES

    SCSTRESC

    Eye Color

    BLUEISH GRAY

    BLUEISH GRAY

    3Data from a standard field is represented in a topic variable
    • For Interventions general-observation class domains, each collected value will be represented in --TRT in its own record. 
    • For Events general-observation class domains, each collected value will be represented in --TERM in its own record.
    • For Findings general-observation class domains, each collected value will be represented in --TESTCD and --TEST in its own record per controlled terminology. 
    4Data from a standard field is represented in variable --OBJ

    When findings are collected about an intervention or event, and the name of the event or intervention is collected in an "Other, specify" CRF field, the value in --OBJ variable depends on whether the Findings record has a parent record and whether the "Other, specify" value was coded.

    Image Added

    Pagenav