...
Element | Type | Description |
---|---|---|
| string | The name of the form. This is required and should be unique within the system. |
| string | The unique form identifier |
| string | The encounter type |
| single-line / multi-line / automatic | The inline rendering mode |
| Array<Section> | A collection of pages that make the form. Each page contains sections and questions. |
| Array<Intent> | A list of intents supported by this form. Intents define specific actions associated with the form. |
Additional form properties
| array of objects | These are the conditions that validate the input data. |
| string/ number/boolean,/object | Default values for fields in the form. |
| boolean | Fields that must be filled out or selected. |
| string | Expression or data related to historical information. |
| object | The option to hide certain parts of the form or fields. |
| string | Expressions that calculate values based on inputs. |
| string | These are additional information or context about a question. |
| array of objects | Responses or answers provided in the form. |
| string | Type of order or sequence for form elements. |
| array of objects | Orders that can be selected or applied. |
| array of objects | This is the mapping of concepts to specific form elements. |
| string | Identifier for a specific concept within the form. |
Pages
A page is a collection of related sections. A typical page definition consists of a label
, inlineRendering
(optional) and a list of section
s. The engine uses the page
’s label to identify it from other pages; that being said, it’s mandatory to keep the page’s label unique. Below is an example of a form with one page
and section
. The section
has 4 questions labelled:
...