| Answer / Solution
First Draft Translations
First Draft Translations are a powerful way for an Administrator to influence the draft output for specified instances to translate a specific word or group of words to something else. Corrections made during the editing process help improve future results. First Draft can learn good habits and bad habits based on transcribed documents in the past and edited documents going forward. Comparison through Consistency is KEY. For example, if some Transcriptionists are letting jobs go through with the term "glandular meatus" instead of the correct term "glanular meatus" First Draft is not able to learn the correct term. Administrators can use the FD Translations feature to override that learning and present the Transcriptionist with the correct term. This feature is extremely specific and will apply to an Author + Document Type.
- Administrator login and password for the IMC.
- Professional Edition of First Draft (KB407)
- In the IMC, go to the First Draft tab ⇒ Tuning sub-tab and click on the »Override Settings link:
- Select the Facility and then Author from the drop-down menu.
- Scroll down to the Professional Settings section, Translations option, and click the »Open link: (Please note that if there is no Translations option showing for an Author-DocType combination, then it is not available while the system builds a language model profile for this combination and will appear after the model has been built with system-generated translations. You will not be able to add manual entries until the system-generated entries are created.)
- The Translations window will open. The results listing includes the following columns:
- Phrase: This is what the draft is generating that you wish to have the system translate to something else.
- Translated To: This is what the draft will translate the specified phrase to.
- Added By: The System or Administrator who added each translation.
- Date Added: Date/Time each translation was added.
- % Translated: What percentage of the time the system detects that this translation occurs.
- Edit: Allows you to edit that entry.
- Mark Bad: Use this option to mark a translation as Bad. See details below.
- Options include:
- Filter/Search Results:
- There are two types of Translations. Choose from the Currently Viewing drop-down menu to see Translations for the selected Document Type.
- System Translations are added automatically in the background by the learning/adaptation process.
- User Translations are those added by an Administrator.
- Document Type: Choose from the "for" drop-down menu to change DocType.
- Translations Containing: If you are looking for a specific Translation enter the text in the Translation containing field.
- Note: If you have changed any of the drop-down menus or entered text in the Translations containing field you must click the Submit button to reload the page with results.
- Add Good Phrase: Adding a good phrase is manually adding a good translation for First Draft. For example, adding "impatient" to translate to "inpatient", so whenever "impatient" is detected by First Draft for the Author + DocType selected, it will automatically translate to "inpatient" for drafts generated after the Translation is saved.
- To add a good phrase for the selected DocType click on Add Good Phrase.
- Enter the Phrase. This is what the draft is generating that you wish to have the system translate to something else. In this example I have entered "critical portions suture".
- Enter the Translate to: This is what the draft will translate the specified phrase to. In this example I have entered "critical portions of the procedure".
- Click Submit.
- Drafts generated after this Translation is submitted will look for the exact phrase "critical portions suture" and always translate it to "critical portions of the procedure" for the selected Author + DocType combination.
- Note: Text entered in the Phrase and Translate to fields is very specific and looks for the words in order. If there is any variation in the words the translation will not occur. If there are several variations it is recommend that you add each one as a separate Good Phrase. See additional notes below.
- Add Bad Phrase: Adding a bad phrase tells the system to NOT do a certain translation. It should very rarely be needed. This would be if you previously added a translation and then later decided that rule wasn't any good, or if the system generated a rule and you didn't like it.
- Edit: Allows you to modify an entry if needed.
- Mark Bad: If a Good Phrase was added by the System or an Administrator in error you can mark it as a Bad Translation by clicking that link on the results list. This will apply to drafts generated after the change is saved.
- The FD Translation step happens before heading detection is applied, so you would not want to accidentally mess around with some important heading phrase entered during the FD Template process. See KB757 for details.
- Casing and Hyphenation are not considered as part of FD Translations because FD Translations are applied prior to casing and hyphenation. Example: FD actually recognizes "stage 1 sleep" because hyphenation rules are applied post speech recognition. In 100% of documents used for training/grading so far, the Transcriptionist has added a hyphen between stage and 1, so FD has learned that the hyphen is needed. Please instruct all MT's on the account to stop using the hyphen so the system can "unlearn" it. In this example, translations will never actually see "stage-1", and even if it somehow did (by adding a pronunciation), the hyphenation rules would add the hyphen back in.
- The InfraWare First Draft Dictionary is essentially the list of words that the First Draft Dictation Recognition service knows how to recognize. In order for a word to appear in the draft output it needs to be in the FD Dictionary. Therefore, all words entered as part of FD Translations need to be in the FD Dictionary. Please see KB571 for details on how to submit words to be added to the FD Dictionary.
- Hyphens: Do not include hyphens in the Phrase.
- Punctuation: Similar to Phrases within FD template fields (KB762), any punctuation included in a Phrase will need to be separated by a space on either side. For example: