To enable .NET developers to leverage the scalability, connectivity, and reliability of the HealthShare® Health Connect, Health Connect supports several types of connections to and from .NET applications.
Connect a .NET application to InterSystems IRIS
ADO.NET for relational access
ADO.NET is a data access technology from the Microsoft .NET Framework that enables programmers to access data sources in HealthShare® Health Connect with SQL in a standard, reliable way.
XEP API for high-speed object access
The XEP (Express Event Persistence) API provided by InterSystems enables .NET applications to store and retrieve objects from HealthShare® Health Connect. More specifically, XEP projects .NET objects as persistent events, which are persistent database objects that store the state of .NET objects.
XEP is optimized for applications that must handle high throughput, such as transaction processing applications. If you use XEP for object persistence, you can avoid the overheard of object-relational mapping.
Native API for direct access to data
The Native API for .NET provides direct access to globals, the tree-based sparse arrays that form the basis of the InterSystems multidimensional storage model and underlie the HealthShare® Health Connect object and SQL interfaces. The Native API exposes these native data structures, which provide very fast, flexible storage and retrieval. The Native API also enables your .NET application to work with Health Connect objects as easily as if they were native .NET objects, and includes the ability to call Health Connect class methods and routines.
Entity Framework for object-relational mapping
Entity Framework is a mapping tool that enables you to map .NET objects to relational tables in HealthShare® Health Connect and eliminates the need for most of the data-access code that developers must typically write.
Connect InterSystems IRIS to an external application
Using the Object Gateway for .NET (for instantiating and manipulating external .NET objects)
Using the InterSystems SQL Gateway (for connecting to external databases via ODBC)
Using the InterSystems ODBC Driver (for connecting to external ODBC data sources)