In the OpenMRS Data Model, the
person table has attributes like gender & birthdate and – through links to other tables – names & addresses. These are attributes (or properties in Java) that are built directly into OpenMRS and, thereby, shared across all implementations. As OpenMRS has been implemented through countries across the world, we've discovered multiple attributes that are needed to meet local needs. For example, in Tanzania, they wanted to record a "ten cell" for each person, which refers to a group of 10 homes. To accommodate these implementation-specific (local) needs, Unknown User (dkayiwa) suggested that we allow for local extensions of the person table. We did this by introducing the
person_attribute_type tables, where the attribute definitions are stored in
person_attribute_type and the actual values for each person are stored in
person_attribute. To date, we have supported some fairly simple attribute types and have had limited capability for supporting more complex attribute types. We are also interested in expanding the "attribute" pattern for local extension of other tables in the data model.
Recent work has added visit attributes to the OpenMRS data model (). This project will take on the task of , to bring person attribute in line with this more generic approach to attributes.
OpenMRS currently supports a limited number of possible data types for Person Attribute Types – e.g. String and Integer. The purpose of this project is to extend the number of attribute types that are supported and, in the process, make the system more flexible.* Create an abstract design that can be expanded to cover additional "attribute" table extensions (e.g., visit_attribute).
person_attribute_type.handler, which specifies an
AttributeTypeHandlerinterface would provide methods to define support for the features specified above (i.e., input mask, choices, validation, single vs. multiple, unique vs. duplicates allowed).
AttributeTypeHandlerfor basic data types: String, Date, Number, etc.
PersonAttributeTypeHandleras an extension of the
AttributeTypeHandlerinterface specifically for persons. We can do the same thing with
VisitAttributeTypeHandlerfor visit-specific attribute types for TRUNK-2131. In contrast,
AttributeTypeHandlerimplementations could be used for both person and visit table extensions.