1. A method comprising:
loading medical image data to make the image data available to an image processing program, the image data having been generated from raw data obtained by a medical imaging system during scanning of an object, and the image data including metadata and pixel data associated with the object, the loading including,
assigning the image data to a data type out of a plurality of possible data types,
subsequently selecting, out of a plurality of data-type-specific loading strategies, a loading strategy assigned to the data type, and
utilizing the selected loading strategy for loading the image data.
2. The method of claim 1, wherein the plurality of possible data types include:
volume image data based on individual slice images as a first data type,
volume image data based on multiframe image data as a second data type,
image data conforming to a whole slide imaging standard within a DICOM standard as a third data type, and
projection image data as a fourth data type.
3. The method of claim 1, wherein the data type is assigned on the basis of the metadata.
4. The method of claim 1, wherein the image data is additionally assigned context data and the loading strategy is selected based on the context data.
5. The method of claim 4, wherein a shared index is generated for the image data of a plurality of medical objects, in which index associated context data is assigned to the image data of a respective object, the index being accessed in order to determine the context data.
6. The method of claim 5, wherein the loading strategy is determined based on information stored in the index.
7. The method of claim 5, wherein the data type is assigned and an entry made in the index as soon as the image data is received from an imaging medical device.
8. The method of claim 4, wherein information from a preceding evaluation of the image data is stored in the context data.
9. The method of claim 4, wherein the loading strategy is selected taking into account information relating to imaging regions of interest which were identified in a preceding assessment.
10. The method of claim 9, wherein a plurality of imaging regions are identified these are loaded in succession according to a weighting.
11. The method of claim 4, wherein the loading strategy is selected taking into account the type of object that is to be examined.
12. The method of claim 4, wherein the loading strategy is selected taking into account examination objectives.
13. The method of claim 1, wherein workflows predefined for image processing on the image processing program are stored and the loading strategy is selected by the sequence of the workflows.
14. A device comprising:
a computer unit including a processor and a memory, the processor having a load module to load medical image data to make the image data available to an image processing program, the image data having been generated from raw data obtained by a medical imaging system during scanning of an object, and the image data including metadata and pixel data associated with the object, the load module being further configured to,
assign the image data to a data type from among a plurality of possible data types,
subsequently select, from among a plurality of data-type-specific loading strategies, a loading strategy assigned to the data type, and
utilize the selected loading strategy for loading the image data.
15. The device of claim 14, wherein the load module comprises:
a data type assignment module for assigning the data type to the image data,
an index generator for generating an index,
an analysis module for automatically extracting context data from a preceding evaluation of the image data, and
a workflow module for controlling the loading of the image data and determining, based on information stored in the index, the loading strategy for loading the image data from an image data memory.
16. The method of claim 2, wherein the data type is assigned based on the metadata.
17. The method of claim 6, wherein the data type is assigned and an entry made in the index in response to receiving the image data from an imaging medical device.
18. A device comprising:
a computer unit including a processor and a memory, the processor having a load module configured to load medical image data to make the image data available to an image processing program, the image data having been generated from raw data obtained by a medical imaging system during scanning of an object, and the image data including metadata and pixel data associated with the object, the load module being further configured to,
assign the image data to a data type from among a plurality of possible data types,
subsequently select, from among a plurality of data-type-specific loading strategies, a loading strategy assigned to the data type, and
utilize the selected loading strategy for loading the image data, wherein
the image data is additionally assigned context data and the loading strategy is selected based on the context data.
19. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 1.
20. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 4.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
What is claimed is:
1. A system for application development, comprising:
a data-modeling framework configured to enable a user to define a logical data model, the data-modeling framework dynamically translating the logical data model into a corresponding physical data model, wherein changes to the logical data model are automatically adjusted in the physical data model accordingly; and
a content management framework coupled to the data-modeling framework, the content management framework configured to provide tools to enable the user to manage content associated with the physical data model based on the logical data model.
2. The system of claim 1, wherein the content-management framework is accessible using a graphical user interface (GUI).
3. The system of claim 1, further comprising presentation templates displaying histories, summaries, edit screens, navigation, and workflow.
4. The system of claim 1, further comprising a security modeling framework that integrates workflow and navigation with access to the content being managed.
5. The system of claim 1, wherein the content management framework automatically generates code for displaying histories, summaries, edit screens, navigation, and workflow.
6. The system of claim 1, further comprising metadata that defines relationships between the logical data model and the physical data model.
7. The system of claim 6, wherein one or more text boxes, buttons, and drop-down lists on the GUI are dynamically generated based on a data type defined in the logical data model.
8. A method for use with an application development system, comprising:
providing a data-modeling framework configured to enable a user to define a logical data model, the data-modeling framework dynamically translating the logical data model into a corresponding physical data model, wherein changes to the logical data model are automatically adjusted in the physical data model accordingly; and
providing a content management framework coupled to the data-modeling framework, the content management framework configured to provide tools to enable the user to manage content associated with the physical data model based on the logical data model.
9. The method of claim 8, wherein providing a content management framework comprises:
defining sets with one or more associated attributes;
defining relationships between the sets;
creating queries by selecting fields in a query display;
defining workflow stages associated with the queries; and
assigning one or more navigation items to the queries.
10. The method of claim 9, further comprising:
providing an editingentry template that automatically generates an editentry screen for adding, editing, deleting, approving, resetting and saving content;
displaying an editingentry screen;
providing a summary template that automatically generates a summary list containing content managed by the system;
displaying the summary list;
providing an edit-history template that automatically generates an edit-history screen; and
displaying the edit-history screen;
providing a workflow template that automatically generates a workflow screen;
displaying the workflow screen; and
updating the physical data model automatically.
11. The method of claim 10, further comprising providing a security modeling framework that integrates workflow and navigation with access to the content being managed.
12. The method of claim 11, wherein the content management framework automatically generates code for displaying the edit-history screen, the summary list, the editingentry screen, and the workflow screen.
13. The method of claim 12, further comprising providing metadata that defines relationships between the logical data model and the physical data model.
14. The method of claim 13, wherein one or more text boxes, buttons, and drop-down lists on the edit-history screen, the summary list, the editingentry screen, and the workflow screen are dynamically generated based on a data type defined in the logical data model.
15. An application development system, comprising:
means for data-modeling by enabling a user to define a logical data model, the data-modeling framework dynamically translating the logical data model into a corresponding physical data model, wherein changes to the logical data model are automatically adjusted in the physical data model accordingly; and
means for content managing by providing tools to enable the user to manage content associated with the physical data model based on the logical data model, wherein the content managing means is coupled to the data-modeling means.
16. The system of claim 15, wherein the content management means:
means for defining sets with one or more associated attributes;
means for defining relationships between the sets;
means for creating queries by selecting fields in a query display;
means for defining workflow stages associated with the queries; and
means for assigning one or more navigation items to the queries.
17. The system of claim 16, further comprising:
means for providing an editingentry template that automatically generates an editentry screen for adding, editing, deleting, approving, resetting and saving content;
means for displaying an editingentry screen;
means for providing a summary template that automatically generates a summary list containing content managed by the system;
means for displaying the summary list;
means for providing an edit-history template that automatically generates an edit-history screen; and
means for displaying the edit-history screen;
means for providing a workflow template that automatically generates a workflow screen;
means for displaying the workflow screen; and
means for updating the physical data model automatically.
18. The system of claim 17, further comprising means for providing a security model that integrates workflow and navigation with access to the content being managed.
19. The system of claim 18, wherein the content management means automatically generates code for displaying the edit-history screen, the summary list, the editingentry screen, and the workflow screen.
20. The system of claim 19, further comprising providing metadata that defines relationships between the logical data model and the physical data model.
21. The system of claim 20, wherein one or more text boxes, buttons, and drop-down lists on the edit-history screen, the summary list, the editingentry screen, and the workflow screen are dynamically generated based on a data type defined in the logical data model.