Previous Topic

Next Topic

Book Contents

Book Index

Study Completion form

Design considerations for Study Completion form

Design consideration

Description

Form title (value of Special Forms property)

Study Completion.

Purpose in the InForm application

Records the completion of a study by a subject or the reason the subject dropped out of the study.

Required form?

No.

Default version generated?

No.

Required items?

If a form is marked as the Study Completion form, the Completion Status or Drop-out Reason special field must also be present:

  • Item—Study completion status.
  • Item type—Integer or Text.
  • Special Fields property—Completion status (Study Completion).

 

  • Item—Drop-out reason.
  • Item type—Integer or Text.
  • Special Fields property—Drop out reason (Study Completion).

Other requirements

  • The Study Completion form cannot be repeating.
  • The Study Completion form must have the Special Forms custom property value of Study Completion and must be the only form in the study with this custom property value.
  • The item with the Completion status (Study Completion) Special Fields custom property must have a codelist that has two codelist items:
    • Yes codelist item—The value of the Study Completion Status Items custom property for this codelist item must be Complete Study (Study Completion).
    • No codelist item—The value of the Study Completion Status Items custom property for this codelist item must be Incomplete Study (Study Completion).
  • The item with the Drop out reason (Study Completion) Special Fields custom property must have a codelist that has at least one codelist item. The code on all codelist items must not have more than 47 characters. During deployment, the codelist item values are converted to InForm resources that are available in the InForm application for Reporting and Analysis. The item must be able to accept only one value.

Designing for a CDD

If you are implementing a Custom-Defined Database (CDD), note that you can map the item with the Drop out reason (Study Completion) property to only one column. For mapping each drop-out reason to a separate CDD column, Oracle suggests the following design:

  • Compound item: Did the subject complete the study?

Create a compound item in which the No response to the study completion status question has multiple-selection child items for each drop-out reason. The compound item and its child items do not have a value for the Special Fields custom property.

  • Hidden Yes No item: Did the subject complete the study?

Create a hidden item with a codelist that has Yes and No codelist items.

Custom properties:

  • Item—Special Fields property value is Completion status (Study Completion).
  • Yes codelist item—Study Completion Status Items value is Complete Study (Study Completion).
  • No codelist item—Study Completion Status Items value is Incomplete Study (Study Completion).
  • Hidden item: Reason for noncompletion

Create a hidden item with a codelist in which each codelist item corresponds to a child item in No response of the visible compound item.

Custom property:

  • Item—Special Fields property value is Drop out reason (Study Completion).
  • Calculation rules

Create calculation rules that map:

  • The Yes response in the compound item to the Yes codelist item in the hidden Yes No item.
  • The No response in the compound item to the No codelist item in the hidden Yes No item.
  • The selected child item in the No response of the compound item to the corresponding codelist item in the hidden Reason for noncompletion item.

    Note: Because the compound item allows multiple selections, and the hidden item requires a single selection, the rule must contain logic that prioritizes the noncompletion reason to select in the hidden item if multiple reasons are selected in the compound item.

  • Mapping

In a CDD mapping, map each child item in the compound item to a different data series. Each data series maps to a separate CDD column.

Illustration of Study Completion form design for CDD

Copyright © 2013 Oracle and/or its affiliates. All rights reserved.