NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

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

...

A Data Entry Form builder is notified of a new study or need for a new clinical data capture form by an end user. The Data Manager/Clinical actor begins with the requirements from the end use, usually an existing form and opens a form editor. The actor can create a new Form. The actor can search for an existing model in the metadata registry and drag it into the pallettepalette. The pallet palette self organizes based on the classes and attributes in the model and the existing relations of items in the model. The actor can delete items in the modules, drag attributes into new modules on their form to organize the form according to their anticipated data entry workflow.

If there is not an existing model that the actor can use, the actor browses existing Forms in the local or remote forms registries that could be reused based on search parameters of the form such as the type of study, the type of form (including but not limited to interview, survey, and clinical trail enrollment) or other criteria. If the Data Manager/Clinical Actor is unable to locate an existing form, the actor may search for From Form Modules in the local or remote Forms registry to construct a new form.

...

If there is not an existing module that the actor can use, the actor can search for possible questions in the metadata repository that meet the questions on their existing form. Search is enhanced by semantic infrastructure to quickly allow users to search for questions by entering text of the question, keywords or values in their value set. The system presents the user with choices the user can put into the forms pallete palette or temporary area once the user has found all the questions needed to create the form.

...

A Data Entry Form builder is notified of a new study or need for a new clinical data capture form by an end user. The Data Manager/Clinical actor begins with the requirements from the end user, usually an existing form, and opens a form editor. The Data Manager/Clinical actor selects to create a new Module. The actor can search for an existing model, form, module or question in the metadata registry and drag it into the pallettepalette.

The actor can chose to have the pallet palette self organize, or to apply manual organization based on the existing form and workflow. If the actor choes chose self organize, the questions in the module are organized based on information in the metadata registry related to the questions in the model. If the attribute is found in several models, the actor can chose the model to apply the relations after inspecting the matching models.

...

The Data Manager/Clinical Form Builder actor searches the existing repository for a form by name, identifier or keywords. The actor pulls the existing form into the form palletpalette. The pallet palette self organizes based on the existing form structure to match to the new form structure (for example, Form to a Form Project, Module to a Common Message Element Type (CMET)(question) ).

...

The actor next defines the rules for skip patterns and form flow logic that is stored with the form. The form is then identified and its associated metadatais metadata is passed to the metadata registry.

...