# Managing Concepts and Metadata

Having well-defined concepts is crucial for every OpenMRS installation. OpenMRS is delivered with just a few basic concepts and it is up to you to gather the rest.

Creating concepts is a complex task which requires expertise and experience so we do not recommend doing it on your own. It is best to contact our community and use some of existing concept dictionaries like MVP or MCL. For more information on how to get in touch with the right people, see the [Getting Help from the OpenMRS Community](../Administering OpenMRS/getting-help-from-the-openmrs-community.md) chapter.

You can either enter concepts on your own manually or use a tool like the Metadata Sharing Module to import them. In this chapter, we will present how to enter concepts manually via the web interface.

To start with you will need to setup Concept Classes. The standard installation includes around 15 predefined concept classes. To view them enter the Administration page > Manage Concept Classes.

1. Add a new Concept Class

2. Click to edit an existing Concept Class

You will see a list with names and descriptions. You can edit them by clicking on a name and also delete by selecting check-boxes next to their names. Note that you cannot delete concept classes that are used in concepts already. There is also a link Add Concept Class to enter new ones.

Concept Datatypes are purposed to indicate different formats of data stored in concepts. They are predefined and read-only. You can view them under Administration > Manage Concept Datatypes.

To view concepts available in your system click Dictionary in the top menu. You will be able to search for particular concepts by name or ID. There is also a check-box that allows to search for retired concepts which are not supposed to be used anymore or are replaced with new ones. You can also enter a new concept from here clicking Add new Concept.

1. Open concept dictionary

2. Add a new concept

3. Search for concepts

4. Search results

Let's create a concept to represent ANTENATAL VISIT REASON. We will use it later in the book in a data entry form. The form for creating a concept allows you to enter Fully Specified Name as well as synonyms. You can add synonyms with Add Synonym button [2]. At least one of the names needs to be marked as Preferred with the radio button next to it.

While creating a new concept you need to decide on datatype. In this case it will be a coded concept that is you will provide a list of answers. Answers need to be defined as concepts. You need to create them beforehand or else add them later.

1. Switch between languages

2. Add a synonym

3. Select datatype

4. Edit a list of answers (this section changes depending on the chosen datatype)

5. Add mappings

Concept Mappings are added to facilitate managing concept dictionaries and point to other concepts which have the same meaning. Mappings are useful when you need to receive or send information to external systems, letting you define how your system's concepts relate to external concepts such as standardized medical vocabularies (e.g., ICD, LOINC, SNOMED).

For example, add a mapping to a concept in the MCL dictionary. You can save the concept now and create some answers.

Repeat the steps and create the concepts PLANNING PREGNANCY and CURRENTLY PREGNANT of Class Finding and Datatype Boolean. The last possible answer will be OTHER of Class Misc and Datatype N/A. After creating three new concepts, you can edit ANTENATAL VISIT REASON and add them as answers.

To view Concept Drugs, go to Administration > Manage Concept Drugs. You can either enter a concept drug by clicking its name to edit it, or you can create a new one through the Add Concept Drug link. You must enter a name and choose one of the concepts of datatypeDrug.

There are different types of Metadata which need to be managed. The list includes Locations, Encounter Types, Order Types, etc. You can view and edit them easily via the Administration page.

A patient identifier is any unique number that can identify a patient. Examples are a Medical Record Number, a National ID, a Social Security number, a driver's license number, etc. A patient can have any number of identifiers. The Patient Identifier Type table defines what type of identifiers are collected in your system.

A patient can have multiple identifiers of each type defined in your system. For example, a patient could have five identifiers of type of "Medical Record Number" because they were seen at five different hospitals that collected five different types of IDs.

The patient search screen searches across all identifier that are still active for a patient.

New identifier types are generally created if they have different characteristics. For example, one identifier can be only a string of numbers, another is a number with a hyphen plus a check digit, etc.

Identifiers uniquely identify patients within the system. Different types of identifiers are distributed by various health care systems. Some of these systems will be within your control, so you will be able to control how identifiers are created and distributed; however, there will likely be identifiers that are not within your control but are useful to record within your system to aid in patient identification.

In order to see predefined identifier types, or to add a new one, go to Administration - Manage Identifier Types. Let's examine OpenMRS Identification Number.

The Regex Format and Description of format fields are empty, but you could add here a regular expression to validate each entered identifier. For example:

\d{1,8}-\d

would allow 1 to 8 digits followed by a dash and a single digit.

It is also possible to choose one of several pre-defined Identifier validators. Here Luhn CheckDigit Validator is used. The purpose of check digits is simple. Any time identifiers (typically number +/- letters) are being manually entered via keyboard, there will be errors. Inadvertent keystrokes or fatigue can cause digits to be rearranged, dropped, or inserted.

Check digits helps to reduce the likelihood of errors by introducing a final digit that is calculated from the prior digits. Using the proper algorithm, the final digit can always be calculated. Therefore, when a number is entered into the system (manually or otherwise), the computer can instantly verify that the final digit matches the digit predicted by the check digit algorithm. If the two do not match, the number is refused. The end result is fewer data entry errors.

Concepts can be easily internationalized; that is you can enter different concept names for every allowed locale. The list of allowed locales is stored in a setting locale.allowed.list as comma separated language codes (for instance en, fr, orde). You can edit the setting from Administration > Maintenance > Settings. See this link for the full list of ISO 639.2 language codes:

https://wiki.openmrs.org/display/docs/Localization+and+Languages

Currently, metadata cannot be internationalized.