Abstract: Systems and methods that facilitate data retrieval in a stateless environment by limiting amount of retrievable data associated with a single client request. A retrieval limitation component partially satisfies a query and retrieves an initial batch of information. Moreover, identifications can further be designated to retrieve additional information if so is required. Accordingly, an application requesting data thru a query can initially be supplied with a limited number of data, which subsequently can be followed by additional data items returned as unique identifiers.

Abstract: An application program interface (API) is provided for requesting, storing, and otherwise accessing data within a health integration network. The API facilitates secure and seamless access to the centrally-stored data by offering authentication/authorization, as well as the ability to receive requests in an extensible language format, such as XML, and returns resulting data in XML format. The data can also have transformation, style and/or schema information associated with it which can be returned in the resulting XML and/or applied to the data beforehand by the API. The API can be utilized in many environment architectures including XML over HTTP and a software development kit (SDK).

Abstract: Systems and methods that facilitate data retrieval in a stateless environment by limiting amount of retrievable data associated with a single client request. A retrieval limitation component partially satisfies a query and retrieves an initial batch of information. Moreover, identifications can further be designated to retrieve additional information if so is required. Accordingly, an application requesting data thru a query can initially be supplied with a limited number of data, which subsequently can be followed by additional data items returned as unique identifiers.

Abstract: An authorization framework is provided that protects data records in a platform, such as a service-based platform, by requiring multiple level entities to be authorized with respect to the data records. For example, the data records can have an associated owner user that can grant access to other users with respect to the data. Additionally, however, the user can also grant access to certain applications that access the platform such that the data records can be initially closed for a user requiring the user to explicitly grant desired access to applications and/or users. In this regard, applications can be forbidden from accessing the data, even on behalf of the user, unless expressly authorized to do so by the user. Thus, the user can make informed decisions regarding who is to have access to its data.

Abstract: A protocol is provided for communicating data between two applications. The protocol can support communication of an extensible markup language (XML) document over hypertext transfer protocol (HTTP) by associating the XML document with a data envelope and sending the data envelope to a disparate application. The data envelope can comprise a header, which can specify supported compression methods, encryption keys, and/or data specific to the disparate application and/or the sending application. The protocol adds a layer of security to the communication and can prevent malicious requests and other attacks. This protocol can also be used in conjunction with a health integration network.

Abstract: An authentication mechanism is provided for a web method platform that allows homogeneous access for different types of clients according to a bootstrapping procedure utilized to establish the session. Different clients can be assigned different levels of trust based in part on the bootstrapping procedure and/or information provided during the procedure. The bootstrapping procedure can produce a token that is used by the clients in subsequent requests to provide previous authentication or state information to the platform. The token can comprise a shared secret used to ensure integrity of communications in some cases, and the token can be opaque to the client. Tokens can expire and require a client to re-bootstrap to provide higher levels of authentication protection, and tokens can be shared among a plurality of application servers to facilitate effective handling of requests in a farmed environment.

Abstract: The adaptation of at least a portion of an object provided by a previous script component to a subsequent script component, despite the subsequent component being incapable of recognizing a format of the at least a portion of the object as provided by the previous component. The previous component generates an object having a property. Adaptation script identifies adaptation(s) to perform on the property prior to being used by the subsequent component. The adaptation is performed, and the adapted property is then used by the subsequent component.

Abstract: Systems and methods that provides for an authorization agnostic access in web service environments to privileged information. A query component can specify how a call is to be made to a data store and predefines the data that is retrievable in response to a query defined thereby (e.g., thru HTTPS, Java script, and the like). The query component can employ a plurality of filters that are implemented as part thereof, to customize retrieval for a predetermined portion of the data for a designated period, and encompass an end-to-end scenario from the browser up to the storage.

Abstract: Systems and methods that facilitate data retrieval in a stateless environment by limiting amount of retrievable data associated with a single client request. A retrieval limitation component partially satisfies a query and retrieves an initial batch of information. Moreover, identifications can further be designated to retrieve additional information if so is required. Accordingly, an application requesting data thru a query can initially be supplied with a limited number of data, which subsequently can be followed by additional data items returned as unique identifiers.

Abstract: An authorization framework is provided that protects data records in a platform, such as a service-based platform, by requiring multiple level entities to be authorized with respect to the data records. For example, the data records can have an associated owner user that can grant access to other users with respect to the data. Additionally, however, the user can also grant access to certain applications that access the platform such that the data records can be initially closed for a user requiring the user to explicitly grant desired access to applications and/or users. In this regard, applications can be forbidden from accessing the data, even on behalf of the user, unless expressly authorized to do so by the user. Thus, the user can make informed decisions regarding who is to have access to its data.

Abstract: An authentication mechanism is provided for a web method platform that allows homogeneous access for different types of clients according to a bootstrapping procedure utilized to establish the session. Different clients can be assigned different levels of trust based in part on the bootstrapping procedure and/or information provided during the procedure. The bootstrapping procedure can produce a token that is used by the clients in subsequent requests to provide previous authentication or state information to the platform. The token can comprise a shared secret used to ensure integrity of communications in some cases, and the token can be opaque to the client. Tokens can expire and require a client to re-bootstrap to provide higher levels of authentication protection, and tokens can be shared among a plurality of application servers to facilitate effective handling of requests in a farmed environment.

Abstract: An application program interface (API) is provided for requesting, storing, and otherwise accessing data within a health integration network. The API facilitates secure and seamless access to the centrally-stored data by offering authentication/authorization, as well as the ability to receive requests in an extensible language format, such as XML, and returns resulting data in XML format. The data can also have transformation, style and/or schema information associated with it which can be returned in the resulting XML and/or applied to the data beforehand by the API. The API can be utilized in many environment architectures including XML over HTTP and a software development kit (SDK).

Abstract: A protocol is provided for communicating data between two applications. The protocol can support communication of an extensible markup language (XML) document over hypertext transfer protocol (HTTP) by associating the XML document with a data envelope and sending the data envelope to a disparate application. The data envelope can comprise a header, which can specify supported compression methods, encryption keys, and/or data specific to the disparate application and/or the sending application. The protocol adds a layer of security to the communication and can prevent malicious requests and other attacks. This protocol can also be used in conjunction with a health integration network.

Abstract: A user interface is provided for rendering platform data to an output device. The data is sent to the user interface from the protocol along with self-describing rendering information. This information can be in a transform format, such as extensible stylesheet language (XSL) and the like, and/or code-based language such as an object-oriented language, sequential language, hierarchical (such as XML) and the like. The user interface utilizes the self-describing rendering information (and/or a rendering method contained therein) to render the data to the output device. In this regard, the user interface is extensible by modifying the self-describing rendering information, which mitigates the need for additional development to the user interface when rendering methods change (for new field additions, cosmetic preferences, etc.).

Abstract: A platform for associating branding information with data is provided to allow a manufacturer of a data device, or other company, to be recognized for its data contribution to a centralized platform, for example. In this regard, companies have incentive to provide data services to users of the platform as the data can comprise branding information related to the company such as an advertisement, link to a main website or product specific websites, logo, additional data related to a request that is specific to the device, and/or additional data regarding users of similar devices. The branding information is rendered along with the data requested.

Abstract: A schema for storing health related data within a health integration network is provided to facilitate housing the data in a common and easy transformable and accessible manner. Utilizing this schema, disparate otherwise proprietary applications can store data formatted according to their own schema within the health integration network providing common accessibility to other applications. The other applications can request the commonly stored data from the health integration network to facilitate data transmission between the disparate applications.