Intro to Objects

The Tendo Object Model (TOM) is a logical representation of the data model for Tendo’s products, which are the interface between Tendo internal services and external consumers to read from and write to the Tendo object database. The object model is a pattern for how objects in the data are defined. 

To see a list of objects for a Tendo tenant, log in to Atrium as an admin, choose Tools from the dropdown menu in the upper left corner, and choose Data on the left side navigation bar. Make sure the Objects tab is selected at the top of the list view.

Tendo Objects

There are two kinds of Tendo objects:

• Standard Objects, . For example, the Appointment object is a standard object.
• Detail Objects, which are child objects of Standard Objects. These are not identifiable and can only be accessed from their parent Standard Object. The Address object is a detail object tied to the Appointment object.

Tendo Object definitions describe the fields, relationships, lifecycles, events and other aspects of a Tendo business entity. Components in the user interface, integration, access control, workflows, and other parts of the Tendo Platform all reference object definitions.

Configuration data in the Tendo system, such as SDUI components, workflows, integration contracts, and permissions and access rules all reference Tendo objects.

Custom Objects

Custom objects can be added by Customer Engagement as a customer healthcare organization needs them. Tendo Objects also can be extended for customer organizations' specific needs, and their Describe API will always return both Tendo-delivered and custom attributes that belong to a specific tenant.

Both standard and custom objects can have custom fields that can be created, edited, or deleted.