Help on Using PSDB

Help See Long Description Concepts - Overview The words " -document in RFS - critical issue " have been added to certain Issues that have potential for injury. Please be sure to document these issues with details in the RFS for the call. Include any details that may help the CHU determine if there was an injury There is a help concept for each concept type. The concept types are: Issue Cause/Troubleshooting Error Resolution Product Software Component Smartminer. General usage information is shown first. See each concept type for How to Contribute information. DO NOT use (select) a help concept to enter new data into the Data Base In addition, this concept discusses Effective searching and Knowledge Object Requirements . Back to Top Effective Searching in the CT PSDB How to find what you are looking for: To effectively use any search engine, it is important to understand the rules. PSDB uses two different search engines simultaneously -one to search “Structured Knowledge” -The other to search unstructured (SmartMiners) - -The Searches work differently When searching SmartMiner:Search the same way you searched Clarify – same way you would search Google or Yahoo When Searching PSDB, if you search the same way, you will NOT find the information you want. The search must be performed differently. PSDB will search for a ALL words, Exact phrase will rank higher than a simple word match in most cases. If you have an Error Number or Part Number, search for the number only . Otherwise, search for a short phrase . LESS IS BEST WHEN SEARCHING PSDB The more text that you enter, the more opportunity for the processor to find words, parts of words, etc. You will get results Sometimes lots of them Observe the Ranking (percentage) Yellow means TEXT match only - no intelligence yet Checkmark the box or, click on yes and back in long description to allow the Knowledge Processor to return INTELLIGENCE! PSDB returns the known links - GREEN. When searching in the CT Knowledge Base there are some key words that may be helpful. PDS - (Proactive Diagnostic Services) These are Engineering validated troubleshooting tips & fixes CTIQ - (CT Image Quality) Library of artifacts, troubleshooting and resolutions. Informative - Check the box next to Informative in the Cause / Troubleshooting concept to find many useful how to knowledge objects may also search for how to Troubleshoot - Troubleshooting techniques Need to know - Click on Need to Know FMI Information Issue Concept - Then select FMI of interest from the resolution concept, open the long description. This concept will contain all known issues with the FMI, and the instructions to allow FE to complete the FMI successfully. Network - Network Troubleshooting. FMI - FMI Information. Service Note - Service Note information. QuickScripts - a collection of Unix based scripts for CT and PET OS Back to Top Knowledge Object Requirements The required concepts for any PSDB Knowledge object are Issue, Cause, Resolution and Product. If the resolution is a software fix then software version is also required. If the resolution is a part then Component is required. Normally, there is not both a software version and a component in a Knowledge Object. Please search for existing knowledge before creating new concepts. Back to Top Issue Concept - The problem from the customer's perspective; the actual incident they're reporting. Usage information Indicate if this applies to the situation. Requirements One Issue concept per Knowledge Object Long Description should have supporting information. If this is an Artifact then include an example. Use proper artifact names when describing an artifact. Back to top To add a new Issue concept ... Select the correct concept type ←1 Name the concept ** ←2 Add Synonyms if needed. ** ←3 Add a short Description. ** ←4 <click> edit to add the Long Description ** ←5 Add attachments if needed ** ←6 <click> Add Concept to finish. ←7 ** Details are discussed below 1→ 2→ 3→ 4↔ 5→ ←6 7→ Name The problem from the customer's perspective; the actual incident they're reporting. If the Issue has the potential to cause patient or operator injury, or equipment damage the words " - document in RFS - critical issue " shall be entered at the end of the name Include exact text from the User Interface of what they're seeing at the present. i.e "Pink popup with message" Include other related indicators such as lamps, noises, or odors. DO NOT include error numbers. For artifacts use the common descriptions found in QA documents from HQ Band Center Smudge Center Artifact Rings Streaks Center Spot Update the artifact library. Example: Bright spot artifact appears off center in head scans. For information only issues, use the phrase HOW TO followed by the service action statement. Example: How to reset the image database. Synonyms Use words that mean the same thing as a particular Concept Name Include common misspellings Don't include suffixes - they are stripped before processing. All words are used as single words - not as phrases. Short Description May contain info to clarify what is shown in the name Should tell if the Long Description contains more info. Leave the Short Description blank if the Name and Long Description are identical. Most of the time the Short Description will simply say "See Long Description for ...." Most Used See Long Description for more information. See Long Description for conditions . See Long Description for artifact. Long Description Include one or more of the following Include Short Description only if there is not other content. ( Do Not leave it blank....in order to allow feedback ) Perform a Screen Snapshot of user interface demonstrating issue and insert it in the html editor. Insert a .jpg file demonstrating the image artifact issue. Include the Major / Minor functions where only when applicable. Include other conditions necessary to reproduce the issue. Notes about the Long Description editor: Safest way to enter text is with the text tool. ←1 Standard Text Formatting buttons exist to change the color, look, font and alignment of your entered text. ←2 Insert images with the upload image button. ←3 Images should be either JPG if it is a picture or GIF if it is a drawing or schematic. See attachment. Provide the drawing number so that the end user can look it up if needed. Images cannot be wider than 600 pixels. That is the maximum width for printing solutions to a printer. If providing an image from a patient. Download the image to Javista first. Use the [Screen Save Active Image] button to save it in the original image size. (usually 512x512 for Axial. May be bigger for Scouts) Use Paint to add any lines or text to explain the artifact. Naming format for images in PSDB. No Spaces in name. ImageName_TodaysDATE_initials.file type. Example: TestImage_12Mar09_xyz.gif Note: If someone uses the name you create to enter their image, they will over write your image. Conversely, if you use a name that someone else already used, you will over write their image. Be Careful. Make your name unique. If you can not read the writing on the drawing then the end user will not be able to either. If it is important then fix it before entering into PSDB If an image already exists in PSDB, and you want to reuse it, use the Insert Image button. ←4 If you know the name of the image just enter it in the Source Path area. If you want to search use the […] Box. Spell Check your work. ←5 Use source view to edit the HTML directly or to fix problems. ←6 1↑ 2↔ 3→ 4↑ 5↑ 6↓ Acceptable attachment types See the attachment for complete information.