METHODS AND SYSTEMS FOR INTEGRATED DESIGN WORKFLOW BETWEEN AN INTRAORAL SCANNER, A DESIGN SERVICE AND A MILLING CENTER

Abstract

Methods and systems for integrated design workflow within a dental product management system. This includes a design connect platform receiving a dental product order, creating a dental product case based on the dental product order, and assigning the dental product case to a design service based on a restoration type provided in the dental product order. The design connect platform provides access to the dental product case via a designer portal graphical user interface (GUI) of the design connect platform. The designer portal GUI provides a workspace for creating a dental product design. Also, the designer portal GUI sends the dental product design to a milling center for fabricating a dental product.

Description

FIELD

This disclosure relates generally to dental management methods and systems between one or more dental offices and one or more dental labs. More specifically, this disclosure relates to methods and systems for providing integrated design workflow between one or more intraoral scanners, one or more design services and one or more milling centers.

BACKGROUND

Dental offices, dental laboratories and dental service organizations (DSOs) typically work together to prepare dental products for patients. These dental products can include, for example, crowns, bridges, dentures, dental implants, orthodontics, dental restorations, etc.

To order a dental product, one or more staff members at a dental office accesses an online web portal for the dental lab they want to prepare the product, fills out a dental product order form using the dental lab web portal, and attaches any additional information (e.g., a dental product prescription, X-rays, photos, etc.) that may be needed by the dental lab. When the dental lab receives the dental product order, a lab technician reviews the information, fabricates the dental product, and mails the product back to the dental office.

SUMMARY

This disclosure relates generally to dental management methods and systems between one or more dental offices and one or more dental labs. More specifically, this disclosure relates to methods and systems for providing integrated design workflow between one or more intraoral scanners, one or more design services and one or more milling centers.

In particular, the embodiments described herein can provide a delivery system-based virtual office that can connect a dental lab to a design center. In some embodiments, the design connect platform can provide design services, chairside and artificial intelligence (AI) based quality control verification and can integrate directly with one or more manufacturing lab systems. Also, the embodiments described herein can provide automated task management and planning as well as business insights including, for example, real time turnaround time and quality reports.

Also, the embodiments described herein can provide intuitive work assignments based on priorities, skill sets, and specification of particular dental product orders.

In some embodiments, a design connect platform can provide a queue management system that can automatically allocate a dental product order to an appropriate design technician based on different rule sets including, for example, particular design technician skills and expertise. Accordingly, a design technician is not provided a list of dental product orders to choose from but is assigned dental product orders from the queue management system.

In some embodiments, the design connect platform can read metadata and can create a dental product order based on metadata stored in a scanned image data (e.g., a three dimensional scanned image) such that manual information entry of a dental product order is not required. In some embodiments, the scanned image data and any prescription information stored as metadata can be exported by an intraoral scanner and imported from a dental product management platform and/or the design connect platform. For example, in some embodiments, only a small portion (e.g., 10%) of dental product orders require manual entry due to human errors, metadata information misplaced, a new intraoral scanner is connected to the design connect platform and/or the dental product management software that has not yet been integrated, for example, by the dental product management platform.

In one embodiment, a method for integrated design workflow within a dental product management system is provided. This includes a design connect platform receiving a dental product order, creating a dental product case based on the dental product order, and assigning the dental product case to a design service based on a restoration type provided in the dental product order. The design connect platform provides access to the dental product case via a designer portal graphical user interface (GUI) of the design connect platform. The designer portal GUI provides a workspace for creating a dental product design. Also, the designer portal GUI sends the dental product design to a milling center for fabricating a dental product.

In another embodiment, a dental product management system configured to provide integrated design workflow is provided. The dental product management system includes a design connect platform configured to receive a dental product order, create a dental product case based on the dental product order, and assign the dental product case to a design service based on a restoration type provided in the dental product order. The design connect platform includes a designer portal GUI. The design connect platform is configured to provide access to the dental product case via the designer portal GUI. Also, the designer portal GUI is configured to provide a workspace for creating a dental product design file and send the dental product design file to a milling center for fabricating a dental product.

BRIEF DESCRIPTION OF THE DRAWINGS

References are made to the accompanying drawings that form a part of this disclosure, and which illustrate embodiments in which the systems and methods described in this Specification can be practiced.

FIG. 1 illustrates a dental product management system, according to one embodiment.

FIG. 2 illustrates a flowchart of a method for providing integrated design workflow between an intraoral scanner, a design service computer and a milling center computer, according to one embodiment.

FIG. 3 illustrates a screenshot of a customer portal GUI provided by a design connect platform for display, for example, on a dental lab computer, according to one embodiment.

FIGS. 4A and 4B illustrate screenshots of a designer portal GUI provided by a design connect platform for display on a design service computer, according to one embodiment.

FIG. 5 is a schematic diagram of architecture for a computer device, according to one embodiment.

Like reference numbers represent like parts throughout.

DETAILED DESCRIPTION

This disclosure relates generally to dental management methods and systems between one or more dental offices and one or more dental labs. More specifically, this disclosure relates to methods and systems for providing integrated design workflow between one or more intraoral scanners, one or more design services and one or more milling centers.

It is noted that: U.S. application Ser. No. ______, “METHODS AND SYSTEMS FOR BI-DIRECTIONAL INTEGRATION BETWEEN AN INTRAORAL SCANNER AND A DENTAL LAB,” (attorney docket no: 21107.0002USU1); and U.S. application Ser. No. ______, “METHODS AND SYSTEMS FOR FINANCIAL MANAGEMENT AND RECONCILIATION WITHIN A DENTAL PROJECT MANAGEMENT SYSTEM,” (attorney docket no: 21107.0004USU1); all filed concurrently herewith on Mar. 24, 2023, and the contents of which are incorporated herein by reference.

FIG. 1 illustrates a dental product management system 100, according to one embodiment. The system 100 includes an intraoral scanner (IOS) 105 at a dental office, a dental lab computer 110 at a dental lab, a dental service organization (DSO) computer 112 at a DSO that are connected to a dental product management platform 120 via a network 118. The system 100 also includes a design service computer 114 and a milling center computer 116 connected to a design connect platform 122 via the network 118. The dental product management platform 120 is connected to the design connect platform 122 via the network 118. It will be appreciated that while only a single intraoral scanner, dental lab, DSO, design service and milling center are shown in FIG. 1, in other embodiments there may be multiple intraoral scanners, dental labs and/or DSOs connected to the dental product management platform 120 and there may be multiple design services and/or milling centers connected to the design connect platform 122.

The intraoral scanner 105 is an electronic device configured to obtain image data (e.g., 3D image data) of anatomical structures within the mouth of a patient. The image data can be used to create a dental product such as, for example, a crown, bridge, denture, dental implant, orthodontic, dental restoration, etc. The intraoral scanner 105 can be located at, for example, a dental office. The intraoral scanner 105 includes a computer 106 and a wand 108. An operator (e.g., dentist, dental hygienist, technician, etc.) at a dental office can use the wand 108 to scan a patient's mouth to obtain image data. The computer 106 can include one or more processors for both controlling operation of the wand 108, including coordinating the scanning and in reviewing and processing the scanning and generation of the image data including surface and internal features. The one or more processors may include or may be coupled with a memory for storing the scanned image data (surface data, internal feature data, etc.). The computer 106 can include one or more inputs (e.g., buttons, touchscreen, keyboard, etc.) to allow operator input for controlling scanning and operation of the intraoral scanner 105. Also, the computer 106 can include a display for allowing the operator to view the scanned image data and other information related to operation of the intraoral scanner 105. The computer 106 can also include communications circuitry, including wireless or wired communications circuitry, for communicating with the wand 108 and/or accessing the dental product management platform 120 via network 118. For example, the computer 106 may be configured to allow the operator to prepare a dental product prescription and combine scanned image data with the dental product prescription using the dental product management platform 120. The computer 106 can be the same as or similar to aspects of the computer device 500 as shown and described in accordance with FIG. 6 below.

The dental lab computer 110 is a computer at a dental lab that is configured to receive dental product prescriptions with scanned image data, fabricate a desired dental product as requested in the dental product prescription, and provide the fabricated dental product to the desired recipient (e.g., a dental office where the intraoral scanner 105 is located). In some embodiments, the dental lab computer 110 is at a location different from the location of the intraoral scanner 105. The dental lab computer 110 is configured to access the dental product management platform 120 via the network 118 to, for example, receive dental product prescriptions and scanned image data. The dental lab computer 110 can be the same as or similar to aspects of the computer device 500 as shown and described in accordance with FIG. 6 below.

The DSO computer 112 is a computer of a DSO that is configured to provide business management and support for one or more dental offices including a dental office where the intraoral scanner is located. In some embodiments, the DSO computer 112 is at a location different from the locations of the intraoral scanner 105 and the dental lab computer 110. The DSO computer 112 is configured to access the dental product management platform 120 via the network 118 to, for example, track dental product management status between one or more dental offices and one or more dental labs, verify and approve invoicing between one or more dental offices and one or more dental labs, obtain quality analysis of dental product orders, obtain dental product orders volume analysis, obtain purchase value analysis of the dental product orders, obtain turnaround time for dental product orders for the one or more dental labs, obtain benchmarking analysis of the dental product orders, etc. The DSO computer 112 can be the same as or similar to aspects of the computer device 500 as shown and described in accordance with FIG. 6 below.

The dental product management platform 120 is configured to provide an online management platform that can connect one or more dental offices (e.g., via an intraoral scanner), one or more dental labs, and one or more DSOs. The intraoral scanner 105, the dental lab computer 110, and the DSO computer 112 can access the dental product management platform 120 via, for example, a graphical user interface (GUI) accessible via a website and/or online software application. The dental product management platform 120 can include one or more application programming interfaces (APIs) that enable, for example, bi-directional intraoral scanner integration between the intraoral scanner 105 and the dental lab computer 110 (as shown in FIG. 2 and described in more detail below); prescription standardization across digital and non-digitized dental product prescriptions across all participating dental offices and dental labs (as shown in FIGS. 4A and 4B and described in more detail below); financial reconciliation from an initial patient visit through a dental office dental product prescription creation, manufacturing lab invoice with dental product order sign off, and DSO payment reconciliation; and interactive voice response (IVRS) to provide order specific and lab specific information on a dental product order, shipment, invoice, billing statuses, etc. In some embodiments, the dental product management platform 120 can be supported by one or more servers similar to the server device 535 shown and described in accordance with FIG. 6 below. The dental product management platform 120 is also configured to communicate with the design connect platform 122. In some embodiments, the dental product management platform 120 and the design connect platform 122 are part of the same platform. For example, in some embodiments the dental product management platform 120 can be connected to the design connect platform 122 via an interface layer. In some embodiments, the dental product management platform 120 can be a cloud based application platform.

The design service computer 114 is a computer configured to provide designer services to design a dental product. In some embodiments, the design service computer 114 is a computer of a design service that is configured to provide designer services for one or more dental offices including a dental office where the intraoral scanner is located. In some embodiments, the design service computer 114 is at a location different from the locations of the intraoral scanner 105 and the dental lab computer 110. In some embodiments, the design computer 114 can be located at a dental office where the intraoral scanner 105 is located. In some embodiments, the design computer 114 can be located at a design center where the dental lab computer 110 is located. The design service computer 114 is configured to access the design connect platform 122 via the network 118 to, for example, obtain dental product order(s) with dental product prescription and scanned image data to allow a designer to generate a design of the desired dental product. The design service computer 114 can be the same as or similar to aspects of the computer device 500 as shown and described in accordance with FIG. 6 below.

The milling center computer 116 is a computer of a milling center that is configured to provide milling services for one or more dental offices including a dental office where the intraoral scanner is located. In some embodiments, the milling center computer 116 can be located where the design computer 114 is located. In some embodiments, the milling center computer 116 is at a location different from the locations of the intraoral scanner 105, the dental lab computer 110, and potentially the design service computer 114. The milling center computer 116 is configured to access the design connect platform 122 via the network 118 to, for example, obtain a generated design of the dental product to allow the milling service to fabricate the desired dental product. In some embodiments, the milling center computer 116 can be configured to access the design connect platform 122 via the network 118 to, for example, obtain dental product order(s) with a dental product prescription and scanned image data to allow a designer at the milling center to generate a design of the desired dental product and then allow the milling service to fabricate the desired dental product. In some embodiments, the milling center computer 116 can be configured to access the dental product management platform 120 via the network 118 to, for example, obtain dental product order(s) with a dental product prescription and scanned image data directly from, for example, the intraoral scanner 105 to allow a designer at the milling center to generate a design of the desired dental product and then allow the milling service to fabricate the desired dental product. The milling center computer 116 can be the same as or similar to aspects of the computer device 500 as shown and described in accordance with FIG. 6 below.

The design connect platform 122 is configured to provide an online design platform that can connect one or more dental labs, one or more design services and one or more milling services. The dental lab computer 110, the design service computer 114 and the milling center computer 116 can access the design connect platform 122 via, for example, a graphical user interface (GUI) accessible via a website and/or online software application. The design connect platform 122 can enable, for example, an integrated design workflow and manufacturing from the dental lab (via the dental lab computer 110) to the design service (via the design service computer 114) and to the milling center (via the milling center computer 116); tracking dental product order(s); real time turnaround time and quality analysis reports; etc. Accordingly, a design center having the design service computer 114 can use the design connect platform 122 to manage design services. In some embodiments, the dental product management platform 120 can be supported by one or more servers similar to the server device 535 shown and described in accordance with FIG. 6 below. The design connect platform 122 is also configured to communicate with the dental product management platform 120. In some embodiments, the design connect platform 122 can interact with the dental product management platform 120 to access dental product orders submitted by, for example, the intraoral scanner 105. In some embodiments, the dental product management platform 120 and the design connect platform 122 are part of the same platform. In some embodiments, the dental product management platform 120 can be a cloud based application platform.

In some embodiments, the design connect platform 122 can include a customer portal GUI (see FIG. 3), a designer portal GUI (see FIGS. 4A and 4B) and an admin portal GUI. The customer portal GUI can be accessible via the dental lab computer 110. In some embodiments, the customer portal GUI is configured to provide a dashboard that can display live dental product orders, on hold dental product orders, in production dental product orders, completed dental product orders, turnaround time for completed dental product orders, etc. In some embodiments, a user, via the customer portal GUI, can upload a dental product prescription and/or scanned image data, select a turnaround time, a destination, a design software, a model requirement, a design approval requirement before placing the dental product order, etc. In some embodiments, the customer portal GUI can also display a dental product order list that includes dental product orders that are new, live on hold, in production, completed, cancelled, etc. In some embodiments, the customer portal GUI can support, for example, dental product order cancellation requests, dental product re-design requests, dental product quality concern requests, dental product billing/payment issue requests, customer portal GUI issue requests, file/attachment issue requests, etc. In some embodiments, the customer portal GUI can store and support user accounts and design preferences for a particular user profile. In some embodiments, the customer portal GUI can include options to make payment(s), access invoice(s), and review payment history. In some embodiments, the customer portal GUI can provide the user with production status on one or more dental product orders, a daily dental product order report and can provide a dental product order archive.

The designer portal GUI can be accessible via the design service computer 114. In some embodiments, the designer portal GUI is configured to provide a dashboard that can display dental product order design(s), dental product order validation(s), and dental product order draft(s). In some embodiments, the designer portal GUI can include intraoral scanner case upload (e.g., allow uploading of a three dimensional image of a patient), multiple dental product orders (e.g., allow opening multiple dental product orders to work on), new dental product order(s) (e.g., allow one or more files to be uploaded to create a new dental product order), and a timer (e.g., to calculate an amount of time to complete a particular dental product order being worked on). In some embodiments, the designer portal GUI can be used to find a particular dental product order by, for example, a dental product order number, a dental product order name, a draft dental product order number, etc. In some embodiments, the designer portal GUI can access a dental product order and begin working on the dental product order. This can include the designer portal GUI being able to access and display dental product order details, files/attachments, design preferences, messages, instructions, etc.

The admin portal GUI can be accessible via design service computer 114. In some embodiments, the admin portal GUI is configured to provide a dashboard that can display dental product accounts (e.g., customers), new dental product orders, dental product orders in progress, dental product order tasks, completed dental product orders, on hold dental product orders, re-work dental product orders, delayed dental product orders, cancelled dental product orders, rush dental product orders, dental product order feedback, signup requests that allow new dental lab(s) to register into the design connect platform 122 for approval prior using the design connect platform 122, etc.

In some embodiments, the admin portal GUI can include dental product transactions, accounts receivables, reports, master data, user management, admin setup, etc. In some embodiments dental product transactions can include action items for an administrator/supervisor of the design connect platform 122 to correct or address including: order correction for allowing an administrator/supervisor to correct any details of the dental product order once submitted by the customer (e.g., design preferences, remarks, design model only, turnaround time, etc.), upload/download files/attachment(s) for allowing an administrator/supervisor to upload a corrected file or any additional files for customer preference, support ticket(s) for allowing a support team of the dental product management platform 120 to reply to a customer request for support, shift allocation for allowing an administrator/supervisor to assign designers to different working shifts, redesign dental product order(s) for allowing an administrator/supervisor to initiate a customer request for a redesign of a completed order, re-assign dental product order(s) for allowing administrator/supervisor to initiate a customer request to assign dental product order(s) to a new designer/design lab, restart previously closed dental product order(s) for allowing an administrator/supervisor to initiate a customer request to restart an order put on hold by a designer/design lab (due to, for example, questions from the designer/design lab, questionable scan quality, etc.), etc.

In some embodiments, the accounts receivables can include sales invoice(s), customer receipt(s), open invoice(s), accounts receivable report(s), etc.

In some embodiments, reports can include duty roster report(s) providing information regarding dental product order allocation and regarding dental product orders processed during a shift, order tracker report(s) providing information regarding all open dental product orders with, for example, time stamps identifying stage of completion, daily count report(s) providing information regarding dental product orders booked during a specific date range, daily order trend report(s) providing information regarding an hourly trend of booked dental product orders versus completed dental product orders for a particular day, productivity report(s) providing information regarding number of dental product orders and dental product case types processed with the amount of time spent for a particular designer/design lab, accuracy report(s) providing information regarding a designer/design lab's quality of work based on quality control parameters, re-work report(s) (e.g., reports consisting of redesigned dental product cases for a selected date range and time that include lab name(s), order number(s), status, unit(s), case type(s), designer login(s), re-work types for internal or external customers, case timings, etc.), re-design report(s) (e.g., reports consisting of dental product order details gone for re-designing for a selected date and time range), turnaround time report(s) providing information regarding a turnaround time for a particular dental product order with a breakup of time spent during each stage of the dental product order, open ticket report(s) providing information regarding support requests raised and pending support tickets yet to be resolved, etc. to analyze and improve dental product design processes.

In some embodiments, master data can include details of dental product(s) including sale item(s) and finished design(s), material(s) required to be used in a restoration, material and product mapping that allows a dental product to be auto-selected based on material selected, price list(s) defining billing to customers based on a combination of factors (e.g., dental product(s), turn-around time, etc.), designation(s) indicating user role, employee(s) indicating designer users, manufacturer(s) indicating partners for fabricating the dental product order(s), customer(s) support type(s) (e.g., indicating categories for customers (e.g., dental labs) to raise questions and ask for help), re-design categories and code(s), quality control parameter(s) and template(s), customer preference, design code(s), etc. In some embodiments, user management can allow a user to handle management of the design center, customer(s), and manufacturer(s).

In an embodiment, the network 118 is representative of the Internet. In an embodiment, the network 40 can include one or more local area networks (LANs), one or more wide area networks (WANs), one or more wireless networks, one or more cellular data networks, suitable combinations thereof, or the like. In an embodiment, aspects of the network 118 can be the same as or similar to aspects of the network 540 as shown and described in accordance with FIG. 6 below.

FIG. 2 illustrates a flowchart of a method 200 for providing integrated design workflow within the dental product management system 100 (e.g., between the intraoral scanner 105, the design service computer 114 and the milling center computer 116), according to one embodiment. The method 200 begins at 205 whereby the dental lab computer 112 and/or the milling center computer 116 uploads a dental product order via the customer portal GUI of the design connect platform 122. The dental product order can include, for example, a dental product prescription, a requested turnaround time, milling center destination, a design software to be used, a restoration or model type, whether a design approval is required, order note(s) and attachments, etc. In some embodiments, the dental product order can be uploaded to the dental product management platform 120 and/or the design connect platform 122 by the intraoral scanner 105. The method 200 then proceeds to 210.

At 210, the design connect platform 122 reviews the dental product order and creates a dental product case (e.g., a sales order for the particular dental product order). In some embodiments, a user via the admin portal GUI can manually update portions of or the entire dental product case based on the dental product order when, for example, the dental product management system 100 fails to download or obtain all of the required information from the intraoral scanner 105. Once the dental product case is complete, the method 200 proceeds to 215.

At 215, the dental product case is assigned to a design queue to the design service computer 114 of a particular design service. In some embodiments, the dental product case can be assigned based on a restoration type. That is, different design services can have different priorities (e.g., whether the dental product case is assigned to a specific designer, whether the customer has opted for a premium service, whether the dental product case is a rush order, etc.), skill sets and/or varying skill levels. The design connect platform 122 can automatically assign the dental product case to the design computer 114 of a particular designer/design service based on the particular skill set(s) and/or skill level(s) required to create the design for the dental product case. That is, the design connect platform 122 can review the dental product order including the dental prescription to determine skills required to complete the design and automatically assign the dental product case to a designer/design service capable of completing the design. For example, the design connect platform 122 can assign the appropriate design service based on one or more of: dental product case type (e.g., whether the dental product case is for posterior, anterior, or a combination of both; whether the dental product case is for a single unit (tooth) or multiple units (teeth); which product is to be designed (e.g., an implant, a crown/bridge, other removables, etc.)); whether the customer opted for a premium service such as, for example, allocating a highly skilled designer/design lab (e.g., Level 5 designer), requesting value added services, etc.; a required turnaround time; the customer requesting the design; whether a model design is required; design tool to be used (e.g., 3Shape, Exocad, ect.); customer's (e.g., dental lab's) preferred designers; etc. For example, a Level 1 designer may be assigned a dental product case when the dental product case only involves a crown for one tooth and a Level 2 designer may be assigned the dental product case when the dental product case involves a crown for two or more teeth. The method 200 then proceeds to 220.

At 220, a designer of a particular design service that has been assigned the dental product can access the dental product case via the designer portal GUI of the design connect platform 122. Based on the requirements of the design product case, the designer can perform the necessary tasks to complete the design including one or more of margin marking at 225, crown designing at 230, model designing at 235 and appliance designing at 240. The designer can also track progress of the design product case using the designer portal GUI of the design connect platform 122. Once the design is completed, a completed design file is uploaded and saved by the designer via the designer portal GUI to the design connect platform 122. The method 200 then proceeds to 245.

At 245, the completed design file undergoes a quality control checkout. In some embodiments, the design file can be reviewed by a quality control person who has access to the design connect platform 122. If the quality of the completed design file is acceptable, the method 200 proceeds to 250. If the quality of the completed design file is not acceptable, the quality control person can correct any deficiencies in the completed design file and upload the corrected design file via the designer portal GUI to the design connect platform 122. The method can then proceed to 250. Optionally, if the quality of the completed design file is not acceptable, the quality control person can send the completed design file back to the designer via the designer portal GUI and the method can return to 220.

At 250, the design connect platform 122 determines whether a design approval is required based on instructions provided in the dental product order uploaded at 205. If a design approval is required, the method 200 proceeds to 255. If design approval is not required, the method 200 proceeds to 260.

At 255, the completed design file is provided to one of the dental lab computer 110, another person at the design center, or the customer for design approval based on instructions provided in the dental product order. For example, in some embodiments, a user at the dental lab computer 110 can approve the completed design using the customer portal GUI of the design connect platform 122. If the completed design file is approved, the method 200 proceeds to 260. If the completed design file is not approved, the method 200 proceeds back to 220 whereby the designer can access the dental product case and make the necessary changes to the completed design.

At 260, the completed design file is provided to the milling center computer 116 of a particular milling center to fabricate a dental product based on the completed design file. In some embodiments, the milling center to be used can be based on routing information provided in the dental product order. In some embodiments, the completed design file is provided to the milling center computer 116 via the design connect platform 122. In some embodiments, the milling center computer 116 can send the completed design file to a three-dimensional (3D) printer for fabrication. Once the dental product is fabricated using the completed design file, the method 200 then proceeds to 265.

At 265, the dental product with an invoice is shipped to the required dental office as requested in the dental product order for use with a patient.

Thus, the method 200 can provide an integrated workflow solution that seamlessly integrates intuitive design assignments based on priorities, skill sets, and specification of particular dental product orders.

FIG. 3 illustrates a screenshot of a customer portal GUI 300 provided by the design connect platform 122 for display, for example, on the dental lab computer 110, according to one embodiment. The customer portal GUI 300 includes a dashboard 305 that displays the number of dental product orders 310, the number of on hold dental product orders 315, the number of in production dental product orders 320, the number of design completed dental product cases 325, and the number of completed dental product cases 327. In some embodiments, selection of any of 310, 315, 320, 325, and 327 will direct the customer portal GUI 300 to display a respective list associated with each of the links 310, 315, 320, 325, 327. For example, user selection of 310 will cause the customer portal GUI 300 to display a list of dental product orders, user selection of 315 will cause the customer portal GUI 300 to display a list of on hold dental product orders, user selection of 320 will cause the customer portal GUI 300 to display a list of in production dental product orders, user selection of 325 will cause the customer portal GUI 300 to display a list of design completed dental product cases (e.g., completed dental product cases in which the completed design file has not yet been downloaded by a milling team/manufacturer for fabrication), and user selection 327 will cause the customer portal GUI 300 to display a list of completed dental product orders (e.g., all completed dental product cases regardless of whether the completed design file has been downloaded) over a set period of time (e.g., 7 days). The dashboard 305 also includes a display 330 of turnaround time for completed dental product orders. The display 330 shown in FIG. 3 illustrates a graphical display of the number of orders completed and the number of orders completed in a set turnaround time over a set period of time. It will be appreciated that in other embodiments, the display 330 can illustrate the turnaround time of dental products in other graphical formats. The customer portal GUI 300 also includes a menu 335 that includes a variety of options for the user. The menu 335 shown in FIG. 3 includes: an upload link 340 that allows a user to upload a dental product prescription and/or scanned image data; an orders sub menu 340 that includes a link 342a to view new dental product orders, a link 342b to display live dental product orders, a link 342c to display on hold dental product orders, a link 342d to display in production dental product orders, a link 342e to display completed dental product orders, and a link 342f to display cancelled dental product orders; a support link 346; a profile sub menu 348 that includes a link 348a to access user accounts and a link 348b to access design preferences; a payment sub menu 350 that includes a link 350a to make a payment, a link 350b to view user invoices, and a link 350c to view payment history; a daily dental product order report link 352; and an archive link 354. The customer portal GUI 300 can also allow a user to select a turnaround time for a particular dental product order, a destination for a particular dental product order, a design software for use on a particular dental product order, a model requirement for a particular dental product order, a design approval requirement for a particular dental product order, etc. In some embodiments, the customer portal GUI 300 can also support, for example, dental product order cancellation requests, dental product re-design requests, dental product quality concern requests, dental product billing/payment issue requests, customer portal GUI issue requests, file/attachment issue requests, etc.

FIGS. 4A and 4B illustrate screenshots of a designer portal GUI 400, 455 provided by the design connect platform 122 for display on the design service computer 114, according to one embodiment. The designer portal GUI 400 shown in FIG. 4A includes a dashboard 405 that displays the number of dental product orders in queue 410, the number of dental product order for re-design 415, the number of dental product orders assigned to the user 420 and the number of user drafts 425. In some embodiments, selection of any of 410, 415, 420 and 425 will direct the designer portal GUI 400 to display a respective list associated with each of the links 410, 415, 420, 425. For example, user selection of 410 will cause the designer portal GUI 400 to display a list of dental product orders in queue, user selection of 415 will cause the designer portal GUI 400 to display a list of on dental product orders for re-design, user selection of 420 will cause the designer portal GUI 400 to display a list of dental product orders assigned to the user, and user selection of 425 will cause the designer portal GUI 400 to display a list of user drafts of particular dental product orders. The designer portal GUI 400 also includes new order link 430 that allows a user to create a new dental product order and a timer link 435 that allows a user to track the amount of time spent on a particular dental product order. The designer portal GUI 400 further includes a design workspace 440 that allows a user to work on a design of a particular dental product order. This can include the designer portal GUI 400 being able to access and display on the design workspace 440 dental product order details, files/attachments, design preferences, messages, instructions, etc. Further, the designer portal GUI 400 includes a search bar 445 with a search menu 450. In some embodiments, the search menu 450 can allow a user to search for a particular dental product order via the search bar 445 by, for example, a dental product order number, a dental product order name, a draft dental product order number, etc.

The designer portal GUI 455 shown in FIG. 4B is a quality control (QC) portal for scan validation of a scan performed by the IOS 105 and for uploading a dental product case in place of a customer. The designer portal GUI 455 can be used, for example, for chairside quality control of a scan performed by the IOS 105, during a QC checkout (e.g., at 245 in FIG. 2), etc. The designer portal GUI 455 includes a dashboard 460 that displays the number of designs 465, the number of validations 470, and the number of user drafts 425. In some embodiments, selection of any of 465, 470 and 425 will direct the designer portal GUI 455 to display a respective list associated with each of the links 465, 470, 425. For example, user selection of 465 will cause the designer portal GUI 455 to display a list of easy designs, user selection of 470 will cause the designer portal GUI 455 to display a list of easy validations, and user selection of 425 will cause the designer portal GUI 455 to display a list of user drafts of particular dental product orders. The designer portal GUI 455 also includes an upload IOS cases link 475 that allows a user to upload an IOS case (e.g., a digital three-dimensional image of a tooth, teeth, oral structure(s), etc. that requires digital designing) on behalf of or in place of a customer (e.g., dental lab), a multiple orders link 480 that allows a user to open multiple dental product orders for validation on a validation workspace 485, a new order link 430 that allows a user to create a new dental product order, and a timer link 435 that allows a user to track the amount of time spent on a particular dental product order. In some embodiments, the upload IOS cases link 475 can be selected when a dentist or dental office sends scanned image data to a dental lab for designing and the dental lab shares the scanned image data to an independent design center via the design connect platform 122. In some embodiments, the upload IOS cases link 475 can be selected when a dentist or dental office sends scanned image data to a first dental lab for designing and then the dentist or dental office decides to use a second dental lab instead of the first dental lab. The dentist or dental office can then send the scanned image data to the second dental lab via the design connect platform 122. In some embodiments, a customer (e.g., dental lab) may share credentials of the IOS 105 to a user (e.g., designer) and the user can use IOS cases link 475 to download dental product cases from an IOS portal on behalf of the customer to upload into the designer portal GUI 455. In some embodiments, the upload IOS cases link 475 can include a number of dental product cases that can be pulled at a time. For example, the upload IOS cases link 475 shown in FIG. 4B shows that five dental product cases can be pulled at a time whereby one dental product case can be assigned to the designer portal GUI 455 for validation and the other four cases can remain as drafts. Similar to the designer portal GUI 400 shown in FIG. 4A, the designer portal GUI 455 further includes the validation workspace 485 that allows a user to validate a design of a particular dental product order. This can include the designer portal GUI 455 being able to access and display on the validation workspace 485 dental product order details, files/attachments, design preferences, messages, instructions, etc. Further, the designer portal GUI 455 includes a search bar 445 with a search menu 450. In some embodiments, the search menu 450 can allow a user to search for a particular dental product order via the search bar 445 by, for example, a dental product order number, a dental product order name, a draft dental product order number, etc.

FIG. 5 is a schematic diagram of architecture for a computer device 500, according to an embodiment. The computer device 500 and any of the individual components thereof can be used for any of the operations described in accordance with any of the computer-implemented methods described herein.

The computer device 500 generally includes a processor 510, memory 520, a network input/output (I/O) 525, storage 530, and an interconnect 550. The computer device 500 can optionally include a user I/O 515, according to some embodiments. The computer device 500 can be in communication with one or more additional computer devices 500 through a network 540.

The computer device 500 is generally representative of hardware aspects of a variety of user devices 501 and a server device 535. The illustrated user devices 501 are examples and are not intended to be limiting. Examples of the user devices 501 include, but are not limited to, a desktop computer 502, a cellular/mobile phone 503, a tablet device 504, and a laptop computer 505. It is to be appreciated that the user devices 501 can include other devices such as, but not limited to, a wearable device, a personal digital assistant (PDA), a video game console, a television, or the like. In an embodiment, the user devices 501 can alternatively be referred to as client devices 501. In such an embodiment, the client devices 501 can be in communication with the server device 535 through the network 540. One or more of the client devices 501 can be in communication with another of the client devices 501 through the network 540 in an embodiment.

The processor 510 can retrieve and execute programming instructions stored in the memory 520 and/or the storage 530. The processor 510 can also store and retrieve application data residing in the memory 520. The interconnect 550 is used to transmit programming instructions and/or application data between the processor 510, the user I/O 515, the memory 520, the storage 530, and the network I/O 540. The interconnect 550 can be, for example, one or more busses or the like. The processor 510 can be a single processor, multiple processors, or a single processor having multiple processing cores. In some embodiments, the processor 510 can be a single-threaded processor. In an embodiment, the processor 510 can be a multi-threaded processor.

The user I/O 515 can include a display 516 and/or an input 517, according to an embodiment. It is to be appreciated that the user I/O 515 can be one or more devices connected in communication with the computer device 500 that are physically separate from the computer device 500. For example, the display 516 and input 517 for the desktop computer 502 can be connected in communication but be physically separate from the computer device 500. In some embodiments, the display 516 and input 517 can be physically included with the computer device 500 for the desktop computer 502. In an embodiment, the user I/O 515 can physically be part of the user device 501. For example, the cellular/mobile phone 503, the tablet device 504, and the laptop 505 include the display 516 and input 517 that are part of the computer device 500. The server device 535 generally may not include the user I/O 515. In an embodiment, the server device 535 can be connected to the display 516 and input 517.

The display 516 can include any of a variety of display devices suitable for displaying information to the user. Examples of devices suitable for the display 516 include, but are not limited to, a cathode ray tube (CRT) monitor, a liquid crystal display (LCD) monitor, a light emitting diode (LED) monitor, or the like.

The input 517 can include any of a variety of input devices or input means suitable for receiving an input from the user. Examples of devices suitable for the input 517 include, but are not limited to, a touchscreen, a keyboard, a mouse, a trackball, a button, a voice command, a proximity sensor, an ocular sensing device for determining an input based on eye movements (e.g., scrolling based on an eye movement), or the like. It is to be appreciated that combinations of the foregoing inputs 517 can be included for the user devices 501. In some embodiments the input 517 can be integrated with the display 516 such that both input and output are performed by the display 516.

The memory 520 is generally included to be representative of a random access memory such as, but not limited to, Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), or Flash. In some embodiments, the memory 520 can be a volatile memory. In some embodiments, the memory 520 can be a non-volatile memory. In some embodiments, at least a portion of the memory can be virtual memory.

The storage 530 is generally included to be representative of a non-volatile memory such as, but not limited to, a hard disk drive, a solid state device, removable memory cards, optical storage, flash memory devices, network attached storage (NAS), or connections to storage area network (SAN) devices, or other similar devices that may store non-volatile data. In some embodiments, the storage 530 is a computer readable medium. In some embodiments, the storage 530 can include storage that is external to the computer device 500, such as in a cloud.

The network I/O 525 is configured to transmit data via a network 540. The network 540 may alternatively be referred to as the communications network 540. Examples of the network 540 include, but are not limited to, a local area network (LAN), a wide area network (WAN), the Internet, or the like. In some embodiments, the network I/O 525 can transmit data via the network 540 through a wireless connection using Wi-Fi, Bluetooth, or other similar wireless communication protocols. In some embodiments, the computer device 500 can transmit data via the network 540 through a cellular, 3G, 4G, or other wireless protocol. In some embodiments, the network I/O 525 can transmit data via a wire line, an optical fiber cable, or the like. It is to be appreciated that the network I/O 525 can communicate through the network 540 through suitable combinations of the preceding wired and wireless communication methods.

The server device 535 is generally representative of a computer device 500 that can, for example, respond to requests received via the network 540 to provide, for example, data for rendering an online service (e.g., a website, an app, etc.) on the user devices 501. The server 535 can be representative of a data server, an application server, an Internet server, or the like.

Aspects described herein can be embodied as a system, method, or a computer readable medium. In some embodiments, the aspects described can be implemented in hardware, software (including firmware or the like), or combinations thereof. Some aspects can be implemented in a non-transitory, tangible computer readable medium, including computer readable instructions for execution by a processor. Any combination of one or more computer readable medium(s) can be used.

The computer readable medium can include a computer readable signal medium and/or a computer readable storage medium. A computer readable storage medium can include any tangible medium capable of storing a computer program for use by a programmable processor to perform functions described herein by operating on input data and generating an output. A computer program is a set of instructions that can be used, directly or indirectly, in a computer system to perform a certain function or determine a certain result. Examples of computer readable storage media include, but are not limited to, a floppy disk; a hard disk; a random access memory (RAM); a read-only memory (ROM); a semiconductor memory device such as, but not limited to, an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), Flash memory, or the like; a portable compact disk read-only memory (CD-ROM); an optical storage device; a magnetic storage device; other similar device; or suitable combinations of the foregoing. A computer readable signal medium can include a propagated data signal having computer readable instructions. Examples of propagated signals include, but are not limited to, an optical propagated signal, an electro-magnetic propagated signal, or the like. A computer readable signal medium can include any computer readable medium that is not a computer readable storage medium that can propagate a computer program for use by a programmable processor to perform functions described herein by operating on input data and generating an output.

An embodiment can be provided to an end-user through a cloud-computing infrastructure. Cloud computing generally includes the provision of scalable computing resources as a service over a network (e.g., the Internet or the like).

The terminology used in this specification is intended to describe particular embodiments and is not intended to be limiting. The terms “a,” “an,” and “the” include the plural forms as well, unless clearly indicated otherwise. The terms “comprises” and/or “comprising,” when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, and/or components.

With regard to the preceding description, it is to be understood that changes may be made in detail, especially in matters of the construction materials employed and the shape, size, and arrangement of parts without departing from the scope of the present disclosure. This specification and the embodiments described are exemplary only, with the true scope and spirit of the disclosure being indicated by the claims that follow.

Claims

1. A method for integrated design workflow within a dental product management system, the method comprising:

a design connect platform receiving a dental product order;

the design connect platform creating a dental product case based on the dental product order;

the design connect platform assigning the dental product case to a design service based on a restoration type provided in the dental product order;

the design connect platform providing access to the dental product case via a designer portal graphical user interface (GUI) of the design connect platform;

the designer portal GUI providing a workspace for creating a dental product design file;

the designer portal GUI sending the dental product design file to a milling center for fabricating a dental product.

2. The method of claim 1, further comprising performing a quality control checkout of the dental product design file.

3. The method of claim 1, further comprising providing access of the dental product design file to a dental lab computer for design approval.

4. The method of claim 1, further comprising reviewing the dental product design file prior to sending the dental product design file to a milling center for fabricating a dental product.

5. The method of claim 1, further comprising the design connect platform determining that a design approval is required based on instructions provided in the dental product order.

6. The method of claim 5, further comprising the designer portal GUI sending the dental product design file to the milling center for fabricating the dental product after design approval of the dental product design file.

7. A dental product management system configured to provide integrated design workflow, the dental product management system comprising:

a design connect platform configured to receive a dental product order, create a dental product case based on the dental product order, and assign the dental product case to a design service based on a restoration type provided in the dental product order,

wherein the design connect platform includes a designer portal graphical user interface (GUI), and wherein the design connect platform is configured to provide access to the dental product case via the designer portal GUI;

wherein the designer portal GUI is configured to provide a workspace for creating a dental product design file, and send the dental product design file to a milling center for fabricating a dental product.

8. The dental product management system of claim 7, wherein the design connect platform is configured to perform a quality control checkout of the dental product design file.

9. The dental product management system of claim 7, wherein the design connect platform is configured to provide access of the dental product design file to a dental lab computer for design approval.

10. The dental product management system of claim 7, wherein the design connect platform is configured to receive a design approval of the dental product design file prior to sending the dental product design file to a milling center for fabricating a dental product.

11. The dental product management system of claim 7, wherein the design connect platform is configured to determine that a design approval is required based on instructions provided in the dental product order.

12. The dental product management system of claim 7, wherein the designer portal GUI is configured to send the dental product design file to the milling center for fabricating the dental product after design approval of the dental product design file.