Improved Office Action Shells, Forms, and Biblio Data Import
ClaimMaster 2019.5 features numerous improvements to the Office Action shells, forms, and PAIR tools:
Create multi-document packages with one click
Both Office Action shell and USPTO form tools now allow you to
simultaneously select and fill multiple documents with the same bibliographic information. The results could be saved to a specified directory or stored in a zip file. In addition, you can include other files, such as annotated Office Action, cited prior art, and clean claims as part of the package.
For example, with a few clicks, you can now generate an Office Action response packet (either saved to a directory or a zip file) that includes a wealth of information to help you respond to the substance of your office action without spending valuable time on formatting and document creation. For example, your OA response packet might include:
- Draft Response – an office action response shell with your application information, caption, response, current claim language, and rejection bases already populated;
- Office Action – an OCRed and annotated version of your office action, allowing you to quickly search the document for rejections, cited art and other key phrases;
- Cited Art – PDFs of the art cited in your office action; and
- Clean claims – a document containing clean claims without amendments for reporting.
- Client Letter – a letter that can be either mailed or emailed to inform your client of the rejection bases and art cited; and
- Client Reporting Email – a draft Outlook email (.msg) with all the necessary attachments and the summary of the Office Action.
Similarly, you can generate multi-document packets with the USPTO forms. To do so, select multiple forms to fill out and specify a destination directory/zip file.
Quickly Import PAIR Data from 3rd Party Docketing Systems
In this release, we’ve added a PAIR Cache import wizard that lets you quickly import bibliographic data from your docketing system into ClaimMaster. The import process is now very straightforward: (1) export bibliographic data from your docketing system to a CSV file, (2) load the CSV file into ClaimMaster’s import wizard, and (3) use the wizard to map the columns in the CSV file to the data used by ClaimMaster:
Once the data is loaded into ClaimMaster’s Private PAIR Cache, you will not need to access PAIR to get data for known application numbers, which can save a lot of time. To access the PAIR Cache Wizard, go to ClaimMaster->Preferences->Private PAIR Settings->Import from CSV tab.
Quickly Create ClaimMaster Shells from Existing Documents
We’ve also added a Shell Template wizard that lets you quickly convert any of your existing documents (e.g., previous Office Action responses) into ClaimMaster shells. All you need to do is to load the base document into the wizard and insert the desired replacement fields from the list into the document. After this, ClaimMaster will automatically convert the document into the required template format and add it to the list of available shell templates:
To access the Shell Wizard, go to ClaimMaster->Preferences->Shell Wizard
Customizable Office Action summary
The Office Action Browser tool now lets you customize not only the citation formation for the prior art, but also the major portions of text listing various rejections, objections, and allowances identified in the Office Action.
To access the this feature, go to ClaimMaster->USPTO Rejections, Shells, and Forms->Identify Rejections/Prior Art in the Office Action and switch to the OA Summary Text & Citations Settings tab.
Auto-Completing Fields in Boilerplate Entries
With ClaimMaster 2019.5, replacement fields (e.g., [INVENTOR], [EXAMINER], [ARTUNIT], [DATE], etc.) used in the boilerplate entry will be automatically updated when the boilerplate passage is inserted into the document, assuming the document contains the values for these fields. In particular, this data will be available if you use ClaimMaster’s shell generation feature to create Word shells, as the generated documents will also store the utilized replacement fields + data in the document’s metadata. The stored information can then be used to fill-in replacement fields in boilerplate paragraphs at any time later.
Click below to read about other improvements in this release: