Uses of Package
org.openmrs

Packages that use org.openmrs

Package	Description
org.openmrs	These classes represent the core domain objects for the OpenMRS project.
org.openmrs.activelist
org.openmrs.aop	This package contains the classes associated with Aspect Oriented Programming (AOP).
org.openmrs.api	The primary OpenMRS API interfaces.
org.openmrs.api.context	This package describes the context framework through which authentication is performed and services provided for the OpenMRS system.
org.openmrs.api.db	OpenMRS database layer interfaces.
org.openmrs.api.db.hibernate	Resources for Hibernate ORM.
org.openmrs.api.handler
org.openmrs.api.impl
org.openmrs.arden
org.openmrs.arden.compiled
org.openmrs.attribute
org.openmrs.cohort	Deprecated
org.openmrs.cohort.impl
org.openmrs.comparator
org.openmrs.hl7	OpenMRS HL7 module.
org.openmrs.hl7.handler
org.openmrs.hl7.impl
org.openmrs.layout.web.address
org.openmrs.layout.web.name
org.openmrs.logic	The OpenMRS Logic Service provides access to granular and derived data.
org.openmrs.logic.datasource	Logic data sources are responsible for providing data to the logic service engine.
org.openmrs.logic.result
org.openmrs.module	OpenMRS Module classes
org.openmrs.module.web
org.openmrs.module.web.extension
org.openmrs.notification
org.openmrs.notification.db
org.openmrs.notification.db.hibernate
org.openmrs.notification.impl
org.openmrs.notification.web
org.openmrs.obs
org.openmrs.obs.handler
org.openmrs.order
org.openmrs.person
org.openmrs.propertyeditor
org.openmrs.report	Deprecated
org.openmrs.report.impl
org.openmrs.reporting	Deprecated
org.openmrs.reporting.data
org.openmrs.reporting.export
org.openmrs.reporting.report
org.openmrs.scheduler
org.openmrs.util	Shared utilities for OpenMRS classes
org.openmrs.validator
org.openmrs.web
org.openmrs.web.controller
org.openmrs.web.controller.concept
org.openmrs.web.controller.encounter
org.openmrs.web.controller.form
org.openmrs.web.controller.location
org.openmrs.web.controller.maintenance
org.openmrs.web.controller.observation
org.openmrs.web.controller.observation.handler
org.openmrs.web.controller.patient
org.openmrs.web.controller.person
org.openmrs.web.controller.provider
org.openmrs.web.controller.user
org.openmrs.web.controller.visit
org.openmrs.web.dwr
org.openmrs.web.form.visit
org.openmrs.web.taglib
org.openmrs.web.taglib.functions
org.openmrs.web.user

Classes in org.openmrs used by org.openmrs

Class and Description
Address Defines the standard fields for an Address in OpenMRS
Attributable Classes marked with this interface are able to be special values for a PersonAttribute.
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseConceptMap Superclass for ConceptMaps and ConceptReferenceTermMaps
BaseCustomizableData Extension of BaseOpenmrsData for classes that support customization via user-defined attributes.
BaseCustomizableMetadata Extension of BaseOpenmrsMetadata for classes that support customization via user-defined attributes.
BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
CareSetting Care Setting defines the scope of care for any piece of data within the medical record.
CareSetting.CareSettingType
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptClass ConceptClass
ConceptDatatype ConceptDatatype
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptSet This represents a single concept within a concept set.
ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
ConceptWord ConceptWord Concept words are the individual terms of which a concept name is composed.
DosingInstructions The instructions for different drug prescriptions can vary greatly.
Drug Drug
DrugOrder DrugOrder
DrugReferenceMap The DrugReferenceMap map object represents a mapping between a drug and alternative drug terminologies.
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterProvider Mapping Class between Encounters and Providers which allows many to many relationship.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Field Field
FieldAnswer FieldAnswer
FieldType FieldType
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationTag An LocationTag allows categorization of Locations
Obs An observation is a single unit of clinical information.
OpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
Order.Action
Order.Urgency
OrderFrequency The frequency at which an Order's action should be repeated, e.g.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PatientIdentifierType.LocationBehavior Enumerates the possible ways that location may be applicable for a particular Patient Identifer Type
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonAttributeType PersonAttributeType
PersonName A Person can have zero to n PersonName(s).
Privilege Privilege
Program Program
ProgramWorkflow ProgramWorkflow
ProgramWorkflowState ProgramWorkflowState
Provider Represents a person who may provide care to a patient during an encounter
Relationship Relationship
RelationshipType Defines a type of relationship between two people in the database.
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
Role A Role is just an aggregater of Privileges.
TestOrder This is a type of order that adds tests specific attributes like: laterality, clinical history, etc.
TestOrder.Laterality
Tribe Deprecated. This object is no longer supported. This functionality has been replaced by the Tribe module. The installation of that module converts this tribe patient attribute to a PersonAttribute and all values are copied over
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitType Represents the assortment of visit types available to an implementation.
Voidable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.activelist

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Concept A Concept object can represent either a question or an answer to a data point.
Obs An observation is a single unit of clinical information.
OpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Patient Defines a Patient in the system.
Person A Person in the system.
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
Voidable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.aop

Class and Description
OpenmrsObject This is the base interface for all OpenMRS-defined classes
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.api

Class and Description
Address Defines the standard fields for an Address in OpenMRS
CareSetting Care Setting defines the scope of care for any piece of data within the medical record.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptClass ConceptClass
ConceptComplex Child class of Concept that has a ComplexObsHandler associated with the Concept.
ConceptDatatype ConceptDatatype
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
ConceptProposal A ConceptProposal is a temporary holder for concept that should be in the system.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptSearchResult An Object of this class represents a search result returned when searching for concepts, it holds extra metadata about the matched concept(s).
ConceptSet This represents a single concept within a concept set.
ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
ConceptStateConversion ConceptStateConversion
ConceptStopWord ConceptStopWord is the real world term used to filter the words for indexing from search phrase.
ConceptWord ConceptWord Concept words are the individual terms of which a concept name is composed.
Drug Drug
DrugIngredient DrugIngredient
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Field Field
FieldAnswer FieldAnswer
FieldType FieldType
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
ImplementationId Every installation of OpenMRS should get a unique implementation id.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationAttribute A value for a user-defined LocationAttributeType that is stored on a Location.
LocationAttributeType A user-defined extension to the Location class.
LocationTag An LocationTag allows categorization of Locations
MimeType Deprecated. This class is no longer used. Mimetypes are determined by the handler for a ConceptComplex now.
Obs An observation is a single unit of clinical information.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
OrderFrequency The frequency at which an Order's action should be repeated, e.g.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonAttributeType PersonAttributeType
PersonName A Person can have zero to n PersonName(s).
Privilege Privilege
Program Program
ProgramWorkflow ProgramWorkflow
ProgramWorkflowState ProgramWorkflowState
Provider Represents a person who may provide care to a patient during an encounter
ProviderAttribute A value for a user-defined ProviderAttributeType that is stored on a Provider.
ProviderAttributeType A user-defined extension to the Provider class.
Relationship Relationship
RelationshipType Defines a type of relationship between two people in the database.
Role A Role is just an aggregater of Privileges.
Tribe Deprecated. This object is no longer supported. This functionality has been replaced by the Tribe module. The installation of that module converts this tribe patient attribute to a PersonAttribute and all values are copied over
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitAttribute A value for a user-defined VisitAttributeType that is stored on a Visit.
VisitAttributeType A user-defined extension to the Visit class.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.api.context

Class and Description
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.api.db

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
CareSetting Care Setting defines the scope of care for any piece of data within the medical record.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptClass ConceptClass
ConceptComplex Child class of Concept that has a ComplexObsHandler associated with the Concept.
ConceptDatatype ConceptDatatype
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
ConceptProposal A ConceptProposal is a temporary holder for concept that should be in the system.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptSearchResult An Object of this class represents a search result returned when searching for concepts, it holds extra metadata about the matched concept(s).
ConceptSet This represents a single concept within a concept set.
ConceptSetDerived ConceptSetDerived
ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
ConceptStateConversion ConceptStateConversion
ConceptStopWord ConceptStopWord is the real world term used to filter the words for indexing from search phrase.
ConceptWord ConceptWord Concept words are the individual terms of which a concept name is composed.
Drug Drug
DrugIngredient DrugIngredient
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Field Field
FieldAnswer FieldAnswer
FieldType FieldType
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationAttribute A value for a user-defined LocationAttributeType that is stored on a Location.
LocationAttributeType A user-defined extension to the Location class.
LocationTag An LocationTag allows categorization of Locations
MimeType Deprecated. This class is no longer used. Mimetypes are determined by the handler for a ConceptComplex now.
Obs An observation is a single unit of clinical information.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
OrderFrequency The frequency at which an Order's action should be repeated, e.g.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonAttributeType PersonAttributeType
PersonName A Person can have zero to n PersonName(s).
Privilege Privilege
Program Program
ProgramWorkflow ProgramWorkflow
ProgramWorkflowState ProgramWorkflowState
Provider Represents a person who may provide care to a patient during an encounter
ProviderAttribute A value for a user-defined ProviderAttributeType that is stored on a Provider.
ProviderAttributeType A user-defined extension to the Provider class.
Relationship Relationship
RelationshipType Defines a type of relationship between two people in the database.
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitAttribute A value for a user-defined VisitAttributeType that is stored on a Visit.
VisitAttributeType A user-defined extension to the Visit class.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.api.db.hibernate

Class and Description
CareSetting Care Setting defines the scope of care for any piece of data within the medical record.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptClass ConceptClass
ConceptComplex Child class of Concept that has a ComplexObsHandler associated with the Concept.
ConceptDatatype ConceptDatatype
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
ConceptProposal A ConceptProposal is a temporary holder for concept that should be in the system.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptSearchResult An Object of this class represents a search result returned when searching for concepts, it holds extra metadata about the matched concept(s).
ConceptSet This represents a single concept within a concept set.
ConceptSetDerived ConceptSetDerived
ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
ConceptStateConversion ConceptStateConversion
ConceptStopWord ConceptStopWord is the real world term used to filter the words for indexing from search phrase.
ConceptWord ConceptWord Concept words are the individual terms of which a concept name is composed.
Drug Drug
DrugIngredient DrugIngredient
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Field Field
FieldAnswer FieldAnswer
FieldType FieldType
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationAttribute A value for a user-defined LocationAttributeType that is stored on a Location.
LocationAttributeType A user-defined extension to the Location class.
LocationTag An LocationTag allows categorization of Locations
MimeType Deprecated. This class is no longer used. Mimetypes are determined by the handler for a ConceptComplex now.
Obs An observation is a single unit of clinical information.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
OrderFrequency The frequency at which an Order's action should be repeated, e.g.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonAttributeType PersonAttributeType
PersonName A Person can have zero to n PersonName(s).
Privilege Privilege
Program Program
ProgramWorkflow ProgramWorkflow
ProgramWorkflowState ProgramWorkflowState
Provider Represents a person who may provide care to a patient during an encounter
ProviderAttribute A value for a user-defined ProviderAttributeType that is stored on a Provider.
ProviderAttributeType A user-defined extension to the Provider class.
Relationship Relationship
RelationshipType Defines a type of relationship between two people in the database.
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitAttribute A value for a user-defined VisitAttributeType that is stored on a Visit.
VisitAttributeType A user-defined extension to the Visit class.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.api.handler

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptProposal A ConceptProposal is a temporary holder for concept that should be in the system.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
Patient Defines a Patient in the system.
Person A Person in the system.
PersonName A Person can have zero to n PersonName(s).
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitType Represents the assortment of visit types available to an implementation.
Voidable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.api.impl

Class and Description
Address Defines the standard fields for an Address in OpenMRS
CareSetting Care Setting defines the scope of care for any piece of data within the medical record.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptClass ConceptClass
ConceptComplex Child class of Concept that has a ComplexObsHandler associated with the Concept.
ConceptDatatype ConceptDatatype
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
ConceptProposal A ConceptProposal is a temporary holder for concept that should be in the system.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptSearchResult An Object of this class represents a search result returned when searching for concepts, it holds extra metadata about the matched concept(s).
ConceptSet This represents a single concept within a concept set.
ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
ConceptStateConversion ConceptStateConversion
ConceptStopWord ConceptStopWord is the real world term used to filter the words for indexing from search phrase.
ConceptWord ConceptWord Concept words are the individual terms of which a concept name is composed.
Drug Drug
DrugIngredient DrugIngredient
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Field Field
FieldAnswer FieldAnswer
FieldType FieldType
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
ImplementationId Every installation of OpenMRS should get a unique implementation id.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationAttribute A value for a user-defined LocationAttributeType that is stored on a Location.
LocationAttributeType A user-defined extension to the Location class.
LocationTag An LocationTag allows categorization of Locations
MimeType Deprecated. This class is no longer used. Mimetypes are determined by the handler for a ConceptComplex now.
Obs An observation is a single unit of clinical information.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
OrderFrequency The frequency at which an Order's action should be repeated, e.g.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonAttributeType PersonAttributeType
PersonName A Person can have zero to n PersonName(s).
Privilege Privilege
Program Program
ProgramWorkflow ProgramWorkflow
ProgramWorkflowState ProgramWorkflowState
Provider Represents a person who may provide care to a patient during an encounter
ProviderAttribute A value for a user-defined ProviderAttributeType that is stored on a Provider.
ProviderAttributeType A user-defined extension to the Provider class.
Relationship Relationship
RelationshipType Defines a type of relationship between two people in the database.
Role A Role is just an aggregater of Privileges.
Tribe Deprecated. This object is no longer supported. This functionality has been replaced by the Tribe module. The installation of that module converts this tribe patient attribute to a PersonAttribute and all values are copied over
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitAttribute A value for a user-defined VisitAttributeType that is stored on a Visit.
VisitAttributeType A user-defined extension to the Visit class.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.arden

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
Obs An observation is a single unit of clinical information.
Patient Defines a Patient in the system.

Classes in org.openmrs used by org.openmrs.arden.compiled

Class and Description
Patient Defines a Patient in the system.

Classes in org.openmrs used by org.openmrs.attribute

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
OpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
Voidable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.cohort

Class and Description
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
OpenmrsObject This is the base interface for all OpenMRS-defined classes

Classes in org.openmrs used by org.openmrs.cohort.impl

Class and Description
Cohort This class represents a list of patientIds.

Classes in org.openmrs used by org.openmrs.comparator

Class and Description
PatientIdentifierType PatientIdentifierType

Classes in org.openmrs used by org.openmrs.hl7

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Person A Person in the system.
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.hl7.handler

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
Patient Defines a Patient in the system.

Classes in org.openmrs used by org.openmrs.hl7.impl

Class and Description
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
Person A Person in the system.

Classes in org.openmrs used by org.openmrs.layout.web.address

Class and Description
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.

Classes in org.openmrs used by org.openmrs.layout.web.name

Class and Description
PersonName A Person can have zero to n PersonName(s).

Classes in org.openmrs used by org.openmrs.logic

Class and Description
Cohort This class represents a list of patientIds.
Patient Defines a Patient in the system.

Classes in org.openmrs used by org.openmrs.logic.datasource

Class and Description
Cohort This class represents a list of patientIds.

Classes in org.openmrs used by org.openmrs.logic.result

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.module

Class and Description
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Privilege Privilege

Classes in org.openmrs used by org.openmrs.module.web

Class and Description
Person A Person in the system.

Classes in org.openmrs used by org.openmrs.module.web.extension

Class and Description
Form Form

Classes in org.openmrs used by org.openmrs.notification

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Patient Defines a Patient in the system.
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.notification.db

Class and Description
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.notification.db.hibernate

Class and Description
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.notification.impl

Class and Description
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.notification.web

Class and Description
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.obs

Class and Description
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.obs.handler

Class and Description
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.order

Class and Description
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Order Encapsulates information about the clinical action of a provider requesting something for a patient e.g requesting a test to be performed, prescribing a medication, requesting the patient to enroll on a specific diet etc.
OrderType OrderTypes are used to classify different types of Orders e.g to distinguish between Serology and Radiology TestOrders

Classes in org.openmrs used by org.openmrs.person

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
OpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Person A Person in the system.
Voidable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.propertyeditor

Class and Description
ConceptAnswer This class represents one option for an answer to a question type of Concept.
ConceptSet This represents a single concept within a concept set.
Program Program

Classes in org.openmrs used by org.openmrs.report

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
Obs An observation is a single unit of clinical information.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
PatientProgram PatientProgram
Program Program
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.

Classes in org.openmrs used by org.openmrs.report.impl

Class and Description
Cohort This class represents a list of patientIds.

Classes in org.openmrs used by org.openmrs.reporting

Class and Description
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
Drug Drug
EncounterType An EncounterType defines how a certain kind of Encounter.
Form Form
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Person A Person in the system.
PersonAttributeType PersonAttributeType
Program Program
ProgramWorkflowState ProgramWorkflowState
RelationshipType Defines a type of relationship between two people in the database.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.reporting.data

Class and Description
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
OpenmrsObject This is the base interface for all OpenMRS-defined classes

Classes in org.openmrs used by org.openmrs.reporting.export

Class and Description
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientProgram PatientProgram
Relationship Relationship

Classes in org.openmrs used by org.openmrs.reporting.report

Class and Description
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
Cohort This class represents a list of patientIds.
OpenmrsObject This is the base interface for all OpenMRS-defined classes

Classes in org.openmrs used by org.openmrs.scheduler

Class and Description
Auditable In OpenMRS, the convention is to track basic audit information for each object related to who initially created the object and when, and who last changed the object and when.
BaseOpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
BaseOpenmrsObject This is the base implementation of the OpenmrsObject interface. It implements the uuid variable that all objects are expected to have.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
OpenmrsObject This is the base interface for all OpenMRS-defined classes
Retireable In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either voided or retired.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.util

Class and Description
Attributable Classes marked with this interface are able to be special values for a PersonAttribute.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptNumeric The ConceptNumeric extends upon the Concept object by adding some number range values
Drug Drug
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
OpenmrsMetadata In OpenMRS, we distinguish between data and metadata within our data model.
Person A Person in the system.
Provider Represents a person who may provide care to a patient during an encounter
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.validator

Class and Description
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PersonName A Person can have zero to n PersonName(s).

Classes in org.openmrs used by org.openmrs.web

Class and Description
PersonName A Person can have zero to n PersonName(s).

Classes in org.openmrs used by org.openmrs.web.controller

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
ConceptDescription ConceptDescription is the localized description of a concept.
ConceptMap The concept map object represents a mapping of Concept to ConceptSource.
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptSet This represents a single concept within a concept set.
Drug Drug
Form Form
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.

Classes in org.openmrs used by org.openmrs.web.controller.concept

Class and Description
ConceptMapType ConceptMapType are used to define relationships between concepts and concept reference terms e.g IS_A or SAME_AS, BROADER_THAN
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptReferenceTermMap The concept Reference Term map object represents a mapping between two Concept Reference Terms.
ConceptStopWord ConceptStopWord is the real world term used to filter the words for indexing from search phrase.

Classes in org.openmrs used by org.openmrs.web.controller.encounter

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
EncounterRole An EncounterRole a role specific to the encounter.
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
LocationTag An LocationTag allows categorization of Locations
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.web.controller.form

Class and Description
Form Form
FormResource A FormResource is meant as a way for modules to add arbitrary information to a Form.

Classes in org.openmrs used by org.openmrs.web.controller.location

Class and Description
LocationAttributeType A user-defined extension to the Location class.

Classes in org.openmrs used by org.openmrs.web.controller.maintenance

Class and Description
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.

Classes in org.openmrs used by org.openmrs.web.controller.observation

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
Obs An observation is a single unit of clinical information.
Person A Person in the system.

Classes in org.openmrs used by org.openmrs.web.controller.observation.handler

Class and Description
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.web.controller.patient

Class and Description
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
Patient Defines a Patient in the system.
PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
PatientIdentifierType PatientIdentifierType
PersonAddress This class is the representation of a person's address.
PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
PersonName A Person can have zero to n PersonName(s).
Relationship Relationship

Classes in org.openmrs used by org.openmrs.web.controller.person

Class and Description
Person A Person in the system.

Classes in org.openmrs used by org.openmrs.web.controller.provider

Class and Description
Provider Represents a person who may provide care to a patient during an encounter
ProviderAttributeType A user-defined extension to the Provider class.

Classes in org.openmrs used by org.openmrs.web.controller.user

Class and Description
Role A Role is just an aggregater of Privileges.
User Defines a User Account in the system.

Classes in org.openmrs used by org.openmrs.web.controller.visit

Class and Description
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
Patient Defines a Patient in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitAttributeType A user-defined extension to the Visit class.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.web.dwr

Class and Description
Cohort This class represents a list of patientIds.
Concept A Concept object can represent either a question or an answer to a data point.
ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
ConceptReferenceTerm A concept reference term is typically name for a concept by which it is referred in another institution like ICD9, ICD10, SNOMED that keeps a concept dictionary or any other OpenMRS implementation
ConceptSearchResult An Object of this class represents a search result returned when searching for concepts, it holds extra metadata about the matched concept(s).
Drug Drug
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
Field Field
Form Form
FormField The FormField object relates/orders the fields on a form A form can have many 0 to n fields associated with it in a hierarchical manor.
GlobalProperty Global properties are simple key-value pairs persisted in the database GPs can be thought of as something similar to environment variables used in operating systems.
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
Obs An observation is a single unit of clinical information.
Patient Defines a Patient in the system.
PatientProgram PatientProgram
PatientState PatientState
Person A Person in the system.
Provider Represents a person who may provide care to a patient during an encounter
Relationship Relationship
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.

Classes in org.openmrs used by org.openmrs.web.form.visit

Class and Description
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.web.taglib

Class and Description
Concept A Concept object can represent either a question or an answer to a data point.
DrugOrder DrugOrder
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
EncounterRole An EncounterRole a role specific to the encounter.
EncounterType An EncounterType defines how a certain kind of Encounter.
Form Form
Location A Location is a physical place, such as a hospital, a room, a clinic, or a district.
LocationTag An LocationTag allows categorization of Locations
Obs An observation is a single unit of clinical information.
Person A Person in the system.
Program Program
Provider Represents a person who may provide care to a patient during an encounter
User Defines a User Account in the system.
Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
VisitType Represents the assortment of visit types available to an implementation.

Classes in org.openmrs used by org.openmrs.web.taglib.functions

Class and Description
Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
Obs An observation is a single unit of clinical information.

Classes in org.openmrs used by org.openmrs.web.user

Class and Description
User Defines a User Account in the system.