CONTROLLED USE MEDICAL APPLICATON

• US 20110191767A1
• Filed: 01/29/2010
• Published: 08/04/2011
• Est. Priority Date: 01/29/2010
• Status: Active Grant

• Current Assignee: Schwegman Lundberg & Woessner PA
• Original Assignee: Open Imaging, Inc.
• Inventors: Chen, Gen-nan, Pinsky, Howard, Swartz, Stephen J., Halpern, Daniel A., Henson, Trent W.
• Granted Patent: US 8,893,120 B2
• Time in Patent Office: Days
• US Class Current: 717/176
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

In an example, a virtualized medical application container can be created, including creating an image of a clean version of an operating system, installing a medical application on the image, and initializing the medical application on the image.

Claims

1. A system comprising:

one or more processors; and

a memory including instructions that, when executed by the one or more processors, causes the one or more processors to;

create a virtualized medical application container, including to;

create an image of a clean version of an operating system;

install a medical application on the image; and

initialize the medical application on the image.

2. The system of claim 1, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to create the virtualized medical application container include instructions to:

configure the medical application to communicate with a client application on a client operating system.

3. The system of claim 1, wherein the instructions that, when executed by the one or more processors, causes the one or more processors to initialize the medical application include instructions to:

restrict access of the medical application to a network interface of the client operating system.

4. The system of claim 1, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to create the image of the clean version of the operating system include instructions to:

create the operating system file system, virtual memory and cache space, kernel drivers, and bootstrap binaries.

5. The system of claim 1, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to install the medical application on the image include instructions to:

install no other software on the image.

6. The system of claim 1, wherein the memory includes instructions that, when executed by the one or more processors, cause the one or more processors to:

create a copy of the virtualized medical application container; and

store the copy of the virtualized medical application container on at least one of the one or more servers.

7. The system of claim 1, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to install the medical application on the image include instructions to:

install a third-party medical application executable, library, configuration file, and database management product.

8. The system of claim 1, wherein the memory includes instructions that, when executed by the one or more processors, cause the one or more processors to store product information about the medical application on one or more servers, wherein the product information includes at least one of a medical application name, a category, a manufacturer, a price per defined measured use, food and drug administration (FDA) clearance information, a user comment, or a user rating.

9. A machine-readable medium containing instructions that, when executed by one or more processors, cause the one or more processors to:

create a virtualized medical application container, including to;

create an image of a clean version of an operating system;

install a medical application on the image; and

initialize the medical application on the image.

10. The machine-readable medium of claim 9, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to create the virtualized medical application container include instructions to:

configure the medical application to communicate with a client application on a client operating system.

11. The machine-readable medium of claim 9, wherein the instructions that, when executed by the one or more processors, causes the one or more processors to initialize the medical application include instructions to:

restrict access of the medical application to a network interface of the client operating system.

12. The machine-readable medium of claim 9, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to create the image of the clean version of the operating system include instructions to:

create the operating system file system, virtual memory and cache space, kernel drivers, and bootstrap binaries.

13. The machine-readable medium of claim 9, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to install the medical application on the image include instructions to:

install no other software on the image.

14. The machine-readable medium of claim 9 containing instructions that, when executed by the one or more processors, cause the one or more processors to:

create a copy of the virtualized medical application container; and

store the copy of the virtualized medical application container on at least one of the one or more servers.

15. The machine-readable medium of claim 9, wherein the instructions that, when executed by the one or more processors, cause the one or more processors to install the medical application on the image include instructions to:

install a third-party medical application executable, library, configuration file, and database management product.

16. The machine-readable medium of claim 9 containing instructions that, when executed by the one or more processors, cause the one or more processors to store product information about the medical application on one or more servers, wherein the product information includes at least one of a medical application name, a category, a manufacturer, a price per defined measured use, food and drug administration (FDA) clearance information, a user comment, or a user rating.

17. A method comprising:

creating a virtualized medical application container, including;

creating an image of a clean version of an operating system;

installing a medical application on the image; and

initializing the medical application on the image.

18. The method of claim 17, wherein the creating the virtualized medical application container includes:

configuring the medical application to communicate with a client application on a client operating system.

19. The method of claim 17, wherein the initializing the medical application includes:

restricting access of the medical application to a network interface of the client operating system.

20. The method of claim 17, wherein the creating the image of the clean version of the operating system includes:

creating the operating system file system, virtual memory and cache space, kernel drivers, and bootstrap binaries.

21. The method of claim 17, wherein the installing the medical application on the image includes:

installing no other software on the image.

22. The method of claim 17, including:

creating a copy of the virtualized medical application container; and

storing the copy of the virtualized medical application container on at least one of the one or more servers.

23. The method of claim 17, wherein the installing the medical application on the image includes:

installing a third-party medical application executable, library, configuration file, and database management product.

24. The method of claim 17, including:

storing product information about the medical application on one or more servers, wherein the product information includes at least one of a medical application name, a category, a manufacturer, a price per defined measured use, food and drug administration (FDA) clearance information, a user comment, or a user rating.