An API is a function of a software application (program) that can receive standardized requests for information or services and provide a response in a form that can be used or acted upon by the requesting program or application.
Clinical interfacing method whereby information resources and clinical resources are presented within the same interface. In addition, different groups have access to resource collections that are clustered by interest.
Information available from more than one source.
Clinical interfacing method whereby information resources and clinical resources are presented within the same user experience or interface.
Client-side clinical interfacing method whereby a common decision making context is shared among multiple disparate information resources, usually through application-to-application messaging.
Client-side clinical interfacing method whereby disparate information applications are able to talk to one another through some sort of application-to-application messaging protocol.
Clinical interfacing method whereby collections of resources are combined, clustered and customized to include external and internal evidence. In a customized environment, resources are linked to workflow.
Data conversion is about how health information is selected and managed for transfer from one health information system into another. Considerations include which information to transfer, how it should be transformed, how much to include, and how to make it accessible.
Client-side information exchanges occur when two or more information systems are open and in use by a 'client' decision-maker. For example, a physician may have an EMR open while an imaging system is open in a separate Internet browser on the same computer. If one application can generate an information request and that request results in an information display change in another application, then a client-side exchange has occurred.
Client-side messaging should adhere to information exchange standards. Examples include the Context Management Standard (CMS, previously CCOW), a sub-set of HL-7, and FHIR. These specify 'application-to-application' (A2A) messaging protocols.
Integration; Interfacing; Interoperation;
Health information is exchanged between data repositories without the necessary participation of end-users. The exchanges use "system-to-system" (S2S) security and messaging protocols, usually through batched data requests and responses expressed Health Language-7 (HL-7) syntax. Interoperation between two independent health information systems usually involves standards-based S2S exchange.
Integrated health information systems bring unite important functions under a common dataset and codes.
Integrate refers to the act of uniting separate systems, or replacing them with a new system, such that the result performs all the same functions within a single system and acts as a uniform entity.
Integration refers to the degree to which a system behaves as if all functions, data and interfaces behave as a cohesive, seamless, entity.
Integrated refers to a system that is or performs as if it is a seamlessly unified whole.
From Canada Health Infoway:
1: The process of bringing together related parts into a single system. To make various components function as a connected system. 2: Combining separately developed parts into a whole so that they work together. The means of integration may vary, from simply mating the parts together at an interface to radically altering the parts or providing something to mediate between them.
Interfacing relates to information exchange at the level of application or server codeset (e.g., instruments, mobile apps, inputs/outputs, Healthkit, etc.).
Interface refers to a part or function of one system that allows for exchange of information with another system.
Interface and Interfacing refer to the ability of one system to complement the functions of another system by consuming or providing information in order to perform or enhance a particular function.
Interoperation relates to standards-based information exchange between discrete systems at the level of datasets (e.g. health information exchange).
Interoperate refers to the act of data, function or service exchange between systems such that data and functions retain both meaning and effect without user intervention.
Interoperability refers to the ability of a system to effectively work with or use the data or functions of another system.
Loosely coupled application roles do not assume that common information about the subject classes participating in a message is available to system components outside of the specific message.
Exchange of information between two data collection points using a common messaging standard ("back end" integration). This transfer of information is transparent to the system user. The messaging capability between the systems is facilitated by network gateways that receive information requests and standardized message formats and perform the tasks necessary to effectively link heterogeneous systems used by various health service providers.
Tightly coupled application roles assume that common information about the subject classes participating in a message is available to system components outside of the specific message.