> For the complete documentation index, see [llms.txt](https://docs.omnivatelehealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnivatelehealth.com/admin/configuration/master.md).
# Master
Admin can manage master fields and subfields efficiently.
### Overview
The Master Management section empowers administrators to customize and manage master fields and subfields, facilitating efficient data organization within the system.
Master Section
### **Adding a Master Field**
1. Click on the "Add Master" button.
2. Enter the name of the master field.
3. Optionally, add subfields by clicking on "Add Subfield" and entering the subfield name.
4. Click "Save" to create the master field.
### **Editing a Master Field**
1. Find the desired master field from the list.
2. Click on "Edit" or "Modify" next to the master field.
3. Update the name or associated codes as needed.
4. Optionally, edit or modify associated subfields.
5. Click "Save" to update the master field.
### **Deleting a Master Field**
1. Locate the master field to delete.
2. Click on "Delete" or "Remove" next to the field.
3. Confirm deletion when prompted.
### **Activating or Deactivating a Master Field**
1. Find the desired field from the list.
2. Toggle the activation status using the provided option (e.g., "Active" or "Inactive").
3. Save changes to update the activation status.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.omnivatelehealth.com/admin/configuration/master.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
