Method and apparatus for producing and accessing composite data

[0002] This is a continuation of application Ser. No. 08/832,688, filed Apr. 11, 1997, now U.S. Pat. No. 5,970,499, which is incorporated herein by reference.

[0003] The present invention relates to information systems and methods, and more particularly to data fusion systems.

[0004] Many applications require the contemporaneous assimilation of large amounts of data. Medical, military, and commercial applications require operators to engage in procedures and make decisions based on data describing various subjects represented by, for example, images, recorded sound, and text. Current technology does not present personnel with a unified view of this subject data to allow them to use all available data to make informed decisions.

[0005] For example, a physician providing medical treatment, reviews image data acquired in multiple modalities, such as magnetic resonance (“MR”), computed tomographic (“CT”), and X-ray images, medical journals describing procedures, video images, such as ultrasound, and atlases describing anatomical structures. A physician must therefore consult several sources to review the data necessary to provide patient treatment. These sources may include multiple computer display terminals located in different parts of a hospital, hard copies of medical images printed on film archived among thousands of images in a hospital film library or remote storage site, and volumes of journals located in the stacks of a hospital library. Also, the sources of data consulted by treating physicians may include medical atlases containing thousands of MR and CT scans of a cadaver corresponding to photographic images of cross-sectional slices taken of various anatomical structures.

[0006] Usually data from these atlases and other sources are not correlated with each other. A cadaver image in an atlas does not usually have the same geometry as a patient receiving treatment, so a physician must mentally fuse the available data which requires correlating the data retrieved from the various sources to develop a treatment plan or to provide information during medical procedures. The difficulties of fusing all of the available data increase if the physician must assimilate the various data types while rendering treatment.

[0007] The World Wide Web (“WWW”) has recently made vast amounts of data stored on local and remote computers easily accessible through a graphical computer interface. The WWW is a network of computers, connected by the Internet, sharing a common file structure and mark-up language for creating files. The two most prevalent languages used to create multimedia WWW files are the hypertext mark-up language (“HTML”) and the virtual reality mark-up language (“VRML”). HTNL is best suited for creating files with text and two-dimensional image data, whereas VRML is designed for creating files containing images of three-dimensional objects. Both languages provide an easy way to combine image, text, and sound data in files accessible by “point-and-click,” computer mouse driven user interfaces called “browsers.”

[0008] A “browser” is a computer program that provides users access to files stored on the WWW. The browser displays files on a computer screen and can run programs, known as “applets,” indicating links to data in other files on the WWW by, for example, underlining text or highlighting areas of an image. By selecting the underlined text or a highlighted image, the browser retrieves the linked data, allowing a user to view data stored on computers in the WWW without needing to know where the information is physically stored. Files can be joined using these “hyperlinks,” which give the name of the file along with an address for a computer storing the file. For example, the text or an image in a file stored on a computer in Switzerland can contain an embedded link to data stored on a computer in the United States. The WWW browser automatically recognizes the linked file data type, so the linked file can be an image, an audio clip, a video, or even an executable computer program. For example, if the linked data is an audio clip, the browser will load a program that takes the audio clip and plays it through the speakers of the user's computer. A browser usually runs on a computer referred to as a “client,” while a computer known as a “server” hosts and produces WWW files requested by a client.

[0009] In particular, the WWW serves as a useful tool for navigating through two- and three-dimensional image data. For example, an image can be displayed by the browser, and different parts of the image can be linked to different files. But, for the most part, this WWW capability is primarily used for providing simple menus of uncorrelated data available on WWW computers. For example, a WWW computer will show an image of people, cars, and boats. By clicking on the image of people, a user can go to on-line chat sessions with people, or by clicking on a boat image, a user gets information about boats.

[0010] The current technology is limited because there does not exist an information system that exploits the data navigation capabilities of the WWW to correlate data retrieved from diverse sources and then assimilate the data into a useful form. For example, the tools available for information gathering in the WWW environment include database search engines and expert systems that assist a user in describing the information sought. However, these tools only retrieve files corresponding to a particular term or pertaining to certain designated subject matter. The retrieved files are not correlated with one another.

[0011] There is, therefore, a need for an information system that harnesses the power of the technology associated with the WWW and other similar image-based information retrieval systems to produce assimilated composite data in a form that operators can readily use.

[0012] The present invention is directed to a method and apparatus for producing and accessing composite data containing co-registered and subject data. The method for automatically producing composite data includes several steps, performed by a server computer. The steps include: creating a mapping relationship between the co-registered data and the subject data by mapping or deforming a template to fit the subject data; filtering the co-registered data; and producing composite data by mapping the filtered co-registered data to the subject data according to the mapping relationship.

[0013] A method consistent with this invention is also directed to steps, performed in a client computer, including: requesting composite data from a server computer; transmitting the subject data to the server computer; receiving the requested composite data from the server computer; presenting the received composite data to an operator; and monitoring the operator's use of composite data.

[0014] An apparatus consistent with this invention for automatically producing composite data containing co-registered data and subject data includes: structure for creating a mapping relationship between the co-registered data and the subject data by mapping or deforming a template to fit the subject data; structure for filtering the co-registered data; and structure for producing composite data by mapping the filtered co-registered data to the subject data according to the mapping relationship.

[0015] Another apparatus consistent with the present invention automatically presents an operator with composite data containing co-registered data and subject data. Such an apparatus includes: structure for requesting composite data from a server computer; structure for transmitting the subject data to the server computer; structure for receiving the requested composite data from the server computer; structure for presenting the received composite data to an operator; and structure for monitoring the operator's use of the received composite data.

[0016] Both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.

[0017] The accompanying drawings provide a further understanding of the invention. They illustrate embodiments of the invention and, together with the description, explain the principles of the invention.

[0018] FIG. 1 is a block diagram of an apparatus for automatically producing composite data containing co-registered data and subject data consistent with the present invention;

[0019] FIG. 2 is a block diagram of another apparatus for automatically producing composite medical data containing co-registered medical data and patient data consistent with the present invention;

[0020] FIG. 3 is flow diagram of a method for automatically producing composite data containing co-registered data and subject data consistent with the present invention;

[0021] FIG. 4 is a schematic diagram of user interaction with the embodiment of the invention shown in the block diagram of FIG. 2;

[0022] FIG. 5 is an illustration of co-registered medical data used in an embodiment of the present invention consistent with the block diagram of FIG. 2;

[0023] FIG. 6 is a display produced in accordance with the embodiment of the present invention shown in the block diagram of FIG. 2; and

[0024] FIG. 7 is a block diagram of a facility for providing composite data in accordance with an embodiment of the present invention.

[0025] Reference will now be made in detail to the preferred embodiments of this invention, examples of which are illustrated in the accompanying drawings.

[0026] To illustrate the principles of this invention, FIG. 1 shows subject data 100, template layer 102, deformation engine 104, mapping engine 106, map 107, filtered, co-registered data 108, search and filter engine 110, links 112, and co-registered databases 114. The term “layer” denotes a grouping of data types represented in, for example, a database on a server computer. To produce composite data 109, deformation engine 104 deforms a template layer 102 to fit subject data 100 generating map 107. When subject data 100 is multi-modal, multiple template layers can be utilized to correlate co-registered data 114 to subject data 100 as well as to correlate multi-modal subject data 100 to itself. A template layer contains reference data locations, or landmarks, used to correlate template data with elements of subject data. Examples of landmarks include data representing points, lines, surfaces, volumes, or other defining features in image data.

[0027] Generally, deformation is the process of mapping one image to another image where both images represent the same structure but have different geometric proportions and orientations. During deformation, mathematical transforms are applied to the images that perform the equivalent of bending, stretching, and rotating template data to match subject data. For example, after deformation, template data in the form of a volume image of a generalized model of the human brain is manipulated so that the anatomical structure in this model has the same size, shape, and orientation as the subject data, the actual anatomy of a patient receiving treatment. There are many techniques available for automatically deforming one set of data to fit a target data set, including rule-based morphology, correlation of selected landmarks in each data set, and a technique fusing selected landmarks and image data. One example of such technique appears in U.S. patent application Ser. No. 08/678,628 filed Jul. 10, 1996, which is herein incorporated by reference.

[0028] Once template layer 102 is deformed to fit subject data 100, a mapping relationship, map 107, is established whereby mapping engine 106 maps co-registered data 114 to subject data 100 producing composite data 109. Co-registered data 114 represents a knowledge base providing supplemental information about structures contained in subject data 100. The co-registered databases and template layer share a common coordinate system, so a data element representing a position in one co-registered database is correlated with a data element representing that same position in each of the other co-registered databases. In an embodiment consistent with the present invention, co-registered data 114 is co-registered using, for example, the deformation techniques described above. The mapping relationship obtained from deforming template layer 102 to fit subject data 100 correlates the co-registered database coordinate system with a subject data coordinate system. Implementing this mapping relationship, mapping engine 106 relates points in the subject data coordinate system to corresponding points in the co-registered database coordinate system, providing a dynamic connection between subject data 100 and co-registered databases 114.

[0029] Search and filter engine 110 controls which elements of co-registered data 114 are mapped to subject data 100 and presented to an operator. Search and filter engine 110 can allow mapping engine 106 to map all or a subset of co-registered data 114 to subject data 100. Links 112 specify relationships among data elements across co-registered databases 114 which are used by search and filter engine 110 to assimilate co-registered data according to a service request by an operator including, for example, an indication of a region or regions of interest in subject data 100. The links 112 may be formed using an appropriate database indexing strategy to assign key-word or concept search tags to associated data elements.

[0030] FIG. 2 shows a preferred embodiment of the present invention for producing composite patient data for medical treatment. Collected patient data 200, includes, for example, MR image 236, CT image 238, and landmarks 240. Template layer 202 includes corresponding MR image 230, CT image 232, and landmark 234 templates. This embodiment also includes a deformation engine 204, mapping engine 206, search and filter engine 210, links 212, and co-registered data 214.

[0031] Co-registered data 214 includes a medical atlas 228, text 226, computer programs 225 (such as applets), labels and landmarks 224, images 222, audio and video clips 220, links to computers located on the WWW 218, and treatment plans 216. Co-registered data can also include co-registered subject data. The forgoing list of co-registered data types is only provided as an example of the types of data that are useful in practicing this invention in the context of providing medical treatment. Persons of ordinary skill will recognize that many other data types may also be useful. One of ordinary skill in the art will also recognize that two or more of the co-registered data types may reside in a single database.

[0032] FIG. 3 is a flow diagram of a method for producing composite medical data consistent with the invention. An operator of a system consistent with this invention wishing to have composite data for medical treatment first identifies and possibly collects patient data 200 using a client computer (step 300). The collected patient data must have a modality (e.g., CT, MR, or X-ray) and protocol (e.g., slice thickness and resolution) that is compatible with a template in template layer 202.

[0033] The client computer then generates request 246 for composite data 244 (step 304). Request 246 includes, for example, an operator identifier, security screening information, and treatment information. The client computer also transmits or enables transmission of (from a radiological database, for example) collected patient data 200 and associated filtering context 242 to the server computer (step 306).

[0034] Responding to client computer request 246 for composite data 244, the server computer selects a template conforming with this request (step 308). Example template, MR 230, employed by the present invention when used for medical treatment includes a three-dimensional MR scan of the same slice thickness, resolution, and collection protocol as the patient MR dataset 236. Associated with the selected template imagery is a set of landmarks 234 identifying anatomical structures in a region of interest for a particular surgical procedure. Next, deformation engine 204 fits the selected template to patient data received from the client computer. The process of deforming the selected template to fit the patient data 200 creates a mapping relationship (map 248) relating template data space to a patient data space coordinate system (step 310). Mapping engine 206 also uses map 248 to relate a point in the patient data space coordinate system to an element of co-registered data 214. Once the mapping relationship is determined by deforming the selected template, all co-registered data 214 can be mapped to patient data 200. Note that if multi-modal patient data is used with multiple corresponding templates, multiple maps 248 can be constructed that can then be used to correlate the multi-modal patient data with each other in addition to correlating co-registered data 214.

[0035] Search and filter engine 210 controls how much of co-registered data 214 is included in the composite data. One reason for such control is that certain data types and/or data elements in co-registered data 214 may not be relevant for some medical treatment. Search and filter engine 210 responds to filtering context 242 and selects co-registered data elements as appropriate for this filtering context (step 312) using links 212 to identify related data elements. The filtering context can be derived from data provided by the client computer during the initial request for composite data (step 304). A filtering context can also be derived from previously stored profiles or histories. The server then produces composite data using mapping engine 206 and map 248 to combine patient data and filtered, co-registered data (step 314), producing composite data 244. The server then transmits composite data 244 and map 248 to the client computer for presentation to an operator (step 318). The operator navigates the composite data by specifying a region of interest in the patient data using a browser interface (step 320). The operator may also use the browser interface to select highlighted text or other specified segments of the composite data, activating a link to a particular region of interest in the patient data.

[0036] Map 248 also allows an operator to access additional composite data (step 322). The server receives a request for additional co-registered data and preferably an associated position in the patient data coordinates from the client and subsequently retrieves and transmits additional co-registered data using mapping engine 206, map 248, search and filter engine 210, and links 212 to additional co-registered data 214. (repetition of steps 312-320).

[0037] An embodiment consistent with the present invention for use in the medical field links a radiologist's report to radiological imagery of a patient. Preferably, in an area of the radiologist's text report stating, for example, “in the left parietal-occipital region is a 1.2 cm hypodense lesion with an irregular border that does not enhance on contrast but is hyperintense on T2 . . . ”, selecting the highlighted word “lesion” activates a link to the patient imagery which highlights the particular sub-region discussed in the report text. Likewise, if the operator selects the lesion site in the displayed patient imagery, the link will be activated to display the section or sections of the text report that discuss the selected region of interest.

[0038] Although the foregoing description of embodiments of the present invention specifically allocate certain operations to client and server computers, one of ordinary skill in the art will recognize that the distribution of specific tasks between client and server computers can vary based on application requirements. Moreover, embodiments of the present invention with several client or server computers are within the scope of this invention. Furthermore, it is also consistent with the present invention that the client and server tasks can be performed in a single computer.

[0039] In a preferred embodiment of the present invention, a graphical user interface designed for browsing data presents composite data 244 to the operator. The interface is preferably executed on networked computers. Computer program code that can be adapted to perform this browsing function includes Internet browsers designed to navigate the WWW, such as Netscape's Navigator and Microsoft's Explorer, and equivalent programs that support links to data stored on networked computers.

[0040] FIG. 4 illustrates operator interaction associated with producing composite data in accordance with an embodiment of the present invention. FIG. 4 shows a database containing co-registered data 400 of several data types, including video 402, text 404, waveforms 406, programs 407, still images 408, and segmentation labels 409; a mapping engine 410; a map 412; a set of links 414 among associated data elements across and within the co-registered databases; a patient data space coordinate system 416; and a universal (“atlas”) coordinate system 418 common to all data stored in co-registered database 400. A physician using this embodiment of the present invention selects any point in patient data space coordinate system 416 to retrieve co-registered data 400 corresponding to the selected point.

[0041] In an example illustrating co-registered data in one embodiment of the invention, still image database 408 contains MR images of a human head, database 406 contains recordings of waveforms produced by certain electrical signals in the brain, video database 402 contains recorded motion picture images of neurosurgical procedures or tutorials for these procedures, text database 404 contains short descriptive paragraphs or full journal articles describing regions of the brain and related surgical plans, database 407 contains programs for processing image data, and database 409 contains segmentation maps outlining brain structures.

[0042] The patient data space coordinate system 416 is a frame of reference for patient specific data. This coordinate system is provided by, for example, an MRI of a patient's head or the surgical field surrounding the patient during operation. Deformation engine 204 computes a mapping relationship relating template layer data points in atlas coordinate system 418 to patient data points in patient data space coordinate system 416. Mapping engine 410 uses this computed mapping relationship to transform co-registered data 400 mapped to atlas coordinate system 418 to patient data space coordinate system 416.

[0043] After mapping, a physician has available during a surgical procedure composite data adapted to the patient's anatomy. This composite data is a representation of (1) a patient's anatomy comprising patient specific data acquired before or during a medical procedure, and (2) data from one or more of the co-registered databases 400.

[0044] Map 412 provides a virtual grid overlaying the patient data space coordinate system 416 allowing an operator to position a pointing device in the patient data to retrieve co-registered data. Selecting a position in map 412 retrieves co-registered data correlated with the selected position by mapping engine 410 through links 414.

[0045] In one embodiment of the invention, map 412 contains a number of positions corresponding to the number of positions in patient data space coordinate system 416 detectable by a surgical navigation system (see, e.g., U.S. Pat. No. 5,383,454). A map position is selected according to the location of a surgical probe in patient data space coordinate system 416 during a medical procedure. For example, during neurosurgery a surgeon placing the probe at a patient's ventricle activates a map position corresponding to the probe position in the ventricle. The activated map position is communicated to mapping engine 410 which queries co-registered databases 400 for data corresponding to the map position in the ventricle. This corresponding co-registered data is deformed to fit the patient's anatomy and combined with patient specific data giving the surgeon composite data related to the patient's ventricle, containing more information than the patient data alone.

[0046] A further illustration of the types of data a physician may require during neurosurgery or during surgical planning is shown in FIG. 5. This figure contains illustrations of five data types available to a surgeon in an embodiment of the present invention including a cross-sectional image 502, a medical journal article 504, electroencephalograph waveforms 506, computer programs 507, video images of the brain 508, and a segmentation map identifying the different regions of the brain 510. Because these data sources have been co-registered to a common atlas coordinate system, a point, such as point 500 in the cerebellum in brain image 502 from database 408, has a corresponding point in each of the other data types in co-registered database 400. For example, point 500 in text database 404 corresponds to article 504 on new surgical techniques involving the cerebellum. Point 500 in waveform database 406 corresponds to recorded waveforms 506 produced by the brain at this location. Point 500 in program database 407 corresponds to applet program 507, which is used to provide enhanced visualization of brain image 502. Point 500 in video database 402 corresponds to video clips 508 of the brain at this location. Point 500 in segmentation map database 409 corresponds to a point within segmentation map 510.

[0047] Each of these examples of data need not be acquired from the patient currently receiving treatment. For example, the data may come from digital anatomical atlases, libraries of cadaver images, or research databases produced by projects such as the “Visible Human” research sponsored by the National Library of Medicine. Data available in a co-registered database would include, for example:

[0048] 1. Anatomic

[0049] Magnetic Resonance Imaging

[0050] Computed Tomography

[0051] Magnetic Resonance Angiography

[0052] Ultra-Sound

[0053] Slice photographic images

[0054] Sulci/Gyri traces

[0055] 2. Functional

[0056] Positron Emission Tomography

[0057] Single Photon Emission Computed Tomography

[0058] Functional Magnetic Resonance images

[0059] Electroencephalograph

[0060] Magnetoencephatography

[0061] 3. Symbolic

[0062] Structure name

[0063] Structure size

[0064] Structure function

[0065] Structure related text cues

[0066] Structure related video cues

[0067] Structure related audio cues

[0068] Structure related labels

[0069] Histology

[0070] Morphological data

[0071] 4. Multimedia

[0072] Video Footage of procedures

[0073] Training, Videos

[0074] Conference, Journal Articles

[0075] Statistics

[0076] 5. Computer Programs

[0077] Applets

[0078] Data Analysis

[0079] Automated Structural Segmentation

[0080] Image Enhancement and Visualization

[0081] These data need not be located in a single database. One of ordinary skill in the art will recognize that individual co-registered databases may be distributed among several databases accessible through, for example, local area computer networks or wide area computer networks connecting local and distributed computers. The combination of the different data components of the co-registered databases produces a generic data model of human anatomy where each data element is correlated through a common coordinate system with corresponding data elements of other types. When planning or providing medical treatment, the invention produces composite data linking co-registered data of a generic model to the specific anatomy of a patient receiving treatment. Examples of other embodiments consistent with the present invention for producing composite data for medical diagnosis, planning, and treatment include, but are not limited to, the following.

[0082] 1. Diagnostic Radiology—co-registered patient magnetic resonance, X-ray, and/or computed tomography imagery are linked to text data such as radiologists' reports, patient case history files, and relevant conference/journal articles. Sequential scans of a patient are co-registered for tracking the growth or reduction of lesions. Data analysis programs are linked to the composite data for computation of quantitative data measurements for planning and monitoring of treatment progress. Co-registered multi-modal patient image data and relevant co-registered data are presented in a common, easy-to-use presentation scheme.

[0083] 2. Radiation Treatment Planning—Three-dimensional segmented atlases are mapped to patient data to produce an object-based model of lesions, targets, and major organs and other critical structures. The patient data with associated object information is utilized by a treatment planning program for computing optimized radiation delivery strategies from target and critical structure information.

[0084] 3. Neurosurgical Targeting—cranial patient imagery is mapped to neurosurgical atlas information containing coordinates and shapes of surgical targets and surrounding neuroanatomic structures. Structural information is linked to audio files for use in-surgery with microrecording probes. Links to statistical databases provide information relating regions of interest to procedures and success rates.

[0085] FIG. 6 shows how one embodiment of the present invention presents composite data to an operator on a computer display having several windows. Window 604 contains patient data in the form of a three-dimensional MR brain scan. Windows 602, 606, and 608 contain axial, sagittal, and coronal photographic section data, respectively, from the Visible Human data set, which are co-registered to the patient data by deformation engine 204. Window 61020 presents co-registered atlas data to an operator. By positioning cross-hairs 612 in Window 604 at a desired point 600, the corresponding point 600 in each of the images in windows 602, 606, and 608 is identified automatically by the location of cross-hairs in those windows. Here, for example, the operator selected point 600 in window 604 corresponding to a region the brain known as the putamen. Atlas data containing views of the putamen are displayed in window 610 with highlighted pointers indicating the putamen in each of the atlas images. The operator can also choose to play a movie showing video images of the putamen by pushing “play movie” button 614. Alternatively the operator may select the word “putamen” in window 610 and cross-hairs 612 will indicate the position of the putamen in patient data window 604 and the Visible Human “atlas” data windows 602, 606, 608.

[0086] FIG. 7 is a block diagram of a facility consistent with the present invention for providing composite data across a computer network to customers under a service contract. In FIG. 7, solid lines indicate a path for both control and data flow and dotted lines indicate data flow only. Facility 700 is preferably connected to a wide area network, such as Internet 701, through firewall 702. Firewall 702 is a computer that monitors all data traffic into and out of facility 700 to prevent unauthorized access to the facility. World Wide Web page 704 provides a graphical user interface to access facility 700. Facility 700 also includes customer account manager 710, which controls functions available to customers with service contracts authorizing access to facility 700.

[0087] User login authentication is performed by customer account manager 710 and control is passed to one of three processes, service request manager 706, customer database manager 708, or results manager 712 depending on the service that the customer chooses. Customers that wish to initiate a new request for composite data are passed to service request manager 706. After successful completion of a composite data request, the customer's account is billed and the status of any pending requests is provided. Customers that wish to view the composite data generated in response to the request are passed to results manager 712. Information pertaining to a customer's account (e.g., billing information, changing passwords, user preferences, etc.) may be obtained by submitting queries to customer database manager 708.

[0088] Service request manager 706 initiates service requests and controls the computational operations required for anatomic mapping. The progress of a service request is tracked and reported to customer account manager 710. Customer database manager 708 administers a database that contains customer account data (not shown). Customer database manager 708 is responsible for controlling and backing up the customer database and it also processes queries from customer account manager 710, service request manager 706, and results manager 712. Results manager 712 integrates the results generated by service request manager 706 with context-specific medical knowledge. Results manager 712 receives information from search and filter engine 720 and mapping engine 722 specific to application requirements. Some results may be provided as visual representations (e.g., mapped segmented structures in a brain image) while others may be expressed in numeric form (e.g., coordinates of a neurosurgical target).

[0089] Preprocessor 714 checks patient data associated with a service request to make sure that the patient data is in the correct format and that the service request is appropriate. Support personnel 724 confirm the check performed by preprocessor 714. Any inconsistencies or anomalies that are found are reported to service request manager 706. Similarly, post processor 718 checks the results of a service request. Support personnel 724 confirm the check performed by preprocessor 718. Any inconsistencies or anomalies that are found are reported to service request manager 706.

[0090] Facility 700 also includes deformation engine 716, search and filter engine 720, and mapping engine 722. Deformation engine 716 computes atlas-to-patient transformations requested by service request manager 706. Search and filter engine 720 processes customer, patient, and procedure contextual data and integrates relevant atlas information according to application requirements. Both results manager 712 and service request manager 706 initiate search and filter engine 720 operations. Following a request from results manager 712, mapping engine 722 applies the results of the deformation process mapping an atlas to the patient data.

[0091] Patient database manager 726 administers a database that contains patient data and corresponding transformations computed by deformation engine 716. Patient database manager 726 serves queries from deformation engine 716, search and filter engine 720, and mapping engine 722 and is also responsible for controlling and backing up the patient database (not shown).

[0092] Atlas database manager 728 administers a database that contains the atlas data (not shown). Atlas database manager 728 serves queries from deformation engine 716, search and filter engine 720, and mapping engine 722 and is also responsible for controlling and backing up the atlas database. Atlas database manager 728 can also perform and/or manage the indexing of the co-registered data databases.

[0093] While there has been illustrated and described what are at present considered to be preferred embodiments and methods of the present invention, persons skilled in the art will understand that various changes and modifications may be made, and equivalents may be substituted without departing from the scope of the invention.

[0094] In addition, many modifications may be made to adapt a particular element, technique or implementation to the teachings of the present invention without departing from the central scope of the invention. For example, disclosed elements may be implemented in hardware, computer program code, or a combination of both hardware and computer program code. Moreover, elements depicted and described separately may be combined and implemented in a single element. Therefore, this invention is not limited to the particular embodiments and methods disclosed, but includes all embodiments falling within the scope of the appended claims.