# US 2010/0145727 A1 · Interaction between healthcare software products

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0145727 A1
- Document ID: US20100145727A1
- Status: Published application
- Kind: A1
- Application number: 12/330,479
- Filed: 2008-12-08
- Published: 2010-06-10
- Earliest claimed: 2008-12-08
- Assignees: Microsoft Corporation
- Inventors: Keith Maurice Toussaint; Minakshi Krishna Velamoor; Kimberly Luu; Puneet Nagpal; John Arthur Hancock; Alex Byung-Hoon Yu
- Web page: https://patentgrep.com/patent/US20100145727A1

## CPC

- G06Q 10/00: Administration; Management
- G16H 10/60: for patient-specific data, e.g. for electronic patient records
- G16H 40/67: for remote operation
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

Patient records may be maintained in healthcare software systems, and two healthcare software systems may communicate to exchange information about a patient. In one example, one of the systems is a provider-oriented system used by a provider such as a hospital, doctor's office, etc., and the other system is a patient-oriented system that the patient uses to manage his or her healthcare records. The patient and the provider may exchange information to allow the systems to communicate with each other. The provider's system may then receive information from the patient's system. The data provided by the patient's system may be voluminous, and the provider's system may extract specific information from that data, and may place the extracted data in a flat data structure.

## Claims

### Claim 1

A first system that receives healthcare data, the first system comprising:
a processor;
a data remembrance component;
healthcare communication software that executes on said processor, that is stored in said data remembrance component, and that obtains, through a network, healthcare data from a second system, said healthcare data relating to a patient, said healthcare communication software obtaining said healthcare data by using a certificate and an application identifier that is exchanged in a setup process and that is recognized by said second system; and
an extraction component that extracts a subset of said healthcare data and that stores said subset in a database.

### Claim 2 (depends on 1)

The first system of claim 1, wherein said healthcare data relates to a human body of said patient.

### Claim 3 (depends on 1)

The first system of claim 1, wherein said healthcare data is in a first format, and wherein the first system further comprises:
a flattening component that stores said subset in a second format, said first format having a non-flat structure, said second format being one or more flat tables.

### Claim 4 (depends on 1)

The first system of claim 1, wherein said first system associates said patient with a code, wherein said patient provides said code to said second system, and wherein said healthcare data comprises, or is accompanied by, an identifier in said first system that said second system determines, through receipt of said code, is associated with said patient.

### Claim 5 (depends on 1)

The first system of claim 1, wherein said extraction component chooses said subset based on an assessment that has been made of a likelihood of said subset being subsequently accessed.

### Claim 6 (depends on 1)

The first system of claim 1, wherein said first system is extensible through a scripting capability, and wherein said extraction component is implemented as a script that has been added to said first system.

### Claim 7 (depends on 1)

The first system of claim 1, wherein said first system obtains said healthcare data from said second system on a schedule specified by said patient.

### Claim 8

A method of receiving healthcare data at a first system from a second system, the method comprising:
receiving a certificate and an application identifier that allows a healthcare provider to access an account at said second system that is maintained by a patient;
providing a code, which is received by said first system from said second system, and which is entered into said second system by said patient;
connecting to said second system using an application that identifies itself using said application identifier; and
obtaining said healthcare data from said second system at a timing based on parameters established by said healthcare provider and said patient.

### Claim 9 (depends on 8)

The method of claim 8, wherein said healthcare data comprises, or is obtained with, a patient identifier that said second system receives from said first system when a connection between said first system and said second system is requested, and wherein the method further comprises:
using said code to determine that said healthcare data relates to said patient.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
selecting a subset of said healthcare data, said subset being selected based on a predication of whether said subset is likely to be used in assessment of said patient or in presentation of information relating to said patient; and
storing said subset in a database.

### Claim 11 (depends on 8)

The method of claim 8, wherein said healthcare data is in a non-flat format, and wherein the method further comprises:
storing a subset of said data in a flat format.

### Claim 12 (depends on 8)

The method of claim 8, wherein said healthcare data is descriptive of a human body of said patient, or of a physical test or examination performed on said human body.

### Claim 13 (depends on 8)

The method of claim 8, further comprising:
receiving a script that selects a subset of said healthcare data or that converts said healthcare data from one form to another form.

### Claim 14 (depends on 8)

The method of claim 8, wherein said parameters specify a schedule on which said healthcare data is to be received, or specify an event that triggers obtaining of said healthcare information.

### Claim 15

One or more computer-readable storage media that store executable instructions that, when executed by a computer, cause the computer to perform a method of processing healthcare data, the method comprising:
obtaining the healthcare data from a system, the healthcare data being in a structured form, said healthcare data relating to a patient;
selecting a subset of said healthcare data based on a criterion, said subset being selected based on an assessment of a likelihood that said subset of said healthcare data will be used in presenting information relating to said patient or in analyzing of said patient;
creating a flat data structure that represents said subset; and
storing said flat data in a database.

### Claim 16 (depends on 15)

The one or more computer-readable storage media of claim 15, wherein said healthcare data is descriptive of a physical examination or a test performed on a human body of said patient.

### Claim 17 (depends on 15)

The one or more computer-readable storage media of claim 15, wherein the method further comprises:
providing a patient identifier which, after said providing, is received as part of, or with, said healthcare data.

### Claim 18 (depends on 17)

The one or more computer-readable storage media of claim 17, wherein an application that obtains said healthcare data from said system uses said code to identify said application to said system.

### Claim 19 (depends on 15)

The one or more computer-readable storage media of claim 15, wherein the method further comprises: configuring parameters governing when said healthcare data is to be obtained, said healthcare parameters specifying a schedule on which said healthcare data is to be communicated, or specifying an event upon which said healthcare data is to be communicated, or specifying that said healthcare information is to be submitted upon an entity's demand.

### Claim 20 (depends on 15)

The one or more computer-readable storage media of claim 15, wherein a script is used to select said subset, said script having been provided by a third-party source that is not a provider of said executable instructions.
