Uses of Interface
org.openmrs.Voidable

Packages that use Voidable

Package	Description
org.openmrs	These classes represent the core domain objects for the OpenMRS project.
org.openmrs.api.handler
org.openmrs.attribute
org.openmrs.person

Uses of Voidable in org.openmrs

Subinterfaces of Voidable in org.openmrs

Modifier and Type	Interface and Description
interface	OpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.

Classes in org.openmrs that implement Voidable

Modifier and Type	Class and Description
class	Allergy Represent allergy
class	BaseChangeableOpenmrsData Base superclass for all mutable OpenmrsData.
class	BaseCustomizableData<A extends Attribute> Extension of BaseOpenmrsData for classes that support customization via user-defined attributes.
class	BaseFormRecordableOpenmrsData Base implementation of FormRecordable that bridges between a saved BaseChangeableOpenmrsData entity and the path in a form where it was recorded.
class	BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
class	Cohort This class represents a list of patientIds.
class	CohortMembership
class	ConceptAttribute
class	ConceptName ConceptName is the real world term used to express a Concept within the idiom of a particular locale.
class	ConceptNameTag ConceptNameTag is a textual tag which can be applied to a ConceptName.
class	Condition The condition class records detailed information about a condition, problem, diagnosis, or other situation or issue.
class	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).
class	DiagnosisAttribute The DiagnosisAttribute, value for the DiagnosisAttributeType that is stored in a Diagnosis.
class	DrugOrder DrugOrder
class	Encounter An Encounter represents one visit or interaction of a patient with a healthcare worker.
class	EncounterProvider Mapping Class between Encounters and Providers which allows many to many relationship.
class	LocationAttribute A value for a user-defined LocationAttributeType that is stored on a Location.
class	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).
class	Obs An observation is a single unit of clinical information.
class	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.
class	OrderAttribute The OrderAttribute, value for the OrderAttributeType that is stored in an Order.
class	OrderGroup Contains a group of Orders that are ordered together within a single encounter,often driven by an OrderSet.
class	OrderGroupAttribute A value for a user-defined OrderGroupAttributeType that is stored in an OrderGroup.
class	OrderSetAttribute A value for a user-defined OrderSetAttributeType that is stored on a OrderSet.
class	Patient Defines a Patient in the system.
class	PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
class	PatientProgram PatientProgram
class	PatientProgramAttribute
class	PatientState PatientState
class	Person A Person in the system.
class	PersonAddress This class is the representation of a person's address.
class	PersonAttribute A PersonAttribute is meant as way for implementations to add arbitrary information about a user/patient to their database.
class	PersonName A Person can have zero to n PersonName(s).
class	ProviderAttribute A value for a user-defined ProviderAttributeType that is stored on a Provider.
class	ReferralOrder This is a type of order that adds referral specific attributes.
class	Relationship Relationship
class	ServiceOrder Provides properties for several order types like TestOrder , ReferralOrder and others depending on the openmrs implementation use case as need arises
class	TestOrder This is a type of order that adds tests specific attributes like: laterality, clinical history, etc.
class	Visit A 'visit' is a contiguous time period where encounters occur between patients and healthcare providers.
class	VisitAttribute A value for a user-defined VisitAttributeType that is stored on a Visit.

Uses of Voidable in org.openmrs.api.handler

Classes in org.openmrs.api.handler with type parameters of type Voidable

Modifier and Type	Interface and Description
interface	UnvoidHandler<V extends Voidable> This is the super interface for all unvoid* actions that take place on all services.
interface	VoidHandler<V extends Voidable> This is the super interface for all void* actions that take place on all services.

Methods in org.openmrs.api.handler with parameters of type Voidable

Modifier and Type	Method and Description
void	VoidSaveHandler.handle(Voidable voidableObject, User currentUser, Date currentDate, String notUsed) This method does not set "voided" to true, but rather only sets the voidedBy/dateVoided if they are null and voided==true.
void	RequireVoidReasonVoidHandler.handle(Voidable voidableObject, User voidingUser, Date voidedDate, String voidReason) Validates that the voidReason is non-null and non-empty for supported objects Should throw IllegalArgumentException if Patient voidReason is null Should throw IllegalArgumentException if Encounter voidReason is empty Should throw IllegalArgumentException if Obs voidReason is blank Should not throw Exception if voidReason is not blank Should not throw Exception if voidReason is null for unsupported types
void	RequireVoidReasonSaveHandler.handle(Voidable voidableObject, User currentUser, Date currentDate, String notUsed) Validates that the voidReason is non-null and non-empty for supported objects Should throw APIException if Patient voidReason is null Should throw APIException if Encounter voidReason is empty Should throw APIException if Encounter voidReason is blank Should not throw Exception if voidReason is not blank Should not throw Exception if voidReason is null for unsupported types
void	BaseVoidHandler.handle(Voidable voidableObject, User voidingUser, Date voidedDate, String voidReason) Sets all void attributes to the given parameters.
void	BaseUnvoidHandler.handle(Voidable voidableObject, User voidingUser, Date origParentVoidedDate, String unused) Called around every unvoid* method to set everything to null.

Uses of Voidable in org.openmrs.attribute

Subinterfaces of Voidable in org.openmrs.attribute

Modifier and Type	Interface and Description
interface	Attribute<AT extends AttributeType,OT extends Customizable<?>> Common interface for user-defined attribute that is are added to a base class.

Classes in org.openmrs.attribute that implement Voidable

Modifier and Type	Class and Description
class	BaseAttribute<AT extends AttributeType,OwningType extends Customizable<?>> Abstract base implementation of Attribute.

Uses of Voidable in org.openmrs.person

Classes in org.openmrs.person that implement Voidable

Modifier and Type	Class and Description
class	PersonMergeLog This class represents the audit of a merge of two persons.