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.activelist
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	BaseCustomizableData<A extends Attribute> Extension of BaseOpenmrsData for classes that support customization via user-defined attributes.
class	BaseOpenmrsData In OpenMRS, we distinguish between data and metadata within our data model.
class	Cohort This class represents a list of patientIds.
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	ConceptSource A concept source is defined as any institution that keeps a concept dictionary.
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	Obs An observation is a single unit of clinical information.
class	Order Dates should be interpreted as follows: If startDate is null then the order has been going on "since the beginning of time" Otherwise the order starts on startDate If discontinued is non-null and true, then the following fields should be ignored: autoExpireDate if discontinuedDate is null then the order was discontinued "the instant after it began" otherwise it was given from its starting date until discontinuedDate Otherwise (discontinued is null or false) if autoExpireDate is null, the order is set to go forever otherwise the order goes until autoExpireDate the following fields should be ignored: discontinuedBy discontinuedDate discontinuedReason It is an error to have discontinued be true and have discontinuedDate be after autoExpireDate.
class	Patient Defines a Patient in the system.
class	PatientIdentifier A Patient can have zero to n identifying PatientIdentifier(s).
class	PatientProgram PatientProgram
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	Relationship Relationship
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.activelist

Classes in org.openmrs.activelist that implement Voidable

Modifier and Type	Class and Description
class	ActiveListItem TODO
class	Allergy TODO
class	Problem TODO

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, java.util.Date currentDate, java.lang.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	RequireVoidReasonSaveHandler.handle(Voidable voidableObject, User currentUser, java.util.Date currentDate, java.lang.String notUsed) Validates that the voidReason is non-null and non-empty for supported objects
void	RequireVoidReasonVoidHandler.handle(Voidable voidableObject, User voidingUser, java.util.Date voidedDate, java.lang.String voidReason) Validates that the voidReason is non-null and non-empty for supported objects
void	BaseUnvoidHandler.handle(Voidable voidableObject, User voidingUser, java.util.Date origParentVoidedDate, java.lang.String unused) Called around every unvoid* method to set everything to null.
void	BaseVoidHandler.handle(Voidable voidableObject, User voidingUser, java.util.Date voidedDate, java.lang.String voidReason) Sets all void attributes to the given parameters.

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.