Skip to content

Commit

Permalink
adding more content
Browse files Browse the repository at this point in the history
  • Loading branch information
erwangranger committed Dec 16, 2023
1 parent 170e571 commit 24ef14b
Show file tree
Hide file tree
Showing 5 changed files with 71 additions and 2 deletions.
11 changes: 11 additions & 0 deletions .github/.wordlist.txt
Original file line number Diff line number Diff line change
Expand Up @@ -123,3 +123,14 @@ YAML
yolo
YOLO
YOLOV

Guillaume
Moutier
Robert
Lundberg
Audrey
Guidera
Chris
Chase
Prasanth
Anbalagan
3 changes: 3 additions & 0 deletions content/modules/ROOT/nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -36,3 +36,6 @@
* 6. Productization and Extrapolations
** xref:06-01-potential-imp-ref.adoc[6.1 Potential improvements and refinements]
** xref:06-02-applicability-other.adoc[6.2 Applicability to other industries]
* 7. End of Lab
** xref:07-01-end-of-lab.adoc[7.1 Thanks]
5 changes: 4 additions & 1 deletion content/modules/ROOT/pages/06-01-potential-imp-ref.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

Although we welcome feedback, critique, we prefer https://github.com/rh-aiservices-bu/insurance-claim-processing/issues[Issues] and https://github.com/rh-aiservices-bu/insurance-claim-processing/pulls[Pull Requests].

But this section of the lab is not meant for Improvements and Refinements to the lab. Instead it is about...
But this section of the lab is not meant for Improvements and Refinements **to the lab**. Instead it is about...

== To the presented prototype

Expand All @@ -24,3 +24,6 @@ Therefore, now, we need to review what was done, and make suggestions along thes
* How efficiently are we going to be able to make updates to its components if we need to? Is there a chance that making a change to the LLM model, the YOLOV8 model, the database, the application, we introduce breaking changes?

* If that is the case, what would we want to do to avoid those possibilities?

* Which parts seem to still be manual and time-consuming, and how could we automate them better, to avoid human errors if we can.

38 changes: 37 additions & 1 deletion content/modules/ROOT/pages/06-02-applicability-other.adoc
Original file line number Diff line number Diff line change
@@ -1,2 +1,38 @@
= pages/06-02-applicability-other.adoc
= Applicability to other industries

Now, the examples we've shown throughout this lab are specific to the Insurance industry, and within that, claims processing.

However, none of the techniques we used here are inherently related to this industry or this use-case.

So let's take some examples, and discuss what we **could** do using the same techniques against **other** use-cases.

== Industries

* Healthcare
* Retail
* Automotive
* Agriculture
* Finance
* Manufacturing
* Education

== Use cases

1. Healthcare
- medical imaging analysis
- patient record summarization

2. Automotive
- Object recognition for autonomous vehicles

3. Agriculture
- crop disease analysis

4. Finance
- loan application paperwork analysis

5. Manufacturing
- Quality control through visual inspection of products

6. Education
- LLM as a teaching assistant
16 changes: 16 additions & 0 deletions content/modules/ROOT/pages/07-01-end-of-lab.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
= Thank you for your participation

We hope that the materials we used during this time together were useful and gave you a better appreciation and understanding of what goes into an intelligent application.

If you notice https://github.com/rh-aiservices-bu/insurance-claim-processing/issues[issues] with the content and/or want to send us a https://github.com/rh-aiservices-bu/insurance-claim-processing/pulls[pull request], we'll appreciate it very much.

== Acknowledgements

Here is a list of people who have participated, directly or indirectly, to the creation and delivery of this lab.

* Guillaume Moutier
* Robert Lundberg
* Audrey Guidera
* Chris Chase
* Prasanth Anbalagan
* Erwan Granger

0 comments on commit 24ef14b

Please sign in to comment.