METHODS, COMPUTER PROGRAM PRODUCTS, APPARATUSES, AND SYSTEMS FOR INTERACTING WITH MEDICAL DATA OBJECTS

• US 20090132285A1
• Filed: 10/31/2008
• Published: 05/21/2009
• Est. Priority Date: 10/31/2007
• Status: Abandoned Application

• Current Assignee: Mckesson Technologies Incorporated (UnitedHealth Group Incorporated)
• Original Assignee: McKesson Information Solutions LLC (McKesson Corp.)
• Inventors: Jakobovits, Rex
• Application Number:
  US12/262,714
• Publication Number:
  US 20090132285A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A method, apparatus, and computer program product are provided for interacting with medical data objects. An apparatus may include a processor configured to map a DICOM object comprising medical data content to a hierarchy of one or more containers. The processor may be further configured to provide a user interface allowing a user to view a representation of the hierarchy and access the medical data content of the one or more containers. The processor may additionally be configured to receive data that a user has added to a container. The processor may also be configured to associate the received data with the DICOM object based at least in part upon the container to which the received data was added. Corresponding methods and computer program products are also provided.

Claims

1. A method comprising:

mapping a Digital Imaging and Communications in Medicine (DICOM) object comprising medical data content to a hierarchy of one or more containers, wherein each container comprises a subset of the medical data content of the DICOM object; and

providing a user interface allowing a user to view a representation of the hierarchy and access the medical data content of the one or more containers.

2. A method according to claim 1, wherein providing a user interface comprises providing a user interface allowing the user to add data to a container;

and further comprising;

receiving data that a user has added to a container; and

associating the received data with the DICOM object based at least in part upon the container to which the received data was added.

3. A method according to claim 2, wherein:

receiving data comprises receiving data not formatted in conformance with DICOM standards; and

associating the received data with the DICOM object comprises;

modifying the received data so that it is compatible with the DICOM object; and

adding the modified received data to the DICOM object based at least in part upon the container to which the received data was added.

4. A method according to claim 1, wherein providing a user interface comprises providing a user interface allowing a user to view the hierarchy of containers as a hierarchy of folders and providing a graphical drag and drop interface allowing a user to add data to a folder.

5. A method according to claim 1, wherein mapping a DICOM object comprises:

determining access permissions defined by the DICOM object for one or more subsets of the medical data content of the DICOM object; and

associating a determined access permission with a container based at least in part upon the subset of the medical data content included in the container.

6. A method according to claim 5, further comprising:

receiving a request from a user to access medical data content of a container;

determining an identity of the user;

determining access permissions associated with the container;

determining whether the user has permission to access the medical data content of the container based at least in part upon the determined identity and the determined access permissions;

providing the user access to the requested medical data content if the user has permission to access the medical data content; and

denying the user request if the user does not have permission to access the requested medical data content.

7. A method according to claim 1, wherein the DICOM object is a patient object comprising one or more exam objects;

and

wherein mapping the DICOM object comprises mapping medical data content of each exam object to a separate container.

8. A method according to claim 1, wherein the DICOM object is an exam object comprising one or more series objects;

and

wherein mapping the DICOM object comprises mapping medical data content of each series object to a separate container.

9. A computer program product comprising at least one computer-readable storage medium having computer-readable program instructions stored therein, the computer-readable program instructions comprising:

a program instruction for mapping a Digital Imaging and Communications in Medicine (DICOM) object comprising medical data content to a hierarchy of one or more containers, wherein each container comprises a subset of the medical data content of the DICOM object; and

a program instruction for providing a user interface allowing a user to view a representation of the hierarchy and access the medical data content of the one or more containers.

10. A computer program product according to claim 9, wherein the program instruction for providing a user interface comprises instructions for providing a user interface allowing the user to add data to a container;

and further comprising;

a program instruction for receiving data that a user has added to a container; and

a program instruction for associating the received data with the DICOM object based at least in part upon the container to which the received data was added.

11. A computer program product according to claim 10, wherein:

the program instruction for receiving data comprises instructions for receiving data not formatted in conformance with DICOM standards; and

the program instruction for associating the received data with the DICOM object comprises;

a program instruction for modifying the received data so that it is compatible with the DICOM object; and

a program instruction for adding the modified received data to the DICOM object based at least in part upon the container to which the received data was added.

12. A computer program product according to claim 9, wherein the program instruction for providing a user interface comprises instructions for providing a user interface allowing a user to view the hierarchy of containers as a hierarchy of folders and providing a graphical drag and drop interface allowing a user to add data to a folder.

13. A computer program product according to claim 9, wherein the program instruction for mapping a DICOM object comprises:

a program instruction for determining access permissions defined by the DICOM object for one or more subsets of the medical data content of the DICOM object; and

a program instruction for associating a determined access permission with a container based at least in part upon the subset of the medical data content included in the container.

14. A computer program product according to claim 13, further comprising:

a program instruction for receiving a request from a user to access medical data content of a container;

a program instruction for determining an identity of the user;

a program instruction for determining access permissions associated with the container;

a program instruction for determining whether the user has permission to access the medical data content of the container based at least in part upon the determined identity and the determined access permissions;

a program instruction for providing the user access to the requested medical data content if the user has permission to access the medical data content; and

a program instruction for denying the user request if the user does not have permission to access the requested medical data content.

15. An apparatus comprising a processor configured to:

map a Digital Imaging and Communications in Medicine (DICOM) object comprising medical data content to a hierarchy of one or more containers, wherein each container comprises a subset of the medical data content of the DICOM object; and

provide a user interface allowing a user to view a representation of the hierarchy and access the medical data content of the one or more containers.

16. An apparatus according to claim 15, wherein the processor is configured to provide a user interface by providing a user interface allowing the user to add data to a container;

and wherein the processor is further configured to;

receive data that a user has added to a container; and

associate the received data with the DICOM object based at least in part upon the container to which the received data was added.

17. An apparatus according to claim 16, wherein the processor is configured to receive data by receiving data not formatted in conformance with DICOM standards;

and

associate the received data with the DICOM object by;

modifying the received data so that it is compatible with the DICOM object; and

adding the modified received data to the DICOM object based at least in part upon the container to which the received data was added.

18. An apparatus according to claim 15, wherein the processor is configured to provide a user interface by providing a user interface allowing a user to view the hierarchy of containers as a hierarchy of folders and providing a graphical drag and drop interface allowing a user to add data to a folder.

19. An apparatus according to claim 15 wherein the processor is configured to map a DICOM object by:

determining access permissions defined by the DICOM object for one or more subsets of the medical data content of the DICOM object; and

associating a determined access permission with a container based at least in part upon the subset of the medical data content included in the container.

20. An apparatus according to claim 19, wherein the processor is further configured to:

receive a request from a user to access medical data content of a container;

determine an identity of the user;

determine access permissions associated with the container;

determine whether the user has permission to access the medical data content of the container based at least in part upon the determined identity and the determined access permissions;

provide the user access to the requested medical data content if the user has permission to access the medical data content; and

deny the user request if the user does not have permission to access the requested medical data content.