Class and Description |
---|
Address
Defines the standard fields for an Address in OpenMRS
|
Allergen
Represent allergen
|
AllergenType |
Allergy
Represent allergy
|
AllergyReaction
Represent allergy reactions
|
AllergySeverity |
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.
|
BaseChangeableOpenmrsData
Base superclass for all mutable OpenmrsData.
|
BaseChangeableOpenmrsMetadata
Base superclass for all mutable OpenmrsMetadata.
|
BaseConceptMap
Superclass for
ConceptMap s and ConceptReferenceTermMap s |
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. |
BaseDosingInstructions |
BaseFormRecordableOpenmrsData
Base implementation of FormRecordable that bridges between a saved BaseChangeableOpenmrsData entity and the path in a form where it was recorded.
|
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. |
CareSetting
Care Setting defines the scope of care for any piece of data within the medical record.
|
CareSetting.CareSettingType |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
CodedOrFreeText
A Concept object can represent either a question or an answer to a data point.
|
Cohort
This class represents a list of patientIds.
|
CohortMembership |
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 . |
ConceptAttribute |
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.
|
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.
|
Condition
The condition class records detailed information about a condition, problem, diagnosis, or other
situation or issue.
|
ConditionClinicalStatus
The ConditionClinicalStatus is what we've historically called "condition status" and what FHIR refers to as
ConditionClinicalStatus .
|
ConditionVerificationStatus
The ConditionVerificationStatus is what we've historically called "diagnosis certainty" and what FHIR refers to as
ConditionVerificationStatus.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
Diagnosis
Diagnosis class defines the identification of the nature of an illness or other problem by
examination of the symptoms during an encounter (visit or interaction of a patient with a
healthcare worker).
|
DosingInstructions
The instructions for different drug prescriptions can vary greatly.
|
Drug
Drug
|
DrugIngredient
DrugIngredient
|
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. |
FormRecordable
Defines the methods to make a bridge between an OpenMrsObject and is position in the form.
|
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
Location s |
Obs
An observation is a single unit of clinical information.
|
Obs.Interpretation |
Obs.Status |
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.FulfillerStatus
Valid values for the status of an order that is received from a filler
|
Order.Urgency |
OrderFrequency
The frequency at which an Order's action should be repeated, e.g.
|
OrderGroup |
OrderSet
Represents the grouping of orders into a set,
so as to give decision support for the doctors
|
OrderSet.Operator
Restrictions put on saving an orderSet.
|
OrderSetMember |
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
|
PatientIdentifierType.UniquenessBehavior
Enumeration for the way to handle uniqueness among identifiers for a given identifier type
|
PatientProgram
PatientProgram
|
PatientProgramAttribute |
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
|
ReferralOrder
This is a type of order that adds referral specific attributes.
|
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
Privilege s. |
ServiceOrder
Provides properties for several order types like TestOrder , ReferralOrder
and others depending on the openmrs implementation use case as need arises
|
ServiceOrder.Laterality |
TestOrder
This is a type of order that adds tests specific attributes like: laterality, clinical history,
etc.
|
User
Defines a User Account in the system.
|
UserSessionListener.Event |
UserSessionListener.Status |
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.
|
Class and Description |
---|
OpenmrsObject
This is the base interface for all OpenMRS-defined classes
|
User
Defines a User Account in the system.
|
Class and Description |
---|
Address
Defines the standard fields for an Address in OpenMRS
|
Allergies
Represents patient allergies
|
Allergy
Represent allergy
|
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.
|
CohortMembership |
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 . |
ConceptAttribute |
ConceptAttributeType |
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.
|
Condition
The condition class records detailed information about a condition, problem, diagnosis, or other
situation or issue.
|
Diagnosis
Diagnosis class defines the identification of the nature of an illness or other problem by
examination of the symptoms during an encounter (visit or interaction of a patient with a
healthcare worker).
|
DiagnosisAttribute
The DiagnosisAttribute, value for the
DiagnosisAttributeType that is stored in a Diagnosis . |
DiagnosisAttributeType
The DiagnosisAttributeType extension to the
Diagnosis class. |
Drug
Drug
|
DrugIngredient
DrugIngredient
|
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
Location s |
MedicationDispense
The MedicationDispense class records detailed information about the provision of a supply of a medication
with the intention that it is subsequently consumed by a patient (usually in response to a prescription).
|
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.
|
Order.FulfillerStatus
Valid values for the status of an order that is received from a filler
|
OrderAttribute
The OrderAttribute, value for the
OrderAttributeType that is stored in an Order . |
OrderAttributeType
The OrderAttributeType, extension to the
Order class. |
OrderFrequency
The frequency at which an Order's action should be repeated, e.g.
|
OrderGroup |
OrderGroupAttribute
A value for a user-defined
OrderGroupAttributeType that is stored in an OrderGroup . |
OrderGroupAttributeType
A user-defined extension to the
OrderGroup class. |
OrderSet
Represents the grouping of orders into a set,
so as to give decision support for the doctors
|
OrderSetAttribute
A value for a user-defined
OrderSetAttributeType that is stored on a OrderSet . |
OrderSetAttributeType
A user-defined extension to the
OrderSet class. |
OrderSetMember |
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
|
PatientProgramAttribute |
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
|
ProgramAttributeType |
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
Privilege s. |
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.
|
Class and Description |
---|
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
|
Role
A Role is just an aggregater of
Privilege s. |
User
Defines a User Account in the system.
|
Class and Description |
---|
Allergies
Represents patient allergies
|
Allergy
Represent allergy
|
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.
|
BaseChangeableOpenmrsMetadata
Base superclass for all mutable OpenmrsMetadata.
|
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. |
CareSetting
Care Setting defines the scope of care for any piece of data within the medical record.
|
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Cohort
This class represents a list of patientIds.
|
CohortMembership |
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 . |
ConceptAttribute |
ConceptAttributeType |
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.
|
Condition
The condition class records detailed information about a condition, problem, diagnosis, or other
situation or issue.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
Diagnosis
Diagnosis class defines the identification of the nature of an illness or other problem by
examination of the symptoms during an encounter (visit or interaction of a patient with a
healthcare worker).
|
DiagnosisAttribute
The DiagnosisAttribute, value for the
DiagnosisAttributeType that is stored in a Diagnosis . |
DiagnosisAttributeType
The DiagnosisAttributeType extension to the
Diagnosis class. |
Drug
Drug
|
DrugIngredient
DrugIngredient
|
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
Location s |
MedicationDispense
The MedicationDispense class records detailed information about the provision of a supply of a medication
with the intention that it is subsequently consumed by a patient (usually in response to a prescription).
|
Obs
An observation is a single unit of clinical information.
|
Obs.Status |
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.
|
OrderAttribute
The OrderAttribute, value for the
OrderAttributeType that is stored in an Order . |
OrderAttributeType
The OrderAttributeType, extension to the
Order class. |
OrderFrequency
The frequency at which an Order's action should be repeated, e.g.
|
OrderGroup |
OrderGroupAttribute
A value for a user-defined
OrderGroupAttributeType that is stored in an OrderGroup . |
OrderGroupAttributeType
A user-defined extension to the
OrderGroup class. |
OrderSet
Represents the grouping of orders into a set,
so as to give decision support for the doctors
|
OrderSetAttribute
A value for a user-defined
OrderSetAttributeType that is stored on a OrderSet . |
OrderSetAttributeType
A user-defined extension to the
OrderSet class. |
OrderSetMember |
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
|
PatientProgramAttribute |
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
|
ProgramAttributeType |
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
Privilege s. |
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.
|
Class and Description |
---|
Allergies
Represents patient allergies
|
Allergy
Represent allergy
|
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. |
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.
|
CohortMembership |
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 . |
ConceptAttribute |
ConceptAttributeType |
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.
|
Condition
The condition class records detailed information about a condition, problem, diagnosis, or other
situation or issue.
|
Diagnosis
Diagnosis class defines the identification of the nature of an illness or other problem by
examination of the symptoms during an encounter (visit or interaction of a patient with a
healthcare worker).
|
DiagnosisAttribute
The DiagnosisAttribute, value for the
DiagnosisAttributeType that is stored in a Diagnosis . |
DiagnosisAttributeType
The DiagnosisAttributeType extension to the
Diagnosis class. |
Drug
Drug
|
DrugIngredient
DrugIngredient
|
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
Location s |
MedicationDispense
The MedicationDispense class records detailed information about the provision of a supply of a medication
with the intention that it is subsequently consumed by a patient (usually in response to a prescription).
|
Obs
An observation is a single unit of clinical information.
|
Obs.Status |
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.
|
OrderAttribute
The OrderAttribute, value for the
OrderAttributeType that is stored in an Order . |
OrderAttributeType
The OrderAttributeType, extension to the
Order class. |
OrderFrequency
The frequency at which an Order's action should be repeated, e.g.
|
OrderGroup |
OrderGroupAttribute
A value for a user-defined
OrderGroupAttributeType that is stored in an OrderGroup . |
OrderGroupAttributeType
A user-defined extension to the
OrderGroup class. |
OrderSet
Represents the grouping of orders into a set,
so as to give decision support for the doctors
|
OrderSetAttribute
A value for a user-defined
OrderSetAttributeType that is stored on a OrderSet . |
OrderSetAttributeType
A user-defined extension to the
OrderSet class. |
OrderSetMember |
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
|
PatientProgramAttribute |
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
|
ProgramAttributeType |
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
Privilege s. |
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.
|
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.
|
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.
|
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.
|
Voidable
In OpenMRS, data are rarely fully deleted (purged) from the system; rather, they are either
voided or retired.
|
Class and Description |
---|
Address
Defines the standard fields for an Address in OpenMRS
|
Allergies
Represents patient allergies
|
Allergy
Represent allergy
|
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.
|
CohortMembership |
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 . |
ConceptAttribute |
ConceptAttributeType |
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.
|
Condition
The condition class records detailed information about a condition, problem, diagnosis, or other
situation or issue.
|
Diagnosis
Diagnosis class defines the identification of the nature of an illness or other problem by
examination of the symptoms during an encounter (visit or interaction of a patient with a
healthcare worker).
|
DiagnosisAttribute
The DiagnosisAttribute, value for the
DiagnosisAttributeType that is stored in a Diagnosis . |
DiagnosisAttributeType
The DiagnosisAttributeType extension to the
Diagnosis class. |
Drug
Drug
|
DrugIngredient
DrugIngredient
|
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
Location s |
MedicationDispense
The MedicationDispense class records detailed information about the provision of a supply of a medication
with the intention that it is subsequently consumed by a patient (usually in response to a prescription).
|
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.
|
Order.FulfillerStatus
Valid values for the status of an order that is received from a filler
|
OrderAttribute
The OrderAttribute, value for the
OrderAttributeType that is stored in an Order . |
OrderAttributeType
The OrderAttributeType, extension to the
Order class. |
OrderFrequency
The frequency at which an Order's action should be repeated, e.g.
|
OrderGroup |
OrderGroupAttribute
A value for a user-defined
OrderGroupAttributeType that is stored in an OrderGroup . |
OrderGroupAttributeType
A user-defined extension to the
OrderGroup class. |
OrderSet
Represents the grouping of orders into a set,
so as to give decision support for the doctors
|
OrderSetAttribute
A value for a user-defined
OrderSetAttributeType that is stored on a OrderSet . |
OrderSetAttributeType
A user-defined extension to the
OrderSet class. |
OrderSetMember |
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
|
PatientProgramAttribute |
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
|
ProgramAttributeType |
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
Privilege s. |
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.
|
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.
|
BaseChangeableOpenmrsData
Base superclass for all mutable OpenmrsData.
|
BaseChangeableOpenmrsMetadata
Base superclass for all mutable OpenmrsMetadata.
|
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. |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
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.
|
Class and Description |
---|
PatientIdentifierType
PatientIdentifierType
|
Class and Description |
---|
Concept
A Concept object can represent either a question or an answer to a data point.
|
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.
|
OpenmrsObject
This is the base interface for all OpenMRS-defined classes
|
Program
Program
|
Provider
Represents a person who may provide care to a patient during an encounter
|
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.
|
BaseChangeableOpenmrsMetadata
Base superclass for all mutable OpenmrsMetadata.
|
BaseOpenmrsMetadata
In OpenMRS, we distinguish between data and metadata within our data model.
|
BaseOpenmrsObject
This is the base implementation of the
OpenmrsObject interface. |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
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.
|
Class and Description |
---|
Concept
A Concept object can represent either a question or an answer to a data point.
|
Form
Form
|
Patient
Defines a Patient in the system.
|
Class and Description |
---|
Person
A Person in the system.
|
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.
|
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.
|
PersonName
A Person can have zero to n PersonName(s).
|
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.
|
Class and Description |
---|
Cohort
This class represents a list of patientIds.
|
Patient
Defines a Patient in the system.
|
Class and Description |
---|
Cohort
This class represents a list of patientIds.
|
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.
|
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
|
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. |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
OpenmrsObject
This is the base interface for all OpenMRS-defined classes
|
Role
A Role is just an aggregater of
Privilege s. |
User
Defines a User Account in the system.
|
Class and Description |
---|
User
Defines a User Account in the system.
|
Class and Description |
---|
User
Defines a User Account in the system.
|
Class and Description |
---|
Role
A Role is just an aggregater of
Privilege s. |
User
Defines a User Account in the system.
|
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.
|
Class and Description |
---|
Obs
An observation is a single unit of clinical information.
|
Class and Description |
---|
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
|
Class and Description |
---|
CareSetting
Care Setting defines the scope of care for any piece of data within the medical record.
|
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.
|
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.
|
Order.Action |
Order.FulfillerStatus
Valid values for the status of an order that is received from a filler
|
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.
|
Provider
Represents a person who may provide care to a patient during an encounter
|
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.
|
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.
|
BaseChangeableOpenmrsData
Base superclass for all mutable OpenmrsData.
|
BaseOpenmrsData
In OpenMRS, we distinguish between data and metadata within our data model.
|
BaseOpenmrsObject
This is the base implementation of the
OpenmrsObject interface. |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
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.
|
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.
|
ConceptAnswer
This class represents one option for an answer to a question type of
Concept . |
ConceptAttributeType |
ConceptClass
ConceptClass
|
ConceptDatatype
ConceptDatatype
|
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
|
ConceptSet
This represents a single concept within a concept set.
|
ConceptSource
A concept source is defined as any institution that keeps a concept dictionary.
|
Drug
Drug
|
Encounter
An Encounter represents one visit or interaction of a patient with a healthcare worker.
|
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.
|
LocationAttributeType
A user-defined extension to the
Location class. |
LocationTag
An LocationTag allows categorization of
Location s |
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.
|
PatientIdentifierType
PatientIdentifierType
|
PersonAttribute
A PersonAttribute is meant as way for implementations to add arbitrary information about a
user/patient to their database.
|
PersonAttributeType
PersonAttributeType
|
Program
Program
|
ProgramWorkflow
ProgramWorkflow
|
ProgramWorkflowState
ProgramWorkflowState
|
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.
|
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.
|
BaseChangeableOpenmrsMetadata
Base superclass for all mutable OpenmrsMetadata.
|
BaseOpenmrsMetadata
In OpenMRS, we distinguish between data and metadata within our data model.
|
BaseOpenmrsObject
This is the base implementation of the
OpenmrsObject interface. |
Changeable
Base interface for domain objects that need to track information related to when they were
changed and the user that last changed them.
|
Creatable
Base interface for domain objects that need to track information related to when they were
created and the user that created them.
|
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.
|
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.
|
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).
|
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.
|
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.
|
Copyright © 2024 OpenMRS Inc.. All rights reserved.