Abstract: Capturing dependencies between variables using a variable agnostic object is disclosed. A system is configured to obtain an indication of a first dependency of a first variable to a second variable via a programming interface and depict the first dependency, the first variable, and the second variable in a first instance of a variable agnostic object in a source code. The system is also configured to obtain an indication of a second dependency of a third variable to a fourth variable via the programming interface and depict the second dependency, the third variable, and the fourth variable in a second instance of the variable agnostic object in the source code. The system is also configured to compile the source code to generate a computer-executable program capturing the first dependency and the second dependency based on the first instance and the second instance of the variable agnostic object.

Abstract: Capturing dependencies between variables using a variable agnostic object is disclosed. A system is configured to obtain an indication of a first dependency of a first variable to a second variable via a programming interface and depict the first dependency, the first variable, and the second variable in a first instance of a variable agnostic object in a source code. The system is also configured to obtain an indication of a second dependency of a third variable to a fourth variable via the programming interface and depict the second dependency, the third variable, and the fourth variable in a second instance of the variable agnostic object in the source code. The system is also configured to compile the source code to generate a computer-executable program capturing the first dependency and the second dependency based on the first instance and the second instance of the variable agnostic object.

Abstract: Embodiments presented herein provide techniques for rendering user-interface elements for an entity type based on a variation metamodel received in response to an API request. When a user invokes a function to access or create an entity, a user interface sends the API request to an API service. The API request identifies the entity type and is associated with context information about the user. The variation metamodel is selected by the API service based on the context information. The user interface receives and parses a response from the API service. The meta model includes metadata describing at least one aspect of a corresponding property of the entity type. Using the metadata as a guide, the user interface renders elements for the properties of the variation schema in a graphical user interface (GUI).

Abstract: The present disclosure relates to accessing data using application programming interface (API) calls. According to one embodiment, a method generally includes receiving, at the API, a request from a client device, where the requesting a data operation. Determining context data associated with the request. Receiving an entity schema based on the context data, where the entity schema includes a metamodel. Processing the request using the entity schema and metamodel, generating a response including the entity schema, and returning the response to the client device.

Abstract: The present disclosure relates to providing a developer experience relevant to a variation of an application programming interface (API). In some embodiments, a request is received from a developer for developer experience information. In certain embodiments, an API variation that is relevant to the developer is identified based on the request. In some embodiments, a custom developer experience is selected based on the API variation. The custom developer experience may comprise developer experience information specific to the API variation.

Abstract: The present disclosure relates to managing variability in an application programming interface (API). According to one embodiment, a method generally includes receiving, from a user, a definition of a variability schema and context information associated with the variability schema. The variability schema generally represents a variation of one or more properties defined in an application programming interface (API). A computing system links the variation and context information to the one or more properties defined in the API. The computing system receives a query to perform one or more actions using the one or more properties, matches context information associated with the query to the context information associated with the variability schema, and processes the query using the variation of the one or more properties.

Abstract: Embodiments presented herein provide techniques for rendering user-interface elements for an entity type based on a variation metamodel received in response to an API request. When a user invokes a function to access or create an entity, a user interface sends the API request to an API service. The API request identifies the entity type and is associated with context information about the user. The variation metamodel is selected by the API service based on the context information. The user interface receives and parses a response from the API service. The meta model includes metadata describing at least one aspect of a corresponding property of the entity type. Using the metadata as a guide, the user interface renders elements for the properties of the variation schema in a graphical user interface (GUI).

Abstract: The present disclosure relates to accessing data using application programming interface (API) calls. According to one embodiment, a method generally includes receiving, at the API, a request from a client device, where the requesting a data operation. Determining context data associated with the request. Receiving an entity schema based on the context data, where the entity schema includes a metamodel. Processing the request using the entity schema and metamodel, generating a response including the entity schema, and returning the response to the client device.

Abstract: A tool or computer-readable medium for interfacing with an infusion pump includes i) computer-readable code for generating a drug library, generating a run profile, or a combination thereof, and ii) computer-readable code for configuring the infusion pump.

Abstract: A tool or computer-readable medium for interfacing with an infusion pump includes i) computer-readable code for generating a drug library, generating a run profile, or a combination thereof, and ii) computer-readable code for configuring the infusion pump.