IP Library Granted Patent US 11,789,682
Granted Patent B2
US 11,789,682 · App. 17/688,808 · Granted Oct 17, 2023

Printing 3D anatomical models for diagnostic and non-diagnostic uses

Inventors: Steven A. Nelson (San Jose, CA); Fred Herold (Boulder, CO); Ryan Hess (Cary, NC); Jeanette Wall (Warner Robins, GA); Patrick Gannon (Santa Rosa, CA); Gary Turner (Weston, FL)
Assignee: Ricoh Company, Ltd.
G06F3/1267B29C64/393G06F3/1204G06F3/1238G06F3/1272G06F21/608B33Y50/02
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,789,682
App. No.
17/688,808
Granted
Oct 17, 2023
Kind
B2
Abstract

Techniques for printing 3D anatomical models for diagnostic and/or non-diagnostic uses are provided. In one technique, a computing system (e.g., a 3D print portal) receives a first API call from a requester system via one or more APIs. The first API call indicates that a requester system has saved 3D printable files in a data repository. In response to receiving the first API call, the computing system sends, to the requester system, a user information form to initiate a production ordering process of printing the 3D printable files.

Claims (52)

1. A computing system comprising:

one or more processors; and

one or more memories storing instructions which, when processed by the one or more processors, cause:

receiving, from a requester system via one or more APIs, a first API call that the requester system has saved 3D printable files in a data repository; and

in response to receiving the first API call that indicates that the requester system has saved 3D printable files in the data repository, sending, to the requester system, a user interface form to initiate a production ordering process of printing the 3D printable files.

2. The computing system of claim 1 , wherein the instructions, when processed by the one or more processors, further cause:

uploading revised 3D printable files to the data repository using the one or more APIs;

sending, to the requester system, a second API call that an update has been made to the 3D printable files.

3. The computing system of claim 2 , wherein the instructions, when processed by the one or more processors, further cause:

receiving, from the requester system, a third API call that indicates that the update is approved.

4. The computing system of claim 1 , wherein the instructions, when processed by the one or more processors, further cause, prior to receiving the first API call:

receiving, from the requester system, a second API call to submit a production order;

in response to receiving the second API call, sending, to the requester system, an order number.

5. The computing system of claim 1 , wherein the instructions, when processed by the one or more processors, further cause:

based on credentials received from a reviewer device that is different than the computing system and the requester system, determining whether to grant, to the reviewer device, access to the 3D printable files.

6. The computing system of claim 5 , wherein the instructions, when processed by the one or more processors, further cause:

transmitting a second API call that indicates that a user of the reviewer device is granted access to the 3D printable files for review.

7. The computing system of claim 6 , wherein the instructions, when processed by the one or more processors, further cause:

receiving a third API call that indicates whether the 3D printable files are approved for 3D printing.

8. The computing system of claim 1 , wherein the instructions, when processed by the one or more processors, further cause:

synchronizing, via an API, with a database system that is separate from the computing system and the requester system, production data that comprises mailing addresses and contact information.

9. A method comprising:

receiving, from a requester system via one or more APIs, a first API call that the requester system has saved 3D printable files in a data repository; and

in response to receiving the first API call that indicates that the requester system has saved 3D printable files in the data repository, sending, to the requester system, a user interface form to initiate a production ordering process of printing the 3D printable files;

wherein the method is performed by one or more computing devices.

10. The method of claim 9 , further comprising:

uploading revised 3D printable files to the data repository using the one or more APIs;

sending, to the requester system, a second API call that an update has been made to the 3D printable files.

11. The method of claim 10 , further comprising:

receiving, from the requester system, a third API call that indicates that the update is approved.

12. The method of claim 9 , further comprising, prior to receiving the first API call:

receiving, from the requester system, a second API call to submit a production order;

in response to receiving the second API call, sending, to the requester system, an order number.

13. The method of claim 9 , further comprising:

based on credentials received from a reviewer device, determining whether to grant, to the reviewer device, access to the 3D printable files.

14. The method of claim 13 , further comprising:

transmitting a second API call that indicates that a user of the reviewer device is granted access to the 3D printable files for review.

15. The method of claim 14 , further comprising:

receiving a third API call that indicates whether the 3D printable files are approved for 3D printing.

16. The method of claim 9 , further comprising:

synchronizing, via an API, with a database system that is separate from a computing system that performs the method and the requester system, production data that comprises mailing addresses and contact information.

17. One or more storage media storing instructions which, when executed by one or more processors, cause:

receiving, from a requester system via one or more APIs, a first API call that the requester system has saved 3D printable files in a data repository; and

in response to receiving the first API call that indicates that the requester system has saved 3D printable files in the data repository, sending, to the requester system, a user interface form to initiate a production ordering process of printing the 3D printable files.

18. The one or more storage media of claim 17 , wherein the instructions, when processed by the one or more processors, further cause:

uploading revised 3D printable files to the data repository using the one or more APIs;

sending, to the requester system, a second API call that an update has been made to the 3D printable files.

19. The one or more storage media of claim 17 , wherein the instructions, when processed by the one or more processors, further cause, prior to receiving the first API call:

receiving, from the requester system, a second API call to submit a production order;

in response to receiving the second API call, sending, to the requester system, an order number.

20. The one or more storage media of claim 17 , wherein the instructions, when processed by the one or more processors, further cause:

based on credentials received from a reviewer device, determining whether to grant, to the reviewer device, access to the 3D printable files.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 11, 2025
From: RICOH COMPANY, LTD.
To: RICOH 3D FOR HEALTHCARE, LLC
Reel/Frame 073919/0839 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 5, 2025
From: RICOH COMPANY, LTD.
To: RICOH 3D FOR HEALTHCARE, LLC
Reel/Frame 073873/0432 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 8, 2022
From: NELSON, STEVEN A.; HEROLD, FRED; HESS, RYAN; WALL, JEANETTE; GANNON, PATRICK; TURNER, GARY
To: RICOH COMPANY, LTD.
Reel/Frame 059194/0460 →
Continuity (1)
Related Publication 20230280958A1 · Sep 7, 2023