SYSTEM FOR MANAGING AND PROCESSING DATA FROM A MEDICAL FACILITY

• US 20150234557A1
• Filed: 10/16/2014
• Published: 08/20/2015
• Est. Priority Date: 02/20/2014
• Status: Active Grant

• Current Assignee: Siemens Healthineers AG (Siemens AG)
• Original Assignee: Siemens AG
• Inventors: DORN, Karlheinz
• Granted Patent: US 10,191,626 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 30/20 for handling medical images, e.g. DICOM, HL7 or PACS

Abstract

A system for managing and processing data in a medical facility is specified. The system includes at least one browser application for running on a user device. The browser application is set up to display data record lists containing a respective list entry for a number of medical data records of at least one particular data type and individual list entries for inspection and processing. The browser application has a multilayer component architecture having a frame layer, a view layer, a view model layer, a model layer and a driver layer. In this case, the components of the view model layer are generic, that is to say independent of the data type.

Claims

1. A system for managing and processing data in a medical facility, having at least one browser application for running on a user device, the browser application being set up to display

data record lists containing a respective list entry for a number of medical data records of at least one particular data type and

individual list entries

for inspection and processing, the browser application being subdivided into the following layers in terms of its component architecture:

a frame layer comprising at least one frame component, the frame component defining a number and arrangement of GUI pages to be displayed at the same time for a respective data record list or GUI pages for a respective list entry, and the frame component also being configured to implement functions for transferring control between different GUI pages,

a view layer comprising a number of components, each respectively specifically defining, for a particular data type, the graphical contents of a GUI page for displaying a data record list or a GUI page for displaying a list entry,

a view model layer comprising a number of components, each defining, for at least one associated component of the view layer, properties and commands for the control elements of the GUI page defined there,

a model layer comprising a number of components, each respectively specifically defining, for a particular data type, the structure of the associated data records, and

a driver layer comprising a number of driver components, each respectively configured to facilitate data access to a particular data memory inside or outside the user device,

the components of the view model layer being independent of the data type.

2. The system of claim 1, wherein the driver components are independent of the data type.

3. The system of claim 1, wherein the or each frame component is independent of the data type.

4. The system of claim 1, wherein the driver layer comprises an application programming interface on which the or each driver component is based.

5. The system of claim 1, wherein the components of the view model layer comprise generic functions for creating, reading, updating and deleting data record lists or individual list entries.

6. The system of claim 1, wherein the browser application is set up to display data record lists and list entries for data records of at least one of the following data types:

patient data, each data record of which respectively contains personal and medical data relating to a particular patient,

tasks or work lists, each data record of which contains a task, or sequence of tasks to be carried out by a medical user,

context data, each data record of which contains context information relating to a medical image data record.

7. The system of claim 1, wherein the browser application is set up to directly access at least one of data records and their associated list entries in a data memory arranged outside the user device.

8. The system of claim 1, further comprising:

an application template and an application configurator, the application configurator being set up to automatically generate the or each browser application from the application template using predefined configuration information, the configuration information comprising at least one of;

details relating to the user device on which the respective browser application is intended to run,

details relating to the or each data type of the data records, the associated list entries and data record lists of which are intended to be displayed and processed using the respective browser application, and

details relating to the or each data memory which is intended to be accessed, by the respective browser application.

9. The system of claim 1, wherein the or each driver component is able to be instantiated repeatedly.

10. The system of claim 1, wherein the data access by the or each driver component is provided asynchronously and independently of the other driver components.

11. The system of claim 6, wherein, the context information relating to a medical, image data record is a reference to the storage location of the image data record.

12. The system of claim 7, wherein the browser application is set up to directly access at least one of data records and their associated list entries in a cloud storage of a public cloud, without using an interposed server.

13. The system, of claim 2, wherein the or each frame component is independent of the data type.

14. The system of claim 2, wherein the driver layer comprises an application programming interface on which the or each driver component is based.

15. The system of claim 2, wherein the components of the view model layer comprise generic functions for creating, reading, updating and deleting data record lists or individual list entries.