Leddycia commited on
Commit
d9876db
·
verified ·
1 Parent(s): 47b2200

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +91 -107
README.md CHANGED
@@ -1,199 +1,183 @@
1
  ---
2
  library_name: transformers
3
- tags: []
 
 
 
 
 
4
  ---
5
 
6
  # Model Card for Model ID
 
7
 
8
- <!-- Provide a quick summary of what the model is/does. -->
9
 
 
 
 
10
 
11
 
12
  ## Model Details
 
13
 
14
- ### Model Description
15
 
16
- <!-- Provide a longer summary of what this model is. -->
17
 
18
- This is the model card of a 🤗 transformers model that has been pushed on the Hub. This model card has been automatically generated.
19
 
20
- - **Developed by:** [More Information Needed]
21
- - **Funded by [optional]:** [More Information Needed]
22
- - **Shared by [optional]:** [More Information Needed]
23
- - **Model type:** [More Information Needed]
24
- - **Language(s) (NLP):** [More Information Needed]
25
- - **License:** [More Information Needed]
26
- - **Finetuned from model [optional]:** [More Information Needed]
27
 
28
- ### Model Sources [optional]
29
 
30
- <!-- Provide the basic links for the model. -->
31
 
32
- - **Repository:** [More Information Needed]
33
- - **Paper [optional]:** [More Information Needed]
34
- - **Demo [optional]:** [More Information Needed]
35
 
36
- ## Uses
37
 
38
- <!-- Address questions around how the model is intended to be used, including the foreseeable users of the model and those affected by the model. -->
39
 
40
- ### Direct Use
41
 
42
- <!-- This section is for the model use without fine-tuning or plugging into a larger ecosystem/app. -->
43
-
44
- [More Information Needed]
45
 
46
- ### Downstream Use [optional]
47
 
48
- <!-- This section is for the model use when fine-tuned for a task, or when plugged into a larger ecosystem/app -->
49
 
50
- [More Information Needed]
51
 
52
- ### Out-of-Scope Use
53
 
54
- <!-- This section addresses misuse, malicious use, and uses that the model will not work well for. -->
55
 
56
- [More Information Needed]
57
 
58
- ## Bias, Risks, and Limitations
59
 
60
- <!-- This section is meant to convey both technical and sociotechnical limitations. -->
61
 
62
- [More Information Needed]
63
 
64
- ### Recommendations
65
 
66
- <!-- This section is meant to convey recommendations with respect to the bias, risk, and technical limitations. -->
67
-
68
- Users (both direct and downstream) should be made aware of the risks, biases and limitations of the model. More information needed for further recommendations.
69
-
70
- ## How to Get Started with the Model
71
-
72
- Use the code below to get started with the model.
73
-
74
- [More Information Needed]
75
-
76
- ## Training Details
77
-
78
- ### Training Data
79
 
80
- <!-- This should link to a Dataset Card, perhaps with a short stub of information on what the training data is all about as well as documentation related to data pre-processing or additional filtering. -->
81
 
82
- [More Information Needed]
83
 
84
- ### Training Procedure
85
 
86
- <!-- This relates heavily to the Technical Specifications. Content here should link to that section when it is relevant to the training procedure. -->
87
 
88
- #### Preprocessing [optional]
89
 
90
- [More Information Needed]
91
 
 
92
 
93
- #### Training Hyperparameters
94
 
95
- - **Training regime:** [More Information Needed] <!--fp32, fp16 mixed precision, bf16 mixed precision, bf16 non-mixed precision, fp16 non-mixed precision, fp8 mixed precision -->
96
 
97
- #### Speeds, Sizes, Times [optional]
98
 
99
- <!-- This section provides information about throughput, start/end time, checkpoint size if relevant, etc. -->
100
 
101
- [More Information Needed]
102
 
103
- ## Evaluation
104
 
105
- <!-- This section describes the evaluation protocols and provides the results. -->
106
 
107
- ### Testing Data, Factors & Metrics
108
 
109
- #### Testing Data
110
 
111
- <!-- This should link to a Dataset Card if possible. -->
112
 
113
- [More Information Needed]
114
 
115
- #### Factors
116
 
117
- <!-- These are the things the evaluation is disaggregating by, e.g., subpopulations or domains. -->
118
 
119
- [More Information Needed]
120
 
121
- #### Metrics
122
 
123
- <!-- These are the evaluation metrics being used, ideally with a description of why. -->
124
 
125
- [More Information Needed]
126
 
127
- ### Results
128
 
129
- [More Information Needed]
130
 
131
- #### Summary
132
 
 
133
 
 
134
 
135
- ## Model Examination [optional]
136
 
137
- <!-- Relevant interpretability work for the model goes here -->
138
 
139
- [More Information Needed]
140
 
141
- ## Environmental Impact
142
 
143
- <!-- Total emissions (in grams of CO2eq) and additional considerations, such as electricity usage, go here. Edit the suggested text below accordingly -->
144
 
145
- Carbon emissions can be estimated using the [Machine Learning Impact calculator](https://mlco2.github.io/impact#compute) presented in [Lacoste et al. (2019)](https://arxiv.org/abs/1910.09700).
146
 
147
- - **Hardware Type:** [More Information Needed]
148
- - **Hours used:** [More Information Needed]
149
- - **Cloud Provider:** [More Information Needed]
150
- - **Compute Region:** [More Information Needed]
151
- - **Carbon Emitted:** [More Information Needed]
152
 
153
- ## Technical Specifications [optional]
154
 
155
- ### Model Architecture and Objective
156
 
157
- [More Information Needed]
158
 
159
- ### Compute Infrastructure
160
 
161
  [More Information Needed]
162
 
163
- #### Hardware
 
164
 
165
- [More Information Needed]
166
 
167
- #### Software
168
 
169
- [More Information Needed]
170
 
171
- ## Citation [optional]
172
 
173
- <!-- If there is a paper or blog post introducing the model, the APA and Bibtex information for that should go in this section. -->
174
 
175
- **BibTeX:**
176
 
177
- [More Information Needed]
178
 
179
- **APA:**
180
 
181
- [More Information Needed]
182
 
183
- ## Glossary [optional]
184
 
185
- <!-- If relevant, include terms and calculations in this section that can help readers understand the model or model card. -->
186
 
187
- [More Information Needed]
188
-
189
- ## More Information [optional]
190
 
191
- [More Information Needed]
192
 
193
- ## Model Card Authors [optional]
194
 
195
- [More Information Needed]
196
 
197
- ## Model Card Contact
198
 
199
- [More Information Needed]
 
1
  ---
2
  library_name: transformers
3
+ tags:
4
+ - healh
5
+ - STD
6
+ - STI
7
+ language:
8
+ - en
9
  ---
10
 
11
  # Model Card for Model ID
12
+ STD-MedGuide is an AI model designed to answer questions about sexually transmitted diseases (STDs/MSTs) in clear, natural language.
13
 
14
+ You give it a question (e.g., “What are the common symptoms of chlamydia?”).
15
 
16
+ The model processes the question and generates a medically relevant answer, based on knowledge it learned from medical QA datasets.
17
+
18
+ It is intended for education and awareness, not as a substitute for professional medical advice.
19
 
20
 
21
  ## Model Details
22
+ 🛠️ Model Details – STD-MedGuide
23
 
24
+ Model Name: STD-MedGuide
25
 
26
+ Base Architecture: FLAN-T5 (small) a text-to-text transformer model designed for instruction-following tasks.
27
 
28
+ Task: Question Answering (QA) focused on sexually transmitted diseases (STDs/MSTs).
29
 
30
+ Dataset Used:
 
 
 
 
 
 
31
 
32
+ CareQA (open-ended medical QA dataset)
33
 
34
+ Medical-QA (open-ended medical QA dataset)
35
 
36
+ Both datasets adapted for French MST terminology and general STD questions.
 
 
37
 
38
+ Training Environment: Google Colab using Hugging Face transformers library.
39
 
40
+ Training Setup:
41
 
42
+ Epochs: 2 planned (beta version checkpoint at step ~171)
43
 
44
+ Batch Size: 4–8 (depending on GPU/CPU availability)
 
 
45
 
46
+ Learning Rate: 5e-5
47
 
48
+ Checkpointing: every 100 steps (to save progress and allow beta sharing)
49
 
50
+ Device: GPU if available (Colab runtime), otherwise CPU
51
 
52
+ Loss Performance:
53
 
54
+ Initial training loss ~21
55
 
56
+ Reduced to ~0.5 in early steps (checkpoint 171)
57
 
58
+ Tokenizer: AutoTokenizer from Hugging Face, compatible with FLAN-T5 small.
59
 
60
+ Output Type: Text generation given a question, generates an answer in natural language.
61
 
62
+ Intended Users: Students, educators, awareness programs, and general audiences seeking information about STDs.
63
 
64
+ Limitations: Not suitable for clinical diagnosis; probabilistic output; may reflect dataset biases.
65
 
66
+ ### Model Description
 
 
 
 
 
 
 
 
 
 
 
 
67
 
68
+ STD-MedGuide is a specialized question-answering model designed to provide reliable and accessible information about sexually transmitted diseases (STDs/MSTs). Built on top of the FLAN-T5 architecture, it has been fine-tuned using medical QA datasets to understand and respond to natural language questions related to sexual health.
69
 
70
+ The model’s primary function is to take a user’s question — for example, “Quels sont les symptômes les plus courants des MST ?” or “How can HIV be prevented?” — and generate a concise, contextually relevant answer. By focusing specifically on STD-related queries, STD-MedGuide can assist students, educators, and awareness programs in spreading accurate information about prevention, symptoms, transmission methods, and general health education.
71
 
72
+ While it produces medically informed responses, STD-MedGuide is not a diagnostic or clinical tool. Instead, it is intended as an educational resource, making medical knowledge more approachable and helping raise awareness about sensitive health topics. Its potential applications include supporting classroom learning, contributing to health campaigns, and serving as an interactive guide for individuals seeking general knowledge about STDs.
73
 
 
74
 
75
+ - **Developed by:** [Saint-Vil Angie-Reyna Leddycia]
76
 
77
+ ## Uses
78
 
79
+ 🏷️ Uses / Applications of STD-MedGuide
80
 
81
+ Educational Tool
82
 
83
+ Helps students, teachers, and healthcare trainees learn about sexually transmitted diseases.
84
 
85
+ Can be integrated into classroom exercises, quizzes, or self-study activities.
86
 
87
+ Awareness and Prevention Campaigns
88
 
89
+ Provides clear, understandable answers for public health awareness.
90
 
91
+ Useful for NGOs, health organizations, or school programs promoting sexual health.
92
 
93
+ Interactive Question-Answering
94
 
95
+ Can serve as a chatbot or interactive assistant to answer general STD questions.
96
 
97
+ Supports engagement in workshops, seminars, or online learning platforms.
98
 
99
+ Reference for Research or Reports
100
 
101
+ Can generate concise explanations of STD symptoms, transmission, and prevention for reports, presentations, or educational materials.
102
 
103
+ Language Adaptation
104
 
105
+ Handles French terminology (MST) and English (STD), making it suitable for bilingual or international educational settings.
106
 
107
+ Note: While STD-MedGuide is a powerful educational tool, it is not a substitute for professional medical advice or clinical diagnosis.
108
 
 
109
 
110
+ ## Bias, Risks, and Limitations
111
 
112
+ ⚠️ Bias, Risks, and Limitations
113
 
114
+ Bias in Training Data
115
 
116
+ STD-MedGuide is fine-tuned on datasets like CareQA and Medical-QA, which may reflect biases in medical literature, language, or cultural context.
117
 
118
+ Certain diseases, symptoms, or populations may be over- or under-represented, affecting the accuracy or completeness of answers.
119
 
120
+ Medical Accuracy and Reliability
121
 
122
+ The model generates responses based on patterns in the training data, not on real-time clinical knowledge.
123
 
124
+ Answers may occasionally be incomplete, outdated, or partially incorrect, so it cannot replace professional medical advice.
125
 
126
+ Language and Context Limitations
127
 
128
+ While the model handles French (MST terminology) and English reasonably well, complex questions or nuanced phrasing may lead to misinterpretation.
129
 
130
+ It may not fully understand ambiguous questions or rare medical scenarios.
131
 
132
+ Ethical and Safety Risks
133
 
134
+ Users could misinterpret answers as formal medical guidance.
135
 
136
+ There is a risk of over-reliance, especially by individuals seeking medical help without consulting healthcare professionals.
 
 
 
 
137
 
138
+ Technical Limitations
139
 
140
+ The current beta version is trained on a limited number of steps (~171), meaning it has not seen the full dataset and could improve with further training.
141
 
142
+ Responses are generated probabilistically, so the model may produce different answers to the same question on repeated queries.
143
 
144
+ Conclusion: STD-MedGuide is best used as an educational and awareness tool, to support learning and information dissemination about STDs, but not for diagnosis or clinical decision-making.
145
 
146
  [More Information Needed]
147
 
148
+ ### Recommendations
149
+ 💡 Recommendations
150
 
151
+ Further Training
152
 
153
+ Continue training on the full dataset to improve accuracy and coverage of STD-related questions.
154
 
155
+ Consider incorporating additional French-language medical datasets to improve bilingual performance.
156
 
157
+ Regular Updates
158
 
159
+ Periodically update the model with new medical knowledge and guidelines to ensure answers stay current.
160
 
161
+ Evaluation and Validation
162
 
163
+ Evaluate on a larger, diverse validation set to measure performance and reduce bias.
164
 
165
+ Consider human-in-the-loop review to check medical accuracy of generated answers.
166
 
167
+ Responsible Use
168
 
169
+ Use the model primarily for education and awareness, not for clinical decision-making.
170
 
171
+ Always include disclaimers when deploying the model to inform users of its limitations.
172
 
173
+ User Interface & Accessibility
 
 
174
 
175
+ Integrate into chatbots, educational platforms, or mobile apps for easier access.
176
 
177
+ Consider adding multilingual support beyond French and English.
178
 
179
+ Bias Mitigation
180
 
181
+ Monitor for biases in answers (e.g., population, gender, age) and refine the training dataset accordingly.
182
 
183
+ Encourage feedback from users to improve answer fairness and relevance.