The recordX framework implements a reusable "file cabinet" construct in which a history of "actions" are indexed against an arbitrary "entity" record. The primary entity contains a customizable collection of fields which can be used to represent a "person, place, or thing" (customer, patient, vacation rental, laptop, etc). Actions are likewise arbitrary, and can be used to describe anything from an appointment to a repair job or license key.
As with ddi,
the recordX core handles the common
application behavior (users, privileges, navigation, rendering forms) so
that development efforts can be focused on the actual business logic.
Current recordX targets include an EMR application, a CRM database, and
(in conjunction with autocall)
an asset-tracking system.