...
Once you have finished installing cTAKES and its separately-bundled resources, you will be able to see what cTAKES is capable of.
Prerequisites
Step
| Example | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. Make sure you have Java 1.8 or higher.
| Windows:
|
Install cTAKES
...
Step
| Example | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. On the cTAKES downloads page, download the User Installation package.
|
| |||||||||||||||||
2. (Recommended) Verify the downloaded files against a signature to ensure you have the proper and complete file. From the following directory, download the signature file that corresponds to your download from step 1 https://www.apache.org/dist/ctakes/ctakes-4.0.0/ Please do not download any of the files that end with .zip or .gz directly from apache.org/dist - use the downloads page listed in step 1 if you need to download cTAKES itself so that a mirror can be used. | No example | |||||||||||||||||
3. Unzip the file you downloaded into a directory that you want to be the cTAKES install location. The compressed files contain a single directory at the top level. This folder we will call <cTAKES_HOME>. It is the directory that contains subdirectories like bin, desc, resources, lib. You will need to refer to this directory later.
Linux:
| Windows:
| |||||||||||||||||
4. Download the cTAKES resources ZIP file with a matching version from the ctakesresources project (More information on cTAKES models). These resources are required to operate cTAKES.
| Windows:
| |||||||||||||||||
5. Copy (or move) the resources to cTAKES_HOME.
| Windows:
Linux:
Mac OSX:
| |||||||||||||||||
6. If you created your own dictionaries for use with a previous release of cTAKES and you plan to use them with cTAKES 4.0, you must convert your dictionaries to be compatible with cTAKES 4.0, which is described in the next section. The dictionaries installed by the above steps do not need to be converted. |
...
CAS Visual Debugger (CVD)
...
Step
| Example | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. Open a command prompt and change to the cTAKES_HOME directory, which is the directory that contains subdirectories like bin, desc, resources, lib. Depending on how you extracted the files,
|
Linux:
| ||||||||||||
2. This step uses AggregatePlaintextFastUMLSProcessor, which requires that you downloaded the cTAKES resources as described in step 4 of Install cTAKES (above) and that you added UMLS access rights (also above). If you haven't done those, you can use the AggregatePlaintextProcessor instead. Start the CAS Visual Debugger and load the AggregatePlaintextFastUMLSProcessor pipeline by running this command (at right)
The GUI opens and then loads the AggregatePlaintextFastUMLSProcessor pipeline. If it appears to be hung, look at the window where you entered the command and you will see what is happening. Once the analysis engine has successfully loaded you should see a tree in the Analysis Results frame:
| Windows:
Linux:
| ||||||||||||
3. Copy the example text from the next cell in this table and paste the contents into the Text section of CVD, replacing the text that is already there. |
| ||||||||||||
4. From the menu bar, click Run -> Run AggregatePlaintextFastUMLSProcessor. Note: If you would like to TEST some simple annotators to ensure it's working without UMLS, you can just load: /desc/ctakes-core/desc/analysis_egine/SentencesAndTokensAggregate.xml |
| ||||||||||||
5. You'll get a list of all the annotations for this clinical document in the Analysis Results frame. Annotations such as named entities, division by sentence, etc from the pipeline are viewable. To see one, in the Analysis Results frame, click on the key in front of:
This will show an AnnotationIndex in the lower frame. Select any annotation in that lower frame and you will see the text discovered in
Now select items in the lower frame to see the text being annotated. |
| ||||||||||||
To run other pipelines, use the Run-> Load AE menu bar command. Navigate to the file you wish to load, such as
Click Open.
|
Collection Processing Engine (CPE)
...
Step
| Example | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1. Open a command prompt and change to the cTAKES_HOME directory, which is the directory that contains subdirectories like bin, desc, resources, lib.
|
Linux:
| ||||||||||||
2. Create a directory for some test data. |
| ||||||||||||
3. The sample dictionary that does not require UMLS rights contains only a few terms. Create a file containing the sentence at right into the testdata directory. | The patient says they took 325 mg aspirin for knee pain. | ||||||||||||
4. Start the collection processing engine by running this command: | Windows:
Linux:
| ||||||||||||
5. This will bring up the Collection Processing Engine Configurator. In the Menu bar click File >Open CPE Descriptor | |||||||||||||
6. Navigate to the following file, which uses the AggregatePlaintextProcessor
| No example | ||||||||||||
7. Change the Collection Reader input directory to testdata, which contains the files to process Within the CAS Consumers pane of the same window, change the output directory to testdata/output | |||||||||||||
8. Click the Play button (green/blue play arrow near the bottom).
| |||||||||||||
9. You should see that one document was processed. You did process a collection of documents. In this case the collection only contained one just to show how to do it. Close the Performance Report window.
| |||||||||||||
10. Close the CPE application. You may be prompted to save changes. Since this was just a test you may click the No button. | No example |
...