📚 Concepts and Metadata Guide 📚

• 1 About this Guide
• 2 🟠 Terminology, Concepts, and Metadata
• 3 🔵 Metadata Management in OpenMRS
• 4 🟣 Best Practices Examples
• 5 🟢 Managing Concepts and Metadata using the Open Concept Lab (OCL) Tool
• 6 ⚫️ Importing Concepts to an OpenMRS Instance
• 7 🟡 Importing Concepts from OpenMRS into OCL
• 8 🔴 Managing Concepts and Metadata using OpenMRS Admin Legacy UI
• 9 ⚪️ Troubleshooting Concept Import Errors
• 10 ⚪️ Additional Resources
• 11 ⚪️ Archives
• 12 ⚪️ Step-by-Step Instructions ➜ How to Create, Add and Clone Concepts

In this guide, we will walk you through how to use OCL for OpenMRS.

There are 2 main ways to manage your concepts: using Admin Legacy UI or using OpenConceptLab (OCL), an open-source terminology management system. We will delve into these 2 approaches but the use of the OCL tool is highly recommended.

Open

About this Guide

🟠 Terminology, Concepts, and Metadata

1. Terminology 

Terminology refers to the standardized set of medical terms and codes used to represent clinical information in a consistent and interoperable manner.

• It provides a common language that healthcare systems and providers can use to ensure clear communication, accurate data capture, and seamless data exchange.

• There are three main classes of terminology that are used differently within health information systems: Administrative, Reference, and Interface. It is important to know when to use each one.

  • Administrative terminologies are generally used to classify ideas and manage administrative tasks like generating bills, some form of reports, etc. 

    • Examples: ICD-10 or ICD-11 from the WHO, primarily used for diagnoses. 

  • Reference terminologies are usually based on ontologies and attempt to model the meaning of an idea. This allows for a sophisticated grouping of ideas based on relationships with other ideas. 

    • Examples:  SNOMED CT (which covers most domains), LOINC (primarily used for laboratories and clinical findings), and RxNORM (used for drugs).

  • Interface terminologies are primarily clinically friendly terms and phrases that users require for the documentation and treatment of patients and other healthcare activities. They make it easier for users to find target information. 

    • Examples: CIEL and IMO’s Core terminology which provide user-friendly terms mapped to many reference and administrative code systems

→ Terminology Application

• Terminology standardizes the language used within clinical workflows, ensuring that all users, whether clinicians, administrators, or data entry staff, have a shared understanding of medical terms. It prevents ambiguity and errors by ensuring that terms like "hypertension" or "diabetes" mean the same across all systems.

• Clinical decision support tools rely on accurate and standardized terminology to function effectively. Terminology defines groups of ideas that trigger alerts or reminders, such as drug interactions or critical lab results.

• Terminology is essential for extracting meaningful insights from clinical data (Reporting/Analytics). Standardized terms enable the system to group and analyze data effectively, such as the number of patients diagnosed with "Type 2 diabetes” (or any more granular forms of Type 2 diabetes).

• A robust terminology foundation allows seamless exchange of not just codes, but also meaning between systems, such as electronic medical records (EMRs) and laboratory information management systems (LIMS). This is called semantic interoperability.

2. Concepts

Concepts are the building blocks of clinical data within healthcare systems, representing specific entities, conditions, or observations. Each concept captures the meaning or definition behind clinical data. The actual definition of a concept may require a paragraph of text, so this means that the definitions can’t be used in EMRs. 

Terms, on the other hand, are the labels or names assigned to concepts to ensure they are clearly understood and easily referenced. Terms have different roles, so there is one FULLY SPECIFIED term that unambiguously identifies the concept in a particular locale. There can be other ones that are in preferred use, or synonyms which help find the concept, but the FULLY SPECIFIED name should always be confirmed as the correct concept.

It's important to note that while the concept is universal, the terms can be localized (i.e., translated into different languages).

• The purpose of concepts is to provide structured and precise definitions for clinical items (e.g., "Body Temperature", "HIV Positive", "Blood Pressure").

  • A concept represents individual pieces of data collected from a patient → questions/answers, diagnoses, procedures, medications, laboratory tests, etc that need to be captured.

• A concept may include a name, description, class, datatype (numeric, text, coded), and mappings to standardized terminologies (e.g., SNOMED or ICD codes).

• Concepts often derive their definition, context, and structure from established terminologies or classification systems. For instance, a concept like "Hypertension" can be associated with a specific meaning and coding system such as the ICD-10 code This mapping to a standard code ensures a universal understanding of the concept, aligns with clinical standards, and supports interoperability, reporting, and accurate data exchange across healthcare systems.  

3. Metadata

Metadata refers to the descriptive information about concepts or terminology that provides context, structure, and rules for their use.

• Metadata aims to manage how concepts and terminologies are implemented in a system, ensuring data integrity, interoperability, and usability.

• Examples:

  • Data type (e.g., numeric, coded, text).

  • Validation rules (e.g., a temperature must be between 35–42°C).

  • Mappings to external terminologies.

  • Localization information (translations, regional adaptations).

Let’s use the CIEL dictionary (the Columbia International eHealth Laboratory dictionary) to illustrate the relationship between terminology, concept, and metadata using "Body Temperature as an example."

• CIEL Code for Body Temperature: CIEL 5088

• Mappings: CIEL maps this concept to external terminologies such as:

  • LOINC: 8310-5 Body temperature

  • SNOMED CT: 386725007 Body temperature (observable entity)

• Purpose: These mappings ensure that "Body Temperature" is recognized consistently in external systems, supporting interoperability and standardization.

Open

Concept Mapping Example

• Concept ID in OpenMRS: CIEL 5088

  • It’s good to note that, in OpenMRS, the concept ID can vary across different installations. However, in the CIEL dictionary, the concept is referenced as "CIEL:5088," where 5088 is the unique concept ID within the Open Concept Lab (OCL) or the authoritative "golden" server where the concept dictionary is managed. Once the CIEL dictionary is installed in an OpenMRS system, the local concept ID assigned may differ from 5088.

• Name:

  • Preferred: "Body Temperature (°C)"

  • Synonyms: "Temperature," "Temp" (may include translations, such as French: "Température (°C)".

• Data Type: Numeric (to capture measurable values).

• Class: Finding (indicating it is a result or observation from a test).

• Units: Celsius (°C) OR Fahrenheit (°F), but not both. If the concept name has °C, then units must match

• Description (this is a definition in words):

  • Patient temperature in degrees centigrade (°C).

• UUID: Unique identifier for each concept which is maintained for every implementation. 

• Mappings to Terminologies:

  • These are relationships between the concept and other codes or terms e.g. body temperature is mapped to LOINC 8310-5 (which ensures global compatibility).

  • LOINC is an example of a reference source or the origin or authority from which the terminology or concept is derived. Others include SNOMED CT, etc.

Open

Body Temperature Concept in OpenMRS

→ Common Mappings

1. SAME-AS∞: Indicates a mapping relationship in which the concept is considered identical or synonymous to the concept specified. This is sometimes called “Self-mapping” or “Gold Mapping” – e.g. when CIEL:5088 is SAME-AS CIEL:5088. The reason these exist is to persist a source’s official concept ID (the concept ID used in OCL) and also as a mapping for cases where local ID assignment is arbitrary (e.g., importing concepts into a database with auto-assign concept IDs), where the concept ID gets changed arbitrarily during import. In cases where OCL’s concept ID is reliably preserved during imports to implementing systems, these self-mappings are unnecessary.

2. same-as: A standard mapping relationship that identifies the concept as exactly equivalent to another concept in a different dictionary or terminology set. For example, the “Malaria” concept is the same as “unspecified Malaria” in ICD-10-WHO.

3. NARROWER-THANThis mapping means that the concept is more specific than the referenced concept. For instance, “Malaria caused by P. falciparum” is narrower than the broader term “Malaria”.

4. BROADER-THAN: This mapping indicates that the concept is more general than the referenced concept. For example, “Malaria” is broader than the more specific concept “Malaria caused by P. falciparum.”

💡 Note:

It's important to note that SAME-AS mappings offer the most utility compared to Narrower-than and Broader-than mappings. Due to their broader established use, SAME-AS mappings are typically the preferred choice when creating mappings.

5. q-and-a: Represent a Question-and-Answer relationship where a concept (e.g., “Malaria”) is used as an answer to a predefined question (e.g., “What was the medical cause of death?”, “Primary reason for referral” etc). 

6. concept-set: Refers to a specific collection of related concepts grouped for organizational purposes. Concept sets are often used to group similar medical terms or conditions for easier management and reference. Some examples include:

• Vital Signs Concept Set → may include Temperature, Pulse, Respiratory Rate, Blood Pressure, and Oxygen Saturation. 

• Cause of death Concept Set → may include Malaria, HIV/AIDS, Heart Failure, and Road Traffic Accidents.

• Common examples of Concept sets include ConvSet, LabSet, and MedSet.

📌 Convenience Set (ConvSet):

• A convenient set is designed to group commonly used concepts that are frequently referenced together for convenience.

  • Diagnoses easily accessible for clinicians during patient visits → may include concepts in the set like Malaria, Hypertension, Diabetes mellitus, Pneumonia, and Gastroenteritis.   

• A convenient set is used to show or report on a subset of concepts.  

  • Examples of these sets → include oncology, pediatric, or NCD diagnosis.

• They can also be used in forms to reference a group of answers or to filter a database query.

• Used to group related concepts.

  • For example, intravenous fluids → include the name of the fluid, volume, and location of the IV.  In OpenMRS, these are stored in the database as an obsgroup with multiple obs.

📌 MedSet:

• A concept set for a collection of drugs that are related → for example, Antiretroviral drugs or TB medication.

📌 LabSet:

• A concept set for a collection of laboratory tests that are related → for example, Hematogram or Liver Function Panel lab tests.

OpenMRS Concept Tables Data Model

Open

OpenMRS Concept Tables Data Model

Open

OpenMRS Concept Examples

🔵 Metadata Management in OpenMRS

In OpenMRS, metadata management is essential for structuring and standardizing medical and administrative data to ensure seamless system functionality and interoperability. Here are several types of metadata managed within OpenMRS:

1. Concepts

2. Locations

3. Encounter Types

4. Order Types

5. Patient Identifier Types

6. Programs

7. Roles and Privileges

8. Forms

9. Relationship Types

10. Drugs

11. Address Hierarchy 

🟣 Best Practices Examples

• Organizations can either create a set of concepts manually (using Admin Legacy UI) or use tools like OpenConceptLab (OCL) which is an open-source terminology management system. The use of the OCL tool is highly recommended because:

  • OCL provides real-time electronic access to terminological resources and straightforward integration with independent software platforms.

  • OCL Online helps you to collaboratively manage, publish, and use terminology in the cloud alongside the global community.

  • OCL advantages include:

    • It allows you to quickly get startup concepts from CIEL or another trusted source.

    • Facilitates the establishment of a “baseline” source using a trusted dictionary.

    • Minimizes duplication of effort both within and across organizations.

    • Allows content management independent of the OpenMRS version.

    • Promotes a transparent and accessible concept dictionary.

    • Enables public sharing of concepts.

• Concepts naming conventions:

  • Use only alphanumeric characters (letters and numbers), with simple punctuation, such as commas (“,”), parentheses (“( )”), and forward slashes (“/”).

  • Descriptions may include non-alphanumeric characters, but sentence case is recommended – with the first letter capitalized unless acronym (e.g., HIV).

  • Collaborate with end users to ensure concept names are clear, meaningful, and aligned with their workflows.

  • Avoid renaming concepts that are already used for storing clinical data, as this may impact data consistency and reporting.

• Concepts should include a clear and unambiguous description (at least in the system's default locale) that defines its meaning and, ideally, outlines its intended use.

• Design for Re-use:

  • Avoid boolean datatype for symptom & diagnosis concepts → Use datatype N/A for these and use them as answers (not questions

🟢 Managing Concepts and Metadata using the Open Concept Lab (OCL) Tool

Open Concept Lab (OCL) is a terminology service that allows for the creation, editing, and management of medical concepts, including those from Columbia International eHealth Laboratory (CIEL). These concepts include diagnoses, procedures, medications, and other healthcare terminologies. Both OCL and CIEL aim to improve healthcare informatics by offering tools that make health data more standardized and accessible.

📌 The OCL tool provides an online repository that facilitates collaborative management of medical terminologies by providing tools for editing, mapping, and localizing concepts from CIEL to meet specific requirements. Multiple stakeholders contribute to the development, maintenance, and update of these concepts and vocabularies. 

• Welcome! — ocl-docs 2.0 documentation

• Open Concept Lab  

📌 CIEL maintains a comprehensive concept dictionary relevant to health information systems in low and middle-income countries (LMICs). CIEL acts as a “single source of truth” for OpenMRS instances, enabling semantic interoperability and reducing redundancy across different instances. 

The CIEL concepts are available within OCL, allowing users to subscribe to, update, or customize these concepts for their specific needs. If an organization or an individual wants to create a dictionary using the Open Concept Lab (OCL) tool, there are several steps involved. Here's a step-by-step guide focusing on the OCL TermBrowser:

Steps for creating a new collection or repository for content

The steps for creating a dictionary using the Open Concept Lab (OCL) include:

1. Accessing OCL TermBrowser

You'll need an account to contribute to or manage terminologies. To access OCL:

i) Visit the OCL Website:
Navigate to the Open Concept Lab website at app.openconceptlab.org.

ii) Log In or Create an Account:

• If you already have an account:

  • Click the "Sign In" button at the top right of the page.

  • Enter your login credentials and proceed.

• If you're new to OCL:

  • Click the "Sign In" button.

  • Select "Register" to create a new account.

  • Enter your email address and set up your account by following the instructions.

  • Check your email inbox for a verification email, and click the link provided to confirm your email address.

iii) Access and Navigate OCL:

• Once logged in, you'll have access to OCL's features.

2. Creating an Organization

i) Log in to OCL

ii) Navigate to Organizations

iii) Create a New Organization

• Click the "Create Organization" button.

• Fill out the necessary details:

• Name: A unique name for the organization.

• Description: A brief summary of the organization’s purpose.

• Add organization website e.g., https://openmrs.org

• Add company name e.g., OpenMRS

• Add “About Org” e.g., Learn more at https://openmrs.org

• Click "Save" to create the organization.

Open

Creating a New Organization

3. Adding Members to the Organization

i) Access the Organization

ii) From the Organizations page, click on the name of the organization you just created.

iii) Manage Members

iv) In the organization’s dashboard, locate and select the "Members" tab

v) Edit Membership

• Add new members 

• Once done, click UPDATE

Open

Adding Members to an Organization

4. Creating Repositories (Sources and Collections)

1️⃣ Creating a New Source (Optional) ➜ For New Concepts (Source):

i) Set up the source:

• Navigate to "Sources" and click + Source.

• Add the short code, short name, full name,  description, language, and source type, and then select OpenMRS Validation Schema under the schema type.

  • Ensure the short code is descriptive and unique as it cannot be changed later.

• For OpenMRS users, additional steps under Advanced Settings are:

  • Enable ID auto-assignment: Set IDs to sequential numbers.

  • Use UUID for external IDs.

ii) Save the source:

1. Create the source, although you may not use it immediately.

Open

Creating a New Source

Open

Advanced Settings

2️⃣ Creating a New Collection ➜ For Organizing Existing Concepts (Collection):

i) Start a new collection:

• Navigate to "User Collections" and click on the + Collection button.

ii) Configure collection details:

• Short Code: Provide a unique short code (e.g., OpenMRS_Demo, mini-demo etc).

  • Ensure it is descriptive and unique as it cannot be changed later.

  • Name and Description: Add a descriptive name and an optional detailed description.

  • Languages: Select the default and supported languages for the collection.

  • Validation Schema: For OpenMRS users, select the OpenMRS Validation Schema to ensure compatibility.

  • Optional Settings: You may add custom attributes, FHIR settings, or an about page.

iii) Save the collection:

• Click the Create Collection button. Your new collection will now appear in your profile.

Open

5. Adding Concepts to the Collection

i) Search for concepts:

• Use the Global Search feature to find concepts (e.g., “Routine Blood Panel” or “Malaria” or “HIV Test Performed” etc).

• Apply filters to narrow results by:

  • Source (e.g., CIEL, LOINC, PIH).

  • Class (e.g., Lab Test, Diagnosis, Procedure, Finding).

  • Data types (e.g. numeric, text, coded).

ii) Review and verify the concept:

• Click on a concept to view details like mappings, associations, and usage (e.g., what questions it answers or sets it belongs to). This step is crucial to ensure that the concept fits your needs in terms of definition, scope, and applicability.

iii) Add to the collection:

• Click Add to Collection and choose your target collection.

• Use the OpenMRS Compatible Cascade option to include mappings and set members. This ensures that related metadata or mappings are also added in a way that's compatible with OpenMRS systems.

• Confirm and wait for the references to be added (this might take a few seconds). Ensure there are no conflicts.

• If successful, you'll see a gREEN MESSAGE indicating that "references added successfully", showing both concepts and mappings.

• If there areRED MESSAGES, it means the concepts (or their mappings) are already in your collection.

iv) Verification of Addition:

• Go back to your collection to verify that the concept, including any answers or mappings, has been added correctly. Check for the presence of the concept and any associated data like answers to questions (e.g., Yes/No for an HIV test Performed).

Open

❶ Search the Concept

Open

❷ Add to Collection

Open

❸ Apply OpenMRS-Compatible Cascade

 

Open

❹ Results Messages

Open

❺ Verification of concepts and mappings added to a collection

➜ Malaria Concept Diagnosis Example

• Search malaria concept under global search

• You can see what other organizations are using it for example, PIH has used the same concept

• Check the CIEL concept since that is what you want to use to build your dictionary and on the right, you will find some mappings used i.e. SAME-AS, CONCEPT-SET-1, Q-AND-A-1

Open

⏺ Mappings Example → SAME-AS, CONCEPT-SET-1, Q-AND-A-1

6. Using OCL Bulk Importer

7. Cloning to source

As stated earlier, when a concept is Close but Not Exact, you may need to tweak it to suit your needs. If for example, you find a concept in CIEL or another source that nearly fits your needs but requires some adjustments you can pick the option "Clone to Source" which will allow you to make a copy of this concept within your source.

📌 Cloning Process:

• Copy with Mappings → "Clone to source" will not only copy the concept but also its mappings. This means all the connections or references to other terminologies or concepts are duplicated with the concept.

📌 Ownership and Independence:

• Ownership → Once you clone a concept to your source, you become the owner of this new instance of the concept. This means:

  • Control → You can modify this concept without affecting the original in CIEL or wherever it came from.

  • Disconnection → By cloning, you break the link to the original CIEL concept. This concept in your source will no longer receive automatic updates or changes from the source.

Example: Let’s search the smoking status concept in the global search → Review the concept and its answers → Clone to source and select the source e.g Mini Demo Source

• Select the source (e.g Mini Demo Source)

• Then select ADD to add the concept selected

• Preview to see the concepts and mappings that will be added

Open

❶ Clone to Source

 

Open

❷ Preview Concepts & Mappings

Open

❸ Details of Concepts being Cloned

Open

❹ Results of Concepts Cloned

Cross-check the mini-demo-source

• Verify that the concept (e.g., "smoking status") and its associated answers have been added.

• Note that these are no longer CIEL concepts; they are owned by the organization or source that created them.

• The advantage now is that you can customize the concept to suit your needs

Open

❺ Verification of Concepts Added

To modify the smoking status concept, click “Edit Concept” action

 

Open

❻ Edit Concept

Click “Edit Concept”

 

Open

❼ Edit Details

• You can add another translation e.g. Swahili translation for Malaria.

  • Select the locale as sw.

  • Enter the description such as Hali ya kuvuta sigara.

  • Set the type to Fully Specified.

  • Mark it as Preferred.

  • Update the comment to indicate Add new locale concept name.

Open

❽ Adding Concept Translations

Open

❾ Checking Translation Added

8. Tweaking the concept to add a new mapping

If you want to tweak a concept to add missing answers, the steps are:-

• Click “Add Concept”

Open

❶ Add Concept

• Add Concept Details

  • Concept Class: Finding

  • Datatype: Coded

  • Locale: English

  • Name: Smokes 33 cigs per day (missing answer)

  • Type: Fully Specified

  • Preferred: Checked

• After adding the concept, verify it by selecting Action → Edit Concept. You will see the details of the concept you added, along with the automatically generated external ID.

Open

❷ Verify Added Details

• Add this mapping as an answer to the concept of "Smoking Status".

  • Within the "Smoking Status" concept, there is currently no answer such as "Smokes 33 cigarettes per day"→ which is what we want to be added as an answer. 

  • To include this as an answer, click on the "Smoking Status" concept.

  • Click “Add New Mapping”

Open

❶ Select Smoking Status Concept

• Click Add New Mappings

  • Set the relationship type to Q&A.

  • Select the source as Mini Demo Source.

  • For the concept, search for Smokes 33 cigarettes per day.

  • Click Save.

Open

❷ Add Details

Open

❸Updated Concept with the Newly Added

9. Creating a Similar Concept

If you already have a concept in your source and need to create a similar one, you can use the “Create Similar” shortcut. For example, if you want to add a new concept for “Congenital blindness” with the same class, datatype, and similar names as “Congenital deafness:”

• Select the concept (checkbox) you want to duplicate.

• Click “Create Similar” → This action automatically copies the class, datatype, and names, which you must update to ensure they are unique and meet validation requirements.

Open

10. Versioning

i) Create a Version: 

• Once you're satisfied with the initial dictionary setup, create a version of your source or collection.

• This is crucial for maintaining historical data and ensuring you can reference specific states in your dictionary.

ii) Ensure Your Workspace is Ready:

• Your "head version" or current workspace contains all the latest work such as the edits or additions to your dictionary or collection.

iii) Create a Version:

• Click + (Manage content)

• Select “Add Version”

Open

Add a Version

iv) Add a Version Number:

• Assign a version ID. For example, if this is your first version, you could label it "Version 1" or simply "1". Subsequent versions would increment from there (e.g., 1.1, 2, etc.).

v) Add a Description:

• Provide a brief description of what this version includes or what changes were made. For instance: “Added socio-demographic concepts."

vi) Check Release:

• Before finalizing, review your changes or check if this version is ready to be 'released' or made available for use or review by others, if applicable.

vii) Click Create:

• Once you've verified everything, click the "Create" button to save this state as an official version. This action will record this point in the history of your project, allowing you to revert to or reference it later if needed.

 

Open

New Source Version Details

11. Adding the cloned concept to the collection

Add the newly cloned concept to your collection (e.g., mini-demo collection).

• You will notice that the owner and source of the added concept (smoking status) are no longer attributed to CIEL.

• Remember to select OpenMRS-compatible cascade

Open

Add Cloned Concept to the Collection

Open

Concept Owner and Source Attribution

12. Mapping to other Concepts (Optional)

Define Relationships → To enhance interoperability, you can map the new concept to others within your source or to external terminologies or standards like SNOMED CT or ICD-10:

1. Open the newly created concept.

2. Click the “Add New Mappings” option.

3. Select existing concepts or input codes from external standards as needed.

4. Click Save

Open

Add a Mappings

Open

Mapping Example for Smoking Status Concept

13. Dictionary Sharing or Subscription

• If you want others to use your dictionary, you can share it by providing access or making it public.

• You can subscribe to your OCL source or collection to automatically update your system with these concepts.

Ongoing Maintenance

• Regularly update your dictionary with new concepts, mappings, or changes in medical terminology.

• Engage with the community for feedback, which might lead to further refinement of your work.

⚫️ Importing Concepts to an OpenMRS Instance

The steps below explain how one can import concepts to an OpenNMS instance.

1. Version & Expansion

• Click on "+ Add Version" in your concept source or collection.

  • Enter the next sequential version number (e.g., start with 1 for your first version and then move sequentially to 2, 3, etc for the subsequent versions).

  • Provide a brief description of what this version adds or changes (e.g., "Added Socio Demographic Concepts").

  • Check "Release" (by default this is unchecked)

  • Click "Create" to finalize the new version.

  • Refresh the page to check if the version and expansions match your input.

Open

❶ Add Version

Open

❷ Version Description

Open

❸ Version & Head Concepts Comparisons

2. Subscription URL Test QA (Optional)

• Copy the subscription URL for the new version.

• Navigate to the OpenMRS Admin page (in your instance).

• Open the "Concept Lab" module in OpenMRS.

• Paste the copied subscription URL for the new version number in the appropriate field.

  • Paste the token or authentication if required.

• Save these changes.

• Click the import tab and then click the "Import" action to begin importing the concepts.

• Review any errors from previous imports in the “Previous Imports” tab.

• Refresh the page to ensure the import was successful.

Open

❶ Subscription URL

Open

❷ Subscription URL and Token

3. Export Version

• Export the new version from the OCL to get a file format that the OpenMRS Initializer can process.

  • Click Export Version Icon

  • Select “Export Version”

  • OCL will create a Zipped file and it will show you when the export version is completed for you. 

Open

Export Version

4. Upload the exported file to your repository

• Go to your repository in your OpenMRS distribution's GitHub repository e.g.

  • https://github.com/openmrs/openmrs-distro-referenceapplication/tree/main/distro/configuration/ocl (OpenMRS)

  • path-drc-emr/distro/configuration/ocl at main · openmrs/path-drc-emr (DRC)

• Click the “Add file” and select the “Upload file” option to upload the exported file from Step 3.

• Choose the file to upload → The Export Version you downloaded.

• Commit Changes

  • Add a commit name e.g., "Added HIV Metadata".

  • Describe changes e.g., "Added HIV TB Screening and WHO Staging concepts".

• Create a new branch:

  • Select "Create a new branch for this commit and start a pull request".

  • Name the branch something descriptive like "/update-hiv-metadata" or "/update-BasicLabTests-metadata".

• Propose Changes: 

  • Click “propose changes” to propose changes.

Open

Concepts File Upload

Open

Propose Changes

5. Create a Pull Request (PR) for the changes 

• Navigate back to your repository's main page and switch the branch from "MAIN" to the newly created branch (e.g., "update-hiv-metadata").

• Path: