Add an example to incorporate remote clinical pipeline and stave

[Leolty]

This PR fixes #42.

Description of changes

This PR is totally based on what has been done by Piyush, here is the reference: https://github.com/Piyush13y/forte/tree/745_clinical_pipeline_stave

The changes include:

1. The JSON files are serialized in the wrong way, and I fix this.
2. I modify some processors in the clinical_processing_pipeline.py, and add an argument to support PlainTextReader(). In case users may not have the mimic iii datasets, they can just use the sample data in the sample_data/notes.txt for the function test.
3. I add more instructions in README.md, according to the errors or obstacles I encountered when I set up the connection between the pipeline and stave.
4. I remove some files that were not used.

Bugs encountered

Initially, the version of Elasticsearch I downloaded is 8.2.2, and I failed the setup of this according to the tutorials. ( Many unsolvable bugs). When I change the version to 7.12.2 (given in README.md), everything works perfectly fine.

[codecov]

Codecov Report

Merging #43 (cedb045) into master (9ecd4a0) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
- Coverage   84.17%   84.14%   -0.04%     
==========================================
  Files           9        8       -1     
  Lines         512      511       -1     
==========================================
- Hits          431      430       -1     
  Misses         81       81              

Impacted Files	Coverage Δ
...te_medical/processors/icd_coding_processor_test.py
...s/forte_medical/readers/mimic3_note_reader_test.py
...dical/processors/negation_context_analysis_test.py
...tex/health/processors/icd_coding_processor_test.py	100.00% <0.00%> (ø)
...ealth/processors/negation_context_analysis_test.py	100.00% <0.00%> (ø)
...s/fortex/health/readers/mimic3_note_reader_test.py	96.29% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us.

[hunterhector]

A few comments, but overall, if this example is runnable it is fine with me. We can improve in the future.

[Leolty]

Could we leave these two issues metioned in the conversations in the future? I am not familiar with the ontology generation yet so it may take much time.

[hunterhector]

Could we leave these two issues metioned in the conversations in the future? I am not familiar with the ontology generation yet so it may take much time.

Actually, it might be important to understand the following items since they are the key for understanding our visualization:

1. Be able to update, and generate ontology
2. Understand how ontologies are related to Stave settings (examples/clinical_pipeline/chat_project.json)

[Leolty]

Could we leave these two issues metioned in the conversations in the future? I am not familiar with the ontology generation yet so it may take much time.

Actually, it might be important to understand the following items since they are the key for understanding our visualization:

1. Be able to update, and generate ontology
2. Understand how ontologies are related to Stave settings (examples/clinical_pipeline/chat_project.json)

Got it. Actually, I understand how the ontologies related to stave. I didn't understand what you meant at first, I thought it was about writing python code to automatically generate ontologies. So I think what you want me to do is to omit most of the ontologies that were already written, write only the extra ones we added here, and then use the generate ontology function to merge them?

[hunterhector]

Could we leave these two issues metioned in the conversations in the future? I am not familiar with the ontology generation yet so it may take much time.

Actually, it might be important to understand the following items since they are the key for understanding our visualization:

1. Be able to update, and generate ontology
2. Understand how ontologies are related to Stave settings (examples/clinical_pipeline/chat_project.json)

Got it. Actually, I understand how the ontologies related to stave. I didn't understand what you meant at first, I thought it was about writing python code to automatically generate ontologies. So I think what you want me to do is to omit most of the ontologies that were already written, write only the extra ones we added here, and then use the generate ontology function to merge them?

Yeah I think you got the idea, basically we don’t need to repeat the ontology spec here again, and be able to comtrol the ontology should help you demo