| 33 | |
| 34 | Mappings are used to specify which field from the source gets used for which field in the output. These are specified in a YAML file. By default this file is called mapping.yaml in the application root directory, but the mapping file path can be defined using the {{{-m=xxx}}} or {{{--mappingFilePath=xxx}}} command line arguments. |
| 35 | |
| 36 | Mappings are defined for Patients, Events and Observations. |
| 37 | |
| 38 | === Observation Mappings |
| 39 | |
| 40 | The types available for observation mappings are: |
| 41 | |
| 42 | * !BooleanTrueField |
| 43 | * !DataSourceConditionalExistenceField |
| 44 | * !DataSourceConditionalExistenceIfNotNullField |
| 45 | * !DataSourceConditionalExistenceIfTrueField |
| 46 | * !DataSourceConditionalExistenceIfValueOneOfField |
| 47 | * !DataSourceEnumerationField |
| 48 | * !DataSourceNumericField |
| 49 | * !DataSourceTextField |
| 50 | * !LiteralTextField |
| 51 | |
| 52 | Observation dates are defined as a list of dates that can be used if they are defined. If the first field in the list is not defined, then next one on the list will be tried and so on. |
| 53 | |
| 54 | The types of date field available are: |
| 55 | |
| 56 | * !DataSourceDateField |
| 57 | * !YearOnlyDateField |
| 58 | |