1. Field of the Invention
The invention relates generally to the field of orthodontics and, more particularly, to computer modeling of teeth.
2. Description of the Background Art
Tooth positioners for finishing orthodontic treatment are described by Kesling in the Am. J. Orthod. Oral. Surg. 31:297-304 (1945) and 32:285-293 (1946). The use of silicone positioners for the comprehensive orthodontic realignment of a patient's teeth is described in Warunek et al. (1989) J. Clin. Orthod. 23:694-700. Clear plastic retainers for finishing and maintaining tooth positions are commercially available from Raintree Essix, Inc., New Orleans, La. 70125, and Tru-Tain Plastics, Rochester, Minn. 55902. The manufacture of orthodontic positioners is described in U.S. Pat. Nos. 5,186,623; 5,059,118; 5,055,039; 5,035,613; 4,856,991; 4,798,534; and 4,755,139.
Other publications describing the fabrication and use of dental positioners include Kleemann and Janssen (1996) J. Clin. Orthodon. 30:673-680; Cureton (1996) J. Clin. Orthodon. 30:390-395; Chiappone (1980) J Clin. Orthodon. 14:121-133; Shilliday (1971) Am. J. Orthodontics 59:596-599; Wells (1970) Am. J Orthodontics 58:351-366; and Cottingham (1969) Am. J. Orthodontics 55:23-31.
Kuroda et al. (1996) Am. J Orthodontics 110:365-369 describes a method for laser scanning a plaster dental cast to produce a digital image of the cast. See also U.S. Pat. No. 5,605,459.
U.S. Pat. Nos. 5,533,895; 5,474,448; 5,454,717; 5,447,432; 5,431,562; 5,395,238; 5,368,478; and 5,139,419, assigned to Ormco Corporation, describe methods for manipulating digital images of teeth for designing orthodontic appliances.
U.S. Pat. No. 5,011,405 describes a method for digitally imaging a tooth and determining optimum bracket positioning for orthodontic treatment. Laser scanning of a molded tooth to produce a three-dimensional model is described in U.S. Pat. No. 5,338,198. U.S. Pat. No. 5,452,219 describes a method for laser scanning a tooth model and milling a tooth mold. Digital computer manipulation of tooth contours is described in U.S. Pat. Nos. 5,607,305 and 5,587,912. Computerized digital imaging of the jaw is described in U.S. Pat. Nos. 5,342,202 and 5,340,309. Other patents of interest include U.S. Pat. Nos. 5,549,476; 5,382,164; 5,273,429; 4,936,862; 3,860,803; 3,660,900; 5,645,421; 5,055,039; 4,798,534; 4,856,991; 5,035,613; 5,059,118; 5,186,623; and 4,755,139.
With the advent of wide area networks such as the Internet, orthodontic prescriptions can be communicated electronically. Also, it is desirable to visualize the appliances that are generated in response to the prescriptions and the result of the orthodontic treatment plan. However, realistic models of the teeth and the appliances require large amounts of data storage and transmission bandwidth. Such requirements limit the quality of the visualization and the number of users that can receive the models over the wide area network.
A computer-implemented method generates a computer model of one or more teeth by receiving as input a digital data set of meshes representing the teeth; selecting a curved coordinate system with mappings to and from a 3D space; and generating a function in the curved coordinate system to represent each tooth.
In another aspect, a computer-implemented method for communicating information on one or more teeth by providing a digital model of a tooth; compressing the digital model; and communicating the digital model over a network.
Implementations of the above aspect may include one or more of the following. The compressing the digital model can include selecting a curved coordinate system with mappings to and from a 3D space; and generating a function in the curved coordinate system to represent each tooth. The compressing the digital model generates a compacted file whose file size is selectable from five kilobytes to fifty or more megabytes in size, depending on the desired quality of the digital model. The model can also cover a plurality of teeth, such as five or ten teeth. The model can also include a jaw and/or gingiva.
Advantages of the system include one or more of the following. The system reduces the amount of data storage space required for storing and communicating teeth treatment information. By utilizing space more efficiently, the system reduces the cost of the system, improves the responsiveness of the system, and allows additional functionality to be implemented.
The system supports fast distance estimation from a point to the tooth's surface. This capability is needed for rapid collision detection. It also supports smoothing of the tooth surface for noise reduction. Such rapid collision detection may support real-time manipulation of the teeth for treatment. For example, a user moves a tooth, and the tooth stops when it comes in contact with another tooth.
The system can also support patching small holes in the model of the teeth that may be generated during the taking of impressions/negative impressions. The system also provides the user with a selectable range of precision in teeth geometry representation.
The system also allows visualization to be used to communicate treatment information in a computer-automated orthodontic treatment plan and appliance. The invention generates a realistic model of the patient's teeth without requiring a user to possess in-depth knowledge of parameters associated with patient dental data compression. Additionally, expertise in 3D software and knowledge of computer architecture is no longer needed to process and translate the captured medical data into a realistic computer model rendering and animation.
The invention allows teeth plan treatment to be generated and communicated in a simple and efficient manner. It also improves the way a treating clinician performs case presentations by allowing the clinician to express his or her treatment plans more clearly and gives a prospective patients an opportunity to visualize the facial changes associated with the proposed treatment. The invention allows multidisciplinary work teams to deal easily and efficiently with the treatment plan. Another major benefit is the ability to visualize and interact with models and processes without the attendant danger, impracticality, or significantly greater expense that would be encountered in the same environment if it were physical. Thus, money and time are saved while the quality of the treatment plan is enhanced.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Systems and methods are provided for modeling teeth in creating a treatment plan. The systems and methods compress data associated with the teeth model to reduce the storage size and transmission time to a treating professional. Based on the treatment plan, the teeth can be incrementally moved using a plurality of discrete appliances, where each appliance successively moves one or more of the patient's teeth by relatively small amounts.
Referring now to
Referring now to
One tool for incrementally repositioning the teeth in a patient's jaw is a set of one or more adjustment appliances. Suitable appliances include any of the known positioners, retainers, or other removable appliances which are used for finishing and maintaining teeth positions in connection with conventional orthodontic treatment. As described below, a plurality of such appliances can be worn by a patient successively to achieve gradual tooth repositioning. A particularly advantageous appliance is the appliance 100, shown in
The polymeric appliance 100 of
A plaster cast of the patient's teeth is obtained by well known techniques, such as those described in Graber, Orthodontics: Principle and Practice, Second Edition, Saunders, Philadelphia, 1969, pp. 401-415. After the tooth casting is obtained, the casting is digitally scanned by a scanner, such as a non-contact type laser or destructive scanner or a contact-type scanner, to produce the IDDS. The data set produced by the scanner may be presented in any of a variety of digital formats to ensure compatibility with the software used to manipulate images represented by the data. In addition to the 3D image data gathered by laser scanning or destructive scanning the exposed surfaces of the teeth, a user may wish to gather data about hidden features, such as the roots of the patient's teeth and the patient's jaw bones. This information is used to build a more complete model of the patient's dentition and to show with more accuracy and precision how the teeth will respond to treatment. For example, information about the roots allows modeling of all tooth surfaces, instead ofjust the crowns, which in turn allows simulation of the relationships between the crowns and the roots as they move during treatment. Information about the patient's jaws and gums also enables a more accurate model of tooth movement during treatment. For example, an x-ray of the patient's jaw bones can assist in identifying any loose teeth, and an MRI can provide information about the density of the patient's gum tissue. Moreover, information about the relationship between the patient's teeth and other cranial features allows accurate alignment of the teeth with respect to the rest of the head at each of the treatment steps. Data about these hidden features may be gathered from many sources, including 2D and 3D x-ray systems, CT scanners, and magnetic resonance imaging (MRI) systems. Using this data to introduce visually hidden features to the tooth model is described in more detail below.
The IDDS is manipulated using a computer having a suitable graphical user interface (GUI) and software appropriate for viewing and modifying the images. More specific aspects of this process will be described in detail below.
Individual tooth and other components may be segmented or isolated in the model to permit their individual repositioning or removal from the digital model. After segmenting or isolating the components, the user will often reposition the tooth in the model by following a prescription or other written specification provided by the treating professional. Alternatively, the user may reposition one or more teeth based on a visual appearance or based on rules and algorithms programmed into the computer. Once the user is satisfied, the final teeth arrangement is incorporated into a final digital data set (FDDS) (step 204).
The FDDS is used to generate appliances that move the teeth in a specified sequence. First, the centers of each tooth model may be aligned using a number of methods. One method is a standard arch. Then, the teeth models are rotated until their roots are in the proper vertical position. Next, the teeth models are rotated around their vertical axis into the proper orientation. The teeth models are then observed from the side, and translated vertically into their proper vertical position. Finally, the two arches are placed together, and the teeth models moved slightly to ensure that the upper and lower arches properly mesh together. The meshing of the upper and lower arches together is visualized using a collision detection process to highlight the contacting points of the teeth.
In step 204, final positions for the upper and lower teeth in a masticatory system of a patient are determined by generating a computer representation of the masticatory system. An occlusion of the upper and lower teeth is computed from the computer representation; and a functional occlusion is computed based on interactions in the computer representation of the masticatory system. The occlusion may be determined by generating a set of ideal models of the teeth. Each ideal model in the set of ideal models is an abstract model of idealized teeth placement that is customized to the patient's teeth, as discussed below. After applying the ideal model to the computer representation, the position of the teeth is optimized to fit the ideal model. The ideal model may be specified by one or more arch forms, or may be specified using various features associated with the teeth.
Based on both the IDDS and the FDDS, a plurality of intermediate digital data sets (INTDDSs) are defined to correspond to incrementally adjusted appliances (step 206). Finally, a set of incremental position adjustment appliances are produced based on the INTDDs and the FDDS (step 208).
Many types of scan data, such as that acquired by an optical scanning system, provide a 3D geometric model (e.g., a triangular surface mesh) of the teeth when acquired. Other scanning techniques, such as the destructive scanning technique described above, provide data in the form of volume elements (“voxels”) that can be converted into a digital geometric model of the tooth surfaces. In one implementation, a marching cubes algorithm is applied to convert the voxels into a mesh, which can undergo a smoothing operation to reduce the jaggedness on the surfaces of the tooth model caused by the marching cubes conversion. One smoothing operation moves individual triangle vertices to positions representing the averages of connected neighborhood vertices to reduce the angles between triangles in the mesh.
The triangles in
Once a 3D model of the tooth surfaces has been constructed, models of the patient's individual teeth can be derived. In one approach, individual teeth and other components are “cut” using a cutting tool to permit individual repositioning or removal of teeth in or from the digital data. After the components are “freed”, a prescription or other written specification provided by a treating professional is followed to reposition the teeth. Alternatively, the teeth may be repositioned based on the visual appearance or based on rules and algorithms programmed into the computer. Once an acceptable final arrangement has been created, the final tooth arrangement is incorporated into a final digital data set (FDDS).
The curve network generation of step 220 is shown in more detail in
In one embodiment of
Each tooth is modeled as though it were a deformed ball. The curve network is a network of M meridian lines and N parallel lines. For each meridian line, a plane is selected to contain the meridian line. A series of points representing an intersection between the plane and the triangle mesh modeling a tooth is determined. The series of points represent a curve whose length is then determined. The length of the meridian is divided by N. If M is 20 and N is 20, a 20×20 grid of points is generated, each point being represented in 3-D. In this manner, M×N 3D points can be transmitted in place of the voluminous mesh representation of the teeth. To further reduce the size of the file, the coordinates of each point are stored using integer values rather than floating point values.
Alternatively, a second process 300 for fitting a curve network to a tooth is shown in
Next, the process 300 selects the number of meridians M. M can range between 20-40. Also, the process 300 selects the number of points on each meridian N. N typically ranges between 2/3M to M. A set of M half planes 0, . . . , (M−1) is created: each half plane goes through the tooth z-axis, and the plane i forms an angle (2*PI/M)*i with the tooth x-axis (step 302). Exemplary half planes are shown in
For each half plane, an intersection with the tooth mesh surface is determined (step 304. This intersection is a polyline that goes from the lower intersection of z-axis with the tooth surface to their upper intersection (points A and B). This line is called a meridian line.
For each meridian line, a length L is determined and S is determined as a function of L/(N−1) (step 306). From a starting point, the process 300 proceeds atong the meridian line and finds points p0=A, p1, . . . , p[N−1]=B such that the point p[n+1] is at the distance S from p[n] along the meridian. Eventually, an M*N list of points in 3D space is generated and saved (step 308). The points can be saved as short integer values rather than floating point values.
The data is saved and sent to a treating professional. To reconstruct a surface, the grid of M by N points is used to generate a surface that closely resembles a tooth. Although 20 is used in one embodiment, other values for M or N can be 30 or 40.
To reconstruct a surface from a M*N grid of points, a Hermit spline is specified that maps a rectangle [0, M]*[0, N] in (u, v) parameter plane into 3D space. The Hermit spline is a bicubic 3D function on each [m, m+1]*[n, n+1] square in parameter plane. The Hermit spline F is a smooth continued function on the [0, M]*[0, N] rectangle. When restricted to any [m, m+1]*[n, n+1] unit square, the spline is a bicubic 3D function. The restriction of F onto [m, m+1]*[n, n+1] square is denoted by f (omitting the indices (m, n) that should signify that functions f are different on different squares).
The function forms a continuous smooth function on the [0, M]*[0, N] rectangle.
To determine a Hermit spline, 3D values F, two derivatives dF/du, dF/dv, and the second mixed derivative d2F/dudv in each nod point (m, n). Thus for each bicubic function f on [m, m+1]*[n, n+1] square, 3D values f, two derivatives df/du, df/dv, and the second mixed derivative d2f/dudv are generated for the four square corners (m, n), (m+1, n), (m, n+1), (m+1, n+1). A unique 3D bicubic function is completely determined by those values. The bicubic functions on the next squares are smoothly connected because the values and derivatives are the same on the common side.
The 3D values F, two derivatives dF/du, dF/dv, and the second mixed derivative d2F/dudv in the nod points (m, n) are specified as follows:
F(m, n)=(m, n)-th grid point P(m, n);
dF/du(m, n)=0.5*(P(m+1, n)-P(m−1, n));
dF/dv(m, n)=0.5*(P(m, n+1)-P(m, n−1));
d2F/dudv(m, n)=0.
After the Hermit spline on the rectangle [0, M]*[0, N] is determined, its values in the more dense grid of points K*L are computed to derive a K*L grid of 3D points. Each of the four points (k, 1), (k+1, k), (k, 1+1), (k+1, 1+1) are associated with two triangles: {(k, 1), (k+1, k), (k, 1+1)} and {(k, 1+1), (k+1, 1+1), (k, 1)}. In this way, 2*K*L triangles are generated that are then rendered as a reconstructed tooth.
A parametric coordinate system is constructed (step 502). The coordinate system specifies the conversion of a point P(φ, θ, r) into 3D space. Φ ranges from 0 to 2π; θ ranges from 0 to π; and r ranges from 0 to positive infinity.
The phi theta φ, θ; space is represented as a regular grid. The step of the grid is determined using the following formulas
d—φ=2*π/φ_Resolution and
d_θ=π/θ_Resolution.
In general, the coordinate system can be specified using other parameters, and should satisfy several requirements:
1. The coordinates should parameterize the entire 3D space, or the 3D space except a small set inside the tooth.
2. Curves phi=const and theta=const should be linear functions of R (rays). The following formula must be used V(x, y, z)=P(phi, theta)+R*Dir(phi, theta).
3. Coordinate system should provide one-to-one mapping so that rays for different phi and theta do not intersect.
4. Solution should account for different types of teeth.
5. Coordinate system should be simple enough to implement inverse transformation, from 3D space to parametric coordinates. It's desired that sets phi=const be planes.
In one embodiment, the (φ, θ, r)->3D transformation is done with the following equations:
phi ε[0, 2π].
theta ε[0, π];
R ε[0, positive infinity).
V(x, y, z)=P(phi, theta)+R*Direction(phi, theta)
P and Direction functions should be selected to minimize the deviation between the original tooth model and the parametric surface. The formulas for P and Direction may be different for incisors and molars. In one embodiment, the formulas are as follows:
For molars and other types of teeth:
P.x=XSize*sin(theta)*[1+sin2(2phi)]cos(phi);
P.y=YSize*sin(theta)*[1+sin2(2phi)]sin(phi);
p.z=ZSize*(1−2*theta/Pi);
Direction.x=sin(theta)*cos(phi);
Direction.y=sin(theta)*sin(phi);
Direction.z=cos(theta);
Additionally, a radius R representative of the tooth is constructed (step 504). The radius determination is shown in more detail in
The process of
Next, the process of
BYTEb=(BYTE)(255* (R−minR)/(maxR minR));
Since maxR−minR is approximately 5-6 mm for human teeth, the error introduced by this formula is 5/255 mm 0.02 mm.
The collision detection or the determination of the intersection line between two surfaces is efficient. During this process, the embodiment computes the elevation of all grid points in one tooth surface over the other one. If two next points in the grid have different sign elevations, then the segment connecting these points intersects the surface. The segment is approximately divided by the surface into parts proportional to the elevation in its ends. The intersection points on the sides of one grid cell may be connected according to the elevation signs in the vertices to generate an intersection line. This embodiment may be speeded up by first computing elevation values for sub-grid (2*2 or 3*3) of points.
In some applications, tooth penetration may be estimated as the maximum of (minus) elevation of the grid points having a negative elevation. In other applications the penetration may be estimated as (minus) sum of negative elevation. Also, each negative elevation may be multiplied by the cell area. In the latter case, the result is equivalent to the volume of the 3D bodies intersection. Due to the geometry representation, certain minor collisions with small penetrations (smaller than the treatment precision) may occur and these small collisions are ignored by the system.
Given a cell size and the angle between cells, the system can estimate how much a tooth may penetrate into another tooth if all its vertices are outside. The penetration may be significant only if there is a sharp outer angle. When the vertices are found with a small elevation, the mesh in those elevated areas are subdivided. (This is similar to starting with 3*3 mesh, and taking a smaller mesh in close areas only.)
When a user drags a tooth model to move it, teeth penetrations are approximately computed, without subdivisions. When a user releases the tooth model, the penetration can be computed more precisely. If a collision exists, the tooth can be moved a small distance to avoid collision.
The teeth penetration and “distance” (positive elevation) between two teeth are estimated quickly. When the tooth movements are small, the elevation is approximately proportional to the tooth movement (the functions are locally linear), so a touching position (a position with zero elevation) can be determined quickly.
The processes of
Moreover, for every 3D point P, the system can easily detect whether the point is inside the tooth for a fast collision detection. It can be accomplished in the following way:
Although the above parametric techniques can be used to compress the storage size of a mesh model of a tooth, other techniques can be used. In another embodiment, decimation operations can be applied to the mesh of teeth to eliminate data points, which improves processing speed. After the smoothing and decimation operation have been performed, an error value is calculated based on the differences between the resulting mesh and the original mesh or the original data, and the error is compared to an acceptable threshold value. The smoothing and decimation operations are applied to the mesh once again if the error does not exceed the acceptable value. The last set of mesh data that satisfies the threshold is stored as the tooth model.
Additionally, the mesh model can be simplified by removing unwanted or unnecessary sections of the model to increase data processing speed and enhance the visual display. Unnecessary sections include those not needed for creation of the tooth-repositioning appliance. The removal of these unwanted sections reduces the complexity and size of the digital data set, thus accelerating manipulations of the data set and other operations. After the user instructs the software to erase unwanted sections, all triangles within the box set by the user are removed and the border triangles are modified to leave a smooth, linear border. The software deletes all of the triangles within the box and clips all triangles that cross the border of the box. This requires generating new vertices on the border of the box. The holes created in the model at the faces of the box are retriangulated and closed using the newly created vertices.
In alternative embodiments, the computer automatically simplifies the digital model by performing the user-oriented functions described above. The computer applies knowledge of orthodontic relevance to determine which portions of the digital model are unnecessary for image manipulation.
In another embodiment, data associated with the 3D model includes features can be compressed based on observed characteristics of the tooth surfaces. For example, the system can use the curvature of a particular molar between the tips of the cusps and the gumline to predict the shape of the roots for that molar. Models of typical root and crown shapes also can be used to provide predict the shape of the tooth. The information used to arrive at the predicted shapes can be used in lieu of the original data, thus effecting data compression.
Other feature detection techniques use databases of known cases or statistical information against which a particular 3D image is matched using conventional image pattern matching and data fitting techniques. One such technique, known as “Maximum a posteriori” (MAP), uses prior images to model pixel values corresponding to distinct object types (classes) as independent random variables with normal (Gaussian) distributions whose parameters (mean and variance) are selected empirically. For each class, a histogram profile is created based on a Gaussian distribution with the specified mean and variance. The prior images supply for each pixel and each class the probability that the pixel belongs to the class, a measure which reflects the relative frequency of each class. Applying Bayes' Rule to each class, the pixel values in the input image are scaled according to the prior probabilities, then by the distribution function. The result is a posterior probability that each pixel belongs to each class. The Maximum a posteriori (MAP) approach then selects for each pixel the class with the highest posterior probability.
Once downloaded to a remote workstation, a treating clinician is able to view a patient's treatment plan and alter or comment on the plan. The client viewer application is implemented in a computer program installed locally on a client computer at the clinician's site. In one implementation, the viewer program downloads a data file from a remote host, such as a file transfer protocol (FTP) server maintained by the treatment plan designer, which can be accessed either through direct connection or through a computer network, such as the World Wide Web. The viewer program uses the downloaded file to present the treatment plan graphically to the clinician. The viewer program also can be used by the treatment plan designer at the host site to view images of a patient's teeth.
3-D images of various orthodontic views can then be rendered after the compressed data of the teeth has been received. In this process, an origin point, or “look from” point associated with a camera view is generated. Next, a “look at” point or a focus point associated with the camera view is determined. In this system, the line from LookFromPoint to LookAtPoint defines the direction the camera is shooting at. Additionally, a camera Z vector, or up vector, is determined.
Pseudo code for generating various orthodontic views is shown below. With reference to the pseudo code, the code defines a boundingbox of one mold (2 arches) which is the smallest cube containing the molds geometry. Other settings associated with the bounding box include:
Once the intermediate and final data sets have been created and reviewed by an orthodontist or suitably trained person, the appliances may be fabricated as illustrated in
After production, the appliances can be supplied to the treating professional all at one time. The appliances are marked in some manner, typically by sequential numbering directly on the appliances or on tags, pouches, or other items which are affixed to or which enclose each appliance, to indicate their order of use. Optionally, written instructions may accompany the system which set forth that the patient is to wear the individual appliances in the order marked on the appliances or elsewhere in the packaging. Use of the appliances in such a manner will reposition the patient's teeth progressively toward the final tooth arrangement.
Because a patient's teeth may respond differently than originally expected, the treating clinician may wish to evaluate the patient's progress during the course of treatment. The system can also do this automatically, starting from the newly measured in-course dentition. If the patient's teeth do not progress as planned, the clinician can revise the treatment plan as necessary to bring the patient's treatment back on course or to design an alternative treatment plan. The clinician may provide comments, oral or written, for use in revising the treatment plan. The clinician also can form another set of plaster castings of the patient's teeth for digital imaging and manipulation. The clinician may wish to limit initial aligner production to only a few aligners, delaying production on subsequent aligners until the patient's progress has been evaluated.
The user interface input devices typically include a keyboard and may further include a pointing device and a scanner. The pointing device may be an indirect pointing device such as a mouse, trackball, touch-pad, or graphics tablet, or a direct pointing device such as a touch-screen incorporated into the display, or a three dimensional pointing device, such as the gyroscopic pointing device described in U.S. Pat. No. 5,440,326, other types of user interface input devices, such as voice recognition systems, can also be used.
User interface output devices typically include a printer and a display subsystem, which includes a display controller and a display device coupled to the controller. The display device may be a cathode ray tube (CRT), a flat-panel device such as a liquid crystal display (LCD), or a projection device. The display subsystem may also provide non-visual display such as audio output.
Storage subsystem 606 maintains the basic required programming and data constructs. The program modules discussed above are typically stored in storage subsystem 606. Storage subsystem 606 typically comprises memory subsystem 608 and file storage subsystem 614.
Memory subsystem 608 typically includes a number of memories including a main random access memory (RAM) 610 for storage of instructions and data during program execution and a read only memory (ROM) 612 in which fixed instructions are stored. In the case of Macintosh-compatible personal computers the ROM would include portions of the operating system; in the case of IBM-compatible personal computers, this would include the BIOS (basic input/output system).
File storage subsystem 614 provides persistent (non-volatile) storage for program and data files, and typically includes at least one hard disk drive and at least one floppy disk drive (with associated removable media). There may also be other devices such as a CD-ROM drive and optical drives (all with their associated removable media). Additionally, the system may include drives of the type with removable media cartridges. The removable media cartridges may, for example be hard disk cartridges, such as those marketed by Syquest and others, and flexible disk cartridges, such as those marketed by Iomega. One or more of the drives may be located at a remote location, such as in a server on a local area network or at a site on the Internet's World Wide Web.
In this context, the term “bus sub-system” is used generically so as to include any mechanism for letting the various components and subsystems communicate with each other as intended. With the exception of the input devices and the display, the other components need not be at the same physical location. Thus, for example, portions of the file storage system could be connected via various local-area or wide-area network media, including telephone lines. Similarly, the input devices and display need not be at the same location as the processor, although it is anticipated that personal computers and workstations typically will be used.
Bus subsystem 604 is shown schematically as a single bus, but a typical system has a number of buses such as a local bus and one or more expansion buses (e.g., ADB, SCSI, ISA, EISA, MCA, NuBus, or PCI), as well as serial and parallel ports. Network connections are usually established through a device such as a network adapter on one of these expansion buses or a modem on a serial port. The client computer may be a desktop system or a portable system.
Scanner 620 is responsible for scanning casts of the patient's teeth obtained either from the patient or from an orthodontist and providing the scanned digital data set information to data processing system 600 for further processing. In a distributed environment, scanner 620 may be located at a remote location and communicate scanned digital data set information to data processing system 600 via network interface 624.
Fabrication machine 622 fabricates dental appliances based on intermediate and final data set information received from data processing system 600. In a distributed environment, fabrication machine 622 may be located at a remote location and receive, data set information from data processing system 600 via network interface 624.
The invention has been described in terms of particular embodiments. Other embodiments are within the scope of the following claims. For example, the three-dimensional scanning techniques described above may be used to analyze material characteristics, such as shrinkage and expansion, of the materials that form the tooth castings and the aligners. Also, the 3D tooth models and the graphical interface described above may be used to assist clinicians that treat patients with conventional braces or other conventional orthodontic appliances, in which case the constraints applied to tooth movement would be modified accordingly. Moreover, the tooth models may be posted on a hypertext transfer protocol (http) web site for limited access by the corresponding patients and treating clinicians.
The current application is a continuation-in-part of U.S. application Ser. No. 09/576,721, filed on May 23, 2000, now U.S. Pat. No. 6,633,789 which was a continuation-in-part of U.S. application Ser. No. 09/506,419, filed on Feb. 17, 2000, now U.S. Pat. No. 6,463,344. The full disclosures of each of these prior applications are incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
2467432 | Kesling | Apr 1949 | A |
3407500 | Kesling | Oct 1968 | A |
3600808 | Reeve | Aug 1971 | A |
3660900 | Andrews | May 1972 | A |
3683602 | Wallshein | Aug 1972 | A |
3738005 | Cohen | Jun 1973 | A |
3860803 | Levine | Jan 1975 | A |
3916526 | Schudy | Nov 1975 | A |
3922786 | Lavin | Dec 1975 | A |
3950851 | Bergersen | Apr 1976 | A |
3983628 | Acevedo | Oct 1976 | A |
4014096 | Dellinger | Mar 1977 | A |
4195046 | Kesling | Mar 1980 | A |
4253828 | Coles et al. | Mar 1981 | A |
4324546 | Heitlinger et al. | Apr 1982 | A |
4324547 | Arcan et al. | Apr 1982 | A |
4348178 | Kurz | Sep 1982 | A |
4478580 | Barrut | Oct 1984 | A |
4500294 | Lewis | Feb 1985 | A |
4504225 | Yoshii | Mar 1985 | A |
4505673 | Yoshii | Mar 1985 | A |
4526540 | Dellinger | Jul 1985 | A |
4575330 | Hull | Mar 1986 | A |
4575805 | Moermann et al. | Mar 1986 | A |
4591341 | Andrews | May 1986 | A |
4609349 | Cain | Sep 1986 | A |
4611288 | Duret et al. | Sep 1986 | A |
4656860 | Orthuber et al. | Apr 1987 | A |
4663720 | Duret et al. | May 1987 | A |
4664626 | Kesling | May 1987 | A |
4676747 | Kesling | Jun 1987 | A |
4742464 | Duret et al. | May 1988 | A |
4755139 | Abbatte et al. | Jul 1988 | A |
4763791 | Halverson et al. | Aug 1988 | A |
4793803 | Martz | Dec 1988 | A |
4798534 | Breads | Jan 1989 | A |
4836778 | Baumrind et al. | Jun 1989 | A |
4837732 | Brandestini et al. | Jun 1989 | A |
4850864 | Diamond | Jul 1989 | A |
4850865 | Napolitano | Jul 1989 | A |
4856991 | Breads et al. | Aug 1989 | A |
4877398 | Kesling | Oct 1989 | A |
4880380 | Martz | Nov 1989 | A |
4889238 | Batchelor | Dec 1989 | A |
4890608 | Steer | Jan 1990 | A |
4935635 | O'Harra | Jun 1990 | A |
4936862 | Walker et al. | Jun 1990 | A |
4937928 | van der Zel | Jul 1990 | A |
4941826 | Loran et al. | Jul 1990 | A |
4964770 | Steinbichler et al. | Oct 1990 | A |
4975052 | Spencer et al. | Dec 1990 | A |
4983334 | Adell | Jan 1991 | A |
5011405 | Lemchen | Apr 1991 | A |
5017133 | Miura | May 1991 | A |
5027281 | Rekow et al. | Jun 1991 | A |
5035613 | Breads et al. | Jul 1991 | A |
5055039 | Abbatte et al. | Oct 1991 | A |
5059118 | Breads et al. | Oct 1991 | A |
5100316 | Wildman | Mar 1992 | A |
5107444 | Wu | Apr 1992 | A |
5121333 | Riley et al. | Jun 1992 | A |
5125832 | Kesling | Jun 1992 | A |
5128870 | Erdman et al. | Jul 1992 | A |
5130064 | Smalley | Jul 1992 | A |
5131843 | Hilgers et al. | Jul 1992 | A |
5131844 | Marinaccio et al. | Jul 1992 | A |
5139419 | Andreiko et al. | Aug 1992 | A |
5145364 | Martz et al. | Sep 1992 | A |
5176517 | Truax | Jan 1993 | A |
5184306 | Erdman et al. | Feb 1993 | A |
5186623 | Breads et al. | Feb 1993 | A |
5257203 | Riley et al. | Oct 1993 | A |
5273429 | Rekow et al. | Dec 1993 | A |
5278756 | Lemchen et al. | Jan 1994 | A |
5328362 | Watson et al. | Jul 1994 | A |
5338198 | Wu et al. | Aug 1994 | A |
5340309 | Robertson | Aug 1994 | A |
5342202 | Deshayes | Aug 1994 | A |
5368478 | Andreiko et al. | Nov 1994 | A |
5382164 | Stern | Jan 1995 | A |
5395238 | Andreiko et al. | Mar 1995 | A |
5431562 | Andreiko et al. | Jul 1995 | A |
5440326 | Quinn | Aug 1995 | A |
5440496 | Andersson et al. | Aug 1995 | A |
5447432 | Andreiko et al. | Sep 1995 | A |
5452219 | Dehoff et al. | Sep 1995 | A |
5454717 | Andreiko et al. | Oct 1995 | A |
5456600 | Andreiko et al. | Oct 1995 | A |
5474448 | Andreiko et al. | Dec 1995 | A |
RE35169 | Lemchen et al. | Mar 1996 | E |
5518397 | Andreiko et al. | May 1996 | A |
5528735 | Strasnick et al. | Jun 1996 | A |
5533895 | Andreiko et al. | Jul 1996 | A |
5542842 | Andreiko et al. | Aug 1996 | A |
5549476 | Stern | Aug 1996 | A |
5562448 | Mushabac | Oct 1996 | A |
5587912 | Andersson et al. | Dec 1996 | A |
5590248 | Zarge et al. | Dec 1996 | A |
5605459 | Kuroda et al. | Feb 1997 | A |
5607305 | Andersson | Mar 1997 | A |
5614075 | Andre | Mar 1997 | A |
5621648 | Crump | Apr 1997 | A |
5645420 | Bergersen | Jul 1997 | A |
5645421 | Slootsky | Jul 1997 | A |
5655653 | Chester | Aug 1997 | A |
5683243 | Andreiko et al. | Nov 1997 | A |
5692894 | Schwartz et al. | Dec 1997 | A |
5725376 | Poirier | Mar 1998 | A |
5725378 | Wang | Mar 1998 | A |
5733126 | Andersson et al. | Mar 1998 | A |
5740267 | Echerer et al. | Apr 1998 | A |
5742700 | Yoon et al. | Apr 1998 | A |
5799100 | Clarke et al. | Aug 1998 | A |
5800174 | Andersson | Sep 1998 | A |
5823778 | Schmitt et al. | Oct 1998 | A |
5848115 | Little et al. | Dec 1998 | A |
5857853 | van Nifterick et al. | Jan 1999 | A |
5866058 | Batchelder et al. | Feb 1999 | A |
5879158 | Doyle et al. | Mar 1999 | A |
5880961 | Crump | Mar 1999 | A |
5880962 | Andersson et al. | Mar 1999 | A |
5882192 | Bergersen | Mar 1999 | A |
5934288 | Avila et al. | Aug 1999 | A |
5957686 | Anthony | Sep 1999 | A |
5964587 | Sato | Oct 1999 | A |
5971754 | Sondhi et al. | Oct 1999 | A |
5975893 | Chishti et al. | Nov 1999 | A |
6015289 | Andreiko et al. | Jan 2000 | A |
6044170 | Migdal et al. | Mar 2000 | A |
6044309 | Honda | Mar 2000 | A |
6049743 | Baba | Apr 2000 | A |
6054990 | Stewart | Apr 2000 | A |
6062861 | Andersson | May 2000 | A |
6068482 | Snow | May 2000 | A |
6099314 | Kopelman et al. | Aug 2000 | A |
6123544 | Cleary | Sep 2000 | A |
6151404 | Pieper | Nov 2000 | A |
6152731 | Jordan et al. | Nov 2000 | A |
6183248 | Chisti et al. | Feb 2001 | B1 |
6190165 | Andreiko et al. | Feb 2001 | B1 |
6205243 | Migdal | Mar 2001 | B1 |
6210162 | Chishti et al. | Apr 2001 | B1 |
6212442 | Andersson et al. | Apr 2001 | B1 |
6217325 | Chisti et al. | Apr 2001 | B1 |
6217334 | Hultgren | Apr 2001 | B1 |
6227850 | Chishti et al. | May 2001 | B1 |
6244861 | Andreiko et al. | Jun 2001 | B1 |
6250918 | Sachdeva et al. | Jun 2001 | B1 |
6260000 | Karasaki et al. | Jul 2001 | B1 |
6300958 | Mallet | Oct 2001 | B1 |
6309215 | Phan et al. | Oct 2001 | B1 |
6315553 | Sachdeva et al. | Nov 2001 | B1 |
6318994 | Chishti et al. | Nov 2001 | B1 |
6322359 | Jordan et al. | Nov 2001 | B1 |
6350119 | Jordan et al. | Feb 2002 | B1 |
6350120 | Sachdeva et al. | Feb 2002 | B1 |
6369815 | Celniker et al. | Apr 2002 | B1 |
6371761 | Cheang et al. | Apr 2002 | B1 |
6382975 | Poirier | May 2002 | B1 |
6398548 | Muhammad et al. | Jun 2002 | B1 |
6402707 | Ernst | Jun 2002 | B1 |
6409504 | Jones et al. | Jun 2002 | B1 |
6431870 | Sachdeva | Aug 2002 | B1 |
6463344 | Pavloskaia et al. | Oct 2002 | B1 |
6463351 | Clynch | Oct 2002 | B1 |
6471512 | Sachdeva et al. | Oct 2002 | B1 |
6482298 | Bhatnagar | Nov 2002 | B1 |
6512994 | Sachdeva | Jan 2003 | B1 |
6514074 | Chishti et al. | Feb 2003 | B1 |
6524101 | Phan et al. | Feb 2003 | B1 |
6540512 | Sachdeva et al. | Apr 2003 | B1 |
6545678 | Ohazama | Apr 2003 | B1 |
6554611 | Chishti et al. | Apr 2003 | B2 |
6558162 | Porter et al. | May 2003 | B1 |
6572372 | Phan et al. | Jun 2003 | B1 |
6602070 | Miller et al. | Aug 2003 | B2 |
6629840 | Chishti et al. | Oct 2003 | B2 |
6633789 | Nikolskiy et al. | Oct 2003 | B1 |
6665570 | Pavloskaia et al. | Dec 2003 | B2 |
6688886 | Hughes et al. | Feb 2004 | B2 |
6705863 | Phan et al. | Mar 2004 | B2 |
6722880 | Chishti et al. | Apr 2004 | B2 |
20020006597 | Andreiko et al. | Jan 2002 | A1 |
20030009252 | Pavlovskaia et al. | Jan 2003 | A1 |
20030139834 | Nikolskiy et al. | Jul 2003 | A1 |
20030224311 | Cronauer | Dec 2003 | A1 |
20040128010 | Pavlovskaia et al. | Jul 2004 | A1 |
20050055118 | Nikolskiy et al. | Mar 2005 | A1 |
Number | Date | Country |
---|---|---|
3031677 | May 1979 | AU |
517102 | Jul 1981 | AU |
5598894 | Jun 1994 | AU |
1121955 | Apr 1982 | CA |
2749802 | May 1978 | DE |
69327661 | Jul 2000 | DE |
091876 | Oct 1983 | EP |
299490 | Jan 1989 | EP |
376873 | Jul 1990 | EP |
490848 | Jun 1992 | EP |
0667753 | Aug 1995 | EP |
774933 | May 1997 | EP |
541500 | Jun 1998 | EP |
731673 | Sep 1998 | EP |
463897 | Jan 1980 | ES |
2369828 | Jun 1978 | FR |
2652256 | Mar 1991 | FR |
1550777 | Aug 1979 | GB |
53-058191 | May 1978 | JP |
04-028359 | Jan 1992 | JP |
08-508174 | Sep 1996 | JP |
WO 9008512 | Aug 1990 | WO |
WO 9104713 | Apr 1991 | WO |
WO 9410935 | May 1994 | WO |
WO9832394 | Jul 1998 | WO |
WO 9844865 | Oct 1998 | WO |
WO 9858596 | Dec 1998 | WO |
Number | Date | Country | |
---|---|---|---|
20020055800 A1 | May 2002 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09576721 | May 2000 | US |
Child | 09888261 | US | |
Parent | 09506419 | Feb 2000 | US |
Child | 09576721 | US |