HEALTH INTEGRATION PLATFORM PROTOCOL

• US 20080101597A1
• Filed: 05/08/2007
• Published: 05/01/2008
• Est. Priority Date: 11/01/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Marcjan, Cezary, Nolan, Sean Patrick, Apacible, Johnson T., Jones, Jeffrey Dick
• Granted Patent: US 8,316,227 B2
• Time in Patent Office: Days
• US Class Current: 380/30
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC

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.

Claims

1. A protocol system that facilitates interpreting data from a remote application, comprising:

a receiving component that receives a portion of a first data envelope comprising a request for data access from an application; and

an analysis component that receives the portion of the first data envelope from the receiving component, determines at least one value relating to the request for data access, and leverages the application to determine a trust-level of the first data envelope based at least in part on the value relating to the request for data access.

2. The system of claim 1, the receiving component incrementally reads the first data envelope and rejects the first data envelope during the incremental read where the trust-level exceeds a threshold.

3. The system of claim 1, the receiving component returns an error data envelope comprising at least one error code where the first data envelope is entirely received and the trust-level exceeds a threshold.

4. The system of claim 1, the application is a health integration network comprising a plurality of data stores that respectively store health related data.

5. The system of claim 4, the trust-level is determined by utilizing the health integration network to evaluate an authorization corresponding to the value relating to the request for data access.

6. The system of claim 5, the value relating to the request for data access is an identifier of a record within the health integration network for which access is requested.

7. The system of claim 6, a user identifier is additionally read from the first data envelope and used in conjunction with the identifier of a record in evaluating the authorization to determine the trust-level.

8. The system of claim 1, further comprising a packaging component that receives response data based at least in part on the first data envelope and packages the response data in a second data envelope.

9. The system of claim 8, further comprising an encryption component that encrypts at least a portion of the second data envelope based on an encryption key specified in the first data envelope.

10. The system of claim 1, the first data envelope is received as an extensible markup language (XML) document over hypertext transfer protocol (HTTP).

11. A method that facilitates utilizing a protocol to send a data request to a remote application, comprising:

receiving a data request to be sent to a remote application;

packaging the data request within an outgoing data envelope as an extensible markup language (XML) document, the outgoing data envelope comprises at least one header;

specifying at least one supported compression method in the header; and

sending the outgoing data envelope to the remote application.

12. The method of claim 11, further comprising receiving a response data envelope from the remote application, the response data envelope is based at least in part on the outgoing data envelope.

13. The method of claim 12, further comprising decompressing at least a portion of the response data envelope based on the supported compression method.

14. The method of claim 11, further comprising specifying at least one public encryption key in the header.

15. The method of claim 14, further comprising receiving a response data envelope from the remote application and decrypting at least a portion of the response data envelope using a private decryption key that corresponds to the public encryption key.

16. The method of claim 11, the remote application is a health integration network comprising a plurality of databases that respectively store health related data.

17. The method of claim 16, the data request is for health related data stored as an XML document in the health integration network.

18. The method of claim 11, the outgoing envelope is sent to the remote application over a hypertext transfer protocol (HTTP) connection.

19. A system for utilizing a protocol to communicate with a remote application, comprising:

means for receiving an extensible markup language (XML) document representing a data envelope, the data envelope comprises a header and a request for data;

means for storing at least one compression method specified in the header; and

means for extracting the request for data from the data envelope and forwarding the request to an underlying application.

20. The system of claim 19, further comprising:

means for packaging a result in a return data envelope, the result based at least in part on the request for data;

means for compressing the result based on the compression method; and

means for sending the return data envelope to a requesting entity.