Rajan Sharma commited on
Commit
f99c4d5
·
verified ·
1 Parent(s): 8f6e031

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +35 -40
README.md CHANGED
@@ -1,40 +1,35 @@
1
- ---
2
- title: ClarityOps Augmented Decision AI
3
- emoji: 🩺
4
- colorFrom: blue
5
- colorTo: gray
6
- sdk: docker
7
- app_port: 7860
8
- pinned: false
9
- license: other
10
- ---
11
-
12
- # Medical Decision Support AI
13
-
14
- A Hugging Face Space providing medical decision support through an AI-powered chatbot interface.
15
-
16
- ## System Information
17
- - Current User: Raj-VedAI
18
- - Timestamps: All times displayed in UTC (YYYY-MM-DD HH:MM:SS format)
19
-
20
- ## Features
21
- - Real-time medical decision support
22
- - UTC timestamp display
23
- - User identification
24
- - Medical knowledge base access
25
- - Interactive chat interface
26
-
27
- ## Usage Guidelines
28
- 1. Enter your medical query in the chat input
29
- 2. Review the AI-generated response along with timestamp
30
- 3. Use example queries for guidance
31
- 4. Note: This is a support tool and should not replace professional medical advice
32
-
33
- ## Technical Details
34
- - Built with Gradio
35
- - Real-time UTC timestamp display
36
- - Secure user identification
37
- - Comprehensive medical knowledge base integration
38
-
39
- ## Disclaimer
40
- This AI assistant is for informational purposes only and should not be used as a substitute for professional medical advice, diagnosis, or treatment.
 
1
+ # Clarity Ops — Two-Phase Medical Analytics Engine
2
+
3
+ This repo implements a universal, scenario-agnostic medical analytics workflow:
4
+
5
+ 1) **Phase 1: Clarification Questions** (<=5, grouped by category)
6
+ 2) **Phase 2: Structured Analysis** (schema-validated, unit-checked, math-verified, policy-aligned)
7
+
8
+ The engine never invents data. If inputs are missing/ambiguous, it asks for clarifications first.
9
+
10
+ ## Quick start
11
+
12
+ 1. Populate a scenario in `/packs/<scenario>/` (see `/packs/mdsi` as an example).
13
+ 2. (Optional) Put known answers to clarifications in `clarifications.json`.
14
+ 3. Run the pipeline (pseudo-call in your orchestration):
15
+ - `run_two_phase.run_clarityops("packs/mdsi")`
16
+ 4. Review the final JSON. It passes:
17
+ - JSON Schema validation
18
+ - Unit/range checks
19
+ - Math consistency
20
+ - Policy/constraints adherence
21
+ 5. (Optional) Compare against `/packs/<scenario>/expected.json` with the rule-based grader.
22
+
23
+ ## Folder overview
24
+ - `/core`: Global medical rules (units, ranges, privacy)
25
+ - `/prompts`: System + two-phase user template
26
+ - `/schemas`: Output schema for Phase 2
27
+ - `/validators`: Hard guardrails (schema/units/math/policy)
28
+ - `/graders`: Rule-based grader for gold answers
29
+ - `/pipeline`: Two-phase orchestration
30
+ - `/packs/<scenario>`: Scenario Pack (inputs, constraints, schema selection, rubric, expected)
31
+
32
+ ## Notes
33
+ - This repo shows reference Python code for validators and pipeline. Hook the prompts into your LLM runner of choice.
34
+ - All numbers are examples unless your scenario pack provides them.
35
+