Table of Contents | ||
---|---|---|
|
...
Type | Example | |
---|---|---|
1 | Coded - Autocomplete with only coded values Usage: Use it when you have fixed set of answers for a concept | "Death Note, Primary Cause of Death": { Where, "Death Note, Primary Cause of Death" = Concept which has answers |
2 | Coded - Autocomplete with coded values and non-coded values | You need to define following hierarchy of concepts (taking example of Chief Complaints here).
All the coded answers should be added to Chief Complaint Answers and not Chief Complaint. This is a hack for now because of inability to ignore loading of children when loading a concept. When we load children it slows down the loading of the form "Chief Complaint Data": { If either of codedConceptName or nonCodedConceptName is not given, It will be treated as autocomplete with only coded values. "multiSelect": true instead of "autocomplete": true true |
3 | Text - Free text type | "Chief Complaint Notes: { |
4 | Boolean - For Yes/No type | "Posture" : { |
5 | Numeric - For numerical values Usage: Recommended to be configured only when the numbers would be small like number of children, pregnancies etc | "No of children" : { |
6 | Date - For dates (without time) | |
7 | Datetime - For dates with time | |
8 | N/A - No data type Usage: This is used for concepts which are used as answer to some other concept |
...
Concept Data Conditions
Any concept in the parent concept set can be enabled / disabled conditionally based on the other concepts value. This makes the long forms usable and intuitive to use. These conditions can also be used to show errors on the forms as well.
...