-
Notifications
You must be signed in to change notification settings - Fork 48
Rules for creating mind maps
nehagoel2 edited this page Feb 8, 2018
·
3 revisions
- The root node of the mind map is the complaint name.
- The root node and the file name must match exactly. This includes spaces and punctuation.
- All nodes should have only the text inside it.
- Attributes should be spelt exactly. Even an extra space or capitalization with the attributes will make a difference. eg: input-type is a valid attribute, but input-Type is not.
- The 1st level nodes should be questions, followed by answers. The pattern is always questions, answers, questions, answers, etc.
- You can program n levels of nodes. However for the sake of front end usability, we suggest limiting it to no more than 4-6 levels.
- Nodes have attributes associated with them that describe the behaviour of the node. The table below lists the main attributes of a mind map and the behaviour they describe.
- As nodes are selected, the app generates a concise "history note". This note is generated by stringing together "language".
- If a node does not have a language attribute, then the text of the node is used as it's language.
- Language should be programmed so that as nodes are selected, a grammatically correct sentence is built. In other words, the question node should start the sentence, and the answer choices should end that sentence. If there are more levels of questions, they should either continue the sentence, or start new sentences.
- Perform physical exams attribute must name the physical exams exactly as in the physical exam mind map.
- Associated symptoms must match to the root node of the associated map. For example, is Coughing is associated with Chest Pain, when using the associated-complaint attribute, the value must exactly match the name of the Coughing mindmap.