Versions Compared

Key

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

Jira
serverIssue Tracker (JIRA)
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
keyODM-72

Element(s)
Element NameMethodDef
Parent ElementsMetaDataVersion
Element XPath(s)/ODM/Study/MetaDataVersion/MethodDef
Element Textual ValueNone
Usage

Conditional. There must be an MethodDef element for each unique MethodOID attribute value in the study.

The MethodOID attribute may be used on the ItemGroupDef or ItemDef elements.

AttributesOID, Name, Type, CommentOID
Child Elements

(Description, MethodSignature, FormalExpression*Alias*, DocumentRef*)

The Description element must be provided and should include a prose description. The MethodSignature element must also be provided and identifies the input parameter and return values for the MethodDef. The Description and MethodSignature are the normative content of the MethodDef.

If a FormalExpression is provided, it must contain a machine-readable expression that implements the Description and MethodSignature. Multiple FormalExpressions can be provided if each has a different Context attribute, allowing the same expression to be represented in forms appropriate to multiple systems. A FormalExpression can reference an external code library such that it can be retrieved for execution at run-time. If MethodDef execution order must be specified then use workflows for this purpose.

Usage/Business Rules
  • Business Rule(s):
    • There must be an MethodDef element for each unique MethodOID attribute value in the study.
    • The MethodOID attribute may be used on the ItemGroupRef or ItemRef elements.
    • MethodDefs associated with ItemRefs may only return a single value.
    • MethodDefs associated with ItemGroupRefs must return one value per ItemRef.