Object Data Access
The HealthShare® Health Connect object model is based on the ODMG (Object Database Management Group) standard and supports many advanced features, including multiple inheritance. There are several ways to create, store, and manipulate objects in Health Connect databases:
InterSystems ObjectScript, the built-in Health Connect programming language, directly manipulates Health Connect objects. ObjectScript class definitions are often used as templates for creating objects, for example, patients, departments, or products. Classes can also be used to group related methods together, even if those methods are not directly associated with a user-defined object.
The XEP (Express Event Persistence) API for Java and XEP API for .Net provided by InterSystems enable Java and .NET applications to store and retrieve Health Connect objects by projecting them as persistent events, which are persistent database objects that store the state of the Java and .NET objects. Using the XEP APIs for object persistence lets you avoid the overheard of object-relational mapping.
The InterSystems Native API for Java and the InterSystems Native API for .NET are lightweight object interfaces to Health Connect for Java and .NET that make it possible for your Java or .NET application to work with Health Connect objects as easily as if they were native Java or .NET objects.
At the click of a button, Health Connect classes can be automatically enabled for XML or JSON. As a result, Health Connect objects are readily available to every commonly used object technology.