Providing a number of web services for imaging optional medical applications

• US 8,380,809 B2
• Filed: 03/05/2009
• Issued: 02/19/2013
• Est. Priority Date: 03/05/2009
• Status: Active Grant

• Current Assignee: Siemens Healthineers AG (Siemens AG)
• Original Assignee: Siemens AG
• Inventors: Becker, Detlef, Dominick, Lutz, Dorn, Karlheinz, Hewett, Andrew John, Pusztai, Artur, Sinha, Subrata, Ukis, Vladyslav
• Primary Examiner(s): RECEK, JASON D
• Application Number:
  US12/379,979
• Publication Number:
  US 20100229153A1
• Time in Patent Office: 1,447 Days
• Field of Search: 709/203, 709217-218, 717/107
• US Class Current: 709/217
• CPC Class Codes: G06F 16/9038 Presentation of query results
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS
• CPC Class Codes: G16H 30/40 for processing medical images, e.g. editing

Abstract

A system and a computer-implemented method are disclosed, as well as a computer readable medium, for providing a number of web services for at least one medical viewing application, so as to provide the application with application-exceeding basic functionalities with regard to a transfer management service, a data management service, a workflow management service, a report management service, a protocol management service, an operating management service and an enterprise application integration management service. A web service of at least one embodiment, in that case, includes at least one remote service component, at least one business object and at least one service component.

Claims

1. A computer-implemented system for providing a number of web services for at least one medical application in the field of image-processing medical technology, so as to make available all-encompassing basic functionalities to the medical applications, the system comprising:

a processor; and

a memory, wherein one web service is configured to implement at least one basic functionality, all web services are respectively configured substantially identically, and all web services include;

at least one remote service component, to allow respectively one application to access at least one web service;

at least one business object component, in which the respective basic functionality is implemented, useable by a remote service component; and

at least one service component, which makes available different basic functionalities and which is useable by a remote service component,

wherein the basic functionalities are selectable from a number of functionalities including transfer management, data management, workflow management, report management, protocol management, operating management and enterprise application integration management.

2. The system according to claim 1, wherein the application is a medical viewing application and the basic functionality made available by the web service covers all functionalities of the viewing application.

3. The system according to claim 1, wherein the web service is accessible by the application, directly or indirectly via a framework.

4. The system according to claim 1, wherein the web services are realizable in at least one of a development environment for the one application and a runtime environment for the one application.

5. The system according to claim 1, wherein the web services provided to the application are addressed in a programming language-independent and platform-independent description language.

6. The system according to claim 5, wherein the programming language-independent and platform-independent description language is WSDL.

7. The system according to claim 1, wherein the system is based on a programming language-independent, platform-independent and protocol-independent architecture.

8. The system according to claim 1, wherein

at least two remote service components are provided,

the at least two remote service components are configured uniformly, and

the at least two remote service components are based on a same configuration diagram.

9. The system according to claim 8, wherein the remote service components are further configured for different web services.

10. The system according to claim 1, wherein a first web service is replaceable by a second web service without having to change the application, which uses the first or second web service.

11. The system according to claim 1, wherein the transfer management service implements basic functionalities for the transfer of DICOM image sets.

12. The system according to claim 1, wherein the transfer management service includes two remote service components including a media access component to provide information on available storage media on a computer and their characteristics, and a network-listener component to monitor a port on a machine for the data transfer and, if necessary, automatically initiate additional processing.

13. The system according to claim 1, wherein the data management service implements basic functionalities for accessing data.

14. The system according to claim 13, wherein the data management service implements basic functionalities for accessing DICOM image data sets.

15. The system according to claim 1, wherein the access to the data management service is at least one of a write and read access.

16. The system according to claim 1, wherein the data management service includes two remote service components including a data management component to implement access to an index repository for DICOM data, and a file access component to implement access to a file system of a computer that is not integrated into a network.

17. The system according to claim 1, wherein the workflow management service is configured to control an interaction between different medical applications.

18. The system according to claim 1, wherein the workflow management service includes two remote service components including a workflow component to generate clinical procedures within a framework of work lists, to coordinate the clinical procedures with respective required applications, to automatically start the required applications, and to create a link between data and applications, and an information component to administer at least one of patient data and performed procedure steps.

19. The system according to claim 1, wherein the report management service implements the basic functionality for combining application-specific partial reports into a uniform medical report.

20. The system according to claim 1, wherein the report management service includes a remote service component including a common reporting data component to transfer individual partial reports to a joint data model and to consolidate the data to prepare one report.

21. The system according to claim 1, wherein the protocol management service implements the basic functionality for administering and distributing protocols within a framework of image data acquisition.

22. The system according to claim 1, wherein the protocol management service includes two remote service components including a protocol management component to provide access to a database for the acquisition protocols so as to administer these, and a protocol distribution component to implement the distribution of the protocols and, in the process, communicate with several medical devices.

23. The system according to claim 1, wherein the operating management service includes several all-encompassing basic functionalities and implements a monitoring of system resources and system operation.

24. The system according to claim 1, wherein the operating management service includes seven remote service components including a GSM component, a CoLicense manager component, a message store component, a central audit component, a central utilization component, a central log component and depot component.

25. The system according to claim 1, wherein the enterprise application integration management service implements basic functionalities for communicating with other medical systems via the exchange of messages.

26. The system according to claim 1, wherein the enterprise application integration management service implements basic functionalities for at least one of sending and receiving messages.

27. The system of claim 1, wherein the web service is configured to expose application programming interfaces (APIs), the APIs including interfaces of the at least one remote service component.

29. A non-transitory computer readable medium, loadable into a computer memory, with commands readable by the computer for implementing the method as disclosed in claim 25 when the commands are realized on the computer.

28. A computer implemented method for providing a number of basic functionalities that encompass all applications at least for a medical application in the field of the image-processing medical technology, wherein respectively one web service implements at least one basic functionality and wherein all web services respectively have substantially the same basic configuration, the method comprising:

providing at least one web service, wherein the web service includes,

at least one remote service component;

at least one business object in which the respective basic functionality is implemented and which is useable by a remote service component, and

at least one service component that provides selected, different basic functionalities and is useable by a remote service component; and

providing access for the application to at least one web service via at least one remote service component, wherein the basic functionalities are selectable from a number of functionalities including transfer management, data management, workflow management, report management, protocol management, operating management and enterprise application integration management.

30. The method of claim 28, wherein the at least one web service is configured to expose application programming interfaces (APIs), the APIs including interfaces of the at least one remote service component.