General Guidelines to Define Observation Forms and Concepts

Follow these recommended guidelines to define observation forms:

Concept and concept sets are part of OpenMRS terminology. When naming a concept and concept set, use a unique but concise name.
Provide a description only if you want that description to show up in the Observations tab as a help text.
Provide a Short Name always. If the Short Name is absent, the fully specified name would be displayed in the UI.
Avoid using special characters except "," and ";" in the fully specified name of the concept. This is to maintain the convention followed in the community.
Make sure that concepts meant for Disease outcomes are defined in the OpenMRS Progress/Followup template and not the Intake template.
There can be observation forms made from the concept of class "Diagnosis" but they are different from diagnosis made via Diagnosis tab.
When naming concepts in a short form (not Short Name) for example, "Anaemia, Diagnosed Date" use capitalization. However, when the concept name reads like a phrase then use "Anaemia, Reason for no treatment" sentence casing. Follow the same for the short name as well. Use short forms only in the Short Name. Use short forms only if they are well understood, e.g. TB. For short forms always use uppercase.
Identify concepts which are used as answers to the coded concepts. The data type for these concepts would be always N/A. If the concept consists of medical terminology then it may be present in the CIEL dictionary. Search for it and if found use the same name for the fully specified name of the concept.
Do not look for a concept set in the CIEL dictionary.

Browser not supported