Data acquisition system

• US 20060080343A1
• Filed: 10/06/2005
• Published: 04/13/2006
• Est. Priority Date: 10/08/2004
• Status: Abandoned Application

• Current Assignee: Draeger Medical Systems Incorporated (FPS Vermögensverwaltung GmbH)
• Original Assignee: Draeger Medical Systems Incorporated (FPS Vermögensverwaltung GmbH)
• Inventors: Rutledge, Jolyn, Penny, Mark, Carter, Linda, Shaffer, Judith A., Xu, Shuyi, Manetta, Amy
• Application Number:
  US11/244,874
• Publication Number:
  US 20060080343A1
• Time in Patent Office: Days
• US Class Current: 1/1
• 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
• CPC Class Codes: G16H 40/63 for local operation

Abstract

A system for acquiring and providing data relating to an entity to a user provides for specification of a user defined time “keeper” or anchor for navigation through an electronic data storage system such that the data displayed from screen to screen is kept in the same time context without requiring user scrolling or multiple mouse clicks. Such a system includes at least one repository of entity related data and information indicating an index associated with the entity related data. A source of configuration data identifies a particular index value for the entity. An acquisition processor accesses the repository to acquire entity related data associated with the particular index value in response to a user command to access entity related data.

Claims

1. A system for acquiring and providing data relating to an entity to a user, comprising:

at least one repository of entity related data together with information representing an index associated with acquisition of said entity related data;

a source of configuration data identifying a particular value for said index; and

an acquisition processor for accessing said at least one repository to acquire entity related data associated with said particular index value in response to a user command to access entity related data.

2. A system according to claim 1, wherein:

said particular index value demarcates an end point; and

said acquisition processor acquires entity related data preceding said particular index value.

3. A system according to claim 1, wherein:

said particular index value demarcates a start point; and

said acquisition processor acquires entity related data following said particular index value.

4. A system according to claim 1, wherein:

said particular index value demarcates a center point; and

said acquisition processor acquires entity related data preceding and following said particular index value.

5. A system according to claim 1, wherein:

said particular index value comprises an index range; and

said acquisition processor acquires entity related data in said index value range.

6. A system according to claim 1, further comprising a display processor for providing data representing a displayed image including said acquired entity related data associated with said particular index value, for presentation to a user.

7. A system according to claim 6, wherein said acquired entity related data is displayed at least one of, (a) to the left, (b) at the center and (c) to the right of said particular index value.

8. A system according to claim 6, wherein said acquired entity related data is displayed at least one of, (a) to the top, (b) at the center and (c) to the bottom of said particular index value.

9. A system according to claim 1, wherein said acquisition processor limits the quantity of said acquired entity related data retrieved from said at least one repository in response to a determined available scrollable image size used for displaying said acquired entity related data to a user.

10. A system according to claim 1, further comprising:

a user interface processor for receiving a user command to access a particular type of entity related data; and

said acquisition processor accesses said at least one repository to acquire entity related data of said particular type.

11. A system according to claim 1, further comprising:

a user interface processor for receiving a user command to access data related to a particular entity related data; and

said acquisition processor accesses said at least one repository to acquire data related to said particular entity.

12. A system according to claim 1, further comprising:

a user interface processor for receiving a user command to access data of a particular type related to a particular entity; and

said acquisition processor accesses said at least one repository to acquire entity related data of said particular type for said particular entity.

13. A system for acquiring and providing particular patient medical record data to a user, comprising:

at least one repository of patient medical record data together with information representing a time associated with acquisition of said medical record data;

a source of configuration data identifying a particular time for a particular patient; and

an acquisition processor for accessing said at least one repository to acquire patient medical record data associated with said particular time in response to user command to access medical record data of said particular patient.

14. A system according to claim 13, wherein:

said time associated with acquisition of said medical record data comprises a date;

said particular time for a particular patient comprises a date; and

said acquisition processor acquires patient medical record data associated with a particular date in response to said user command to access medical record data of said particular patient.

15. A system according to claim 13, wherein:

said particular time demarcates an end time; and

said acquisition processor acquires patient medical record data preceding said particular time.

16. A system according to claim 13, wherein:

said particular time demarcates a start time; and

said acquisition processor acquires patient medical record data occurring after said particular time.

17. A system according to claim 13, wherein:

said particular time demarcates a center time; and

said acquisition processor acquires patient medical record data preceding and following said particular time.

18. A system according to claim 13, wherein:

said particular time comprises a time range; and

said acquisition processor acquires patient medical record data in said time range.

19. A system according to claim 13, further comprising a display processor for providing data representing a displayed image including said acquired patient medical record data associated with said particular time, for presentation to a user.

20. A system according to claim 19, wherein said acquired patient medical record data is displayed at least one of, (a) to the left, (b) at the center and (c) to the right of said particular time.

21. A system according to claim 19, wherein said acquired patient medical record data is displayed at least one of, (a) to the top, (b) at the center and (c) to the bottom of said particular time.

22. A system according to claim 13, wherein said acquisition processor limits the quantity of said acquired patient medical record data retrieved from said at least one repository in response to a determined available scrollable image size used for displaying said acquired patient medical record data to a user.

23. A system according to claim 13, further comprising:

a user interface processor for receiving a user command to access a particular type of patient data of said particular patient; and

said acquisition processor accesses said at least one repository to acquire patient medical record data of said particular type.

24. A system according to claim 13, wherein said particular type of patient data is selected from a plurality of different types of patient data associated with a corresponding plurality of images navigable by said user.

25. A system according to claim 24, wherein said plurality of different types of patient data comprise two or more of, (a) blood pressure parameters, (b) ventilation parameters, (c) vital sign parameters, (d) blood oxygen concentration representative parameters and (e) infusion pump parameters associated with fluid delivery.

26. A system according to claim 13, wherein said particular type of patient data is selected from a plurality of different types of patient data associated with a corresponding plurality of portions of a single image, said user command to access said particular type of patient data being received in response to user selection of a displayed image element associated with a corresponding type of patient data in said single image.

27. A system according to claim 13, further comprising a communication processor for communicating data identifying said particular time to a second different executable application for use by said second different executable application in initiating acquisition of patient medical record data associated with said particular time in response to a user command to access medical record data of said particular patient received via user selection of an image element in an image display associated with said second different executable application.

28. A system supporting navigability and interoperability between different executable applications, comprising:

at least one repository including a plurality of different types of data together with information representing a time associated with data within a particular type, said plurality of different types of data being associated with a plurality of different entities;

first and second different executable applications having access to configuration data identifying a particular time associated with a particular type of data and a particular entity; and

said first and second different executable applications access said at least one repository to acquire a particular type of data associated with said particular time in response to user command to access a particular type of data associated with a particular entity.

29. A system according to claim 28, wherein said first and second different executable applications access said at least one repository to acquire a particular type of data associated with said particular time in response to user commands received via user selection of image elements in image displays associated with said first and second different executable applications, providing presentation of data in a consistent time portion upon navigation between images associated with different executable applications.

30. A method for acquiring and providing entity related data to a user, comprising the activities of:

storing, in at least one repository, entity related data together with information representing an index value associated with acquisition of said entity related data;

receiving user entered configuration data identifying a particular index value; and

accessing said at least one repository to acquire entity related data associated with said particular index value in response to user command to access entity related data.

31. An electronic data storage medium incorporating machine readable instructions for performing the activities of claim 30.

32. A method for acquiring and providing particular patient medical record data to a user, comprising the activities of:

storing, in at least one repository, patient medical record data together with information representing a time associated with acquisition of said medical record data;

receiving user entered configuration data identifying a particular time for a particular patient; and

accessing said at least one repository to acquire patient medical record data associated with said particular time in response to user command to access medical record data of said particular patient.

33. An electronic data storage medium incorporating machine readable instructions for performing the activities of claim 32.