Method and apparatus for operative event documentation and related data management

• US 8,185,409 B2
• Filed: 01/30/2008
• Issued: 05/22/2012
• Est. Priority Date: 11/29/2001
• Status: Active Grant

• Current Assignee: Integration Management, Inc. (Centauri Health Solutions, Inc.)
• Original Assignee: Boundarymedical Incorporated (Centauri Health Solutions, Inc.)
• Inventors: Putnam, Matt D., Smith, Mark G.
• Primary Examiner(s): Najarian, Lena
• Application Number:
  US12/022,719
• Publication Number:
  US 20080221922A1
• Time in Patent Office: 1,574 Days
• Field of Search: 705/2, 705/3, 705/4, 600/300
• US Class Current: 705/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/08 Insurance
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS

Abstract

In one embodiment, method and apparatus are disclosed which provide that a plurality of physicians each enter operative event data into an operative event database, wherein the operative event data documents planned or completed operative events and the physicians enter the operative event data use a wide area network through a user interface assisting the physicians in coding operative events in a consistent manner. The physicians access the operative event database to obtain information concerning upcoming or previously performed operative events, with a service provider maintaining an on-line system including one or more servers to support the entering of operative event data into the database through the Internet and the user interface. Further, the physicians subscribe to the on-line system wherein the physicians are allowed access and use the on-line system, and wherein the physicians retain control over the use and disposition of the operative event data entered by the physician.

Claims

1. A method comprising:

accessing an operative event database that stores coded operative events, each coded operative event being cross-referenced to a region of an anatomy in the operative event database;

accessing a profile of a subscriber physician, the profile identifying a specialty of the subscriber physician;

providing a user interface comprising a graphical rendering of the anatomy;

detecting a selection of a particular region of the anatomy, the selection being made using the user interface;

retrieving, from the operative event database, a listing of coded operative events that are cross-referenced to the selected, particular region of the anatomy and are related to the specialty of the subscriber physician;

detecting an additional selection of a coded operative event from the listing, the additional selection being made using the user interface;

receiving patient outcome data associated with an operative event, the patient outcome data being entered through the user interface;

correlating the patient outcome data with the coded operative event, the coded operative event being associated with the operative event, the correlating defining a correlation of the patient outcome data with the coded operative event;

storing the patient outcome data and the correlation into the operative event database, the operative event database being included in an on-line system maintained by an application service provider, the application service provider maintaining an integrity of the patient outcome data, the operative event database being configured to further store a plurality of operative event data associated with a plurality of operative events performed at a plurality of organizations; and

making a summary of the plurality of operative event data and a plurality of associated patient outcome data for the subscriber physician accessible to a potential patient.

2. The method of claim 1, wherein the user interface is based on a predefined template.

3. The method of claim 2, wherein the predefined template configures the user interface in a particular language.

4. The method of claim 2, wherein the predefined template configures the user interface to provide a surgical plan.

5. The method of claim 2, wherein the predefined template is modifiable by a user.

6. The method of claim 1, further comprising making one or more of the patient outcome data or the plurality of operative event data accessible to the plurality of organizations.

7. A method comprising:

accessing an operative event database that stores coded operative events, each coded operative event being cross-referenced to a region of an anatomy in the operative event database;

accessing a profile of a subscriber physician, the profile identifying a specialty of the subscriber physician;

providing a user interface comprising a graphical rendering of the anatomy;

detecting a selection of a particular region of the anatomy, the selection being made using the user interface;

retrieving, from the operative event database, a listing of coded operative events that are cross-referenced to the selected, particular region of the anatomy and are related to the specialty of the subscriber physician;

detecting an additional selection of a coded operative event from the listing, the additional selection being made using the user interface;

receiving patient outcome data that is correlated with the coded operative event, wherein the patient outcome data, the coded operative event, and a correlation of the patient outcome data with the coded operative event being entered through the user interface;

storing the patient outcome data and the coded operative event into the operative event database, the operative event database being included in an on-line system maintained by an application service provider, the application service provider maintaining an integrity of the patient outcome data, the operative event database being configured to further store a plurality of operative event data associated with a plurality of operative events performed at a plurality of organizations; and

making a summary of the plurality of operative event data and a plurality of associated patient outcome data for a subscriber physician accessible to a potential patient,

wherein the user interface is based on a predefined template.

8. The method of claim 7, wherein the patient outcome data is associated with an operative event from the plurality of operative events.

9. The method of claim 7, wherein the coded operative event is one or more of a CPT code or an ICD9 code.

10. An on-line system, comprising:

an operative event database configured to store a plurality of operative event data associated with a plurality of operative events performed by a plurality of organizations and configured to store a plurality of coded operative events, each coded operative event being cross-referenced to a region of an anatomy in the operative event database; and

a hardware-implemented satisfaction data input module operatively associated with the operative event database, the satisfaction data module to;

access a profile of a subscriber physician, the profile identifying a specialty of the subscriber physician;

provide a user interface comprising a graphical rendering of the anatomy;

detect a selection of a particular region of the anatomy, the selection being made using the user interface;

retrieve, from the operative event database, a listing of coded operative events that are cross-referenced to the selected, particular region of the anatomy and are related to the specialty of the subscriber physician;

detect an additional selection of a coded operative event from the listing, the additional selection being made using the user interface;

receive patient outcome data associated with an operative event, the patient outcome data being entered through the user interface;

correlate the patient outcome data with the coded operative event, the coded operative event being associated with the operative event; and

make a summary of the plurality of operative event data and a plurality of associated patient outcome data for a subscriber physician accessible to a potential patient.

11. The on-line system of claim 10, wherein the operative event database and the satisfaction data input module are included in an on-line system maintained by an application service provider, the application service provider maintaining an integrity of the patient outcome data.

12. The on-line system of claim 10, further comprising a system database configured to store a predefined template.

13. The on-line system of claim 12, wherein the predefined template configures the user interface to provide a surgical plan.

14. The on-line system of claim 12, wherein the predefined template configures the user interface in a particular language.