Notice: This application will enforce Multi-factor authentication (MFA) for NIH users beginning the evening of Wed Aug 3rd.
NIH | National Cancer Institute | NCI Wiki  

Contents of this Page

The Forms Metadata group was formed as a result of a recognized need by ISO JTC1 SC 32 WG2 at the Plenary meeting in Sydney Australia in May 2008. A period of one year was use to analyze three areas of focus, Forms Metadata is focused on the standards required for describing data collection instruments as metadata, and should start by reviewing and editing the working description of Forms Metadata found below, to guide the scope/focus of the work effort. Members who have requested a wiki account may edit the description posted below for clarity or add descriptive information to enhance understanding.

At the ISO JTC1 SC 32 WG2 meeting in JeJu, Korea in June 2009, the study period for Forms Metadata was extended for one year. The other two areas, Services and Ontology were ended and folded into ISO 19763 Part 5 and 3 respectively as pre-existing areas that will address the requirement for metamodels in these areas.

A form is a document (printed or electronic) with instructions and spaces in which to write or enter data. It can be used on a web page to collect data and save it to a desktop file, print or fax it, or to submit data to a server. Forms allow the user to enter information directly into fill-in-the-blank text fields or free-form text areas, select choices using checkboxes, radio buttons, drop-down menus if electronic, or enter information through fill-in-the blank tables or spreadsheet like formats. Some forms are completed by an interviewer, either in person or via a telephone survey, or filled by the user in person or via a mail in response. Forms can have characteristics such as an intended demographic audience, target reading level, languages and version number.

For the purpose of the study period, Forms Metadata is defined as the set of discrete classes and attributes, and relationships between them, that are necessary and sufficient to unambiguously describe and enable registration and discovery of constructs for collecting data, sufficient such that someone other than the original author can use the form in a software application for data collection.

This implies that the original structure of the form and its contents are described thoroughly and usable by both humans and computers. Typically these constructs are referred to as 'forms', 'surveys', or 'questionnaires'. The information about the form must include the ability to cite references on which the form design is based, information about instructions and the spaces in which to write or enter data, the intent and purpose of the form, the identification and naming of the form and other administrative information to manage a registration of the form throughout its lifecycle.

There are various types of forms:

  • Statistical forms
  • Surveys, Questionnaires
  • Clinical trials data collection forms (Case Report Forms - CRFs)
  • Population Science Measures, for example, quality of life

Form Metadata includes:

  • A structured set of metadata identifying the collection of information to be collected (Sections, Modules, Questions) by the form and attributes about the form itself.
  • Link to Rules for Form Completion
  • Rights - can the form be reused? By whom? What is the process for authorization, etc.
  • Standard way to describe minimal Rendering information to describe how the form looks
  • 'Behavior' - skip pattern
  • Form Structure - number and order of sections on the form
  • Standard way to associate the semantics of the Question and Answer Set (for example, to associate an item on the form with a 11179 Data Element, DEC or Value Domain)

Use Cases and Requirements

[study group members - please describe use cases or examples here, and attach related documents or presentations, or provide links to urls where such information can be found]

  • Exit Disclaimer logo CDISC ODM (Operational Data Model) - presented in Portugal, Nov. 18, 2008
  • OASIS Exit Disclaimer logo - not sure which standard might pertain here - someone needs to research this
  • UN/CEFACT Exit Disclaimer logo - Forms Metamodel - needs to be researched more - could not find a Forms Metamodel
  • UN eDocs Exit Disclaimer logo - Cross Border Trade 'form templates' - may have an implicit formmetamodel
  • ISO 15000-5 ebXML Exit Disclaimer logo
  • ISO 7372 Exit Disclaimer logo - Free Trade Data Elements -not sure it this applies, needs to be researched
  • Adobe Exit Disclaimer logo pdf formmetamodel - this is a proprietary commercial software systems.  What we are striving for is an Open Standard.  If someone can get hold of the metamodel, it might be infromative.
  • MS InfoPath Exit Disclaimer logo - has a metamodelfor their forms - Similar to Adobe, but may be more open
  • XForms 1.0 Exit Disclaimer logo - language for representing forms
  • GForge Archive Forms Metadata Docs



  • No labels