diff --git a/.DS_Store b/.DS_Store
index 74b86ac8..d9fbe333 100644
Binary files a/.DS_Store and b/.DS_Store differ
diff --git a/.gitignore b/.gitignore
index 13d99561..d834f808 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,5 @@
-.DS_Store
+git .DS_Store
 .idea/
 .venv
 .venv/*
+node_modules
diff --git a/SDKs/android/ekascribe.mdx b/SDKs/android/ekascribe.mdx
new file mode 100644
index 00000000..dde90259
--- /dev/null
+++ b/SDKs/android/ekascribe.mdx
@@ -0,0 +1,369 @@
+# EkaScribe SDK Documentation
+
+EkaScribe SDK (Voice2Rx) is an Android SDK for voice-based medical transcription and documentation.
+It provides real-time voice recording, transcription, and intelligent medical documentation
+generation with support for multiple languages and output formats.
+
+**Version:** 3.0.7
+
+**Minimum Android SDK:** 23 (Android 6.0)
+
+---
+
+## 1. Installation
+
+### Add Maven Repository
+
+Add the JitPack repository to your project's `settings.gradle.kts` (or `build.gradle`):
+
+```kotlin
+dependencyResolutionManagement {
+    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
+    repositories {
+        google()
+        mavenCentral()
+        // Add below line to fetch SDK from Jitpack
+        maven { url = uri("<https://jitpack.io>") }
+    }
+}
+
+```
+
+### Add Dependencies
+
+Add the EkaScribe SDK and required networking dependency to your app's `build.gradle.kts`:
+
+```kotlin
+dependencies {
+    implementation("com.github.eka-care:Eka-Scribe-Android:${LATEST_VERSION}")
+}
+
+```
+
+### Required Permissions
+
+Add the following permissions to your `AndroidManifest.xml`:
+
+```xml
+<uses-permission android:name="android.permission.RECORD_AUDIO" />
+<uses-permission android:name="android.permission.INTERNET" />
+<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
+```
+
+**Note:** You must request `RECORD_AUDIO` permission at runtime for Android 6.0 and above.
+
+---
+
+## 2. Initialization
+
+Initialize the SDK in your `Application` class or main `Activity`.
+
+### Step 1: Implement Lifecycle Callbacks
+
+Create a class that implements `Voice2RxLifecycleCallbacks` to handle session events.
+
+```kotlin
+import com.eka.voice2rx_sdk.sdkinit.Voice2RxLifecycleCallbacks
+import com.eka.voice2rx_sdk.common.models.EkaScribeError
+
+class MyVoice2RxCallbacks : Voice2RxLifecycleCallbacks {
+    override fun onStartSession(sessionId: String) {
+        // Recording started
+    }
+
+    override fun onStopSession(sessionId: String, recordedFiles: Int) {
+        // Get result when ready after stopping the session
+        CoroutineScope(Dispatchers.IO).launch {
+            Voice2Rx.pollEkaScribeResult(sessionId = sessionId).onSuccess {
+                Log.d(TAG, it.templates.toString())
+            }.onFailure {
+                Log.d(TAG, "error : ${it.message.toString()}")
+            }
+        }
+    }
+
+    override fun onPauseSession(sessionId: String) {
+        // Recording paused
+    }
+
+    override fun onResumeSession(sessionId: String) {
+        // Recording resumed
+    }
+
+    override fun onError(error: EkaScribeError) {
+        // Handle error
+    }
+}
+
+```
+
+### Step 2: Implement TokenStorage
+
+The networking module requires a `TokenStorage` implementation to handle authentication tokens.
+
+```kotlin
+import com.eka.networking.token.TokenStorage
+
+class MyTokenStorage : TokenStorage {
+    override fun getAccessToken(): String {
+        return "access_token"
+    }
+
+    override fun getRefreshToken(): String {
+        return "refresh_token"
+    }
+
+    override fun saveTokens(accessToken: String, refreshToken: String) {
+        // save tokens
+    }
+
+    override fun onSessionExpired() {
+        // SessionExpired refresh token expired
+    }
+}
+```
+
+### Step 3: Configure and Initialize
+
+Initialize `Voice2Rx` with `Voice2RxInitConfig` and `NetworkConfig`.
+
+```kotlin
+import com.eka.voice2rx_sdk.sdkinit.Voice2Rx
+import com.eka.voice2rx_sdk.sdkinit.Voice2RxInitConfig
+import com.eka.networking.client.NetworkConfig
+import com.eka.networking.client.AuthConfig
+
+// 1. Configure Network
+val networkConfig = NetworkConfig(
+    appId = "your-app-id",
+    baseUrl = "<https://api.eka.care/>",
+    appVersionName = BuildConfig.VERSION_NAME,
+    appVersionCode = BuildConfig.VERSION_CODE,
+    isDebugApp = false // false in production environment,
+    apiCallTimeOutInSec = 30L,
+    headers = mapOf(), // Optional headers
+    tokenStorage = MyTokenStorage()
+)
+
+// 2. Configure SDK
+val config = Voice2RxInitConfig(
+    voice2RxLifecycle = MyVoice2RxCallbacks(),
+    networkConfig = networkConfig,
+)
+
+// 3. Initialize
+Voice2Rx.init(config, context)
+
+```
+
+---
+
+## 3. Core API Reference
+
+All main functions are available via the `Voice2Rx` singleton object.
+
+### Recording Control
+
+### `startVoice2Rx`
+
+Starts a new voice recording session.
+
+```kotlin
+fun startVoice2Rx(
+    mode: String = Voice2RxType.CONSULTATION.value, // "consultation" or "dictation"
+    patientDetails: PatientDetails? = null,
+    outputFormats: List<Template>, // Max 2 formats
+    languages: List<String>,       // Max 2 languages
+    modelType: String,             // e.g., "pro"
+    onError: (EkaScribeError) -> Unit,
+    onStart: (String) -> Unit
+)
+
+```
+
+**Example:**
+
+```kotlin
+// Define output templates using Template(templateId, templateName)
+val outputFormats = listOf(
+    Template(templateId = "19288d2f-81a9-46a6-b804-9651242a9b3e", templateName = "SOAP Note")
+)
+
+val languages = listOf("en-IN")
+
+Voice2Rx.startVoice2Rx(
+    mode = Voice2RxType.DICTATION.value,
+    outputFormats = outputFormats,
+    languages = languages,
+    modelType = "pro" // or lite for faster results,
+    onError = { error -> Log.e("SDK", "Error: ${error.errorDetails.message}") },
+    onStart = { sessionId -> Log.d("SDK", "Started: $sessionId") }
+)
+
+```
+
+### `pauseVoice2Rx`
+
+Pauses the current recording.
+
+```kotlin
+Voice2Rx.pauseVoice2Rx()
+
+```
+
+### `resumeVoice2Rx`
+
+Resumes a paused recording.
+
+```kotlin
+Voice2Rx.resumeVoice2Rx()
+
+```
+
+### `stopVoice2Rx`
+
+Stops the recording and triggers processing.
+
+```kotlin
+Voice2Rx.stopVoice2Rx()
+
+```
+
+### `isCurrentlyRecording`
+
+Checks if a recording is in progress.
+
+```kotlin
+val isRecording = Voice2Rx.isCurrentlyRecording()
+
+```
+
+### Data & Results
+
+### `getSessionOutput`
+
+Retrieves the transcription/generated output for a session.
+
+```kotlin
+suspend fun getSessionOutput(sessionId: String): Result<SessionResult>
+
+```
+
+### `pollEkaScribeResult`
+
+Polls for results, useful for waiting until processing completes.
+
+```kotlin
+suspend fun pollEkaScribeResult(sessionId: String): Result<SessionResult>
+
+```
+
+### `getHistoryVoice2Rx`
+
+Fetches session history.
+
+```kotlin
+suspend fun getHistoryVoice2Rx(count: Int? = null): Voice2RxHistoryResponse?
+
+```
+
+### `getFullRecordingFile`
+
+Gets the audio file for a session.
+
+```kotlin
+fun getFullRecordingFile(sessionId: String): Result<File>
+
+```
+
+### Session Info & Monitoring
+
+### `getSessionUploadInfoAsFlow`
+
+Observe the upload stage of a session (Uploading, Processing, Completed).
+
+```kotlin
+suspend fun getSessionUploadInfoAsFlow(sessionId: String): Flow<VoiceTransactionStage>?
+
+```
+
+### `getVoiceActivityFlow`
+
+Flow for real-time voice activity (speech detection, amplitude).
+
+```kotlin
+fun getVoiceActivityFlow(): Flow<VoiceActivityData>?
+
+```
+
+### `getAudioQualityFlow`
+
+Flow for real-time audio quality metrics (STOI, PESQ, SI-SDR).
+
+```kotlin
+fun getAudioQualityFlow(): Flow<AudioQualityMetrics?>?
+
+```
+
+### Configuration & Templates
+
+### `getTemplates`
+
+Get available output templates.
+
+```kotlin
+suspend fun getTemplates(): Result<List<TemplateItem>>?
+
+```
+
+### `getUserConfigs`
+
+Get user configuration including supported languages and modes.
+
+```kotlin
+suspend fun getUserConfigs(): Result<UserConfigs>
+
+```
+
+### `updateUserConfigs`
+
+Update user preferences (selected language, mode, etc.).
+
+```kotlin
+suspend fun updateUserConfigs(selectedUserPreferences: SelectedUserPreferences): Result<Boolean>
+
+```
+
+---
+
+## 4. Error Handling
+
+Errors are returned via `EkaScribeError`.
+
+**Common Error Codes:**
+
+- `SUPPORTED_OUTPUT_FORMATS_COUNT_EXCEEDED`: Max 2 output formats allowed.
+- `SUPPORTED_LANGUAGES_COUNT_EXCEEDED`: Max 2 languages allowed.
+- `LANGUAGE_LIST_CAN_NOT_BE_EMPTY`
+- `OUTPUT_FORMAT_LIST_CAN_NOT_BE_EMPTY`
+
+**Data Class:**
+
+```kotlin
+data class EkaScribeError(
+    val sessionId: String,
+    val errorDetails: EkaScribeErrorDetails, // Contains 'message', 'displayMessage', 'code'
+    val voiceError: VoiceError
+)
+
+```
+
+## 5. Cleanup
+
+Call `releaseResources()` when the SDK is no longer needed (e.g., in `onDestroy` of your host
+Activity/Application).
+
+```kotlin
+Voice2Rx.releaseResources()
+
+```
\ No newline at end of file
diff --git a/SDKs/android/voice-to-rx.mdx b/SDKs/android/voice-to-rx.mdx
deleted file mode 100644
index cc4535c0..00000000
--- a/SDKs/android/voice-to-rx.mdx
+++ /dev/null
@@ -1,331 +0,0 @@
-# Voice2Rx Android SDK
-
-[![](https://jitpack.io/v/eka-care/eka-v2rx-android.svg)](https://jitpack.io/#eka-care/eka-v2rx-android/latest)
-
-## Table of Contents
-
-1. [Overview](#overview)
-2. [Prerequisites](#prerequisites)
-3. [Installation](#installation)
-4. [Initialization](#initialization)
-    - [Set up logging callbacks for SDK events](#set-up-logging-callbacks-for-sdk-events)
-5. [Basic Usage](#basic-usage)
-    - [Starting a Voice Session](#starting-a-voice-session)
-    - [Stopping a Voice Session](#stopping-a-voice-session)
-    - [Checking Session Status](#checking-session-status)
-6. [Working with Sessions](#working-with-sessions)
-    - [Retrieving Session History](#retrieving-session-history)
-    - [Sample Structured Rx Data](#sample-structured-rx-data)
-    - [Sample Clinical Notes Output](#sample-clinical-notes-output)
-7. [Advanced Features](#advanced-features)
-    - [Retrying a Session](#retrying-a-session)
-8. [Cleanup](#cleanup)
-9. [Links](#links)
-
----
-
-## Overview
-
-Voice2Rx is an Android SDK that allows voice transcription and structured prescription data generation for healthcare applications.
-
-## Prerequisites
-
-Before integrating the Voice2Rx SDK, ensure that your Android project meets the following requirements:
-
-- Android API level 24 or higher
-- Kotlin 1.9.0 or higher
-- Microphone permission in your AndroidManifest.xml:
-    
-    ```xml
-    
-    <uses-permission android:name="android.permission.RECORD_AUDIO" />
-    <uses-permission android:name="android.permission.INTERNET" />
-    ```
-    
-- Runtime permission handling for microphone access
-
-## Installation
-
-Add the following dependency to your `app/build.gradle.kts` file:
-
-```kotlin
-implementation("com.github.eka-care:eka-v2rx-android:2.0.3")
-```
-
-## Initialization
-
-To initialize the SDK, you need to implement the `IOkHttpSetup` interface and provide the necessary configuration:
-
-```kotlin
-// Create object implementing IOkHttpSetup interface to provide auth tokens
-class EkaAuthConfigImpl : EkaAuthConfig {
-    override suspend fun refreshToken(): String {
-        // return new auth token after refresh
-    }
-
-    override fun sessionExpired() {
-				// callback function for session expired
-    }
-}
-
-// Initialize the SDK
-Voice2Rx.init(
-    context = context,
-    config = Voice2RxInitConfig(
-        voice2RxLifecycle = object : Voice2RxLifecycleCallbacks {
-            override fun onStartSession(sessionId: String) {
-            }
-
-            override fun onStopSession(
-                sessionId: String,
-                recordedFiles: Int
-            ) {
-            }
-
-            override fun onPauseSession(sessionId: String) {
-            }
-
-            override fun onResumeSession(sessionId: String) {
-            }
-
-            override fun onError(
-                sessionId: String,
-                error: VoiceError
-            ) {
-            }
-        },
-        authorizationToken = // provide eka auth token,
-        ekaAuthConfig = EkaAuthConfigImpl(),
-    )
-)
-```
-
-### Set up logging callbacks for SDK events
-
-```kotlin
-Voice2Rx.setEventLogger(
-    object : LogInterceptor {
-        override fun logEvent(eventLog: EventLog) {
-            when(eventLog) {
-                is EventLog.Error -> {
-
-                }
-                is EventLog.Warning -> {
-
-                }
-                is EventLog.Info -> {
-
-                }
-            }
-        }
-    }
-)
-```
-
-## Basic Usage
-
-### Starting a Voice Session
-
-To start a voice recording session:
-
-```kotlin
-// Start a voice session in DICTATION or CONSULTATION mode
-Voice2Rx.startVoice2Rx(
-    mode = Voice2RxType.DICTATION,
-    onError = {}
-)
-// The onStart callback (defined in init) will be triggered when the session begins
-```
-
-### Stopping a Voice Session
-
-To stop a voice recording session:
-
-```kotlin
-// Stop the current voice session
-Voice2Rx.stopVoice2Rx()
-// The onStop callback will be triggered with the sessionId
-```
-
-### Checking Session Status
-
-To check if a recording session is currently active:
-
-```kotlin
-// Returns true if a recording session is in progress
-val isRecording = Voice2Rx.isCurrentlyRecording()
-```
-
-## Working with Sessions
-
-### Retrieving Session History
-
-To access previous recording sessions:
-
-```kotlin
-// Get all recording sessions
-val sessions = Voice2Rx.getSessions()
-
-// Access a specific session (example using the first session)
-val session = sessions.firstOrNull()
-val sessionProcessingStatus = Voice2Rx.getVoice2RxSessionStatus(sessionId = session.sessionId)
-val sessionOutput = Voice2Rx.getVoiceSessionData(sessionId = session.sessionId)
-
-```
-
-### Sample Structured Rx Data
-
-The SDK returns structured prescription data in JSON format:
-
-```json
-{
-  "prescription": {
-    "advices": [
-      {
-        "id": "locale-4f1e59b7c71003546b7bb5aadb89280b",
-        "parsedText": "Take bedrest for at least 7 days",
-        "text": "Take bedrest for at least 7 days"
-      },
-      {
-        "id": "locale-b3ca8e9447de58b3738549ec3c8db922",
-        "parsedText": "Do exercise with physiotherapist",
-        "text": "Do exercise with physiotherapist"
-      }
-    ],
-    "followup": {
-      "date": "2025-03-09T00:00:00.000000Z"
-    },
-    "labTests": [
-      {
-        "common_name": "Blood sugar test",
-        "id": "locale-5686e09a70ffcbc355b372f57b744752",
-        "name": "Blood sugar test"
-      },
-      {
-        "common_name": "Liver function test",
-        "id": "locale-9b501b45359316407782679ce7eeabac",
-        "name": "Liver function test"
-      },
-      {
-        "common_name": "X-ray",
-        "id": "locale-3c51a99d9bbfefde7ba517f3316899f2",
-        "name": "X-ray"
-      }
-    ],
-    "language": "EN",
-    "medications": [
-      {
-        "duration": {
-          "custom": "3 Days",
-          "unit": "Days",
-          "value": 3
-        },
-        "frequency": {
-          "custom": "1-1-1",
-          "dose": [
-            "1",
-            "1",
-            "1"
-          ],
-          "frequency": "3",
-          "pattern_id": "fp-1",
-          "period": 1,
-          "period_unit": "day"
-        },
-        "id": "locale-a0fdc63d09d1d255b00796ade40bb3c6",
-        "name": "Molo 650 tablet",
-        "original_name": "mdolo 650 tablet",
-        "linked": {
-          "eka_id": "b-4974923412"
-        }
-      }
-    ],
-    "symptoms": [
-      {
-        "id": "locale-f532fde6e2a357af72b9de6aa1f0e65e",
-        "name": "Fever",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-6a44898c82426d50cb083373d59b155a",
-        "name": "Headache",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-867fc9a3c94474b3c77ee9a0b5aae022",
-        "name": "Leg pain",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-a7033cb31b1991cc8f4c9c751a8452b6",
-        "name": "Neck pain",
-        "status": "preliminary"
-      }
-    ]
-  }
-}
-
-```
-
-### Sample Clinical Notes Output
-
-The SDK can also generate a formatted markdown output:
-
-```markdown
-**Chief Complaints**
-- Fever
-- Headache
-- Leg pain
-- Neck pain
-
-**Assessment**
-- Symptomatic fever with multiple body pains
-
-**Plan**
-- Medications:
-  - Mdolo 650 tablet - TID for 3 days
-- Investigations advised:
-  - Blood test
-  - Blood sugar test
-  - Liver function test
-  - X-ray
-- Physiotherapy referral
-
-**Patient Instructions**
-- Take complete bed rest for 7 days
-- Follow up after 15 days with all investigation reports
-- Continue physiotherapy sessions
-- Take prescribed medications as directed
-
-```
-
-## Advanced Features
-
-### Retrying a Session
-
-To retry processing a session:
-
-```kotlin
-Voice2Rx.retrySession(
-    context = context,
-    sessionId = sessionId,
-    onResponse = { responseState ->
-        // Handle the retry response
-        // Indicates whether retry was successful or not
-    }
-)
-```
-
-## Cleanup
-
-When you're done using the SDK, free up resources:
-
-```kotlin
-// Release all resources
-Voice2Rx.dispose()
-
-```
-
-## Links
-
-- [GitHub Repository](https://github.com/eka-care/eka-v2rx-android)
\ No newline at end of file
diff --git a/SDKs/backend/ekapython-sdk.mdx b/SDKs/backend/ekapython-sdk.mdx
index ddadcfb5..3aa3799d 100644
--- a/SDKs/backend/ekapython-sdk.mdx
+++ b/SDKs/backend/ekapython-sdk.mdx
@@ -50,44 +50,6 @@ token_response = client.auth.login()
 access_token = token_response["access_token"]
 ```
 ---
-### Records Management
-
-```python
-# Upload a document
-response = client.records.upload_document(
-    file_path="/path/to/lab_report.pdf",
-    document_type="lr",  # lab report
-    tags=["covid", "test"],
-    title="COVID-19 Test Report"
-)
-document_id = response["document_id"]
-
-# List documents
-documents = client.records.list_documents()
-for doc in documents.get("items", []):
-    print(doc["record"]["item"]["document_id"])
-
-# Get a specific document
-document = client.records.get_document(document_id)
-
-# Update a document
-client.records.update_document(
-    document_id=document_id,
-    document_type="ps",  # prescription
-    tags=["medication"]
-)
-
-# Delete a document
-client.records.delete_document(document_id)
-
-# Retrieve health records in FHIR format
-records = client.records.retrieve_health_records(
-    identifier="care_context_123",
-    hip_id="hip123",
-    health_id="user@abdm"
-)
-```
----
 ### Vitals Management
 
 ```python
diff --git a/SDKs/backend/go-sdk.mdx b/SDKs/backend/go-sdk.mdx
index 60e1a4b2..401f8418 100644
--- a/SDKs/backend/go-sdk.mdx
+++ b/SDKs/backend/go-sdk.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Go SDK'
+title: 'Golang'
 ---
 
 A Go SDK for integrating with Eka Care’s healthcare APIs, including ABDM (Ayushman Bharat Digital Mission) services.
diff --git a/SDKs/backend/report-parsing-sdk-java.mdx b/SDKs/backend/report-parsing-sdk-java.mdx
new file mode 100644
index 00000000..a9e1cb4c
--- /dev/null
+++ b/SDKs/backend/report-parsing-sdk-java.mdx
@@ -0,0 +1,165 @@
+---
+title: 'Java'
+description: 'A Java Spring Boot SDK for parsing medical documents using Eka Care APIs'
+---
+
+# Overview
+
+[Report Parsing SDK on GitHub](https://github.com/eka-care/reports-parsing-sdk/tree/main/java)
+
+A Java Spring Boot SDK for processing medical documents through the Eka Care API. This SDK supports document submission, result polling, and FHIR data extraction.
+
+## Prerequisites
+
+- **JDK 17+** (verify with `java -version`)
+- **Maven** (verify with `mvn -version`)
+- **IDE**: IntelliJ IDEA, Eclipse, or VS Code with Java extensions
+- **Eka Care API Credentials**: Valid client ID and secret
+
+---
+
+## Project Structure
+
+```
+ekacare-sdk/
+├── src/main/java/com/example/ekacare/
+│   ├── sdk/EkaCareSDK.java
+│   ├── service/EkaCareService.java
+│   └── controller/DocumentController.java
+├── src/main/resources/application.properties
+└── pom.xml
+```
+
+---
+
+## Setup Instructions
+
+### Step 1: Create Spring Boot Project
+
+**Via Spring Initializr:**
+- Visit [start.spring.io](https://start.spring.io)
+- Select Maven, Java 17, Spring Boot 3.2.0
+- Add "Spring Web" dependency
+- Generate and extract
+
+**Via IntelliJ IDEA:**
+File → New → Project → Spring Initializr → Configure with Java 17 and Spring Boot 3.2.0
+
+### Step 2: Add SDK Files
+
+Copy files from the repository to respective directories:
+- `EkaCareSDK.java` → `src/main/java/com/example/ekacare/sdk/`
+- `EkaCareService.java` → `src/main/java/com/example/ekacare/service/`
+- `application.properties` → `src/main/resources/`
+- `pom.xml` → project root
+
+### Step 3: Configure Credentials
+
+Update `application.properties`:
+
+```properties
+ekacare.client.id=YOUR_CLIENT_ID_HERE
+ekacare.client.secret=YOUR_CLIENT_SECRET_HERE
+```
+
+### Step 4: Build
+
+```bash
+mvn clean install
+```
+
+---
+
+## Quick Start
+
+### Direct SDK Usage
+
+```java
+try (EkaCareSDK sdk = new EkaCareSDK("CLIENT_ID", "CLIENT_SECRET")) {
+    Map<String, Object> result = sdk.processAndWait(
+        "/path/to/document.jpg",
+        "smart",
+        10,  // poll interval (seconds)
+        300  // timeout (seconds)
+    );
+    Map<String, Object> data = (Map<String, Object>) result.get("data");
+    System.out.println("FHIR: " + data.get("fhir"));
+}
+```
+
+### Spring Boot Service
+
+```java
+@Component
+public class MyDocumentProcessor {
+    @Autowired
+    private EkaCareService ekaCareService;
+
+    public void process() throws InterruptedException {
+        Map<String, Object> result = ekaCareService
+            .processDocumentAndWait("/path/to/document.jpg", "smart");
+        System.out.println("Result: " + result);
+    }
+}
+```
+
+---
+
+## REST API Endpoints
+
+The SDK provides REST endpoints for document processing:
+
+| Method | Endpoint | Purpose |
+|--------|----------|---------|
+| POST | `/api/documents/process?task=smart` | Async document submission |
+| GET | `/api/documents/{id}/result` | Retrieve processing result |
+| POST | `/api/documents/process-sync?task=smart` | Sync processing (waits for completion) |
+
+---
+
+## Task Options
+
+When processing documents, you can specify different task types:
+
+| Task | Description |
+|------|-------------|
+| `smart` | Smart report parsing |
+| `pii` | PII (Personally Identifiable Information) detection |
+| `both` | Combined smart parsing and PII detection |
+
+---
+
+## Example cURL Requests
+
+```bash
+# Submit document asynchronously
+curl -X POST http://localhost:8080/api/documents/process?task=smart \
+  -F "file=@/path/to/document.jpg"
+
+# Get processing result
+curl http://localhost:8080/api/documents/abc123/result
+
+# Synchronous processing (waits for completion)
+curl -X POST http://localhost:8080/api/documents/process-sync?task=smart \
+  -F "file=@/path/to/document.jpg"
+```
+
+---
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| File Not Found | Use absolute paths or verify relative path correctness |
+| Authorization (401) | Validate credentials in properties file |
+| Maven Build Fails | Run `mvn clean install -U` |
+| Port 8080 In Use | Change in `application.properties`: `server.port=8081` |
+
+### Large File Upload
+
+For large files, increase limits in `application.properties`:
+
+```properties
+spring.servlet.multipart.max-file-size=50MB
+spring.servlet.multipart.max-request-size=50MB
+```
diff --git a/SDKs/backend/report-parsing-sdk.mdx b/SDKs/backend/report-parsing-sdk.mdx
new file mode 100644
index 00000000..6ae9b95a
--- /dev/null
+++ b/SDKs/backend/report-parsing-sdk.mdx
@@ -0,0 +1,126 @@
+---
+title: 'Python'
+description: 'A Python SDK for parsing medical documents using Eka Care APIs'
+---
+
+# Overview
+
+[Report Parsing SDK on GitHub](https://github.com/eka-care/reports-parsing-sdk/tree/main/python)
+
+A comprehensive Python SDK for interacting with the Eka Care Medical Records API. This SDK enables you to upload and process medical documents with support for smart report parsing and PII detection.
+
+## Installation
+
+Install from source:
+
+```bash
+git clone https://github.com/eka-care/reports-parsing-sdk.git
+cd reports-parsing-sdk/python
+pip install -e .
+```
+
+---
+
+## Quick Start
+
+Basic initialization and document processing:
+
+```python
+from ekacare_sdk import EkaCareSDK
+
+# Initialize the SDK with your credentials
+sdk = EkaCareSDK(
+    client_id="your_client_id",
+    client_secret="your_client_secret"
+)
+
+# Process a document
+result = sdk.process_document(
+    "/path/to/lab_report.jpg",
+    task="smart"
+)
+
+# Get the document ID from the result
+print(f"Document ID: {result['document_id']}")
+
+# Retrieve the processing results
+response = sdk.get_document_result(result['document_id'])
+print(response['data'])
+
+# Clean up
+sdk.close()
+```
+
+---
+
+## Configuration
+
+### Environment Variables
+
+Create a `.env` file with your credentials:
+
+```bash
+EKACARE_CLIENT_ID=your_client_id
+EKACARE_CLIENT_SECRET=your_client_secret
+EKACARE_BASE_URL=https://api.eka.care
+```
+
+### Using Configuration Class
+
+Load settings from environment variables or configure manually:
+
+```python
+from ekacare_sdk.config import EkaCareConfig
+
+# Load from environment
+config = EkaCareConfig.from_env()
+sdk = EkaCareSDK(config.client_id, config.client_secret)
+```
+
+---
+
+
+## Features
+
+The SDK provides the following capabilities:
+
+- **Automatic Authentication**: Handles token management automatically
+- **Document Processing**: Upload and process medical documents
+- **Polling Support**: Built-in polling for asynchronous results
+- **Environment Configuration**: Easy setup via environment variables
+
+---
+
+## Task Options
+
+When processing documents, you can specify different task types:
+
+| Task | Description |
+|------|-------------|
+| `smart` | Default option - Smart report parsing |
+| `pii` | PII (Personally Identifiable Information) detection |
+| `both` | Combined smart parsing and PII detection |
+
+Example:
+
+```python
+# Smart report parsing (default)
+result = sdk.process_document("/path/to/report.pdf", task="smart")
+
+# PII detection
+result = sdk.process_document("/path/to/report.pdf", task="pii")
+
+# Both smart parsing and PII detection
+result = sdk.process_document("/path/to/report.pdf", task="both")
+```
+
+---
+
+## API Reference
+
+### Primary Methods
+
+| Method | Description |
+|--------|-------------|
+| `process_document(file_path, doc_type="lr", task="smart")` | Upload and process a document |
+| `get_document_result(document_id)` | Retrieve processing results for a document |
diff --git a/SDKs/ios/eka-scribe.mdx b/SDKs/ios/eka-scribe.mdx
deleted file mode 100644
index 4c5af053..00000000
--- a/SDKs/ios/eka-scribe.mdx
+++ /dev/null
@@ -1,807 +0,0 @@
-# EkaScribe
-
-A Swift package for voice-to-prescription functionality with floating UI components, audio recording, and real-time transcription capabilities for medical consultation applications.
-
-[![Swift Version](https://img.shields.io/badge/Swift-5.5+-orange.svg)](https://swift.org)
-[![Platform](https://img.shields.io/badge/Platform-iOS%2014.0+-blue.svg)](https://developer.apple.com/ios/)
-[![License](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
-
-## Overview
-
-EkaScribe empowers healthcare applications with advanced voice recording and transcription capabilities. It provides a seamless integration for medical consultation workflows, enabling doctors to record patient interactions and automatically generate prescriptions through AI-powered voice analysis.
-
-### Key Features
-
-- 🎙️ **Voice Activity Detection (VAD)** - Intelligent audio recording with automatic speech detection
-- 🔄 **Real-time Transcription** - Live audio-to-text conversion during consultations
-- 📱 **Floating UI Interface** - Picture-in-picture recording interface that stays accessible
-- 🏥 **Medical Context Aware** - Specialized for healthcare terminology and prescription generation
-- 📊 **Session Management** - Complete recording session lifecycle management
-- ☁️ **Cloud Integration** - Automatic audio upload and processing
-
-## Table of Contents
-
-- [Requirements](#requirements)
-- [Installation](#installation)
-- [Quick Start](#quick-start)
-- [Core Components](#core-components)
-- [Integration Guide](#integration-guide)
-- [Configuration](#configuration)
-- [Usage Examples](#usage-examples)
-- [Best Practices](#best-practices)
-- [API Reference](#api-reference)
-
-## Requirements
-
-- **iOS**: 14.0+
-- **Swift**: 5.5+
-- **Xcode**: 13.0+
-
-### System Permissions
-
-Add the following permissions to your app's `Info.plist`:
-
-```xml
-<key>NSMicrophoneUsageDescription</key>
-<string>This app needs microphone access to record medical consultations</string>
-<key>NSLocalNetworkUsageDescription</key>
-<string>This app needs network access to upload and process audio recordings</string>
-```
-
-## Installation
-
-### Swift Package Manager
-
-Add EkaScribe to your project using Swift Package Manager:
-
-1. In Xcode, select **File → Add Package Dependencies**
-2. Enter the repository URL:
-   ```
-   https://github.com/eka-care/EkaVoiceToRx.git
-   ```
-3. Choose the version or branch
-4. Add to your target
-
-### Package.swift
-
-```swift
-dependencies: [
-    .package(url: "https://github.com/eka-care/EkaVoiceToRx.git", from: "1.0.0")
-]
-```
-
-## Quick Start
-
-Here's a minimal example to get you started:
-
-```swift
-import EkaScribe
-import SwiftUI
-
-class ConsultationViewController: UIViewController {
-    private var viewModel: VoiceToRxViewModel?
-    
-    override func viewDidLoad() {
-        super.viewDidLoad()
-        setupVoiceToRx()
-    }
-    
-    private func setupVoiceToRx() {
-        // Configure the package
-        configureEkaScribe()
-        
-        // Initialize view model
-        viewModel = VoiceToRxViewModel(
-            voiceToRxInitConfig: V2RxInitConfigurations.shared,
-            voiceToRxDelegate: self
-        )
-        
-        // Show floating interface
-        Task {
-            await showFloatingRecordingInterface()
-        }
-    }
-    
-    private func configureEkaScribe() {
-        let config = V2RxInitConfigurations.shared
-        config.ownerName = "Dr. Smith"
-        config.ownerOID = "doctor123"
-        config.subOwnerName = "John Doe"
-        config.subOwnerOID = "patient456"
-        config.appointmentID = "appointment789"
-    }
-    
-    private func showFloatingRecordingInterface() async {
-        await FloatingVoiceToRxViewController.shared.showFloatingButton(
-            viewModel: viewModel!,
-            conversationType: .conversation,
-            liveActivityDelegate: nil
-        )
-    }
-}
-
-// MARK: - FloatingVoiceToRxDelegate
-extension ConsultationViewController: FloatingVoiceToRxDelegate {
-    func onCreateVoiceToRxSession(id: UUID?, params: VoiceToRxContextParams?) {
-        print("Session created with ID: \(id?.uuidString ?? "unknown")")
-    }
-    
-    func moveToDeepthoughtPage(id: UUID) {
-        // Navigate to prescription results page
-        print("Moving to results page for session: \(id)")
-    }
-    
-    func errorReceivingPrescription(id: UUID, errorCode: VoiceToRxErrorCode, transcriptText: String) {
-        print("Error in session \(id): \(errorCode)")
-    }
-    
-    func updateAppointmentsData(appointmentID: String, voiceToRxID: String) {
-        print("Updated appointment \(appointmentID) with voice session \(voiceToRxID)")
-    }
-}
-```
-
-## Core Components
-
-### VoiceToRxViewModel
-
-The central view model that manages the entire voice recording and processing workflow.
-
-```swift
-public class VoiceToRxViewModel: ObservableObject {
-    @Published public var screenState: RecordConsultationState
-    @Published public var filesProcessed: Set<String>
-    @Published public var uploadedFiles: Set<String>
-    
-    public var sessionID: UUID?
-    public var contextParams: VoiceToRxContextParams?
-}
-```
-
-#### Recording States
-
-```swift
-public enum RecordConsultationState {
-    case retry                          // Ready to retry after error
-    case startRecording                 // Initial state, ready to start
-    case listening(conversationType: VoiceConversationType) // Currently recording
-    case paused                        // Recording paused
-    case processing                    // Processing audio/generating prescription
-    case resultDisplay(success: Bool)  // Showing results
-    case deletedRecording             // Recording deleted
-}
-```
-
-#### Conversation Types
-
-```swift
-public enum VoiceConversationType: String, CaseIterable {
-    case conversation = "consultation"  // Doctor-patient conversation
-    case dictation                     // Direct prescription dictation
-}
-```
-
-### FloatingVoiceToRxViewController
-
-Provides a system-wide floating interface for recording control, similar to FaceTime's picture-in-picture.
-
-```swift
-public class FloatingVoiceToRxViewController: UIViewController {
-    public static let shared = FloatingVoiceToRxViewController()
-    
-    public func showFloatingButton(
-        viewModel: VoiceToRxViewModel,
-        conversationType: VoiceConversationType,
-        liveActivityDelegate: LiveActivityDelegate?
-    ) async
-    
-    public func hideFloatingButton()
-}
-```
-
-### Configuration Classes
-
-#### V2RxInitConfigurations
-
-Central configuration object for session parameters:
-
-```swift
-public class V2RxInitConfigurations {
-    public static let shared = V2RxInitConfigurations()
-    
-    public var modelContainer: ModelContainer?
-    public var ownerName: String?          // Doctor name
-    public var ownerOID: String?           // Doctor ID
-    public var ownerUUID: String?          // Doctor UUID
-    public var subOwnerOID: String?        // Patient ID
-    public var appointmentID: String?      // Appointment identifier
-    public var subOwnerName: String?       // Patient name
-}
-```
-
-## Integration Guide
-
-### Step 1: Configure Dependencies
-
-Set up authentication and core configurations:
-
-```swift
-private func configureAuthentication() {
-    // Set up authentication tokens
-    AuthTokenHolder.shared.authToken = KeychainHelper.fetchAuthToken()
-    AuthTokenHolder.shared.refreshToken = KeychainHelper.fetchRefreshToken()
-    AuthTokenHolder.shared.bid = JWTDecoder.shared.businessId
-}
-
-private func configureSessionParameters() {
-    let config = V2RxInitConfigurations.shared
-    
-    // Doctor information
-    config.ownerName = doctorName
-    config.ownerOID = doctorOID
-    config.ownerUUID = doctorUUID
-    
-    // Patient information
-    config.subOwnerName = patientName
-    config.subOwnerOID = patientOID
-    
-    // Appointment context
-    config.appointmentID = appointmentID
-    
-    // Database context
-    config.modelContainer = SwiftDataRepoContext.modelContext.container
-}
-```
-
-### Step 2: Implement Required Delegates
-
-#### FloatingVoiceToRxDelegate (Required)
-
-```swift
-extension YourViewController: FloatingVoiceToRxDelegate {
-    func onCreateVoiceToRxSession(id: UUID?, params: VoiceToRxContextParams?) {
-        guard let sessionId = id,
-              let patientId = params?.patient?.id else {
-            print("Failed to create session - missing required parameters")
-            return
-        }
-        
-        // Create local database entry
-        createLocalSessionRecord(sessionId: sessionId, patientId: patientId)
-        
-        // Update UI to reflect active session
-        updateUIForActiveSession(sessionId)
-    }
-    
-    func moveToDeepthoughtPage(id: UUID) {
-        // Navigate to prescription review/edit page
-        let storyboard = UIStoryboard(name: "Prescription", bundle: nil)
-        guard let prescriptionVC = storyboard.instantiateViewController(
-            withIdentifier: "PrescriptionViewController"
-        ) as? PrescriptionViewController else { return }
-        
-        prescriptionVC.sessionID = id
-        prescriptionVC.isEditMode = true
-        
-        navigationController?.pushViewController(prescriptionVC, animated: true)
-    }
-    
-    func errorReceivingPrescription(id: UUID, errorCode: VoiceToRxErrorCode, transcriptText: String) {
-        handleTranscriptionError(
-            sessionId: id,
-            error: errorCode,
-            transcript: transcriptText
-        )
-    }
-    
-    func updateAppointmentsData(appointmentID: String, voiceToRxID: String) {
-        // Update appointment record with voice session reference
-        Task {
-            await AppointmentService.shared.updateAppointment(
-                id: appointmentID,
-                voiceSessionId: voiceToRxID
-            )
-        }
-    }
-}
-```
-
-#### LiveActivityDelegate (Optional)
-
-For iOS Live Activities support during recording:
-
-```swift
-extension YourViewController: LiveActivityDelegate {
-    func startLiveActivity(patientName: String) async {
-        guard #available(iOS 16.1, *) else { return }
-        
-        let attributes = RecordingActivityAttributes(patientName: patientName)
-        let initialState = RecordingActivityState(
-            status: "Recording consultation...",
-            startTime: Date()
-        )
-        
-        do {
-            let activity = try Activity<RecordingActivityAttributes>.request(
-                attributes: attributes,
-                content: .init(state: initialState, staleDate: nil)
-            )
-            print("Live Activity started: \(activity.id)")
-        } catch {
-            print("Failed to start Live Activity: \(error)")
-        }
-    }
-    
-    func endLiveActivity() async {
-        guard #available(iOS 16.1, *) else { return }
-        
-        for activity in Activity<RecordingActivityAttributes>.activities {
-            await activity.end(nil, dismissalPolicy: .immediate)
-        }
-    }
-}
-```
-
-### Step 3: Initialize and Control Recording
-
-```swift
-class ConsultationViewController: UIViewController {
-    private var viewModel: VoiceToRxViewModel?
-    private var cancellables = Set<AnyCancellable>()
-    
-    override func viewDidLoad() {
-        super.viewDidLoad()
-        setupVoiceToRx()
-        observeRecordingStates()
-    }
-    
-    private func setupVoiceToRx() {
-        viewModel = VoiceToRxViewModel(
-            voiceToRxInitConfig: V2RxInitConfigurations.shared,
-            voiceToRxDelegate: self
-        )
-    }
-    
-    private func observeRecordingStates() {
-        viewModel?.$screenState
-            .receive(on: DispatchQueue.main)
-            .sink { [weak self] state in
-                self?.handleStateChange(state)
-            }
-            .store(in: &cancellables)
-    }
-    
-    private func handleStateChange(_ state: RecordConsultationState) {
-        switch state {
-        case .startRecording:
-            updateUI(status: "Ready to record")
-            
-        case .listening(let conversationType):
-            updateUI(status: "Recording \(conversationType.rawValue)...")
-            
-        case .paused:
-            updateUI(status: "Recording paused")
-            
-        case .processing:
-            updateUI(status: "Processing audio...")
-            showProcessingIndicator()
-            
-        case .resultDisplay(let success):
-            hideProcessingIndicator()
-            if success {
-                showSuccessMessage()
-            } else {
-                showErrorMessage()
-            }
-            
-        case .deletedRecording:
-            updateUI(status: "Recording deleted")
-            
-        case .retry:
-            updateUI(status: "Ready to retry")
-        }
-    }
-    
-    // MARK: - Recording Controls
-    
-    @IBAction func startRecordingTapped(_ sender: UIButton) {
-        Task {
-            await startRecording()
-        }
-    }
-    
-    @IBAction func pauseRecordingTapped(_ sender: UIButton) {
-        viewModel?.pauseRecording()
-    }
-    
-    @IBAction func resumeRecordingTapped(_ sender: UIButton) {
-        do {
-            try viewModel?.resumeRecording()
-        } catch {
-            showError("Failed to resume recording: \(error.localizedDescription)")
-        }
-    }
-    
-    @IBAction func stopRecordingTapped(_ sender: UIButton) {
-        Task {
-            await viewModel?.stopRecording()
-        }
-    }
-    
-    private func startRecording() async {
-        // Show floating interface first
-        await FloatingVoiceToRxViewController.shared.showFloatingButton(
-            viewModel: viewModel!,
-            conversationType: .conversation,
-            liveActivityDelegate: self
-        )
-        
-        // Start the actual recording
-        await viewModel?.startRecording(conversationType: .conversation)
-    }
-}
-```
-
-## Configuration
-
-### Audio Configuration
-
-EkaScribe automatically configures optimal audio settings, but you can customize them:
-
-```swift
-// Access the recording configuration
-let audioConfig = RecordingConfiguration.shared
-
-// Customize audio parameters (optional)
-audioConfig.sampleRate = 48000           // Default: 48kHz
-audioConfig.audioBufferSize = 4800       // Default: 4800 samples
-audioConfig.requiredSampleRate = 16000   // Processing rate: 16kHz
-```
-
-### Network Configuration
-
-Configure upload and processing endpoints:
-
-```swift
-// These are typically configured automatically through your app's backend integration
-// Contact your backend team for the proper endpoint configuration
-```
-
-## Usage Examples
-
-### Basic Recording Session
-
-```swift
-// Start a consultation recording
-await viewModel.startRecording(conversationType: .conversation)
-
-// The floating UI will appear automatically
-// User can control recording through the floating interface
-
-### Dictation Mode
-
-```swift
-// For direct prescription dictation
-await viewModel.startRecording(conversationType: .dictation)
-
-// This mode is optimized for single-speaker medical dictation
-// Less background noise filtering, more focused on medical terminology
-```
-
-### Session Management
-
-```swift
-// Delete current recording
-if let sessionID = viewModel.sessionID {
-    viewModel.deleteRecording(id: sessionID)
-}
-
-// Clear session data
-viewModel.clearSession()
-
-// Retry failed operations
-viewModel.retryIfNeeded()
-```
-
-### Custom UI Integration
-
-```swift
-// Create custom SwiftUI view with EkaScribe
-struct CustomRecordingView: View {
-    @ObservedObject var viewModel: VoiceToRxViewModel
-    
-    var body: some View {
-        VStack {
-            // Recording status
-            Text(recordingStatusText)
-                .font(.headline)
-                .foregroundColor(statusColor)
-            
-            // Control buttons
-            HStack {
-                Button(action: startRecording) {
-                    Image(systemName: "mic.circle.fill")
-                        .font(.system(size: 50))
-                        .foregroundColor(.red)
-                }
-                
-                Button(action: pauseRecording) {
-                    Image(systemName: "pause.circle.fill")
-                        .font(.system(size: 50))
-                        .foregroundColor(.orange)
-                }
-                
-                Button(action: stopRecording) {
-                    Image(systemName: "stop.circle.fill")
-                        .font(.system(size: 50))
-                        .foregroundColor(.gray)
-                }
-            }
-            
-            // Progress indicator
-            if case .processing = viewModel.screenState {
-                ProgressView("Processing audio...")
-                    .padding()
-            }
-        }
-        .padding()
-    }
-    
-    private var recordingStatusText: String {
-        switch viewModel.screenState {
-        case .startRecording: return "Ready to Record"
-        case .listening(let type): return "Recording \(type.rawValue.capitalized)"
-        case .paused: return "Paused"
-        case .processing: return "Processing..."
-        case .resultDisplay(let success): return success ? "Complete" : "Error"
-        case .deletedRecording: return "Deleted"
-        case .retry: return "Ready to Retry"
-        }
-    }
-    
-    private var statusColor: Color {
-        switch viewModel.screenState {
-        case .listening: return .red
-        case .paused: return .orange
-        case .processing: return .blue
-        case .resultDisplay(let success): return success ? .green : .red
-        default: return .primary
-        }
-    }
-}
-```
-
-## Best Practices
-
-### Memory Management
-
-```swift
-class ConsultationViewController: UIViewController {
-    private var viewModel: VoiceToRxViewModel?
-    private var cancellables = Set<AnyCancellable>()
-    
-    deinit {
-        // Clean up resources
-        viewModel?.clearSession()
-        cancellables.removeAll()
-        
-        // Hide floating interface
-        Task {
-            await FloatingVoiceToRxViewController.shared.hideFloatingButton()
-        }
-    }
-    
-    override func viewWillDisappear(_ animated: Bool) {
-        super.viewWillDisappear(animated)
-        
-        // Pause recording when leaving screen
-        if case .listening = viewModel?.screenState {
-            viewModel?.pauseRecording()
-        }
-    }
-}
-```
-
-### Network Optimization
-
-```swift
-private func setupNetworkMonitoring() {
-    // Monitor network connectivity for reliable uploads
-    let monitor = NWPathMonitor()
-    monitor.pathUpdateHandler = { [weak self] path in
-        DispatchQueue.main.async {
-            if path.status == .satisfied {
-                // Network available - retry failed uploads
-                self?.viewModel?.retryIfNeeded()
-            } else {
-                // Network unavailable - inform user
-                self?.showNetworkUnavailableWarning()
-            }
-        }
-    }
-    
-    let queue = DispatchQueue(label: "NetworkMonitor")
-    monitor.start(queue: queue)
-}
-```
-
-### Performance Optimization
-
-```swift
-// Optimize for long recording sessions
-private func optimizeForLongSessions() {
-    // Configure audio session for extended use
-    let audioSession = AVAudioSession.sharedInstance()
-    try? audioSession.setCategory(
-        .playAndRecord,
-        mode: .voiceChat,
-        options: [.defaultToSpeaker, .allowBluetooth]
-    )
-    
-    // Enable low-power mode optimizations
-    ProcessInfo.processInfo.performActivity(
-        options: .automaticTerminationDisabled,
-        reason: "Recording medical consultation"
-    ) { /* recording activity */ }
-}
-```
-
-## API Reference
-
-### VoiceToRxViewModel
-
-#### Properties
-
-```swift
-// Published properties for UI binding
-@Published public var screenState: RecordConsultationState
-@Published public var filesProcessed: Set<String>
-@Published public var uploadedFiles: Set<String>
-
-// Session information
-public var sessionID: UUID?
-public var contextParams: VoiceToRxContextParams?
-```
-
-#### Methods
-
-```swift
-// Core recording methods
-public func startRecording(conversationType: VoiceConversationType) async
-public func stopRecording() async
-public func pauseRecording()
-public func resumeRecording() throws
-
-// Session management
-public func deleteRecording(id: UUID)
-public func clearSession()
-public func retryIfNeeded()
-
-// Initialization
-public init(
-    voiceToRxInitConfig: V2RxInitConfigurations,
-    voiceToRxDelegate: FloatingVoiceToRxDelegate
-)
-```
-
-### FloatingVoiceToRxViewController
-
-#### Methods
-
-```swift
-// Show/hide floating interface
-public func showFloatingButton(
-    viewModel: VoiceToRxViewModel,
-    conversationType: VoiceConversationType,
-    liveActivityDelegate: LiveActivityDelegate?
-) async
-
-public func hideFloatingButton()
-```
-
-### Delegate Protocols
-
-#### FloatingVoiceToRxDelegate
-
-```swift
-protocol FloatingVoiceToRxDelegate {
-    func onCreateVoiceToRxSession(id: UUID?, params: VoiceToRxContextParams?)
-    func moveToDeepthoughtPage(id: UUID)
-    func errorReceivingPrescription(id: UUID, errorCode: VoiceToRxErrorCode, transcriptText: String)
-    func updateAppointmentsData(appointmentID: String, voiceToRxID: String)
-}
-```
-
-#### LiveActivityDelegate
-
-```swift
-protocol LiveActivityDelegate {
-    func startLiveActivity(patientName: String) async
-    func endLiveActivity() async
-}
-```
-
-### Configuration Classes
-
-#### V2RxInitConfigurations
-
-```swift
-public class V2RxInitConfigurations {
-    public static let shared: V2RxInitConfigurations
-    
-    // Core identifiers
-    public var ownerName: String?      // Doctor name
-    public var ownerOID: String?       // Doctor OID
-    public var ownerUUID: String?      // Doctor UUID
-    public var subOwnerOID: String?    // Patient OID
-    public var subOwnerName: String?   // Patient name
-    public var appointmentID: String?  // Appointment ID
-    
-    // Data context
-    public var modelContainer: ModelContainer?
-}
-```
-
-#### AuthTokenHolder
-
-```swift
-public class AuthTokenHolder {
-    public static let shared: AuthTokenHolder
-    
-    public var authToken: String?
-    public var refreshToken: String?
-    public var bid: String?
-}
-```
-
-#### 3. Session Creation Failures
-
-**Symptoms**: `onCreateVoiceToRxSession` not called or called with nil values
-
-**Solutions**:
-```swift
-// Verify all required configurations are set
-let config = V2RxInitConfigurations.shared
-assert(config.ownerOID != nil, "Doctor OID is required")
-assert(config.subOwnerOID != nil, "Patient OID is required")
-assert(config.appointmentID != nil, "Appointment ID is required")
-
-// Check authentication
-assert(AuthTokenHolder.shared.authToken != nil, "Auth token is required")
-```
-
-### Debug Mode
-
-Enable detailed logging for troubleshooting:
-
-```swift
-#if DEBUG
-// EkaScribe provides debug prints automatically
-// Check Xcode console for detailed logs including:
-// - Audio engine status
-// - Upload progress
-// - Session lifecycle
-// - Error details
-#endif
-```
-
-### Support Resources
-
-- **GitHub Issues**: [Report bugs or request features](https://github.com/eka-care/EkaVoiceToRx/issues)
-- **Documentation**: Check this guide and inline code documentation
-- **Sample Project**: Request access to the sample integration project
-- **Technical Support**: Contact the EkaScribe team for integration assistance
-
----
-
-## License
-
-EkaScribe is available under the MIT license. See the LICENSE file for more info.
-
-## Contributing
-
-We welcome contributions! Please see our contributing guidelines for details on how to submit pull requests, report issues, and suggest improvements.
-
----
-
-*Made with ❤️ by the Eka.Care team*
diff --git a/SDKs/web-sdk/abha-sdk.mdx b/SDKs/web-sdk/abha-sdk.mdx
deleted file mode 100644
index 2d63313b..00000000
--- a/SDKs/web-sdk/abha-sdk.mdx
+++ /dev/null
@@ -1,383 +0,0 @@
----
-title: ABHA SDK
-description: "Complete implementation guide for the ABHA[Ayushman Bharat Digital Mission] SDK"
----
-
-# ABHA SDK Implementation
-
-This guide provides everything you need to integrate the ABHA SDK into your application.
-
-## Overview
-
-The ABHA SDK allows you to integrate Create ABHA, Login with ABHA flows into your healthcare applications. It provides:
-
-- **Create ABHA**: Create a new ABHA using Mobile or Aadhaar
-- **Login with ABHA**: Login with ABHA address[PHR Address], ABHA number, Adhaar number or Mobile number linked to your ABHA into your healthcare application.
-
-## Installation
-
-### Prerequisites
-
-- A modern web browser.
-- Your domain must be whitelisted with Eka Care to avoid CORS(Cross-Origin Resource Sharing) error.
-  (Contact Eka Care to request API access and domain whitelisting.)
-- A valid HTML container element where the SDK will mount.
-
-### Setup
-
-Add the following HTML and script tags to your webpage:
-
-```html
-<!DOCTYPE html>
-<html>
-  <head>
-    <title>ABHA SDK Integration</title>
-
-    <!-- Include ABHA SDK CSS -->
-    <link
-      rel="stylesheet"
-      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
-    />
-  </head>
-  <body>
-    <h1>ABHA SDK Demo</h1>
-
-    <!-- Mount Button -->
-    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
-
-    <!-- Container for ABHA SDK -->
-    <div id="sdk_container"></div>
-
-    <!-- Include ABHA SDK JS -->
-    <script
-      type="module"
-      async
-      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
-    ></script>
-
-    <script>
-      function mountABHASDK() {
-        window.initAbhaApp({
-          containerId: "sdk_container",
-        
-         // Pass access token and oid
-          data: {
-            accessToken: "<your_access_token>", // Pass the access token you have
-            oid: "<your_oid_if_available>", // Pass if you have the OID
-          },
-
-          // Success callback
-          onSuccess: async (params) => {
-            console.log("ABHA flow completed successfully:", params);
-            // Example: Store ABHA data in your app
-            dispatch({
-              type: "set-only-healthid-data",
-              healthIdData: formatter(params.response.data),
-            });
-          },
-
-          // Error callback
-          onError: (params) => {
-            console.error("ABHA flow failed:", params);
-            if (window.EkaAbha) {
-              window.EkaAbha.onAbhaFailure(JSON.stringify(params));
-            }
-          },
-        });
-      }
-    </script>
-  </body>
-</html>
-```
-## Core Functions
-
-### 1. initAbhaApp
-
-Initializes and renders the ABHA SDK in your specified container.
-
-**Parameters:**
-
-| Name          | Type                                    | Required    | Description                                                                                                                                    |
-| ------------- | --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `containerId` | `string`                                | ✅           | The HTML element ID where the SDK will mount.                                                                                                  |
-| `data`        | `{ accessToken: string; oid?: string }` | ⚙️ Optional |  Configuration data for secure API integration. <br/>- `accessToken`: Pass the access token you have. <br/>- `oid`: Pass if available. |
-| `onSuccess`   | `(params: AbhaSuccessParams) => void`   | ✅           | Triggered when the user successfully creates or logs in to ABHA.                                                                               |
-| `onError`     | `(params: AbhaErrorParams) => void`     | ✅           | Triggered when an error occurs during the ABHA flow.                                                                                           |
-
-**Example:**
-
-```javascript
-window.initAbhaApp({
-  containerId: "sdk_container",
-  data: {
-    accessToken: "your_access_token_here",
-    oid: "optional_oid_here",
-  },
-  onSuccess: (params) => {
-    console.log("ABHA created successfully!", params);
-  },
-  onError: (error) => {
-    console.error("ABHA flow failed:", error);
-  },
-});
-```
-
-## Callback Parameters
-
-### onSuccess Callback
-
-The onAbhaSuccess callback is triggered when the ABHA flow completes successfully.
-It returns verified user details and tokens, which can be used to log in or continue the user’s session.
-
-**Callback Signature:**
-
-```typescript
-onSuccess: (params: TOnAbhaSuccessParams) => void;
-```
-
-**Type Definitions**
-
-```typescript
-export type TOnAbhaSuccessParams = {
-  response: TAuthVerifyV2Response;
-};
-
-export type TAuthVerifyV2Response = {
-  skip_state: number;
-  method: AUTH_METHOD;
-  data?: {
-    tokens: {
-      sess: string;
-      refresh: string;
-    };
-    profile: TProfileRecord;
-  };
-  txn_id: string;
-  error?: {
-    code: number;
-    message: string;
-  };
-};
-```
-
-**Parameters**
-| Key        | Type                    | Description                                                                                                |
-| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
-| `response` | `TAuthVerifyV2Response` | The complete ABHA verification response, containing session tokens, user profile, and transaction details. |
-
-
-
-**Example:**
-
-```javascript
-const onSuccess = (params) => {
-  console.log("ABHA Success:", params.response);
-
-  const abhaNumber = params.response.data?.profile?.abha_number;
-  const userName = params.response.data?.profile?.name;
-
-  alert(`Welcome ${userName}! Your ABHA Number: ${abhaNumber}`);
-
-  // Optionally pass data to native bridge
-  if (window.EkaAbha) {
-    window.EkaAbha.onAbhaSuccess(JSON.stringify(params));
-  }
-};
-```
-
-### onError Callback
-The onError callback is triggered whenever an ABHA flow fails or is interrupted.
-It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
-
-**Callback Signature:**
-
-```typescript
-onError: (params: TOnAbhaFailureParams) => void;
-```
-
-**Type Definitions**
-
-```typescript
-type TOnAbhaFailureParams = {
-  error?: string;
-  response?: TAuthVerifyV2Response;
-};
-
-export type TAuthVerifyV2Response = {
-  skip_state: number;
-  method: AUTH_METHOD;
-  data?: {
-    tokens: {
-      sess: string;
-      refresh: string;
-    };
-    profile: TProfileRecord;
-  };
-  txn_id: string;
-  error?: {
-    code: number;
-    message: string;
-  };
-};
-```
-
-**Parameters**
-| Key        | Type                     | Description                                                      |
-| ---------- | ------------------------ | ---------------------------------------------------------------- |
-| `error`    | `string?`                | Short description of the failure or error message.               |
-| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
-
-
-**Example:**
-
-```javascript
-const onError = (params) => {
-  console.error("ABHA Error:", params);
-
-  if (params.response?.error?.code === 1001) {
-    alert("Authentication failed. Please try again.");
-  } else if (params.error === "NETWORK_ERROR") {
-    alert("Please check your internet connection.");
-  } else {
-    alert("Something went wrong. Please retry.");
-  }
-
-  // Forward the error to native handler if available
-  if (window.EkaAbha) {
-    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
-  }
-};
-```
-
-**Suggest Handling**
--Always log the full error response (params) for debugging.
--Display friendly error messages for known error.code values.
--If params.response is present, inspect response.error.message for more detail.
--If integrating with native apps, forward the serialized error object:
-```javascript
-window.EkaAbha.onAbhaFailure(JSON.stringify(params));
-```
-
-### Container Styling
-Ensure your container has sufficient space:
-```html
-<div
-  id="sdk_container"
-  style="width: 100%; height: 600px; border: 1px solid #ddd;"
-></div>
-```
-
-## Complete Implementation Example
-
-```html
-<!DOCTYPE html>
-<html>
-  <head>
-    <title>ABHA SDK Complete Example</title>
-    <link
-      rel="stylesheet"
-      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
-    />
-  </head>
-  <body>
-    <h1>ABHA SDK Demo</h1>
-
-    <button onclick="mountABHASDK()">Launch ABHA SDK</button>
-
-    <div
-      id="sdk_container"
-      style="width: 100%; height: 600px; border: 1px solid #ccc;"
-    ></div>
-
-    <script
-      type="module"
-      async
-      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
-    ></script>
-
-    <script>
-      function mountABHASDK() {
-        window.initAbhaApp({
-          containerId: "sdk_container",
-          data: {
-            accessToken: "<your_access_token>", 
-            oid: "<your_oid_if_available>", 
-          },
-          onSuccess: (params) => {
-            console.log("ABHA flow completed successfully:", params);
-          },
-          onError: (params) => {
-            console.error("ABHA flow failed:", params);
-          },
-        });
-      }
-    </script>
-  </body>
-</html>
-```
-
-## Type Definitions
-
-```typescript
-interface InitAbhaAppParams {
-  containerId: string;
-  data?: {
-    accessToken: string;
-    oid?: string;
-  };
-  onSuccess: (params: AbhaSuccessParams) => void;
-  onError: (params: AbhaErrorParams) => void;
-}
-
-interface AbhaSuccessParams {
-  response: {
-    data: {
-      abha_number?: string;
-      abha_address?: string;
-      name?: string;
-      gender?: string;
-      yearOfBirth?: string;
-      mobile?: string;
-    };
-  };
-  message: string;
-  status: "SUCCESS";
-}
-
-interface AbhaErrorParams {
-  status: "FAILED";
-  message: string;
-  error_code?: string;
-  details?: any;
-}
-```
-
-## Troubleshooting
-
-### Common Issues
-
-#### 1. SDK Not Rendering
-
-**Problem**: Nothing appears in the container.
-
-**Solution**:
-- Ensure containerId matches an existing HTML element.
-- Verify the SDK JS and CSS are correctly loaded.
-- Check browser console for errors.
-
-#### 2. Callback Not Triggered
-
-**Problem**: onSuccess or onError isn’t firing.
-
-**Solution**:
-- Make sure both callbacks are passed as valid functions.
-- Avoid race conditions (e.g., calling before SDK fully loads).
-
-#### 3. Styling Issues
-
-**Problem**: SDK content appears misaligned or clipped.
-
-**Solution**:
-- Give your container a fixed height (e.g., 600px).
-- Ensure no parent element uses overflow: hidden.
-
diff --git a/SDKs/web-sdk/abha-sdk/abha-consent.mdx b/SDKs/web-sdk/abha-sdk/abha-consent.mdx
new file mode 100644
index 00000000..df31e2b9
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/abha-consent.mdx
@@ -0,0 +1,353 @@
+---
+title: Consent Management
+description: "Complete implementation guide for the ABHA SDK to be used for ABHA Consent Management Flow."
+---
+
+
+# ABHA SDK - Consent Management Implementation
+
+This guide provides everything you need to integrate the ABHA SDK into your application for ABHA Consent Management.
+- **ABHA Consent Management**: Manage Consent requests raised by healthcare providers to share medical records securely.
+
+### Implementation Example
+
+Add the following HTML and script tags to your webpage:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>ABHA SDK Integration for ABHA Consent Management</title>
+
+    <!-- Include ABHA SDK CSS -->
+    <link
+      rel="stylesheet"
+      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
+    />
+  </head>
+  <body>
+    <h1>ABHA SDK Demo</h1>
+
+    <!-- Mount Button -->
+    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
+
+    <!-- Container for ABHA SDK -->
+    <div id="sdk_container"></div>
+
+    <!-- Include ABHA SDK JS -->
+    <script
+      type="module"
+      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
+    ></script>
+
+    <script>
+      function mountABHASDK() {
+        window.initAbhaApp({
+          containerId: "sdk_container",
+          clientId: 'ext',
+
+         // Pass the data here: 
+          data: {
+             accessToken: '<available_access_token>', // Pass the access token you have without Bearer prefix
+             oid: '<patient_oid>', // Pass Patient OID
+             hipId:'<available_HFR_ID>', // Pass the HFR ID you have
+             identifier:'abc@abdm', // Pass the phr address as identifier
+             identifier_type:"phr_address",  // Pass the identifier type i.e. "phr_address"
+             consent_id: '<consent_id_of_the_consent_raised>' // Pass the consent id of the consent request raised by the healthcare provider
+             flow:'consent', // Pass the flow as consent
+             orgIconUrl: "<url_of_your_org_logo>", // Pass the url of the logo of your organisation for ex https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png
+             linkToOrgIcon: "<url_of_image_to_link_abha_to_your_org>", // Pass the url of an image which depicts linking abha to your organisation for ex https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp
+          },
+
+          //Consent Successs callback
+          onConsentSuccess: (params) => {
+            console.log("ABHA Consent flow completed successfully:", params);
+            
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaConsentSuccess(JSON.stringify(params));
+            }
+          },
+
+          // Error callback
+          onError: (params) => {
+            console.error("ABHA SDK failed:", params);
+
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+            }
+          },
+
+          // Abha Close callback
+          onAbhaClose: () => {
+            console.log("ABHA SDK closed");
+          },
+         
+        });
+      }
+    </script>
+  </body>
+</html>
+```
+## Core Functions
+
+### 1. initAbhaApp
+
+Initializes and renders the ABHA SDK in your specified container.
+
+**Parameters:**
+
+| Name          | Type                                    | Required    | Description                                                                                                                                    |
+| ------------- | --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `containerId` | `string`                                | ✅           | The HTML element ID where the SDK will mount.                                                                                                  |
+| `clientId` | `string`                                | ✅           | Provide clientId as `ext`.                                                                                                  |
+| `data` | `{`<br/>`accessToken: string;`<br/>`oid?: string;`<br/> `hipId?: string;`<br/>`identifier: string;`<br/>`identifier_type: string;`<br/>`consent_id: string;`<br/>`flow: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string;`<br/>`}` | ⚙️ Optional | Configuration data for initializing the ABHA flow.<br/>- <strong>accessToken:</strong> Pass the access token you have generated from [Connect Login ](https://developer.eka.care/api-reference/authorization/client-login) API without the word `Bearer`.<br/>- <strong>oid:</strong> Pass the OID of the patient if available. <br/>- <strong>hipId:</strong> Pass the HFR ID you have.<br/>- <strong>identifier:</strong> Pass the identifier value i.e. phr address to get it kyced.<br/>- <strong>identifier_type:</strong> Pass the type of identifier which you passed in `identifier` key i.e. "phr_address". <br/>- <strong>consent_id:</strong> Pass the consent_id of the consent request raised. <br/>- <strong>flow:</strong> Pass the type of flow for which you want to use SDK for i.e. `consent` for Consent flow. <br/>- <strong>orgIconUrl:</strong> Public CDN URL of the logo of your organisation url should start with https://. [Example](https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png)<br/>- <strong>linkToOrgIcon:</strong> Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. [Example](https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp)<br/> <br/> `keys with ? are optional.` |
+| `onConsentSuccess`   | `(params: TOnAbhaConsentSuccessParams) => void`   | ✅           | Triggered when the consent flow completes successfully.
+| `onError`     | `(params: TOnAbhaFailureParams) => void`     | ✅           | Triggered when an error occurs during the ABHA flow.       
+| `onAbhaClose`     | `() => void`     | ✅           | Triggered when SDK closes.                                                                                           |
+
+**Example:**
+
+```javascript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  data: {
+    accessToken: "your_access_token_here",
+    oid: "patient_oid_here",
+    hipId:"available_HFR_ID",
+    identifier: "phr_address_of_the_patient"
+    identifier_type: "phr_address"
+    consent_id: "id_of_the_consent_raised_by_healthcare_provider"
+    flow: "consent"
+    linkToOrgIcon: "url_of_image_to_link_abha_to_your_org",
+  },
+  onConsentSuccess: (params) => {
+    console.log("ABHA consent flow completed successfully!", params);
+  },
+  onError: (error) => {
+    console.error("ABHA flow failed:", error);
+  },
+  onAbhaClose: (error) => {
+    console.error("ABHA SDK closed");
+  },
+});
+```
+
+## Callback Parameters
+
+
+### onConsentSuccess Callback
+
+The onConsentSuccess callback is triggered when the ABHA Consent flow completes successfully. 
+It returns a confirmation message indicating that the Consent flow ended successfully.
+
+**Callback Signature:**
+
+```typescript
+onConsentSuccess: (params: TOnAbhaConsentSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaConsentSuccessParams = string;
+```
+
+**Parameters**
+|         | Type                    | Description                                                                                                |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `TOnAbhaConsentSuccessParams` | `string` | A confirmation message from SDK post Consent flow completion |
+
+
+
+**Example:**
+
+```javascript
+const onConsentSuccess = (params) => {
+  console.log("Consent Flow completed:", params);
+
+  alert("Consent flow completed successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaConsentSuccess(params);
+  }
+};
+```
+
+### onError Callback
+The onError callback is triggered whenever an ABHA flow fails or is interrupted.
+It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
+
+**Callback Signature:**
+
+```typescript
+onError: (params: TOnAbhaFailureParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaFailureParams = {
+  error?: string;
+  response?: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+
+```
+
+**Parameters**
+| Key        | Type                     | Description                                                      |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `error`    | `string?`                | Short description of the failure or error message.               |
+| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
+
+
+**Example:**
+
+```javascript
+const onError = (params) => {
+  console.error("ABHA Error:", params);
+
+  if (params.response?.error?.code === 1001) {
+    alert("Authentication failed. Please try again.");
+  } else if (params.error === "NETWORK_ERROR") {
+    alert("Please check your internet connection.");
+  } else {
+    alert("Something went wrong. Please retry.");
+  }
+
+  // Forward the error to native handler if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+  }
+};
+```
+
+### onAbhaClose Callback
+
+The onAbhaClose callback is triggered when the ABHA SDK flow gets closed. 
+
+**Callback Signature:**
+
+```typescript
+onAbhaClose: () => void;
+```
+
+**Example:**
+
+```javascript
+const onAbhaClose = () => {
+  console.log("ABHA SDK Closed");
+};
+```
+
+**Parameters**
+| Key        | Type                     | Description                                                      |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `identifier`    | `string?`                | It will be login identifier value filled by user.               |
+| `identifier_type` | `IdentifierType[]?` | It will be type of login identifier. |
+
+**Suggest Handling**
+- Always log the full error response (params) for debugging.
+- Display friendly error messages for known error.code values.
+- If params.response is present, inspect response.error.message for more detail.
+- If integrating with native apps, forward the serialized error object:
+```javascript
+window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+```
+
+## Container Styling
+Ensure your container has sufficient space:
+```html
+<div
+  id="sdk_container"
+  style="width: 100%; height: 600px; border: 1px solid #ddd;"
+></div>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### 1. SDK Not Rendering
+
+**Problem**: Nothing appears in the container.
+
+**Solution**:
+- Ensure containerId matches an existing HTML element.
+- Verify the SDK JS and CSS are correctly loaded.
+- Check browser console for errors.
+
+#### 2. APIs Not Being Called
+
+**Problem**: API requests are not triggered after the SDK is mounted.
+
+**Solution**:
+- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
+- To prevent CORS-related issues, ensure that your domain is whitelisted.
+
+#### 3. Callback Not Triggered
+
+**Problem**: onSuccess, onError, onKYCSuccess, onConsentSuccess, onAbhaClose isn’t firing.
+
+**Solution**:
+- Make sure callbacks are passed as valid functions.
+- Avoid race conditions (e.g., calling before SDK fully loads).
+
+#### 4. Styling Issues
+
+**Problem**: SDK content appears misaligned or clipped.
+
+**Solution**:
+- Give your container a fixed height (e.g., 600px).
+- Ensure no parent element uses overflow: hidden.
+
diff --git a/SDKs/web-sdk/abha-sdk/abha-kyc.mdx b/SDKs/web-sdk/abha-sdk/abha-kyc.mdx
new file mode 100644
index 00000000..2d36dd88
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/abha-kyc.mdx
@@ -0,0 +1,344 @@
+---
+title: Profile KYC
+description: "Complete implementation guide for the ABHA SDK to be used for ABHA KYC Verification Flow."
+---
+
+# ABHA SDK - Profile KYC Implementation
+
+This guide provides everything you need to integrate the ABHA SDK into your application for ABHA Profile KYC Verification.
+- **ABHA Profile KYC**: Get your ABHA address KYC verified.
+
+### Implementation Example
+
+Add the following HTML and script tags to your webpage:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>ABHA SDK Integration for ABHA Profile KYC</title>
+
+    <!-- Include ABHA SDK CSS -->
+    <link
+      rel="stylesheet"
+      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
+    />
+  </head>
+  <body>
+    <h1>ABHA SDK Demo</h1>
+
+    <!-- Mount Button -->
+    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
+
+    <!-- Container for ABHA SDK -->
+    <div id="sdk_container"></div>
+
+    <!-- Include ABHA SDK JS -->
+    <script
+      type="module"
+      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
+    ></script>
+
+    <script>
+      function mountABHASDK() {
+        window.initAbhaApp({
+          containerId: "sdk_container",
+          clientId: 'ext',
+
+         // Pass the data here: 
+          data: {
+             accessToken: "<your_access_token>", // Pass the access token you have
+             oid: "<patient_oid>", // Pass OID of the patient
+             hipId: "<available_HFR_ID>", // Pass the HFR ID you have
+             identifier:'<phr_address_of_the_patient_to_be_kyced>', // Pass the phr address as identifier to get it kyc verified 
+             identifier_type:"phr_address",  // Pass the identifier type i.e. "phr_address"
+             flow:'abha-kyc', // Pass the flow as abha-kyc
+             orgIconUrl: "<url_of_your_org_logo>", // Pass the url of the logo of your organisation for ex https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png
+             linkToOrgIcon: "<url_of_image_to_link_abha_to_your_org>", // Pass the url of an image which depicts linking abha to your organisation for ex https://cdn.eka.c
+          },
+
+          // KYC Success callback
+          onKYCSuccess: (params) => {
+            console.log("ABHA KYC Verified successfully:", params);
+            
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaKYCSuccess(JSON.stringify(params));
+            }
+          },
+
+          // Error callback
+          onError: (params) => {
+            console.error("ABHA SDK failed:", params);
+
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+            }
+          },
+
+          // Abha Close callback
+          onAbhaClose: () => {
+            console.log("ABHA SDK closed");
+          }, 
+
+        });
+      }
+    </script>
+  </body>
+</html>
+```
+## Core Functions
+
+### 1. initAbhaApp
+
+Initializes and renders the ABHA SDK in your specified container.
+
+**Parameters:**
+
+| Name          | Type                                    | Required    | Description                                                                                                                                    |
+| ------------- | --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `containerId` | `string`                                | ✅           | The HTML element ID where the SDK will mount.                                                                                                  |
+| `clientId` | `string`                                | ✅           | Provide clientId as `ext`.                                                                                                  |
+| `data` | `{`<br/>`accessToken: string;`<br/>`oid?: string;`<br/>`hipId?: string;`<br/>`identifier: string;`<br/>`identifier_type: string;`<br/>`flow: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string;`<br/>` }` | ⚙️ Optional | Configuration data for initializing the ABHA flow. <br/><br/>- <strong>accessToken:</strong> Pass the access token you have generated from [Connect Login ](https://developer.eka.care/api-reference/authorization/client-login) API without the word `Bearer`.<br/>- <strong>oid:</strong> Pass the OID of the patient if available.<br/>- <strong>hipId:</strong> Pass the HFR ID you have.<br/>- <strong>identifier:</strong> Pass the identifier value i.e. phr address to get it kyced.<br/>- <strong>identifier_type:</strong> Pass the type of identifier which you passed in `identifier` key i.e. "phr_address".  <br/>- <strong>flow:</strong> Pass the type of flow for which you want to use SDK for i.e. `abha-kyc` for KYC flow.<br/>- <strong>orgIconUrl:</strong> Public CDN URL of the logo of your organisation url should start with https://. [Example](https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png)<br/>- <strong>linkToOrgIcon:</strong> Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. [Example](https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp)<br/> <br/> `keys with ? are optional.` |
+| `onKYCSuccess`   | `(params: TOnAbhaKycSuccessParams) => void`   | ✅  | Triggered when the user KYC verified successfully.
+| `onError`     | `(params: TOnAbhaFailureParams) => void`     | ✅           | Triggered when an error occurs during the ABHA flow.       
+| `onAbhaClose`     | `() => void`     | ✅           | Triggered when SDK closes.          
+
+**Example:**
+
+```javascript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  data: {
+    accessToken: "your_access_token_here",
+    oid: "patient_oid_here",
+    identifier: "phr_address_of_the_patient_to_be_kyced"
+    identifier_type: "phr_address"
+    flow: "abha-kyc"
+    hipId: "available HFR ID",
+    linkToOrgIcon: "url_of_image_to_link_abha_to_your_org",
+  },
+  onKYCSuccess: (params) => {
+    console.log("ABHA KYC verification successful!", params);
+  },
+  onError: (error) => {
+    console.error("ABHA flow failed:", error);
+  },
+  onAbhaClose: (error) => {
+    console.error("ABHA SDK closed");
+  },
+});
+```
+
+## Callback Parameters
+
+
+### onKYCSuccess Callback
+
+The onKYCSuccess callback is triggered when the ABHA KYC flow completes successfully. 
+It returns a confirmation message indicating that the KYC has been verified.
+
+**Callback Signature:**
+
+```typescript
+onKYCSuccess: (params: TOnAbhaKycSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaKycSuccess = string;
+```
+
+**Parameters**
+|         | Type                    | Description                                                                                                |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `TOnAbhaKycSuccess` | `string` | A confirmation message from SDK post KYC verification |
+
+
+
+**Example:**
+
+```javascript
+const onKYCSuccess = (params) => {
+  console.log("KYC verification Success:", params);
+
+  alert("KYC was verified successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaKYCSuccess(params);
+  }
+};
+```
+
+### onError Callback
+The onError callback is triggered whenever an ABHA flow fails or is interrupted.
+It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
+
+**Callback Signature:**
+
+```typescript
+onError: (params: TOnAbhaFailureParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaFailureParams = {
+  error?: string;
+  response?: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+
+```
+
+**Parameters**
+| Key        | Type                     | Description                                                      |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `error`    | `string?`                | Short description of the failure or error message.               |
+| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
+
+
+**Example:**
+
+```javascript
+const onError = (params) => {
+  console.error("ABHA Error:", params);
+
+  if (params.response?.error?.code === 1001) {
+    alert("Authentication failed. Please try again.");
+  } else if (params.error === "NETWORK_ERROR") {
+    alert("Please check your internet connection.");
+  } else {
+    alert("Something went wrong. Please retry.");
+  }
+
+  // Forward the error to native handler if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+  }
+};
+```
+
+### onAbhaClose Callback
+
+The onAbhaClose callback is triggered when the ABHA SDK flow gets closed. 
+
+**Callback Signature:**
+
+```typescript
+onAbhaClose: () => void;
+```
+
+**Example:**
+
+```javascript
+const onAbhaClose = () => {
+  console.log("ABHA SDK Closed");
+};
+```
+
+**Suggest Handling**
+- Always log the full error response (params) for debugging.
+- Display friendly error messages for known error.code values.
+- If params.response is present, inspect response.error.message for more detail.
+- If integrating with native apps, forward the serialized error object:
+```javascript
+window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+```
+
+## Container Styling
+Ensure your container has sufficient space:
+```html
+<div
+  id="sdk_container"
+  style="width: 100%; height: 600px; border: 1px solid #ddd;"
+></div>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### 1. SDK Not Rendering
+
+**Problem**: Nothing appears in the container.
+
+**Solution**:
+- Ensure containerId matches an existing HTML element.
+- Verify the SDK JS and CSS are correctly loaded.
+- Check browser console for errors.
+
+#### 2. APIs Not Being Called
+
+**Problem**: API requests are not triggered after the SDK is mounted.
+
+**Solution**:
+- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
+- To prevent CORS-related issues, ensure that your domain is whitelisted.
+
+#### 3. Callback Not Triggered
+
+**Problem**: onSuccess, onError, onKYCSuccess, onConsentSuccess, onAbhaClose isn’t firing.
+
+**Solution**:
+- Make sure callbacks are passed as valid functions.
+- Avoid race conditions (e.g., calling before SDK fully loads).
+
+#### 4. Styling Issues
+
+**Problem**: SDK content appears misaligned or clipped.
+
+**Solution**:
+- Give your container a fixed height (e.g., 600px).
+- Ensure no parent element uses overflow: hidden.
+
diff --git a/SDKs/web-sdk/abha-sdk/abha-login-create.mdx b/SDKs/web-sdk/abha-sdk/abha-login-create.mdx
new file mode 100644
index 00000000..bc510084
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/abha-login-create.mdx
@@ -0,0 +1,440 @@
+---
+title: Registration
+description: "Complete implementation guide for the ABHA SDK to be used for ABHA Login or Create."
+---
+
+# ABHA SDK - Login or Create 
+
+This guide provides everything you need to integrate the ABHA SDK into your application for Create ABHA, Login with ABHA flows into your healthcare applications. It provides:
+
+- **Create ABHA**: Create a new ABHA using Mobile or Aadhaar.
+- **Login with ABHA**: Login to your exisiting ABHA using PHR Address, ABHA number, Aadhaar number or Mobile number.
+
+### Implementation Example
+
+Add the following HTML and script tags to your webpage:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>ABHA SDK Integration</title>
+
+    <!-- Include ABHA SDK CSS -->
+    <link
+      rel="stylesheet"
+      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
+    />
+  </head>
+  <body>
+    <h1>ABHA SDK Demo</h1>
+
+    <!-- Mount Button -->
+    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
+
+    <!-- Container for ABHA SDK -->
+    <div id="sdk_container"></div>
+
+    <!-- Include ABHA SDK JS -->
+    <script
+      type="module"
+      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
+    ></script>
+
+    <script>
+      function mountABHASDK() {
+        window.initAbhaApp({
+          containerId: "sdk_container",
+          clientId: 'ext',
+        
+         // Pass access token and oid
+          data: {
+            accessToken: "<your_access_token>", // Pass the access token you have
+            oid: "<patient_oid>", // Pass OID of the patient
+            hipId: "<available_HFR_ID>", // Pass the HFR ID you have
+            orgIconUrl: "<url_of_your_org_logo>", // Pass the url of the logo of your organisation for ex https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png
+            linkToOrgIcon: "<url_of_image_to_link_abha_to_your_org>", // Pass the url of an image which depicts linking abha to your organisation for ex https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp
+            skipABHAEnable: "<boolean_value_here>" // Pass boolean as true if you want Skip ABHA button to be enabled on login screen
+          },
+
+          // Success callback
+          onSuccess: (params) => {
+            console.log("ABHA Registration flow completed successfully:", params);
+            
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaSuccess(JSON.stringify(params));
+            }
+          },
+
+          // Error callback
+          onError: (params) => {
+            console.error("ABHA SDK failed:", params);
+
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+            }
+          },
+
+          // Abha Close callback
+          onAbhaClose: () => {
+            console.log("ABHA SDK closed");
+          },
+
+          // Skip ABHA callback
+          onSkipAbha: (params) => {
+            console.log("ABHA flow SKIPPED:", params);
+          },
+
+        });
+      }
+    </script>
+  </body>
+</html>
+```
+## Core Functions
+
+### 1. initAbhaApp
+
+Initializes and renders the ABHA SDK in your specified container.
+
+**Parameters:**
+
+| Name          | Type                                    | Required    | Description                                                                                                                                    |
+| ------------- | --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `containerId` | `string`                                | ✅           | The HTML element ID where the SDK will mount.                                                                                                  |
+| `clientId` | `string`                                | ✅           | Provide clientId as `ext`.                                                                                                  |
+| `data` | `{`<br/>`accessToken: string;`<br/>`oid?: string;`<br/>`hipId?: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string;`<br/>`skipABHAEnable?: boolean;`<br/>`}` | ⚙️ Optional | Configuration data for initializing the ABHA flow. <br/><br/>- <strong>accessToken:</strong> Pass the access token you have generated from [Connect Login ](https://developer.eka.care/api-reference/authorization/client-login) API without the word `Bearer`. <br/>- <strong>oid:</strong> Pass the OID of the patient if available. <br/>- <strong>hipId:</strong> Pass the HFR ID you have. <br/>- <strong>orgIconUrl:</strong> Public CDN URL of the logo of your organisation url should start with https://. [Example](https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png)<br/>- <strong>linkToOrgIcon:</strong> Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. [Example](https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp)<br/>- <strong>skipABHAEnable:</strong> Pass the boolean as true if you want Skip ABHA button to be enabled on login screen.<br/><br/> `keys with ? are optional.` |
+| `onSuccess`   | `(params: TOnAbhaSuccessParams) => void`   | ✅           | Triggered when the user successfully creates or logs in to ABHA.                                                                               |
+| `onError`     | `(params: TOnAbhaFailureParams) => void`     | ✅           | Triggered when an error occurs during the ABHA flow.       
+| `onAbhaClose`     | `() => void`     | ✅           | Triggered when SDK closes.       
+| `onSkipAbha`   | `(params: TOnSkipABHA) => void`   | ⚙️ Optional | Triggered if the ABHA flow is skipped.                                                                                       |                                                                                    |
+
+**Example:**
+
+```javascript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  data: {
+    accessToken: "your_access_token_here",
+    oid: "patient_oid_here",
+    hipId: "available HFR ID",
+    linkToOrgIcon: "url_of_image_to_link_abha_to_your_org",
+    skipABHAEnable: "boolean_value_here"
+  },
+  onSuccess: (params) => {
+    console.log("ABHA created successfully!", params);
+  },
+  onError: (error) => {
+    console.error("ABHA flow failed:", error);
+  },
+  onAbhaClose: (error) => {
+    console.error("ABHA SDK closed");
+  },
+  onSkipAbha: (params) => {
+    console.log("ABHA flow skipped by user:", params);
+  },
+
+});
+```
+
+## Callback Parameters
+
+### onSuccess Callback
+
+The onSuccess callback is triggered when the ABHA flow completes successfully.
+It returns verified user details and tokens, which can be used to log in or continue the user’s session.
+
+**Callback Signature:**
+
+```typescript
+onSuccess: (params: TOnAbhaSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaSuccessParams = {
+  response: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+
+```
+
+**Parameters**
+| Key        | Type                    | Description                                                                                                |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `response` | `TAuthVerifyV2Response` | The complete ABHA verification response, containing session tokens, user profile, and transaction details. |
+
+
+
+**Example:**
+
+```javascript
+const onSuccess = (params) => {
+  console.log("ABHA Success:", params.response);
+
+  const abhaNumber = params.response.data?.profile?.abha_number;
+  const userName = params.response.data?.profile?.name;
+
+  alert(`Welcome ${userName}! Your ABHA Number: ${abhaNumber}`);
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaSuccess(JSON.stringify(params));
+  }
+};
+```
+
+### onError Callback
+The onError callback is triggered whenever an ABHA flow fails or is interrupted.
+It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
+
+**Callback Signature:**
+
+```typescript
+onError: (params: TOnAbhaFailureParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaFailureParams = {
+  error?: string;
+  response?: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+
+```
+
+**Parameters**
+| Key        | Type                     | Description                                                      |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `error`    | `string?`                | Short description of the failure or error message.               |
+| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
+
+
+**Example:**
+
+```javascript
+const onError = (params) => {
+  console.error("ABHA Error:", params);
+
+  if (params.response?.error?.code === 1001) {
+    alert("Authentication failed. Please try again.");
+  } else if (params.error === "NETWORK_ERROR") {
+    alert("Please check your internet connection.");
+  } else {
+    alert("Something went wrong. Please retry.");
+  }
+
+  // Forward the error to native handler if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+  }
+};
+```
+
+### onAbhaClose Callback
+
+The onAbhaClose callback is triggered when the ABHA SDK flow gets closed. 
+
+**Callback Signature:**
+
+```typescript
+onAbhaClose: () => void;
+```
+
+**Example:**
+
+```javascript
+const onAbhaClose = () => {
+  console.log("ABHA SDK Closed");
+};
+```
+
+### onSkipAbha Callback
+
+The onSkipAbha callback is triggered when the ABHA SDK flow is skipped. The callback is functional when skipABHAEnable is set to true in the data parameter while initializing the SDK.
+
+**Callback Signature:**
+
+```typescript
+onSkipAbha: (params: TOnSkipABHA) => void;
+```
+
+**Example:**
+
+```javascript
+const onSkipAbha = (params) => {
+  console.log("ABHA SDK Skipped:", params);
+};
+```
+**Type Definitions**
+
+```typescript
+ type IdentifierType = "mobile" | "aadhaar_number" | "abha_number" | "phr_address";
+
+ type TOnSkipABHA = {
+  identifier?: string;
+  identifier_type?: IdentifierType[]; // No default value here
+};
+```
+
+**Parameters**
+| Key        | Type                     | Description                                                      |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `identifier`    | `string?`                | It will be login identifier value filled by user.               |
+| `identifier_type` | `IdentifierType[]?` | It will be type of login identifier. |
+
+
+
+**Suggest Handling**
+- Always log the full error response (params) for debugging.
+- Display friendly error messages for known error.code values.
+- If params.response is present, inspect response.error.message for more detail.
+- If integrating with native apps, forward the serialized error object:
+```javascript
+window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+```
+
+## Container Styling
+Ensure your container has sufficient space:
+```html
+<div
+  id="sdk_container"
+  style="width: 100%; height: 600px; border: 1px solid #ddd;"
+></div>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### 1. SDK Not Rendering
+
+**Problem**: Nothing appears in the container.
+
+**Solution**:
+- Ensure containerId matches an existing HTML element.
+- Verify the SDK JS and CSS are correctly loaded.
+- Check browser console for errors.
+
+#### 2. APIs Not Being Called
+
+**Problem**: API requests are not triggered after the SDK is mounted.
+
+**Solution**:
+- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
+- To prevent CORS-related issues, ensure that your domain is whitelisted.
+
+#### 3. Callback Not Triggered
+
+**Problem**: onSuccess, onError, onKYCSuccess, onConsentSuccess, onAbhaClose isn’t firing.
+
+**Solution**:
+- Make sure callbacks are passed as valid functions.
+- Avoid race conditions (e.g., calling before SDK fully loads).
+
+#### 4. Styling Issues
+
+**Problem**: SDK content appears misaligned or clipped.
+
+**Solution**:
+- Give your container a fixed height (e.g., 600px).
+- Ensure no parent element uses overflow: hidden.
\ No newline at end of file
diff --git a/SDKs/web-sdk/abha-sdk/abha-s&s.mdx b/SDKs/web-sdk/abha-sdk/abha-s&s.mdx
new file mode 100644
index 00000000..00161377
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/abha-s&s.mdx
@@ -0,0 +1,348 @@
+---
+title: Scan & Share
+description: "Complete implementation guide for the ABHA SDK to be used for ABHA Scan & Share Book Appointment Flow."
+---
+
+# ABHA SDK - Scan & Share Implementation
+
+This guide provides everything you need to integrate the ABHA SDK into your application for ABHA Scan & Share Book Appointment Flow.
+
+- **ABHA Scan & Share**: Get your Appointments Booked through ABHA.
+
+### Implementation Example
+
+Add the following HTML and script tags to your webpage:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>ABHA SDK Integration for ABHA Scan & Share</title>
+
+    <!-- Include ABHA SDK CSS -->
+    <link
+      rel="stylesheet"
+      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
+    />
+  </head>
+  <body>
+    <h1>ABHA SDK Demo</h1>
+
+    <!-- Mount Button -->
+    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
+
+    <!-- Container for ABHA SDK -->
+    <div id="sdk_container"></div>
+
+    <!-- Include ABHA SDK JS -->
+    <script
+      type="module"
+      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
+    ></script>
+
+    <script>
+      function mountABHASDK() {
+        window.initAbhaApp({
+          containerId: "sdk_container",
+          clientId: 'ext',
+
+         // Pass the data here:
+          data: {
+             oid: "<patient_oid>", // Pass OID of the patient
+             hipId: "<available_HFR_ID>", // Pass the HFR ID you have
+             counter_id: "<available_HIP_code>" // Pass the facility HIP code
+             identifier:'<phr_address_of_the_patient>', // Pass the phr address as identifier of the patient
+             identifier_type:"phr_address",  // Pass the identifier type i.e. "phr_address"
+             flow:'scan-share', // Pass the flow as scan-share
+             orgIconUrl: "<url_of_your_org_logo>", // Pass the url of the logo of your organisation for ex https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png
+             linkToOrgIcon: "<url_of_image_to_link_abha_to_your_org>", // Pass the url of an image which depicts linking abha to your organisation for ex https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp
+          },
+
+          // Scan & Share Success callback
+          onAppointmentBookedSuccess: (params) => {
+            console.log("Appointment Booked successfully:", params);
+
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAppointmentBookedSuccess(JSON.stringify(params));
+            }
+          },
+
+          // Error callback
+          onError: (params) => {
+            console.error("ABHA SDK failed:", params);
+
+            // Example: Store ABHA data in your app
+            if (window.EkaAbha) {
+              window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+            }
+          },
+
+          // Abha Close callback
+          onAbhaClose: () => {
+            console.log("ABHA SDK closed");
+          },
+
+        });
+      }
+    </script>
+  </body>
+</html>
+```
+
+## Core Functions
+
+### 1. initAbhaApp
+
+Initializes and renders the ABHA SDK in your specified container.
+
+**Parameters:**
+
+| Name                         | Type                                                                                                                                                           | Required | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `containerId`                | `string`                                                                                                                                                       | ✅       | The HTML element ID where the SDK will mount.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `clientId`                   | `string`                                                                                                                                                       | ✅       | Provide clientId as `ext`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `data`                       | `{`<br/>`oid?: string;`<br/>`hipId?: string;`<br/>`counter_id?: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string;`<br/>`identifier: string;`<br/>`identifier_type: string;`<br/>`flow: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string; `<br/>`}` | ✅       | Configuration data for initializing the ABHA flow. <br/><br/>- <strong>oid:</strong> Pass the OID of the patient if available.<br/>- <strong>hipId:</strong> Pass the HFR ID you have.<br/>- <strong>counter_id:</strong> Pass the HIP code of the facility you have.<br/>- <strong>identifier:</strong> Pass the identifier value i.e. phr address of the patient.<br/>- <strong>identifier_type:</strong> Pass the type of identifier which you passed in `identifier` key i.e. "phr_address". <br/>- <strong>flow:</strong> Pass the type of flow for which you want to use SDK for i.e. `scan-share` for Scan & Share Flow.<br/>- <strong>orgIconUrl:</strong> Public CDN URL of the logo of your organisation url should start with https://. [Example](https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png)<br/>- <strong>linkToOrgIcon:</strong> Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. [Example](https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp)<br/> <br/> `keys with ? are optional.` |
+| `onAppointmentBookedSuccess` | `(params: TOnAbhaSnSAppointmentSuccessParams) => void`                                                                                                         | ✅       | Triggered when the Appointment is booked and token gets generated successfully.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `onError`                    | `(params: TOnAbhaFailureParams) => void`                                                                                                                       | ✅       | Triggered when an error occurs during the ABHA flow.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `onAbhaClose`                | `() => void`                                                                                                                                                   | ✅       | Triggered when SDK closes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+
+**Example:**
+
+```javascript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  data: {
+    oid: "patient_oid_here",
+    hipId: "available_HFR_ID",
+    counter_id: "available_HIP_code"
+    identifier: "phr_address_of_the_patient"
+    identifier_type: "phr_address"
+    flow:'scan-share', // Pass the flow as scan-share
+  },
+  onAppointmentBookedSuccess: (params) => {
+    console.log("Appointment Booked successfully!", params);
+  },
+  onError: (error) => {
+    console.error("ABHA flow failed:", error);
+  },
+  onAbhaClose: (error) => {
+    console.error("ABHA SDK closed");
+  },
+});
+```
+
+## Callback Parameters
+
+### onAppointmentBookedSuccess Callback
+
+The onAppointmentBookedSuccess callback is triggered when the appointment is booked and token gets generated successfully.
+It returns a confirmation message indicating that the Appointment is booked.
+
+**Callback Signature:**
+
+```typescript
+onAppointmentBookedSuccess: (params: TOnAbhaSnSAppointmentSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaSnSAppointmentSuccess = string;
+```
+
+**Parameters**
+| | Type | Description |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `onAppointmentBookedSuccess` | `string` | A confirmation message from SDK post Appointment Token generation |
+
+**Example:**
+
+```javascript
+const onAppointmentBookedSuccess = (params) => {
+  console.log("Appointment Booked successfully!:", params);
+
+  alert("Appointment Booked successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAppointmentBookedSuccess(params);
+  }
+};
+```
+
+### onError Callback
+
+The onError callback is triggered whenever an ABHA flow fails or is interrupted.
+It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
+
+**Callback Signature:**
+
+```typescript
+onError: (params: TOnAbhaFailureParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaFailureParams = {
+  error?: string;
+  response?: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+```
+
+**Parameters**
+| Key | Type | Description |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `error` | `string?` | Short description of the failure or error message. |
+| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
+
+**Example:**
+
+```javascript
+const onError = (params) => {
+  console.error("ABHA Error:", params);
+
+  if (params.response?.error?.code === 1001) {
+    alert("Authentication failed. Please try again.");
+  } else if (params.error === "NETWORK_ERROR") {
+    alert("Please check your internet connection.");
+  } else {
+    alert("Something went wrong. Please retry.");
+  }
+
+  // Forward the error to native handler if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+  }
+};
+```
+
+### onAbhaClose Callback
+
+The onAbhaClose callback is triggered when the ABHA SDK flow gets closed.
+
+**Callback Signature:**
+
+```typescript
+onAbhaClose: () => void;
+```
+
+**Example:**
+
+```javascript
+const onAbhaClose = () => {
+  console.log("ABHA SDK Closed");
+};
+```
+
+**Suggest Handling**
+
+- Always log the full error response (params) for debugging.
+- Display friendly error messages for known error.code values.
+- If params.response is present, inspect response.error.message for more detail.
+- If integrating with native apps, forward the serialized error object:
+
+```javascript
+window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+```
+
+## Container Styling
+
+Ensure your container has sufficient space:
+
+```html
+<div
+  id="sdk_container"
+  style="width: 100%; height: 600px; border: 1px solid #ddd;"
+></div>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### 1. SDK Not Rendering
+
+**Problem**: Nothing appears in the container.
+
+**Solution**:
+
+- Ensure containerId matches an existing HTML element.
+- Verify the SDK JS and CSS are correctly loaded.
+- Check browser console for errors.
+
+#### 2. APIs Not Being Called
+
+**Problem**: API requests are not triggered after the SDK is mounted.
+
+**Solution**:
+
+- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
+- To prevent CORS-related issues, ensure that your domain is whitelisted.
+
+#### 3. Callback Not Triggered
+
+**Problem**: onSuccess, onError, onAppointmentBookedSuccess, onAbhaClose isn’t firing.
+
+**Solution**:
+
+- Make sure callbacks are passed as valid functions.
+- Avoid race conditions (e.g., calling before SDK fully loads).
+
+#### 4. Styling Issues
+
+**Problem**: SDK content appears misaligned or clipped.
+
+**Solution**:
+
+- Give your container a fixed height (e.g., 600px).
+- Ensure no parent element uses overflow: hidden.
diff --git a/SDKs/web-sdk/abha-sdk/abha-sdk-theme.mdx b/SDKs/web-sdk/abha-sdk/abha-sdk-theme.mdx
new file mode 100644
index 00000000..c698bd36
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/abha-sdk-theme.mdx
@@ -0,0 +1,211 @@
+---
+title: Custom Theming
+description: "Customize the ABHA SDK colors to match your application's branding"
+---
+
+# ABHA SDK - Customizing the Theme
+
+The ABHA SDK supports full color-token overriding. You can pass a `theme` object during initialization to match your application's branding.
+
+## Passing theme to initAbhaApp
+
+The `theme` parameter is an optional key in `initAbhaApp`. Pass it alongside your other configuration:
+
+| Name    | Type     | Required     | Description                                               |
+| ------- | -------- | ------------ | --------------------------------------------------------- |
+| `theme` | `object` | ⚙️ Optional  | Color token overrides to match your organisation's design system. All keys are optional — only supply the tokens you want to change. |
+
+```javascript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  clientId: "ext",
+  theme: {
+    // pass only the tokens you want to override
+  },
+  data: { /* ... */ },
+  onSuccess: (params) => { /* ... */ },
+  onError: (params) => { /* ... */ },
+});
+```
+
+## Default Theme Colors
+
+If no theme is provided, the SDK uses the following default values:
+
+```typescript
+const defaultAbhaColors = {
+  semantic: {
+    error: '#BD0F0F',
+    warning: '#FCB069',
+    success: '#27B961',
+  },
+  primary: {
+    brand: '#6B5CE0', // Main buttons, radios, and active states
+  },
+  surface: {
+    base: '#FFFFFF',      // Background of pages
+    subtle: '#F2F4F7',    // Card backgrounds
+    muted: '#E4E7EC',     // Dividers and borders
+    strong: '#BEC5D0',
+    success: '#D5F6E2',   // Success background alerts
+    neutral: '#0000000D',
+    danger: '#DD3F3F',
+    abhaCard: '#232477',  // Specific background for the ABHA ID card
+  },
+  content: {
+    primary: '#111B31',   // Heading and main text
+    secondary: '#4B596D', // Subtext
+    muted: '#9EA8B8',     // Disabled or placeholder text
+    success: '#1B7E43',   // Success text
+    enabled: '#ffffff',   // Enabled button text color
+  },
+  qrCodeColors: {
+    fgColor: '#000000',   // Color of the QR code dots
+    bgColor: '#FFFFFF'    // Background of the QR code
+  }
+};
+```
+
+## Overriding the Theme
+
+To customize the look, add the `theme` key to your `initAbhaApp` configuration:
+
+```typescript
+window.initAbhaApp({
+  containerId: "sdk_container",
+  clientId: "ext",
+  theme: {
+    primary: {
+      brand: '<your_org_primary_color>',    // Brand color
+    },
+    semantic: {
+      error: '<your_semantic_error_color>',
+      warning: '<your_semantic_warning_color>',
+      success: '<your_semantic_success_color>',
+    },
+    surface: {
+      base: '<your_base_color>',            // Background of pages
+      subtle: '<your_subtle_color>',        // Card backgrounds
+      muted: '<your_muted_color>',          // Dividers and borders
+      strong: '<your_strong_color>',
+      success: '<your_success_color>',      // Success background alerts
+      neutral: '<your_neutral_color>',
+      danger: '<your_danger_color>',
+      abhaCard: '<your_abhaCard_color>',    // Specific background for the ABHA ID card
+    },
+    content: {
+      primary: '<your_content_primary_color>',     // Heading and main text
+      secondary: '<your_content_secondary_color>', // Subtext
+      muted: '<your_content_muted_color>',         // Disabled or placeholder text
+      success: '<your_content_success_color>',     // Success text
+      enabled: '<enabled_button_text_color>',      // Enabled button text color
+    },
+    qrCodeColors: {
+      fgColor: '<your_qrcode_dot_color>',  // Color of the QR code dots
+      bgColor: '<your_qrcode_bg_color>'    // Background of the QR code
+    }
+  },
+  data: {
+    orgIconUrl: "https://your-domain.com/logo.png",
+    // ... rest of your data
+  },
+  onSuccess: (params) => { /* ... */ },
+  onError: (params) => { /* ... */ },
+  // ... other methods
+});
+```
+
+## Troubleshooting
+
+### Common Theming Issues
+
+#### 1. Button Not Visible or Hard to See
+
+**Problem**: A button appears invisible, blends into the background, or is difficult to read.
+
+**Cause**: This typically happens when `primary.brand` and `content.enabled` are too similar (e.g., both set to white or both dark), making the button label invisible against its background.
+
+**Solution**:
+- Ensure `primary.brand` (button background) and `content.enabled` (button text) have sufficient contrast.
+- A dark `primary.brand` should pair with a light `content.enabled` (e.g., `#ffffff`), and vice versa.
+
+```typescript
+theme: {
+  primary: {
+    brand: ‘#1A237E’,   // Dark button background
+  },
+  content: {
+    enabled: ‘#FFFFFF’, // Light text on button — must contrast with brand
+  },
+}
+```
+
+#### 2. Color Discrepancy — Overrides Not Taking Effect
+
+**Problem**: You passed a theme but some colors still appear as defaults.
+
+**Cause**: Token keys may be misspelled, nested incorrectly, or using the wrong casing.
+
+**Solution**:
+- Double-check that your token keys exactly match the structure in [Default Theme Colors](#default-theme-colors). The SDK performs a shallow merge — missing or misnamed keys fall back to defaults silently.
+- Verify nesting: tokens like `surface.base` must be passed as `surface: { base: ‘...’ }`, not as a flat key.
+
+```typescript
+// ❌ Wrong — flat key, will be ignored
+theme: {
+  ‘surface.base’: ‘#F9FAFB’,
+}
+
+// ✅ Correct — nested object
+theme: {
+  surface: {
+    base: ‘#F9FAFB’,
+  },
+}
+```
+
+#### 3. Success / Error States Look Off
+
+**Problem**: Success alerts, error messages, or validation states are visually inconsistent or unreadable.
+
+**Cause**: Overriding only `semantic.success` without also updating `surface.success` and `content.success` (or vice versa) breaks the foreground/background pairing for state banners.
+
+**Solution**: Always override semantic state colors as a group — the background surface token, the text content token, and the semantic indicator token together.
+
+| State   | Tokens to keep in sync                                          |
+| ------- | --------------------------------------------------------------- |
+| Success | `semantic.success`, `surface.success`, `content.success`        |
+| Error   | `semantic.error`, `surface.danger`                              |
+| Warning | `semantic.warning`                                              |
+
+#### 4. ABHA Card Color Not Changing
+
+**Problem**: The ABHA ID card background color is not updating despite passing a theme.
+
+**Solution**: The card background is controlled by `surface.abhaCard`, not `surface.base` or `primary.brand`. Pass it explicitly:
+
+```typescript
+theme: {
+  surface: {
+    abhaCard: ‘#1A237E’, // Override the ABHA card background
+  },
+}
+```
+
+#### 5. QR Code Invisible or Unreadable
+
+**Problem**: The QR code is not scannable or appears blank.
+
+**Cause**: `qrCodeColors.fgColor` and `qrCodeColors.bgColor` may have been set to the same or similar colors.
+
+**Solution**: Maintain high contrast between the QR dot color and background — black on white is the most reliable combination for scanner compatibility.
+
+```typescript
+theme: {
+  qrCodeColors: {
+    fgColor: ‘#000000’, // QR dots — keep dark
+    bgColor: ‘#FFFFFF’, // QR background — keep light
+  },
+}
+```
+
diff --git a/SDKs/web-sdk/abha-sdk/get-started.mdx b/SDKs/web-sdk/abha-sdk/get-started.mdx
new file mode 100644
index 00000000..635fdfbd
--- /dev/null
+++ b/SDKs/web-sdk/abha-sdk/get-started.mdx
@@ -0,0 +1,559 @@
+---
+title: Get Started
+description: "Complete implementation guide for the ABHA[Ayushman Bharat Digital Mission] SDK"
+---
+
+# ABHA SDK - Implementation
+
+This guide provides everything you need to integrate the ABHA SDK into your application.
+
+## Overview
+
+The ABHA SDK allows you to integrate flows—such as Create ABHA, Login, Profile KYC, Consent Management, and Scan & Share—into your healthcare application, while offering customizable theme options. It provides:
+
+- **Create ABHA**: Create a new ABHA using Mobile or Aadhaar.
+- **Login with ABHA**: Login to your exisiting ABHA using PHR Address, ABHA number, Aadhaar number or Mobile number.
+- **ABHA Consent Management**: Manage Consent requests raised by healthcare providers to share medical records securely.
+- **ABHA Profile KYC**: Get your ABHA address KYC verified.
+- **ABHA Scan & Share**: Get your Appointments Booked through ABHA.
+- **Customizing the Theme**: Customize the ABHA SDK colors to match your application's branding.
+
+## Installation
+
+### Prerequisites
+
+- A modern web browser.
+- Your domain must be whitelisted with Eka Care to avoid CORS(Cross-Origin Resource Sharing) error.
+  (Contact Eka Care to request API access and domain whitelisting.)
+- A valid HTML container element where the SDK will mount.
+
+### Setup
+
+Add the following HTML and script tags to your webpage:
+
+```html
+<!DOCTYPE html>
+<html>
+  <head>
+    <title>ABHA SDK Integration</title>
+
+    <!-- Include ABHA SDK CSS -->
+    <link
+      rel="stylesheet"
+      href="https://unpkg.com/@eka-care/abha/dist/sdk/abha/css/abha.css"
+    />
+  </head>
+  <body>
+    <h1>ABHA SDK Demo</h1>
+
+    <!-- Mount Button -->
+    <button class="button" onclick="mountABHASDK()">Mount SDK</button>
+
+    <!-- Container for ABHA SDK -->
+    <div id="sdk_container"></div>
+
+    <!-- Include ABHA SDK JS -->
+    <script
+      type="module"
+      src="https://unpkg.com/@eka-care/abha/dist/sdk/abha/js/abha.js"
+    ></script>
+
+    <script>
+      function mountABHASDK() {
+        window.initAbhaApp({
+          containerId: "sdk_container",
+          clientId: "ext",
+
+          // theme object
+          theme: {
+            // pass only the tokens you want to override
+          },
+
+          // data object
+          data: {
+            // pass the required data as per the flow
+          },
+
+          // Success callback
+          onSuccess: (params) => {
+            console.log(
+              "ABHA Registration flow completed successfully:",
+              params,
+            );
+          },
+
+          //KYC Successs callback
+          onKYCSuccess: (params) => {
+            console.log("ABHA KYC Verified successfully:", params);
+          },
+
+          //Consent Successs callback
+          onConsentSuccess: (params) => {
+            console.log("ABHA Consent flow completed successfully:", params);
+          },
+
+          // Scan & Share Success callback
+          onAppointmentBookedSuccess: (params) => {
+            console.log("Appointment Booked successfully:", params);
+          },
+
+          // Skip ABHA callback
+          onSkipAbha: (params) => {
+            console.log("ABHA flow SKIPPED:", params);
+          },
+
+          // Abha Close callback
+          onAbhaClose: () => {
+            console.log("ABHA SDK closed");
+          },
+
+          // Error callback
+          onError: (params) => {
+            console.error("ABHA SDK failed:", params);
+          },
+        });
+      }
+    </script>
+  </body>
+</html>
+```
+
+## Core Functions
+
+### 1. initAbhaApp
+
+Initializes and renders the ABHA SDK in your specified container.
+
+**Parameters:**
+
+| Name               | Type                                                                                                                                                                                                                                                     | Required    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `containerId`      | `string`                                                                                                                                                                                                                                                 | ✅          | The HTML element ID where the SDK will mount.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `clientId`         | `string`                                                                                                                                                                                                                                                 | ✅          | Provide clientId as `ext`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `data`             | `{`<br/>`accessToken: string;`<br/>`hipId: string;`<br/>`oid?: string;`<br/>`identifier?: string;`<br/>`identifier_type?: string;`<br/>`counter_id?: string;`<br/>`consent_id?: string;`<br/>`flow?: string;`<br/>`orgIconUrl?: string;`<br/>`linkToOrgIcon?: string;`<br/>`skipABHAEnable?: boolean;`<br/>`}` | ⚙️ Optional | Configuration data for initializing the ABHA flow. <br/><br/>- <strong>accessToken:</strong> Pass the access token you have generated from [Connect Login ](https://developer.eka.care/api-reference/authorization/client-login) API without the word `Bearer`. <br/>- <strong>hipId:</strong> Pass the HFR ID you have. <br/>- <strong>oid:</strong> Pass oid of patient if available / needed in the flow. <br/>- <strong>identifier:</strong> Pass the login identifier value i.e. mobile number / aadhaar number / phr address / abha number.<br/>- <strong>identifier_type:</strong> Pass the type of identifier which you passed in `identifier` key i.e. "mobile" / "aadhaar_number" / "phr_address" / "abha_number" /. If not known pass undefined.<br/>- <strong>counter_id:</strong> Pass the HIP code of the facility you have.<br/>- <strong>consent_id:</strong> Pass the consent_id of the consent request raised. <br/>- <strong>flow:</strong> Pass the type of flow for which you want to use SDK for i.e. `abha-kyc` for KYC flow / `consent` for Consent flow. <br/>- <strong>orgIconUrl:</strong> Public CDN URL of the logo of your organisation url should start with https://. [Example](https://cdn.eka.care/vagus/cl5jgf0u500070shaetqw0r5l.png)<br/>- <strong>linkToOrgIcon:</strong> Public CDN URL of the icon representing “Link ABHA to your organisation” url should start with https://. [Example](https://cdn.eka.care/vagus/cm6agrs5000090tfwfz984x5b.webp)<br/>- <strong>skipABHAEnable:</strong> Pass the boolean as true if you want Skip ABHA button to be enabled on login screen. <br/><br/> `keys with ? are optional and needs to be passed as per flow requirement.` |
+| `theme`            | `object`                                                                                                                                                                                                                                                 | ⚙️ Optional | Color token overrides to match your organisation's design system. All keys are optional — only supply the tokens you want to change. [Refer here](https://developer.eka.care/SDKs/web-sdk/abha-sdk/abha-sdk-theme)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `onSuccess`        | `(params: TOnAbhaSuccessParams) => void`                                                                                                                                                                                                                 | ✅          | Triggered when the user successfully creates or logs in to ABHA.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `onKYCSuccess`     | `(params: TOnAbhaKycSuccessParams) => void`                                                                                                                                                                                                              | ⚙️ Optional | Triggered when the user KYC verified successfully.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `onConsentSuccess` | `(params: TOnAbhaConsentSuccessParams) => void`                                                                                                                                                                                                          | ⚙️ Optional | Triggered when the consent flow completes successfully.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `onAppointmentBookedSuccess`   | `(params: TOnAbhaSnSAppointmentSuccessParams) => void`   | ✅  | Triggered when the Appointment is booked and token gets generated successfully.
+| `onSkipAbha`       | `(params: TOnSkipABHA) => void`                                                                                                                                                                                                                          | ⚙️ Optional | Triggered if the ABHA flow is skipped.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `onAbhaClose`      | `() => void`                                                                                                                                                                                                                                             | ✅          | Triggered when SDK closes.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `onError`          | `(params: TOnAbhaFailureParams) => void`                                                                                                                                                                                                                 | ✅          | Triggered when an error occurs during the ABHA flow.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+
+## Callback Parameters
+
+### onSuccess Callback
+
+The onSuccess callback is triggered when the ABHA flow completes successfully.
+It returns verified user details and tokens, which can be used to log in or continue the user’s session.
+
+**Callback Signature:**
+
+```typescript
+onSuccess: (params: TOnAbhaSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaSuccessParams = {
+  response: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+```
+
+**Parameters**
+| Key | Type | Description |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `response` | `TAuthVerifyV2Response` | The complete ABHA verification response, containing session tokens, user profile, and transaction details. |
+
+**Example:**
+
+```javascript
+const onSuccess = (params) => {
+  console.log("ABHA Success:", params.response);
+
+  const abhaNumber = params.response.data?.profile?.abha_number;
+  const userName = params.response.data?.profile?.name;
+
+  alert(`Welcome ${userName}! Your ABHA Number: ${abhaNumber}`);
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaSuccess(JSON.stringify(params));
+  }
+};
+```
+
+### onKYCSuccess Callback
+
+The onKYCSuccess callback is triggered when the ABHA KYC flow completes successfully.
+It returns a confirmation message indicating that the KYC has been verified.
+
+**Callback Signature:**
+
+```typescript
+onKYCSuccess: (params: TOnAbhaKycSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaKycSuccess = string;
+```
+
+**Parameters**
+| | Type | Description |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `TOnAbhaKycSuccess` | `string` | A confirmation message from SDK post KYC verification |
+
+**Example:**
+
+```javascript
+const onKYCSuccess = (params) => {
+  console.log("KYC verification Success:", params);
+
+  alert("KYC was verified successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaKYCSuccess(params);
+  }
+};
+```
+
+### onConsentSuccess Callback
+
+The onConsentSuccess callback is triggered when the ABHA Consent flow completes successfully.
+It returns a confirmation message indicating that the Consent flow ended successfully.
+
+**Callback Signature:**
+
+```typescript
+onConsentSuccess: (params: TOnAbhaConsentSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaConsentSuccessParams = string;
+```
+
+**Parameters**
+| | Type | Description |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `TOnAbhaConsentSuccessParams` | `string` | A confirmation message from SDK post Consent flow completion |
+
+**Example:**
+
+```javascript
+const onConsentSuccess = (params) => {
+  console.log("Consent Flow completed:", params);
+
+  alert("Consent flow completed successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaConsentSuccess(params);
+  }
+};
+```
+
+### onAppointmentBookedSuccess Callback
+
+The onAppointmentBookedSuccess callback is triggered when the appointment is booked and token gets generated successfully.
+It returns a confirmation message indicating that the Appointment is booked.
+
+**Callback Signature:**
+
+```typescript
+onAppointmentBookedSuccess: (params: TOnAbhaSnSAppointmentSuccessParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaSnSAppointmentSuccess = string;
+```
+
+**Parameters**
+| | Type | Description |
+| ---------- | ----------------------- | ---------------------------------------------------------------------------------------------------------- |
+| `onAppointmentBookedSuccess` | `string` | A confirmation message from SDK post Appointment Token generation |
+
+**Example:**
+
+```javascript
+const onAppointmentBookedSuccess = (params) => {
+  console.log("Appointment Booked successfully!:", params);
+
+  alert("Appointment Booked successfully!");
+
+  // Optionally pass data to native bridge if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAppointmentBookedSuccess(params);
+  }
+};
+```
+
+### onSkipAbha Callback
+
+The onSkipAbha callback is triggered when the ABHA SDK flow is skipped. The callback is functional when skipABHAEnable is set to true in the data parameter while initializing the SDK.
+
+**Callback Signature:**
+
+```typescript
+onSkipAbha: (params: TOnSkipABHA) => void;
+```
+
+**Example:**
+
+```javascript
+const onSkipAbha = (params) => {
+  console.log("ABHA SDK Skipped:", params);
+};
+```
+
+**Type Definitions**
+
+```typescript
+type IdentifierType =
+  | "mobile"
+  | "aadhaar_number"
+  | "abha_number"
+  | "phr_address";
+
+type TOnSkipABHA = {
+  identifier?: string;
+  identifier_type?: IdentifierType[]; // No default value here
+};
+```
+
+**Parameters**
+| Key | Type | Description |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `identifier` | `string?` | It will be login identifier value filled by user. |
+| `identifier_type` | `IdentifierType[]?` | It will be type of login identifier. |
+
+### onAbhaClose Callback
+
+The onAbhaClose callback is triggered when the ABHA SDK flow gets closed.
+
+**Callback Signature:**
+
+```typescript
+onAbhaClose: () => void;
+```
+
+**Example:**
+
+```javascript
+const onAbhaClose = () => {
+  console.log("ABHA SDK Closed");
+};
+```
+
+### onError Callback
+
+The onError callback is triggered whenever an ABHA flow fails or is interrupted.
+It provides details about the failure through structured parameters, allowing you to handle or forward the error appropriately (for example, to native apps or monitoring tools).
+
+**Callback Signature:**
+
+```typescript
+onError: (params: TOnAbhaFailureParams) => void;
+```
+
+**Type Definitions**
+
+```typescript
+type TOnAbhaFailureParams = {
+  error?: string;
+  response?: TAuthVerifyV2Response;
+};
+
+type TAuthVerifyV2Response = {
+  skip_state: number;
+  method: AUTH_METHOD;
+  data?: {
+    tokens: {
+      sess: string;
+      refresh: string;
+    };
+    profile: TProfileRecord;
+  };
+  txn_id: string;
+  error?: {
+    code: number;
+    message: string;
+  };
+};
+
+enum AUTH_METHOD {
+  EMAIL = 1,
+  MOBILE = 2,
+  ABHA = 7,
+}
+
+type TProfileRecord = {
+  fln: string;
+  fn: string;
+  mn?: string;
+  ln?: string;
+  gen?: "M" | "F" | "O" | "U" | undefined; // 'male' | 'female' | 'other' | 'unknown'
+  dob?: string;
+  mobile?: string;
+  email?: string;
+  uuid?: string;
+  bloodgroup?: "" | "A+" | "A-" | "B+" | "B-" | "O+" | "O-" | "AB+" | "AB-";
+  pic?: string;
+  as?: string;
+  "dob-valid"?: boolean;
+  "is-d"?: boolean;
+  "is-d-s"?: boolean;
+  "is-p"?: boolean;
+  oid: string;
+  at: string;
+  type?: 1 | 2 | 3 | 4 | 5 | 6;
+  "health-ids"?: Array<string>;
+  abha_number?: string;
+  kyc_verified?: boolean;
+};
+```
+
+**Parameters**
+| Key | Type | Description |
+| ---------- | ------------------------ | ---------------------------------------------------------------- |
+| `error` | `string?` | Short description of the failure or error message. |
+| `response` | `TAuthVerifyV2Response?` | Partial or full API response object returned from ABHA services. |
+
+**Example:**
+
+```javascript
+const onError = (params) => {
+  console.error("ABHA Error:", params);
+
+  if (params.response?.error?.code === 1001) {
+    alert("Authentication failed. Please try again.");
+  } else if (params.error === "NETWORK_ERROR") {
+    alert("Please check your internet connection.");
+  } else {
+    alert("Something went wrong. Please retry.");
+  }
+
+  // Forward the error to native handler if available
+  if (window.EkaAbha) {
+    window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+  }
+};
+```
+
+**Suggest Handling**
+
+- Always log the full error response (params) for debugging.
+- Display friendly error messages for known error.code values.
+- If params.response is present, inspect response.error.message for more detail.
+- If integrating with native apps, forward the serialized error object:
+
+```javascript
+window.EkaAbha.onAbhaFailure(JSON.stringify(params));
+```
+
+## Container Styling
+
+Ensure your container has sufficient space:
+
+```html
+<div
+  id="sdk_container"
+  style="width: 100%; height: 600px; border: 1px solid #ddd;"
+></div>
+```
+
+## Troubleshooting
+
+### Common Issues
+
+#### 1. SDK Not Rendering
+
+**Problem**: Nothing appears in the container.
+
+**Solution**:
+
+- Ensure containerId matches an existing HTML element.
+- Verify the SDK JS and CSS are correctly loaded.
+- Check browser console for errors.
+
+#### 2. APIs Not Being Called
+
+**Problem**: API requests are not triggered after the SDK is mounted.
+
+**Solution**:
+
+- Ensure that the accessToken is passed correctly (do not include the Bearer prefix) and that the token has not expired.
+- To prevent CORS-related issues, ensure that your domain is whitelisted.
+
+#### 3. Callback Not Triggered
+
+**Problem**: onSuccess, onError, onKYCSuccess, onConsentSuccess, onAbhaClose isn’t firing.
+
+**Solution**:
+
+- Make sure callbacks are passed as valid functions.
+- Avoid race conditions (e.g., calling before SDK fully loads).
+
+#### 4. Styling Issues
+
+**Problem**: SDK content appears misaligned or clipped.
+
+**Solution**:
+
+- Give your container a fixed height (e.g., 600px).
+- Ensure no parent element uses overflow: hidden.
diff --git a/abdm-connect.mdx b/abdm-connect.mdx
deleted file mode 100644
index e95a0261..00000000
--- a/abdm-connect.mdx
+++ /dev/null
@@ -1,178 +0,0 @@
----
-title: "ABDM Connect"
----
-
-**ABDM (Ayushman Bharat Digital Mission) Connect** is a crucial component of EKA Connect that integrates your healthcare systems with India’s national digital health infrastructure.
-
-The ABDM Connector is designed as a powerful, plug-and-play API suite that simplifies the integration of various healthcare solutions into the Ayushman Bharat Digital Mission (ABDM) ecosystem. Whether you're looking to connect Electronic Health Records (EHR), hospital management systems, or other healthcare platforms, this connector facilitates seamless interoperability.
-
-## Key Features
-
-* **Full Support for All ABDM Functionalities**:
-  The connector offers a complete range of services required to connect to ABDM, including creating and linking Health IDs (ABHA), handling consent management, sharing health records, and much more.
-
-* **Flexible Infrastructure Options**:
-  You can choose between using our shared cloud infrastructure—perfect for rapid deployment with minimal overhead—or setting up your own private cloud for greater control and security.
-
-Whether you are a healthcare provider, technology partner, or hospital network, the ABDM Connector ensures a smooth, compliant, and efficient integration experience with the ABDM framework, empowering you to deliver better healthcare services at scale.
-
-## How to Onboard in ABDM Connect
-
-There are two ways to onboard into ABDM Connect through EKA Connect:
-
-### **Option 1: Use Your Own Client ID and Client Secret (ABDM Credentials)**
-
-* If your healthcare institution or provider is already registered with the ABDM, you can use the Client ID and Client Secret provided by ABDM.
-
-* This allows you to authenticate and start using the ABDM services directly.
-
-### **Option 2: Onboard as a Hospital or Healthcare Information Provider (HIP)**
-
-* If you are a hospital or healthcare provider looking to integrate with ABDM through EKA, you can onboard directly via the EKA Connect platform.
-
-* EKA will help you obtain the necessary credentials and guide you through the steps of becoming a **Healthcare Information Provider (HIP)** under the ABDM.
-
-## Registration Process
-
-Once you are onboarded to ABDM Connect, the next crucial step is registration, which involves creating an **ABHA Address** and an **ABHA Number**. This process helps link your healthcare information into one system, making it easier for you to manage and access your health data.
-
-* API Reference: [Registration](https://developer.eka.care/api-reference/user-app/abdm-connect/registration/intro)
-
-### What is an ABHA Address and ABHA Number?
-
-#### 1. **ABHA Number**:
-
-1. **What is it?**
-
-* A 14-digit number (e.g., 1241-2312-3123) you get after completing **KYC** (Know Your Customer) verification.
-
-1. **KYC Methods**:
-
-* **Online**: Aadhaar
-
-* **Offline**: PAN Card, Driving License
-
-1. **Why do you need it?**
-
-* Required for PMJAY insurance (for low-income families).
-
-* Some hospitals need this for outpatient services (OPD).
-
-1. **How does it work?**
-
-* When you create an ABHA Number, they also generate an ABHA Address in the background (e.g., `124151351351@abdm`), which is helpful for assisted users.
-
-* Unlike ABHA Addresses, you can only have **one unique ABHA Number**.
-
-#### 2. **ABHA Address**:
-
-1. **What is it?**
-
-* A unique identifier for your digital health records.
-
-* Used for most health-related transactions like consents, document transfers, etc.
-
-1. **Examples**:
-
-* `nisha@abdm`
-
-* `rani@abdm`
-
-1. **How many can you have?**
-
-* You can create up to **X** ABHA Addresses for a single mobile number.
-
-1. **Why would you want more than one?**
-
-* **Privacy**: Keep certain health information, like mental health records, separate with a private ABHA Address.
-
-#### 3. How to Get an ABHA Number
-
-You can create your ABHA Number through two simple methods:
-
-1. Using Aadhaar
-
-2. Using Mobile Authentication
-
-## Post-Registration Process
-
-After registering on ABDM Connect, several key APIs come into play to manage your healthcare data. Here are the main areas you’ll interact with:
-
-***
-
-### **1. Profile APIs** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/profile/getting-started))
-
-The Profile API offers a comprehensive set of endpoints designed to help users manage and access their profile information in a user-friendly way. This is essential for Personal Health Record (PHR) applications, as users need a dedicated section to view their demographic details and make updates when necessary.
-
-Key Features:
-Once registered, you can manage your profile through these APIs, which include:
-
-* **Assets API**: Handles your digital health assets.
-
-* **Details API**: Manages profile details and related operations.
-
-***
-
-### **2. Care Contexts** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/care-contexts/getting-started))
-
-A Care Context represents a logical grouping of health records. Each HMIS, LMIS, or PHR system should determine how to organize data into one or more care contexts for a user.
-
-Key Features:
-
-* **View Linked Records**: Lets you view all health records linked to your ABHA Number.
-
-* **Link Records**: Provides the ability to add new health records to your profile.
-
-***
-
-### **3. Providers/Health Information Providers (HIP)** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/providers/getting-started))
-
-Healthcare Information Providers (HIPs) hold or manage the patient's health records. Through this API, users can retrieve detailed information about healthcare providers, including their care contexts, and search for providers by name to find and link their care contexts/documents.
-
-***
-
-### **4. Consent Management** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/consents/getting-started))
-
-When a healthcare provider or organization (known as a Health Information User or HIU) wants to access your health records linked to your ABHA address, they first need to ask for your **consent**.
-
-Key Features:
-
-* **Review and Customize**: When you receive a consent request, you can review the details and even customize the request.
-
-* **Granting Consent**: Once satisfied with the request, you can approve it, allowing the HIU to access your health data.
-
-* **Revoking Consent**: If you change your mind, you can revoke the consent, ensuring the HIU deletes any copies of your health data.
-
-Consent management gives you full control over who can see your health information, ensuring secure and private data sharing.
-
-***
-
-### **5. Share Profile** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/scan-and-share/getting-started))
-
-Every Personal Health Record (PHR) app needs to allow users to easily share their ABHA address and profile information with healthcare facilities by scanning a QR code.
-
-Key Features:
-
-* **Scan the QR Code**: The app integrates with the phone camera to scan a QR code at a health facility.
-
-* **QR Code Details**: The code contains a link with important details like the facility's ID and specific context to help process user information securely.
-
-***
-
-### **6. User Session** ([API Reference](https://developer.eka.care/api-reference/user-app/abdm-connect/session/getting-started))
-
-When you create or register an ABHA, a user session is created with the ABHA Gateway. This session is temporary and expires after a certain period.
-
-Key Features:
-
-* **Session Expiry**: After expiry, any action requiring ABHA Gateway authentication will return an error.
-
-* **Session Renewal**: Authenticate using a mobile OTP to create a new session.
-
-Steps:
-
-1. **Generate Mobile OTP**
-
-2. **Verify Mobile OTP**
-
-This ensures session security while protecting your data.
\ No newline at end of file
diff --git a/ai-tools/agent-kit/agents.mdx b/ai-tools/agent-kit/agents.mdx
new file mode 100644
index 00000000..97e54eb7
--- /dev/null
+++ b/ai-tools/agent-kit/agents.mdx
@@ -0,0 +1,106 @@
+---
+title: Agents
+description: Build agents with GenericAgent
+---
+
+## GenericAgent
+
+The main agent class that orchestrates LLM, tools, and conversation:
+
+```python
+from echo import GenericAgent, AgentConfig, LLMConfig, ConversationContext
+
+agent = GenericAgent(
+    agent_config=agent_config,
+    llm_config=llm_config,
+    tools=[tool1, tool2],  # Optional tools
+)
+
+# Run with conversation context
+context = ConversationContext()
+context.add_message(Message(
+    role=MessageRole.USER,
+    content=[TextMessage(text="Your query here")],
+))
+
+result = await agent.run(context)
+print(result.llm_response.text)
+```
+
+## Agent Result
+
+The `run()` method returns an `AgentResult`:
+
+```python
+result = await agent.run(context)
+
+# Response text
+print(result.llm_response.text)
+
+# Updated context (for multi-turn)
+context = result.context
+
+# Tool calls made
+for item in result.llm_response.verbose:
+    if item.type == "tool":
+        print(f"Called: {item.tool_name}")
+
+# Elicitations (UI components)
+for elicit in result.llm_response.elicitations:
+    print(f"Component: {elicit.details.component}")
+
+# Errors
+if result.error:
+    print(f"Error: {result.error}")
+```
+
+## Multi-Turn Conversations
+
+Maintain context across turns:
+
+```python
+context = ConversationContext()
+
+# Turn 1
+context.add_message(Message(role=MessageRole.USER, content=[TextMessage(text="What is diabetes?")]))
+result = await agent.run(context)
+context = result.context
+
+# Turn 2 (agent remembers context)
+context.add_message(Message(role=MessageRole.USER, content=[TextMessage(text="What are the types?")]))
+result = await agent.run(context)
+```
+
+## Handling Elicitations
+
+When agent returns UI components for user input:
+
+```python
+result = await agent.run(context)
+
+if result.llm_response.elicitations:
+    elicit = result.llm_response.elicitations[0]
+
+    # Show options to user
+    options = elicit.details.input.get('options', [])
+    for i, opt in enumerate(options, 1):
+        print(f"{i}. {opt}")
+
+    # Get user selection and add as tool result
+    user_choice = get_user_input()
+    context.add_message(Message(
+        role=MessageRole.TOOL,
+        content=[ToolResult(tool_id=elicit.tool_id, result=user_choice)],
+    ))
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Tools" icon="wrench" href="/ai-tools/agent-kit/tools">
+    Add tools to agents
+  </Card>
+  <Card title="Streaming" icon="stream" href="/ai-tools/agent-kit/streaming">
+    Real-time responses
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/configuration.mdx b/ai-tools/agent-kit/configuration.mdx
new file mode 100644
index 00000000..d6a7162d
--- /dev/null
+++ b/ai-tools/agent-kit/configuration.mdx
@@ -0,0 +1,82 @@
+---
+title: Configuration
+description: Configure LLMs, tools, and agent settings
+---
+
+## LLMConfig
+
+Configure which LLM provider and model to use:
+
+```python
+from echo import LLMConfig
+
+llm_config = LLMConfig(
+    provider="openai",      # "openai", "anthropic", or "gemini"
+    model="gpt-4o-mini",    # Model identifier
+    temperature=0.2,        # 0.0-1.0, lower = more focused
+    max_tokens=2000,        # Max response length
+    max_iterations=5,       # Max tool use iterations
+)
+```
+
+See [LLM Providers](/ai-tools/agent-kit/llm-providers) for provider-specific details.
+
+## AgentConfig
+
+Combines **PersonaConfig** + **TaskConfig** to form the system prompt:
+
+```python
+from echo import AgentConfig, PersonaConfig, TaskConfig
+
+agent_config = AgentConfig(
+    persona=PersonaConfig(
+        role="Medical Assistant",           # Agent's identity
+        goal="Help with medical queries",   # What agent tries to achieve
+        backstory="A helpful medical AI",   # Background context
+    ),
+    task=TaskConfig(
+        description="Answer health questions using available tools",
+        expected_output="Accurate, helpful medical information",
+    ),
+)
+```
+
+**Generated System Prompt:**
+```
+You are a Medical Assistant.
+Your goal is: Help with medical queries
+Background: A helpful medical AI
+Task: Answer health questions using available tools
+Expected output: Accurate, helpful medical information
+```
+
+## Environment Variables
+
+<Tabs>
+  <Tab title="OpenAI">
+    ```bash
+    export OPENAI_API_KEY=sk-...
+    ```
+  </Tab>
+  <Tab title="Anthropic">
+    ```bash
+    export ANTHROPIC_API_KEY=sk-ant-...
+    ```
+  </Tab>
+  <Tab title="Gemini">
+    ```bash
+    export GOOGLE_API_KEY=...
+    ```
+  </Tab>
+</Tabs>
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Tools" icon="wrench" href="/ai-tools/agent-kit/tools">
+    Create and configure tools
+  </Card>
+  <Card title="LLM Providers" icon="brain" href="/ai-tools/agent-kit/llm-providers">
+    Provider-specific configuration
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/examples.mdx b/ai-tools/agent-kit/examples.mdx
new file mode 100644
index 00000000..b332fa22
--- /dev/null
+++ b/ai-tools/agent-kit/examples.mdx
@@ -0,0 +1,178 @@
+---
+title: Examples
+description: Complete working examples
+---
+
+## Basic Agent
+
+```python
+import asyncio
+from echo import (
+    GenericAgent, AgentConfig, LLMConfig, PersonaConfig, TaskConfig,
+    ConversationContext, Message, MessageRole, TextMessage
+)
+
+async def main():
+    agent = GenericAgent(
+        agent_config=AgentConfig(
+            persona=PersonaConfig(
+                role="Health Educator",
+                goal="Explain health topics simply",
+                backstory="A friendly health educator",
+            ),
+            task=TaskConfig(
+                description="Answer health questions clearly",
+                expected_output="Simple, accurate explanations",
+            ),
+        ),
+        llm_config=LLMConfig(provider="openai", model="gpt-4o-mini"),
+        tools=[],
+    )
+
+    context = ConversationContext()
+    context.add_message(Message(
+        role=MessageRole.USER,
+        content=[TextMessage(text="What is cholesterol?")],
+    ))
+
+    result = await agent.run(context)
+    print(result.llm_response.text)
+
+asyncio.run(main())
+```
+
+## Streaming with Elicitation
+
+```python
+import asyncio
+from echo import get_llm, LLMConfig, StreamEventType, ConversationContext
+from echo_agents.tools.elicitation import SelectionElicitationTool
+
+async def main():
+    llm = get_llm(LLMConfig(provider="openai", model="gpt-4o-mini"))
+    tools = [SelectionElicitationTool()]
+    context = ConversationContext()
+
+    system_prompt = """You are a medical assistant collecting symptoms.
+    Use elicit_selection to present symptom options as buttons."""
+
+    context.add_message(Message(
+        role=MessageRole.USER,
+        content=[TextMessage(text="I'm not feeling well")],
+    ))
+
+    print("Assistant: ", end="", flush=True)
+
+    async for event in llm.invoke_stream(context, tools=tools, system_prompt=system_prompt):
+        if event.type == StreamEventType.TEXT:
+            print(event.text, end="", flush=True)
+        elif event.type == StreamEventType.TOOL_CALL_START:
+            print(f"\n[Tool: {event.json.get('tool_name')}]")
+        elif event.type == StreamEventType.DONE:
+            print()
+            if event.llm_response.elicitations:
+                elicit = event.llm_response.elicitations[0]
+                print(f"\n📋 {elicit.details.input.get('text')}")
+                for opt in elicit.details.input.get('options', []):
+                    print(f"   • {opt}")
+
+asyncio.run(main())
+```
+
+## MCP Agent
+
+```python
+import asyncio
+import os
+from echo import (
+    GenericAgent, AgentConfig, LLMConfig, PersonaConfig, TaskConfig,
+    MCPConnectionManager, MCPServerConfig, MCPTransport,
+    ConversationContext, Message, MessageRole, TextMessage
+)
+
+async def main():
+    # Connect to Eka MCP
+    manager = MCPConnectionManager(MCPServerConfig(
+        transport=MCPTransport.STREAMABLE_HTTP,
+        url="https://mcp.eka.care/mcp",
+        headers={"x-eka-jwt-payload": os.getenv("EKA_JWT_PAYLOAD")},
+    ))
+
+    mcp_tools = await manager.get_tools()
+    print(f"Tools: {[t.name for t in mcp_tools]}")
+
+    agent = GenericAgent(
+        agent_config=AgentConfig(
+            persona=PersonaConfig(
+                role="Medical Assistant",
+                goal="Help with patient queries using tools",
+                backstory="A helpful medical AI with access to patient data",
+            ),
+            task=TaskConfig(
+                description="Use tools to answer queries accurately",
+                expected_output="Information from tools when appropriate",
+            ),
+        ),
+        tools=mcp_tools,
+        llm_config=LLMConfig(provider="openai", model="gpt-4o-mini", max_iterations=5),
+    )
+
+    context = ConversationContext()
+    context.add_message(Message(
+        role=MessageRole.USER,
+        content=[TextMessage(text="Search for patient Kumar")],
+    ))
+
+    result = await agent.run(context)
+
+    # Show tool calls
+    for item in result.llm_response.verbose:
+        if item.type == "tool":
+            print(f"[Tool] {item.tool_name}")
+
+    print(f"\nAssistant: {result.llm_response.text}")
+
+    await MCPConnectionManager.cleanup_all()
+
+asyncio.run(main())
+```
+
+## Multi-Turn Conversation
+
+```python
+async def conversation():
+    agent = GenericAgent(
+        agent_config=agent_config,
+        llm_config=llm_config,
+        tools=tools,
+    )
+
+    context = ConversationContext()
+
+    for i in range(10):
+        user_input = input(f"[{i+1}] You: ").strip()
+        if user_input.lower() == "quit":
+            break
+
+        context.add_message(Message(
+            role=MessageRole.USER,
+            content=[TextMessage(text=user_input)],
+        ))
+
+        result = await agent.run(context)
+        print(f"Assistant: {result.llm_response.text}\n")
+
+        # Update context for next turn
+        context = result.context
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Eka MCP Server" icon="server" href="/ai-tools/mcp-server/introduction">
+    Healthcare tools via MCP
+  </Card>
+  <Card title="Tools" icon="wrench" href="/ai-tools/agent-kit/tools">
+    Create custom tools
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/installation.mdx b/ai-tools/agent-kit/installation.mdx
new file mode 100644
index 00000000..ca023235
--- /dev/null
+++ b/ai-tools/agent-kit/installation.mdx
@@ -0,0 +1,46 @@
+---
+title: Installation
+description: Install Echo - open-source agent framework
+---
+
+[Echo](https://github.com/eka-care/echo) is open-source and available on GitHub.
+
+## Requirements
+
+- Python 3.11+
+
+## Install from PyPI
+
+```bash
+pip install echo-sdk
+```
+
+Or with uv:
+
+```bash
+uv pip install echo-sdk
+```
+
+## Install from GitHub
+
+```bash
+pip install git+https://github.com/eka-care/echo.git
+```
+
+## Verify
+
+```python
+import echo
+print(f"Echo SDK version: {echo.__version__}")
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Configuration" icon="gear" href="/ai-tools/agent-kit/configuration">
+    Configure LLMs and tools
+  </Card>
+  <Card title="Quickstart" icon="rocket" href="/ai-tools/agent-kit/quickstart">
+    Build your first agent
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/introduction.mdx b/ai-tools/agent-kit/introduction.mdx
new file mode 100644
index 00000000..8fcedb75
--- /dev/null
+++ b/ai-tools/agent-kit/introduction.mdx
@@ -0,0 +1,82 @@
+---
+title: Overview
+description: Build AI agents with Echo - an open-source, LLM-agnostic framework
+---
+
+<Info>
+**Open Source** - Echo is available on [GitHub](https://github.com/eka-care/echo)
+</Info>
+
+Build AI agents for healthcare applications with **Echo** - an open-source Python framework that works with any LLM provider.
+
+<CardGroup cols={2}>
+  <Card title="LLM-Agnostic" icon="brain">
+    Switch between OpenAI, Anthropic, or Gemini without changing agent code
+  </Card>
+  <Card title="Tool System" icon="wrench">
+    Base tools, elicitation tools for UI, or MCP server tools
+  </Card>
+  <Card title="Streaming" icon="stream">
+    Real-time events: TEXT, TOOL_CALL_START, TOOL_CALL_END, DONE
+  </Card>
+  <Card title="Framework-Agnostic" icon="cubes">
+    Standalone or integrate with FastAPI, Flask, etc.
+  </Card>
+</CardGroup>
+
+## Architecture
+
+<Frame caption="Echo SDK Architecture">
+  <img src="/images/echo-architecture.png" alt="Echo SDK Architecture" />
+</Frame>
+
+| Layer | Components |
+|-------|------------|
+| **Agent** | GenericAgent orchestrates using AgentConfig + Tools + LLM |
+| **Tools** | BaseTool, BaseElicitationTool, MCP Tools |
+| **LLM** | OpenAI, Anthropic, Gemini via unified LLMConfig |
+| **Streaming** | StreamEventType: TEXT, TOOL_CALL_START/END, DONE, ERROR |
+
+## Who Should Use This?
+
+<CardGroup cols={2}>
+  <Card title="Healthcare Developers" icon="laptop-code">
+    Build AI-powered healthcare applications
+  </Card>
+  <Card title="Platform Engineers" icon="server">
+    Create multi-provider agent infrastructure
+  </Card>
+  <Card title="Integration Teams" icon="plug">
+    Connect AI agents to healthcare systems via MCP
+  </Card>
+  <Card title="AI Researchers" icon="flask">
+    Experiment with models and tool configurations
+  </Card>
+</CardGroup>
+
+## Installation
+
+```bash
+pip install echo-sdk
+```
+
+Or install from source:
+
+```bash
+pip install git+https://github.com/eka-care/echo.git
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Quickstart" icon="rocket" href="/ai-tools/agent-kit/quickstart">
+    Build your first agent
+  </Card>
+  <Card title="Configuration" icon="gear" href="/ai-tools/agent-kit/configuration">
+    Tools, LLMs, AgentConfig
+  </Card>
+</CardGroup>
+
+<Note>
+**Contribute** - [github.com/eka-care/echo](https://github.com/eka-care/echo)
+</Note>
diff --git a/ai-tools/agent-kit/llm-providers.mdx b/ai-tools/agent-kit/llm-providers.mdx
new file mode 100644
index 00000000..f82eeda8
--- /dev/null
+++ b/ai-tools/agent-kit/llm-providers.mdx
@@ -0,0 +1,129 @@
+---
+title: LLM Providers
+description: Configure OpenAI, Anthropic, and Gemini
+---
+
+## Provider Comparison
+
+| Provider | Models | Best For |
+|----------|--------|----------|
+| **OpenAI** | gpt-4o, gpt-4o-mini, gpt-4-turbo | General purpose, cost-effective |
+| **Anthropic** | claude-sonnet-4, claude-3-opus | Advanced reasoning, long context |
+| **Gemini** | gemini-1.5-pro, gemini-pro | Multimodal, Google ecosystem |
+
+---
+
+## Configuration
+
+<Tabs>
+  <Tab title="OpenAI">
+    **Environment:**
+    ```bash
+    export OPENAI_API_KEY=sk-...
+    ```
+
+    **Config:**
+    ```python
+    from echo import LLMConfig, get_llm
+
+    llm_config = LLMConfig(
+        provider="openai",
+        model="gpt-4o-mini",
+        temperature=0.2,
+        max_tokens=2000,
+    )
+
+    llm = get_llm(llm_config)
+    ```
+
+    **Models:** `gpt-4o`, `gpt-4o-mini`, `gpt-4-turbo`, `gpt-3.5-turbo`
+  </Tab>
+
+  <Tab title="Anthropic">
+    **Environment:**
+    ```bash
+    export ANTHROPIC_API_KEY=sk-ant-...
+    ```
+
+    **Config:**
+    ```python
+    from echo import LLMConfig, get_llm
+
+    llm_config = LLMConfig(
+        provider="anthropic",
+        model="claude-sonnet-4-20250514",
+        temperature=0.2,
+        max_tokens=2000,
+    )
+
+    llm = get_llm(llm_config)
+    ```
+
+    **Models:** `claude-sonnet-4-20250514`, `claude-3-opus-20240229`, `claude-3-haiku-20240307`
+  </Tab>
+
+  <Tab title="Gemini">
+    **Environment:**
+    ```bash
+    export GOOGLE_API_KEY=...
+    ```
+
+    **Config:**
+    ```python
+    from echo import LLMConfig, get_llm
+
+    llm_config = LLMConfig(
+        provider="gemini",
+        model="gemini-1.5-pro",
+        temperature=0.2,
+        max_tokens=2000,
+    )
+
+    llm = get_llm(llm_config)
+    ```
+
+    **Models:** `gemini-1.5-pro`, `gemini-pro`, `gemini-pro-vision`
+  </Tab>
+</Tabs>
+
+---
+
+## Switching Providers
+
+Change one line to switch providers:
+
+```python
+# OpenAI
+llm_config = LLMConfig(provider="openai", model="gpt-4o-mini")
+
+# Anthropic
+llm_config = LLMConfig(provider="anthropic", model="claude-sonnet-4-20250514")
+
+# Gemini
+llm_config = LLMConfig(provider="gemini", model="gemini-1.5-pro")
+```
+
+Agent code remains the same.
+
+---
+
+## LLMConfig Parameters
+
+| Parameter | Type | Default | Description |
+|-----------|------|---------|-------------|
+| `provider` | str | Required | `"openai"`, `"anthropic"`, `"gemini"` |
+| `model` | str | Required | Model identifier |
+| `temperature` | float | 0.7 | Randomness (0.0-1.0) |
+| `max_tokens` | int | 4096 | Max response length |
+| `max_iterations` | int | 5 | Max tool use iterations |
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Streaming" icon="stream" href="/ai-tools/agent-kit/streaming">
+    Real-time responses
+  </Card>
+  <Card title="Examples" icon="lightbulb" href="/ai-tools/agent-kit/examples">
+    Complete examples
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/mcp-integration.mdx b/ai-tools/agent-kit/mcp-integration.mdx
new file mode 100644
index 00000000..7f7f4a92
--- /dev/null
+++ b/ai-tools/agent-kit/mcp-integration.mdx
@@ -0,0 +1,105 @@
+---
+title: MCP Integration
+description: Connect to MCP servers for external tools
+---
+
+## MCPServerConfig
+
+```python
+from echo import MCPConnectionManager, MCPServerConfig, MCPTransport
+
+config = MCPServerConfig(
+    transport=MCPTransport.STREAMABLE_HTTP,
+    url="https://mcp.eka.care/mcp",
+    headers={"x-eka-jwt-payload": "..."},  # Auth header
+)
+```
+
+## Connect and Get Tools
+
+```python
+manager = MCPConnectionManager(config)
+tools = await manager.get_tools()
+
+print(f"Found {len(tools)} tools:")
+for tool in tools:
+    print(f"  - {tool.name}: {tool.description}")
+```
+
+## Use with GenericAgent
+
+```python
+from echo import GenericAgent, AgentConfig, LLMConfig
+
+# Get MCP tools
+manager = MCPConnectionManager(config)
+mcp_tools = await manager.get_tools()
+
+# Create agent with MCP tools
+agent = GenericAgent(
+    agent_config=AgentConfig(
+        persona=PersonaConfig(
+            role="Medical Assistant",
+            goal="Help with medical queries using tools",
+            backstory="A helpful medical AI",
+        ),
+        task=TaskConfig(
+            description="Use available tools to answer queries",
+            expected_output="Accurate information using tool results",
+        ),
+    ),
+    tools=mcp_tools,
+    llm_config=LLMConfig(provider="openai", model="gpt-4o-mini"),
+)
+
+# Run
+result = await agent.run(context)
+```
+
+## Multiple MCP Servers
+
+```python
+MCP_SERVERS = [
+    MCPServerConfig(
+        transport=MCPTransport.STREAMABLE_HTTP,
+        url="https://mcp.eka.care/mcp",
+        headers={"x-eka-jwt-payload": os.getenv("EKA_JWT_PAYLOAD")},
+    ),
+    MCPServerConfig(
+        transport=MCPTransport.STREAMABLE_HTTP,
+        url="https://other-mcp.example.com/mcp",
+    ),
+]
+
+# Collect tools from all servers
+all_tools = []
+for server_config in MCP_SERVERS:
+    manager = MCPConnectionManager(server_config)
+    tools = await manager.get_tools()
+    all_tools.extend(tools)
+
+# Use combined tools
+agent = GenericAgent(
+    agent_config=agent_config,
+    tools=all_tools,
+    llm_config=llm_config,
+)
+```
+
+## Cleanup
+
+```python
+# When done, cleanup all connections
+await MCPConnectionManager.cleanup_all()
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Eka MCP Server" icon="server" href="/ai-tools/mcp-server/introduction">
+    Available healthcare tools
+  </Card>
+  <Card title="Examples" icon="lightbulb" href="/ai-tools/agent-kit/examples">
+    Complete MCP examples
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/quickstart.mdx b/ai-tools/agent-kit/quickstart.mdx
new file mode 100644
index 00000000..e587385f
--- /dev/null
+++ b/ai-tools/agent-kit/quickstart.mdx
@@ -0,0 +1,102 @@
+---
+title: Quickstart
+description: Build your first AI agent with Echo in 5 minutes
+---
+
+Get started with [Echo](https://github.com/eka-care/echo) in 5 minutes.
+
+<Steps>
+  <Step title="Install">
+    ```bash
+    pip install echo-sdk
+    ```
+  </Step>
+
+  <Step title="Set API Key">
+    ```bash
+    export OPENAI_API_KEY=sk-...
+    # or ANTHROPIC_API_KEY or GOOGLE_API_KEY
+    ```
+  </Step>
+
+  <Step title="Create Agent">
+    ```python
+    import asyncio
+    from echo import (
+        GenericAgent, AgentConfig, LLMConfig,
+        PersonaConfig, TaskConfig, ConversationContext,
+        Message, MessageRole, TextMessage
+    )
+
+    # LLM configuration
+    llm_config = LLMConfig(
+        provider="openai",
+        model="gpt-4o-mini",
+        temperature=0.2,
+        max_tokens=2000,
+    )
+
+    # Agent configuration (persona + task = system prompt)
+    agent_config = AgentConfig(
+        persona=PersonaConfig(
+            role="Healthcare Assistant",
+            goal="Help users with health queries",
+            backstory="A knowledgeable medical AI assistant",
+        ),
+        task=TaskConfig(
+            description="Answer health-related questions accurately",
+            expected_output="Clear, helpful medical information",
+        ),
+    )
+
+    async def main():
+        agent = GenericAgent(
+            agent_config=agent_config,
+            llm_config=llm_config,
+            tools=[],
+        )
+
+        context = ConversationContext()
+        context.add_message(Message(
+            role=MessageRole.USER,
+            content=[TextMessage(text="What are symptoms of dehydration?")],
+        ))
+
+        result = await agent.run(context)
+        print(result.llm_response.text)
+
+    asyncio.run(main())
+    ```
+  </Step>
+
+  <Step title="Run">
+    ```bash
+    python my_agent.py
+    ```
+  </Step>
+</Steps>
+
+## With Streaming
+
+```python
+from echo import get_llm, StreamEventType
+
+llm = get_llm(LLMConfig(provider="openai", model="gpt-4o-mini"))
+
+async for event in llm.invoke_stream(context, system_prompt="You are helpful."):
+    if event.type == StreamEventType.TEXT:
+        print(event.text, end="", flush=True)
+    elif event.type == StreamEventType.DONE:
+        print("\n--- Done ---")
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Tools" icon="wrench" href="/ai-tools/agent-kit/tools">
+    Add tools to your agent
+  </Card>
+  <Card title="MCP Integration" icon="plug" href="/ai-tools/agent-kit/mcp-integration">
+    Connect to Eka MCP Server
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/streaming.mdx b/ai-tools/agent-kit/streaming.mdx
new file mode 100644
index 00000000..90705d0a
--- /dev/null
+++ b/ai-tools/agent-kit/streaming.mdx
@@ -0,0 +1,105 @@
+---
+title: Streaming
+description: Real-time response streaming with typed events
+---
+
+Stream responses in real-time with typed events.
+
+## StreamEventType
+
+| Event | Description |
+|-------|-------------|
+| `TEXT` | Text content chunk |
+| `TOOL_CALL_START` | Agent calling a tool |
+| `TOOL_CALL_END` | Tool call completed |
+| `DONE` | Stream completed |
+| `ERROR` | Error occurred |
+
+## Basic Streaming
+
+```python
+from echo import get_llm, LLMConfig, StreamEventType, ConversationContext
+
+llm = get_llm(LLMConfig(provider="openai", model="gpt-4o-mini"))
+context = ConversationContext()
+
+# Add user message
+context.add_message(Message(
+    role=MessageRole.USER,
+    content=[TextMessage(text="Explain diabetes briefly")],
+))
+
+# Stream response
+async for event in llm.invoke_stream(context, system_prompt="You are helpful."):
+    if event.type == StreamEventType.TEXT:
+        print(event.text, end="", flush=True)
+    elif event.type == StreamEventType.TOOL_CALL_START:
+        print(f"\n[Tool: {event.json.get('tool_name')}]", end="")
+    elif event.type == StreamEventType.TOOL_CALL_END:
+        print(" ✓")
+    elif event.type == StreamEventType.DONE:
+        print("\n--- Done ---")
+        final_response = event.llm_response
+        context = event.context
+    elif event.type == StreamEventType.ERROR:
+        print(f"\n[Error: {event.error}]")
+```
+
+## Streaming with Tools
+
+```python
+from echo_agents.tools.elicitation import SelectionElicitationTool
+
+llm = get_llm(LLMConfig(provider="openai", model="gpt-4o-mini"))
+tools = [SelectionElicitationTool()]
+
+async for event in llm.invoke_stream(context, tools=tools, system_prompt=prompt):
+    if event.type == StreamEventType.TEXT:
+        print(event.text, end="", flush=True)
+    elif event.type == StreamEventType.TOOL_CALL_START:
+        print(f"\n🔧 {event.json.get('tool_name')}")
+    elif event.type == StreamEventType.TOOL_CALL_END:
+        print("   ✓ Done")
+    elif event.type == StreamEventType.DONE:
+        # Check for elicitations
+        if event.llm_response.elicitations:
+            elicit = event.llm_response.elicitations[0]
+            print(f"\n📋 {elicit.details.input.get('text')}")
+            for opt in elicit.details.input.get('options', []):
+                print(f"   • {opt}")
+```
+
+## DONE Event
+
+The `DONE` event contains:
+
+```python
+elif event.type == StreamEventType.DONE:
+    response = event.llm_response
+
+    # Final text
+    print(response.text)
+
+    # Verbose tool calls
+    for item in response.verbose:
+        if item.type == "tool":
+            print(f"Tool used: {item.tool_name}")
+
+    # Elicitations (UI components)
+    for elicit in response.elicitations:
+        print(f"UI: {elicit.details.component}")
+
+    # Updated context for next turn
+    context = event.context
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Examples" icon="lightbulb" href="/ai-tools/agent-kit/examples">
+    Complete streaming examples
+  </Card>
+  <Card title="MCP Integration" icon="plug" href="/ai-tools/agent-kit/mcp-integration">
+    Stream with MCP tools
+  </Card>
+</CardGroup>
diff --git a/ai-tools/agent-kit/tools.mdx b/ai-tools/agent-kit/tools.mdx
new file mode 100644
index 00000000..87e9f38c
--- /dev/null
+++ b/ai-tools/agent-kit/tools.mdx
@@ -0,0 +1,189 @@
+---
+title: Tools
+description: Create base tools, elicitation tools, and use MCP tools
+---
+
+Echo SDK supports three tool types:
+
+| Type | Purpose | Returns |
+|------|---------|---------|
+| **BaseTool** | Standard operations | `str` |
+| **BaseElicitationTool** | UI components for user input | `ElicitationDetails` |
+| **MCP Tool** | External tools from MCP servers | Auto-wrapped |
+
+---
+
+## BaseTool
+
+Standard tools that perform operations and return string results:
+
+```python
+from echo.tools.base_tool import BaseTool
+from typing import Any, Dict, Optional
+
+class ClinicalGuidelinesRetrieverTool(BaseTool):
+    """Retrieve clinical guidelines from knowledge base."""
+
+    name: str = "retrieve_clinical_guidelines"
+    description: str = (
+        "Retrieve relevant clinical guidelines for a medical query. "
+        "Use this before making triage recommendations."
+    )
+
+    @property
+    def input_schema(self) -> Dict[str, Any]:
+        return {
+            "type": "object",
+            "properties": {
+                "query": {
+                    "type": "string",
+                    "description": "Medical query to search",
+                },
+                "num_results": {
+                    "type": "integer",
+                    "description": "Number of results",
+                    "default": 5,
+                },
+            },
+            "required": ["query"],
+        }
+
+    async def run(
+        self,
+        query: str = "",
+        num_results: Optional[int] = None,
+        **kwargs,
+    ) -> str:
+        if not query:
+            return "Error: No query provided."
+
+        results = self.kb.retrieve(query=query, num_results=num_results or 5)
+        return self._format_results(results)
+```
+
+---
+
+## BaseElicitationTool
+
+Tools that present UI components to collect user input:
+
+```python
+from echo.tools import BaseElicitationTool, ElicitationDetails
+from typing import Any, Dict, List
+
+class SelectionElicitationTool(BaseElicitationTool):
+    """Present single/multi-select options to user."""
+
+    name: str = "elicit_selection"
+    description: str = (
+        "Ask choice questions to the user. Presents options as buttons. "
+        "Use component='pills' for single select, 'multi' for multi-select."
+    )
+
+    @property
+    def elicitation_components(self):
+        return [
+            SelectionElicitationComponent.PILLS,
+            SelectionElicitationComponent.MULTI_SELECT,
+        ]
+
+    @property
+    def input_schema(self) -> Dict[str, Any]:
+        return {
+            "type": "object",
+            "properties": {
+                "component": {
+                    "type": "string",
+                    "enum": ["pills", "multi"],
+                    "description": "pills=single select, multi=multi-select",
+                },
+                "options": {
+                    "type": "array",
+                    "items": {"type": "string"},
+                    "description": "Options to display",
+                },
+                "text": {
+                    "type": "string",
+                    "description": "Question text above options",
+                },
+            },
+            "required": ["component", "options", "text"],
+        }
+
+    async def run(
+        self,
+        component: str,
+        text: str,
+        options: List[str],
+        **kwargs,
+    ) -> ElicitationDetails:
+        options_formatted = [{"label": opt, "value": opt} for opt in options]
+        return await super().run(component, text=text, options=options_formatted)
+```
+
+**Elicitation Components:**
+- `pills` - Single select buttons
+- `multi` - Multi-select checkboxes
+- `otp` - OTP verification input
+- `doctor_list` - Doctor selection cards
+
+---
+
+## MCP Tools
+
+Tools from MCP servers are auto-discovered and wrapped:
+
+```python
+from echo import MCPConnectionManager, MCPServerConfig, MCPTransport
+
+# Connect to MCP server
+manager = MCPConnectionManager(MCPServerConfig(
+    transport=MCPTransport.STREAMABLE_HTTP,
+    url="https://mcp.eka.care/mcp",
+    headers={"Authorization": "Bearer <token>"},
+))
+
+# Get tools
+mcp_tools = await manager.get_tools()
+
+# Use with agent
+agent = GenericAgent(
+    agent_config=agent_config,
+    tools=mcp_tools,
+    llm_config=llm_config,
+)
+```
+
+See [MCP Integration](/ai-tools/agent-kit/mcp-integration) for details.
+
+---
+
+## Using Tools with Agent
+
+```python
+from echo import GenericAgent
+
+# Combine tool types
+all_tools = [
+    ClinicalGuidelinesRetrieverTool(),
+    SelectionElicitationTool(),
+    *mcp_tools,  # Tools from MCP server
+]
+
+agent = GenericAgent(
+    agent_config=agent_config,
+    tools=all_tools,
+    llm_config=llm_config,
+)
+```
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="MCP Integration" icon="plug" href="/ai-tools/agent-kit/mcp-integration">
+    Connect to MCP servers
+  </Card>
+  <Card title="Streaming" icon="stream" href="/ai-tools/agent-kit/streaming">
+    See tool calls in real-time
+  </Card>
+</CardGroup>
diff --git a/ai-tools/mcp-server/authentication.mdx b/ai-tools/mcp-server/authentication.mdx
new file mode 100644
index 00000000..852175e8
--- /dev/null
+++ b/ai-tools/mcp-server/authentication.mdx
@@ -0,0 +1,200 @@
+---
+title: Authentication
+description: Securely connect your AI assistant to Eka.care
+---
+
+## Overview
+
+Eka.care MCP supports two authentication methods to fit different integration needs:
+
+<CardGroup cols={2}>
+  <Card title="OIDC Flow (Recommended)" icon="shield-check">
+    **Best for:** Healthcare providers and clinics
+
+    Auto-authenticate with your Eka.care account. No manual credential management needed.
+  </Card>
+  <Card title="Client Credentials" icon="key">
+    **Best for:** Third-party integrations
+
+    Use API credentials (Client ID, Secret, API Key) for programmatic access.
+  </Card>
+</CardGroup>
+
+---
+
+## Method 1: OIDC Flow (Auto-Authentication)
+
+This is the **easiest and most secure** method. Your AI assistant authenticates using your Eka.care login, just like logging into the dashboard.
+
+### How It Works
+
+<Steps>
+  <Step title="You start your MCP client">
+    Claude Desktop or any MCP-compatible client
+  </Step>
+  <Step title="MCP initiates OIDC flow">
+    Opens a secure browser window
+  </Step>
+  <Step title="You log in to Eka.care">
+    Use your existing Eka.care credentials
+  </Step>
+  <Step title="Connection established">
+    Your AI assistant now has secure access
+  </Step>
+</Steps>
+
+<Frame>
+  <img src="/images/OIDC.png" alt="OIDC Authentication Flow" />
+  {/* Screenshot placeholder: Diagram showing OIDC flow steps */}
+</Frame>
+
+## Method 2: Client Credentials
+
+Use this method if you have API credentials (Client ID, Client Secret, API Key) from the Eka.care team.
+
+### How It Works
+
+Your MCP server authenticates directly with Eka.care APIs using:
+- **Client ID**: Your application identifier
+- **Client Secret**: Secret key for authentication
+- **API Key**: to connect to a specefic workspace from your client_id / client_secret
+
+### Setup Client Credentials
+
+**1. Get your credentials:**
+
+Get your client id and client secret from Eka developer [console](https://console.eka.care/api-keys/)
+- Client ID
+- Client Secret
+
+If you are a standalone devleoper and wish to access workspaces of Eka Users you can either implement OIDC ( Oauth ) flow or get API Key from users workspace [Hub](https://hub.eka.care/account/account/apitoken/)
+- API Key
+
+
+For any issues you can contact **ekaconnect@eka.care** and request:
+
+**2. Configure your `.env` file:**
+
+```bash .env
+# API Configuration
+EKA_API_BASE_URL=https://api.eka.care
+
+# Client Credentials
+EKA_CLIENT_ID=your_client_id_here
+EKA_CLIENT_SECRET=your_client_secret_here
+EKA_API_KEY=your_api_key_here
+
+# Server Settings (optional)
+EKA_MCP_SERVER_HOST=localhost
+EKA_MCP_SERVER_PORT=8000
+EKA_LOG_LEVEL=INFO
+```
+
+<Warning>
+**Security Best Practices:**
+- Never commit credentials to version control
+- Use `.gitignore` to exclude `.env` file
+- Rotate credentials periodically
+- Use different credentials for development and production
+</Warning>
+
+**3. Update Claude Desktop config:**
+
+```json claude_desktop_config.json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "/full/path/to/.venv/bin/python",
+      "args": ["-m", "eka_mcp_sdk.server"],
+      "env": {
+        "EKA_CLIENT_ID": "your_client_id_here",
+        "EKA_CLIENT_SECRET": "your_client_secret_here",
+        "EKA_API_KEY": "your_api_key_here",
+        "EKA_API_BASE_URL": "https://api.eka.care"
+      }
+    }
+  }
+}
+```
+
+**4. Test your connection:**
+
+```bash
+# Start the MCP server
+eka-mcp-server
+```
+
+You should see:
+```
+INFO: Authentication successful
+INFO: MCP Server running on http://localhost:8000
+```
+
+### Credential Management Tips
+
+<AccordionGroup>
+  <Accordion title="How to test credentials">
+    **Quick test with curl:**
+    ```bash
+    curl -X POST https://api.eka.care/api/v1/auth/token \
+      -H "Content-Type: application/json" \
+      -H "X-API-KEY: your_api_key" \
+      -d '{
+        "client_id": "your_client_id",
+        "client_secret": "your_client_secret",
+        "grant_type": "client_credentials"
+      }'
+    ```
+
+    Should return an access token if credentials are valid.
+  </Accordion>
+
+  <Accordion title="Token expiration">
+    **Automatic refresh:** The MCP server automatically refreshes tokens before they expire.
+
+    **Default expiration:** Tokens typically last 1 hour and are refreshed automatically.
+
+    **No action needed:** You don't need to manually manage token lifecycle.
+  </Accordion>
+
+  <Accordion title="Multiple environments">
+    **Development:**
+    ```bash .env.development
+    EKA_CLIENT_ID=dev_client_id
+    EKA_CLIENT_SECRET=dev_client_secret
+    EKA_API_KEY=dev_api_key
+    EKA_API_BASE_URL=https://api-dev.eka.care
+    ```
+
+    **Production:**
+    ```bash .env.production
+    EKA_CLIENT_ID=prod_client_id
+    EKA_CLIENT_SECRET=prod_client_secret
+    EKA_API_KEY=prod_api_key
+    EKA_API_BASE_URL=https://api.eka.care
+    ```
+  </Accordion>
+
+  <Accordion title="Credential rotation">
+    **When to rotate:**
+    - Every 90 days (recommended)
+    - If credentials may be compromised
+    - When team members leave
+
+    **How to rotate:**
+    1. Contact ekaconnect@eka.care for new credentials
+    2. Update your `.env` file
+    3. Restart the MCP server
+    4. Update Claude Desktop config if needed
+  </Accordion>
+</AccordionGroup>
+
+---
+
+<Note>
+**Need Credentials?** Contact **ekaconnect@eka.care** with:
+- Your organization name
+- Integration type (OIDC or Client Credentials)
+- Use case description
+- Expected API usage volume
+</Note>
diff --git a/ai-tools/mcp-server/integrations/custom-client.mdx b/ai-tools/mcp-server/integrations/custom-client.mdx
new file mode 100644
index 00000000..1aa780f3
--- /dev/null
+++ b/ai-tools/mcp-server/integrations/custom-client.mdx
@@ -0,0 +1,245 @@
+---
+title: Custom MCP Client
+description: Integrate Eka.care MCP into your own application
+---
+
+## Overview
+
+Want to build your own AI-powered healthcare application? You can integrate Eka.care MCP into any application that supports the Model Context Protocol standard.
+
+<CardGroup cols={2}>
+  <Card title="Build AI Health Apps" icon="mobile">
+    Create custom healthcare assistants
+  </Card>
+  <Card title="Automation Tools" icon="robot">
+    Automate clinic workflows
+  </Card>
+  <Card title="Internal Tools" icon="wrench">
+    Custom admin dashboards
+  </Card>
+  <Card title="Web Services" icon="globe">
+    API-powered AI services
+  </Card>
+</CardGroup>
+
+---
+
+## Quick Integration
+
+### Using the MCP SDK
+
+The easiest way is to use the official MCP SDK in your preferred language:
+
+<Tabs>
+  <Tab title="Python">
+    ```python
+    from mcp import ClientSession, StdioServerParameters
+    from mcp.client.stdio import stdio_client
+
+    # Create MCP client connection
+    server_params = StdioServerParameters(
+        command="/path/to/.venv/bin/python",
+        args=["-m", "eka_mcp_sdk.server"],
+        env={
+            "EKA_CLIENT_ID": "your_client_id",
+            "EKA_CLIENT_SECRET": "your_client_secret",
+            "EKA_API_KEY": "your_api_key"
+        }
+    )
+
+    async with stdio_client(server_params) as (read, write):
+        async with ClientSession(read, write) as session:
+            # Initialize connection
+            await session.initialize()
+
+            # List available tools
+            tools = await session.list_tools()
+            print(f"Available tools: {[t.name for t in tools]}")
+
+            # Call a tool
+            result = await session.call_tool(
+                "search_patients",
+                arguments={"prefix": "Kumar"}
+            )
+            print(result)
+    ```
+  </Tab>
+
+  <Tab title="TypeScript">
+    ```typescript
+    import { Client } from "@modelcontextprotocol/sdk/client/index.js";
+    import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
+
+    const transport = new StdioClientTransport({
+      command: "/path/to/.venv/bin/python",
+      args: ["-m", "eka_mcp_sdk.server"],
+      env: {
+        EKA_CLIENT_ID: "your_client_id",
+        EKA_CLIENT_SECRET: "your_client_secret",
+        EKA_API_KEY: "your_api_key"
+      }
+    });
+
+    const client = new Client({
+      name: "my-healthcare-app",
+      version: "1.0.0"
+    }, {
+      capabilities: {}
+    });
+
+    await client.connect(transport);
+
+    // List available tools
+    const tools = await client.listTools();
+    console.log("Available tools:", tools.tools.map(t => t.name));
+
+    // Call a tool
+    const result = await client.callTool({
+      name: "search_patients",
+      arguments: { prefix: "Kumar" }
+    });
+    console.log(result);
+    ```
+  </Tab>
+
+  <Tab title="Go">
+    ```go
+    package main
+
+    import (
+        "context"
+        "fmt"
+        "github.com/modelcontextprotocol/sdk-go/client"
+    )
+
+    func main() {
+        // Create MCP client
+        c := client.NewStdioClient(
+            "/path/to/.venv/bin/python",
+            []string{"-m", "eka_mcp_sdk.server"},
+            map[string]string{
+                "EKA_CLIENT_ID":     "your_client_id",
+                "EKA_CLIENT_SECRET": "your_client_secret",
+                "EKA_API_KEY":       "your_api_key",
+            },
+        )
+
+        // Connect
+        ctx := context.Background()
+        if err := c.Connect(ctx); err != nil {
+            panic(err)
+        }
+        defer c.Close()
+
+        // List tools
+        tools, err := c.ListTools(ctx)
+        if err != nil {
+            panic(err)
+        }
+        fmt.Printf("Available tools: %+v\n", tools)
+
+        // Call a tool
+        result, err := c.CallTool(ctx, "search_patients", map[string]interface{}{
+            "prefix": "Kumar",
+        })
+        if err != nil {
+            panic(err)
+        }
+        fmt.Printf("Result: %+v\n", result)
+    }
+    ```
+  </Tab>
+</Tabs>
+
+---
+
+## HTTP Integration
+
+Prefer REST APIs? Deploy the MCP server with HTTP transport:
+
+### Setup HTTP Server
+
+```python server.py
+from fastmcp import FastMCP
+from eka_mcp_sdk.tools.patient_tools import register_patient_tools
+from eka_mcp_sdk.tools.appointment_tools import register_appointment_tools
+
+# Create FastMCP instance
+mcp = FastMCP("Eka.care MCP")
+
+# Register tools
+register_patient_tools(mcp)
+register_appointment_tools(mcp)
+
+# Run with HTTP transport
+if __name__ == "__main__":
+    import uvicorn
+    uvicorn.run(mcp.get_asgi_app(), host="0.0.0.0", port=8000)
+```
+
+### Call via HTTP
+
+```bash
+# List available tools
+curl http://localhost:8000/tools
+
+# Call a tool
+curl -X POST http://localhost:8000/call_tool \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "search_patients",
+    "arguments": {"prefix": "Kumar"}
+  }'
+```
+
+---
+
+## Docker Deployment
+
+Deploy as a containerized service:
+
+```dockerfile Dockerfile
+FROM python:3.11-slim
+
+WORKDIR /app
+
+# Install dependencies
+COPY requirements.txt .
+RUN pip install -r requirements.txt
+
+# Copy MCP server code
+COPY . .
+
+# Install package
+RUN pip install -e .
+
+# Expose port
+EXPOSE 8000
+
+# Run server
+CMD ["python", "-m", "eka_mcp_sdk.server"]
+```
+
+```yaml docker-compose.yml
+version: '3.8'
+
+services:
+  eka-mcp:
+    build: .
+    ports:
+      - "8000:8000"
+    environment:
+      - EKA_CLIENT_ID=${EKA_CLIENT_ID}
+      - EKA_CLIENT_SECRET=${EKA_CLIENT_SECRET}
+      - EKA_API_KEY=${EKA_API_KEY}
+      - EKA_API_BASE_URL=https://api.eka.care
+    restart: unless-stopped
+```
+
+---
+
+<Note>
+**Building Something Cool?** We'd love to hear about it!
+- Email us: ekaconnect@eka.care
+- Get featured in our showcase!
+</Note>
diff --git a/ai-tools/mcp-server/introduction.mdx b/ai-tools/mcp-server/introduction.mdx
new file mode 100644
index 00000000..cfacfbc3
--- /dev/null
+++ b/ai-tools/mcp-server/introduction.mdx
@@ -0,0 +1,382 @@
+---
+title: Eka MCP Server
+description: Connect your AI assistant to Eka.care's healthcare platform
+---
+
+<Frame>
+  <img src="/images/eka-remote-mcp.png" alt="MCP Overview" />
+  {/* Screenshot placeholder: Show diagram of AI Assistant <-> MCP <-> Eka.care APIs */}
+</Frame>
+
+**Model Context Protocol (MCP)** is an open standard that lets AI assistants like Claude connect directly to your applications and data securely. Think of it as a universal adapter that helps AI understand and work with your healthcare systems.
+
+Eka's MCP server follows the authenticated remote [MCP spec](https://modelcontextprotocol.io/specification/2025-03-26), so the server is centrally hosted and managed. Instead of copying and pasting patient data or manually creating appointments, your AI assistant can handle appointment booking, prescription creation, and patient lookups automatically with built in Authentication and HIPAA-compliant data handling.
+
+
+## Setup Instructions
+
+### General
+
+Eka's MCP server is currently supporting Streamable HTTP transport. It uses OAuth 2.0 with OpenID Connect (OIDC) flow for dynamic client registration for authentication at the following address:
+
+- HTTP : `https://mcp.eka.care/mcp`
+
+For setup instructions on specific clients, continue reading ..
+
+
+<AccordionGroup>
+  <Accordion title="VS Code (macOS)" icon="apple">
+
+**Requirements:** VS Code 1.95+ with GitHub Copilot
+
+1. Press `Cmd + Shift + P`
+2. Type and select **MCP: Add Server**
+3. Choose **HTTP** *(HTTP or Server-Sent Events)*
+4. Enter URL: `https://mcp.eka.care/mcp`
+5. Enter server name: `eka-care-mcp`
+6. Authenticate with your Eka.care email
+
+Done! Test by asking Copilot: *"Search for patient Raj Kumar"*
+
+  </Accordion>
+
+  <Accordion title="VS Code (Windows)" icon="windows">
+
+**Requirements:** VS Code 1.95+ with GitHub Copilot
+
+1. Press `Ctrl + Shift + P`
+2. Type and select **MCP: Add Server**
+3. Choose **HTTP** *(HTTP or Server-Sent Events)*
+4. Enter URL: `https://mcp.eka.care/mcp`
+5. Enter server name: `eka-care-mcp`
+6. Authenticate with your Eka.care email
+
+Configuration saved to: `%APPDATA%\Code\User\globalStorage\github.copilot-chat\mcp.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Paid(macOS/Windows)" icon="crown">
+
+**Requirements:** Claude Paid subscription
+
+1. Open Claude Desktop
+2. Click **Settings** → **Connectors** → **Add custom connector**
+3. Type the name as **Eka-Care-mcp**
+4. Type the URL as **https://mcp.eka.care/mcp**
+5. Tap **Add**
+6. Authenticate with Eka.care
+7. Save and restart
+
+Pro users get higher rate limits and priority access.
+
+Config(macOS): `~/Library/Application Support/Claude/claude_desktop_config.json`
+Config(Windows): `%APPDATA%\Claude\claude_desktop_config.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Free(macOS)" icon="message">
+
+**Requirements:** Claude Desktop app (Free tier)
+
+1. Open Claude Desktop
+2. Click **Settings** (bottom-left gear icon)
+3. Navigate to **Developer** → **Edit Config**
+4. Add this configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "https://mcp.eka.care/mcp"]
+    }
+  }
+}
+```
+
+5. Save and restart Claude Desktop
+6. Authenticate when prompted
+
+Config location: `~/Library/Application Support/Claude/claude_desktop_config.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Free(Windows)" icon="message">
+
+**Requirements:** Claude Desktop app (Free tier)
+
+1. Open Claude Desktop
+2. Click **Settings** (gear icon)
+3. Go to **Developer** → **Edit Config**
+4. Add:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "https://mcp.eka.care/mcp"]
+    }
+  }
+}
+```
+
+5. Save and restart Claude
+6. Authenticate when prompted
+
+Config location: `%APPDATA%\Claude\claude_desktop_config.json`
+
+  </Accordion>
+  <Accordion title="ChatGPT (Go/Paid)" icon="code">
+
+**Requirements:** Free chatgpt does not provide the remote mcp connectors currently, You should have >Go model.
+
+1. Open https://chatgpt.com/
+2. Go to profile (Left bottom)
+3. Click **Settings**
+4. Navigate to **Apps and Connectors**
+5. Scroll down and inside the Developer mode, switch it on
+6. Inside Apps and Connectors, tap **Create app**
+7. Enter the name **eka-care-mcp**
+8. Enter the URL **https://mcp.eka.care/mcp** and tap **Create**
+9. Authenticate when prompted
+
+  </Accordion>
+  <Accordion title="Cursor (macOS)" icon="code">
+
+**Requirements:** Cursor IDE
+
+1. Open Cursor
+2. Press `Cmd + Shift + P`
+3. Type **Cursor settings**
+4. Select **Tools & MCP**
+5. Tap on **New MCP Server**
+6. Add server configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+7. Tap on Connect to Authenticate with Eka.care
+8. Restart Cursor
+
+Config location: `~/Library/Application Support/Cursor/User/globalStorage/mcp.json`
+
+  </Accordion>
+
+  <Accordion title="Cursor (Windows)" icon="code">
+
+**Requirements:** Cursor IDE
+
+1. Open Cursor
+2. Press `Ctrl + Shift + P`
+3. Type **Cursor settings**
+4. Select **Tools & MCP**
+5. Tap on **New MCP Server**
+6. Add server configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+7. Restart Cursor
+8. Complete authentication
+
+Config: `%APPDATA%\Cursor\User\globalStorage\mcp.json`
+
+
+  </Accordion>
+
+  <Accordion title="Zed (macOS)" icon="z">
+
+**Requirements:** Zed Editor with AI features enabled
+
+1. Open Zed
+2. Go to **Zed** → **Settings** → **Language Models**
+3. Scroll to **MCP Servers**
+4. Click **Add Server**
+5. Enter:
+   - Name: `eka-care`
+   - URL: `https://mcp.eka.care/mcp`
+   - Transport: `HTTP`
+
+6. Save and restart Zed
+7. Authenticate when prompted
+
+Config location: `~/.config/zed/settings.json`
+
+  </Accordion>
+
+  <Accordion title="Zed (Windows)" icon="z">
+
+**Requirements:** Zed Editor with AI features
+
+1. Open Zed
+2. Settings → Language Models
+3. MCP Servers → Add Server
+4. Configure:
+   - Name: `eka-care`
+   - URL: `https://mcp.eka.care/mcp`
+   - Transport: `HTTP`
+
+5. Save and restart
+6. Complete authentication
+
+Config: `%APPDATA%\Zed\settings.json`
+
+<Frame>
+  <img src="/images/mcp-zed-windows.png" alt="Zed Windows Setup" />
+</Frame>
+
+  </Accordion>
+
+  <Accordion title="Windsurf (macOS)" icon="wind">
+
+**Requirements:** Windsurf IDE
+
+1. Open Windsurf
+2. Press `Cmd + ,` for Settings
+3. Navigate to **Extensions** → **MCP**
+4. Add server:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+5. Restart Windsurf
+6. Authenticate with Eka.care
+
+<Frame>
+  <img src="/images/mcp-windsurf-mac.png" alt="Windsurf macOS Setup" />
+</Frame>
+
+  </Accordion>
+
+  <Accordion title="Windsurf (Windows)" icon="wind">
+
+**Requirements:** Windsurf IDE
+
+1. Open Windsurf
+2. Press `Ctrl + ,` for Settings
+3. Extensions → MCP
+4. Add configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+5. Restart Windsurf
+6. Complete authentication
+
+<Frame>
+  <img src="/images/mcp-windsurf-windows.png" alt="Windsurf Windows Setup" />
+</Frame>
+
+  </Accordion>
+
+</AccordionGroup>
+
+You simply tell your AI assistant:
+
+<CodeGroup>
+```text Natural Language
+"Book an appointment for patient Raj Kumar with Dr. Singh tomorrow at 10 AM,
+and create a prescription for Amoxicillin 500mg, 3 times daily for 7 days"
+```
+</CodeGroup>
+
+And it's done!
+
+<Frame>
+  <img src="/images/claude-prompt.png" alt="Example Conversation" />
+  {/* Screenshot placeholder: Show actual Claude Desktop conversation doing this task */}
+</Frame>
+
+## Who Should Use This?
+
+<CardGroup cols={2}>
+  <Card title="Healthcare Providers" icon="user-doctor">
+    Doctors, clinics, and hospitals using Eka.care for patient management
+  </Card>
+  <Card title="Health Tech Companies" icon="hospital">
+    Platforms building healthcare workflows and automation
+  </Card>
+  <Card title="Medical Administrators" icon="clipboard-user">
+    Staff managing appointments, records, and prescriptions
+  </Card>
+  <Card title="Developers" icon="code">
+    Engineers building AI-powered healthcare applications
+  </Card>
+</CardGroup>
+
+## What Can You Do?
+
+<AccordionGroup>
+  <Accordion title="Patient Management">
+    - Search and retrieve patient records
+    - Add new patients
+    - Update patient information
+    - View complete medical history
+  </Accordion>
+
+  <Accordion title="Appointment Management">
+    - Check available slots
+    - Book appointments
+    - Reschedule or cancel
+    - View appointment history
+  </Accordion>
+
+  <Accordion title="Prescriptions">
+    - Generate digital prescriptions
+    - View prescription history
+    - Access medication details
+  </Accordion>
+
+  <Accordion title="Doctor & Clinic Operations">
+    - Retrieve doctor profiles
+    - Access clinic information
+    - View available services
+  </Accordion>
+</AccordionGroup>
+
+For more details on supported tools visit the [Supported Tools](/ai-tools/mcp-server/supported-tools) page.
+
+<Note>
+**Need Help?** Email us at ekaconnect@eka.care
+</Note>
diff --git a/ai-tools/mcp-server/supported-tools.mdx b/ai-tools/mcp-server/supported-tools.mdx
new file mode 100644
index 00000000..1171c2c3
--- /dev/null
+++ b/ai-tools/mcp-server/supported-tools.mdx
@@ -0,0 +1,127 @@
+---
+title: Supported Tools
+description: Complete list of available MCP tools and their capabilities
+---
+
+# Supported Tools
+
+Eka MCP provides 20+ tools across patient management, appointments, prescriptions, and clinic operations. All tools support natural language queries through your AI assistant.
+
+## Patient Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `search_patients` | Search for patients by name, mobile, email, or patient ID | `query` (string), `limit` (optional) | List of matching patients with IDs, contact info, and basic details |
+| `get_patient_details` | Retrieve complete patient information | `patient_id` (string) | Full patient profile including medical history, demographics, and appointments |
+| `add_patient` | Register a new patient | `name`, `mobile`, `email` (optional), `dob` (optional), `gender` (optional) | New patient ID and confirmation |
+| `update_patient` | Modify existing patient information | `patient_id`, fields to update | Updated patient details |
+
+## Appointment Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `get_available_slots` | Check doctor's availability | `doctor_id`, `date`, `clinic_id` (optional) | List of available time slots |
+| `book_appointment` | Schedule a new appointment | `patient_id`, `doctor_id`, `slot_time`, `clinic_id` | Appointment ID and confirmation |
+| `get_appointments` | List appointments by various filters | `patient_id` OR `doctor_id` OR `date`, `status` (optional) | List of appointments with details |
+| `reschedule_appointment` | Change appointment timing | `appointment_id`, `new_slot_time` | Updated appointment details |
+| `cancel_appointment` | Cancel scheduled appointment | `appointment_id`, `reason` (optional) | Cancellation confirmation |
+| `get_appointment_details` | Retrieve specific appointment info | `appointment_id` | Complete appointment information |
+
+## Prescription Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `create_prescription` | Generate digital prescription | `patient_id`, `medications` (array), `doctor_id`, `advice` (optional) | Prescription ID and details |
+| `get_prescriptions` | View prescription history | `patient_id`, `from_date` (optional), `to_date` (optional) | List of prescriptions |
+| `get_prescription_details` | Retrieve specific prescription | `prescription_id` | Complete prescription with medications and advice |
+| `update_prescription` | Modify existing prescription | `prescription_id`, fields to update | Updated prescription |
+
+## Doctor & Clinic Operations
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `get_doctor_profile` | Access doctor information | `doctor_id` | Doctor details, qualifications, specializations |
+| `search_doctors` | Find doctors by name or specialization | `query`, `specialization` (optional) | List of matching doctors |
+| `get_clinic_details` | Retrieve clinic information | `clinic_id` | Clinic address, services, contact info |
+| `get_doctor_clinics` | List clinics associated with doctor | `doctor_id` | Array of clinic details |
+| `get_clinic_services` | View services offered by clinic | `clinic_id` | List of available services |
+
+## Medication Database
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `search_medications` | Look up medicine information | `query` (drug name) | Medicine details, dosage forms, manufacturers |
+| `get_medication_details` | Get complete drug information | `medication_id` | Full drug profile with interactions and contraindications |
+
+## Tool Parameters
+
+
+## Usage Examples
+
+### Simple Queries
+```text
+"Search for patient Raj Kumar"
+→ Uses: search_patients
+
+"Show Dr. Singh's available slots tomorrow"
+→ Uses: get_available_slots
+
+"Get prescription history for patient 12345"
+→ Uses: get_prescriptions
+```
+
+### Complex Workflows
+```text
+"Book appointment for Raj Kumar with Dr. Singh tomorrow at 10 AM
+and create prescription for Amoxicillin"
+→ Uses: search_patients → book_appointment → create_prescription
+```
+
+## Rate Limits
+
+| Plan | Requests/Minute | Requests/Day |
+|------|-----------------|--------------|
+| Free | 10 | 1,000 |
+| Pro | 60 | 10,000 |
+| Enterprise | Unlimited | Unlimited |
+
+## Error Handling
+
+All tools return standardized error responses:
+
+```json
+{
+  "error": true,
+  "message": "Patient not found",
+  "code": "PATIENT_NOT_FOUND"
+}
+```
+
+### Common Error Codes
+
+- `PATIENT_NOT_FOUND` - Patient ID doesn't exist
+- `SLOT_UNAVAILABLE` - Appointment slot already booked
+- `INVALID_PARAMETERS` - Missing or incorrect parameters
+- `UNAUTHORIZED` - Authentication required
+- `RATE_LIMIT_EXCEEDED` - Too many requests
+
+## Need More Details?
+
+<CardGroup cols={2}>
+  <Card title="Introduction" icon="rocket" href="/ai-tools/mcp-server/introduction">
+    Get started with Eka MCP
+  </Card>
+  <Card title="Authentication" icon="lock" href="/ai-tools/mcp-server/authentication">
+    Setup authentication methods
+  </Card>
+  <Card title="Custom Client" icon="code" href="/ai-tools/mcp-server/integrations/custom-client">
+    Build your own MCP client
+  </Card>
+  <Card title="API Reference" icon="book" href="/api-reference/authorization/getting-started">
+    Complete API documentation
+  </Card>
+</CardGroup>
+
+---
+
+**Questions?** Email ekaconnect@eka.care
diff --git a/api-reference/authorization/authorization.yml b/api-reference/authorization/authorization.yml
index 930829ea..eb19f86b 100644
--- a/api-reference/authorization/authorization.yml
+++ b/api-reference/authorization/authorization.yml
@@ -220,15 +220,12 @@ components:
   schemas:
     AccountConnectLoginRequest:
       properties:
-        api_key:
-          description: Optional, API Token for business id
-          type: string
         client_id:
           type: string
         client_secret:
           type: string
-        user_token:
-          description: Optional, User token for user id
+        sharing_key:
+          description: Optional, key for accessing another workspace
           type: string
       required:
         - client_id
diff --git a/api-reference/authorization/getting-started.mdx b/api-reference/authorization/getting-started.mdx
index d14d3c52..6c8ce213 100644
--- a/api-reference/authorization/getting-started.mdx
+++ b/api-reference/authorization/getting-started.mdx
@@ -7,6 +7,110 @@ The Eka API Authentication process ensures secure access to sensitive healthcare
 - **Client Application:** A third-party application that communicates with Eka's API.
 - **Eka API Gateway:** The server-side component that authenticates and processes API requests.
 
+
+## Setting Up Your Eka Account
+This is a **one-time setup** required before you can start using Eka services.
+
+<Note>
+<a href="https://login.eka.care/workspace/sign-in/?next=https://console.eka.care&product_type=emr&signup=user_only&tab=sign-up" target="_blank">Click here to visit Eka signup page to get started</a>.
+</Note>
+
+<Note>
+Eka supports multiple sign-up options such as Google, Apple, Email Address, and Username.
+In this guide, we’ll use <strong>Email Address</strong> to walk through the setup steps.
+</Note>
+
+
+
+<Steps>
+    <Step title="Choose Sign Up method of your choice">
+        On the welcome screen, select your preferred sign-up option.
+        For this guide, we will choose <strong>Continue with Email Address</strong>.
+
+        ![Eka sign-up options screen](images/eka-sign-up-options.png)
+    </Step>
+    <Step title="Enter your email address">
+        Enter your email address and click <strong>Submit</strong>
+
+        ![Eka enter email](images/enter-email.png)
+    </Step>
+    <Step title="Verify Email Using OTP">
+        Enter the one-time password (OTP) sent to your email address and click <strong>Confirm</strong>
+
+        <img
+        src="images/verify-otp.png"
+        alt="OTP verification screen"
+        data-zoomable
+        />
+    </Step>
+    <Step title="Create Workspace">
+        You need to setup your workspace you use Eka. Enter your details and click on <strong>Next</strong>
+        <img
+        src="images/setup-workspace.png"
+        alt="OTP verification screen"
+        data-zoomable
+        />
+  </Step>
+
+  <Step title="Automatic Account Creation and Login">
+    After submitting workspace details:
+    - Your Eka account is created
+    - You are automatically logged in
+    - Your workspace is ready to use
+
+    <img
+      src="images/console-dashboard.png"
+      alt="Eka dashboard after signup"
+      data-zoomable
+    />
+  </Step>
+</Steps>
+
+## Creating API Credentials
+
+Once your Eka account is set up, you can use the **Eka Developer Console**
+to create and manage API client credentials. <a href="https://console.eka.care" target="_blank">Click here to visit Eka Developer Console</a>.
+
+
+<Steps>
+  <Step title="Open the Eka Console Dashboard">
+    Once logged in, you’ll land on the Eka Console dashboard.
+
+    From the **Quick Actions** section, click
+    <strong>Manage API Credentials (Client IDs and Secrets)</strong>.
+
+    <img
+      src="images/developer-console-homepage.png"
+      alt="Eka Console dashboard with Manage API Credentials highlighted"
+      data-zoomable
+    />
+  </Step>
+    <Step title="Create a New API Client">
+   Enter the required required details and click <strong>Create</strong>.
+        <img
+      src="images/create-api-creds.png"
+      alt="Eka Console dashboard with Manage API Credentials highlighted"
+      data-zoomable
+    />
+  </Step>
+    <Step title="Copy Client Credentials">
+    After the client is created, securely copy:
+    - <code>client_id</code>
+    - <code>client_secret</code>
+
+<img
+      src="images/save-client-secret.png"
+      alt="Eka Console dashboard with Manage API Credentials highlighted"
+      data-zoomable
+    />
+
+    <Note>
+    Store the client secret securely. It will not be shown again.
+    </Note>
+  </Step>
+</Steps>
+
+### Authenticating with Eka APIs
 <Steps>
 <Step title="Obtain an Access Token">
     Authenticate your client using the [login](/api-reference/authorization/client-login) API. This will return both an access token and a refresh token, which you will use for subsequent API requests.
@@ -20,12 +124,93 @@ The Eka API Authentication process ensures secure access to sensitive healthcare
     To ensure continuous access to the API, implement logic to manage token expiration and renewal.
 
     - If an API request returns a `401 Unauthorized` status code, it indicates that the access token has expired.
-    - Use the [refresh token](/api-reference/authorization/refresh-token) API to obtain a new access token and re-authenticate.
+    - Use the [refresh token](/api-reference/authorization/refresh-token-v2) API to obtain a new access token and re-authenticate.
 </Step>
 </Steps>
 
+## Accessing Another Workspace Using a Sharing Key
+
+Eka allows access to another workspace using a **Sharing Key**. Developers who wish to access another workspace must request a Sharing Key
+from the owner of that workspace. The Sharing Key can be generated from the Hub.
+<a href="https://hub.eka.care/account/" target="_blank">Click here to visit Hub</a>.
+
+
+<Steps>
+  <Step title="Generate a Sharing Key">
+    Click on <strong> API Token </strong> to visit page to view and manage sharing keys.
+    Click on <strong> Create </strong> and, provide the required information to create sharing key.
+
+    <img
+      src="images/hub-home.png"
+      alt="Eka Console dashboard with Manage API Credentials highlighted"
+      data-zoomable
+    />
+        <img
+      src="images/create-sharing-key.png"
+      alt="Create Sharing Key"
+      data-zoomable
+    />
+  </Step>
+
+  <Step title="Provide the Sharing Key During Authentication">
+After completing this step, continue to
+<a href="/api-reference/authorization/getting-started#authenticating-with-eka-apis">
+Authenticating with Eka APIs
+</a>
+to generate an access token (provide <strong> sharing_key </strong> in request body) and start making API requests.
+
+  </Step>
+</Steps>
+
 ---
 
+## Long Lived Access Token
+
+A Long-Lived Access Token is designed for backend-to-backend (server-to-server) communication between trusted systems.
+
+**Why use a Long-Lived Token?**
+
+- Simplifies authentication for system-to-system API calls
+- Eliminates the need to repeatedly generate short-lived access tokens
+- Ideal for long-running services and internal integrations
+
+**When should you use this?**
+
+- You are making backend-to-backend API calls
+- You do not want to manage token refresh logic
+- The integration is between trusted parties
+
+<Steps>
+  <Step title="Generate Long Lived Token">
+    <a href="https://console.eka.care" target="_blank">Click here to visit Eka Developer Console</a>
+    <p>From the **Quick Actions** section, click
+    <strong>Manage API Credentials (Client IDs and Secrets)</strong>.</p>
+    Click More options(three dot menu) and click on **Create Long Live Token**
+
+    <img
+      src="images/create-long-lived-token.png"
+      alt="Eka Console dashboard with Manage API Credentials highlighted"
+      data-zoomable
+    />
+  </Step>
+  <Step title="Copy Long Live Token">
+    After the token is created, securely copy it.
+
+    <img
+      src="images/save-long-lived-token.png"
+      alt="Save Long Live Token"
+      data-zoomable
+    />
+
+    <Note>
+    Store the token securely. It will not be shown again.
+    </Note>
+  </Step>
+  <Step title="Using Long Lived Token">
+      Include the token in the `Authorization` header of every API request to authenticate and access Eka’s services
+  </Step>
+</Steps>
+
 ## Best Practices
 
 - Safeguard your client credentials (client_id and client_secret) at all times.
diff --git a/api-reference/authorization/images/console-dashboard.png b/api-reference/authorization/images/console-dashboard.png
new file mode 100644
index 00000000..5c137706
Binary files /dev/null and b/api-reference/authorization/images/console-dashboard.png differ
diff --git a/api-reference/authorization/images/create-api-creds.png b/api-reference/authorization/images/create-api-creds.png
new file mode 100644
index 00000000..b31246c6
Binary files /dev/null and b/api-reference/authorization/images/create-api-creds.png differ
diff --git a/api-reference/authorization/images/create-long-lived-token.png b/api-reference/authorization/images/create-long-lived-token.png
new file mode 100644
index 00000000..3a13de0b
Binary files /dev/null and b/api-reference/authorization/images/create-long-lived-token.png differ
diff --git a/api-reference/authorization/images/create-sharing-key.png b/api-reference/authorization/images/create-sharing-key.png
new file mode 100644
index 00000000..4fd9ae05
Binary files /dev/null and b/api-reference/authorization/images/create-sharing-key.png differ
diff --git a/api-reference/authorization/images/dashboard.png b/api-reference/authorization/images/dashboard.png
new file mode 100644
index 00000000..f3223e2f
Binary files /dev/null and b/api-reference/authorization/images/dashboard.png differ
diff --git a/api-reference/authorization/images/developer-console-homepage.png b/api-reference/authorization/images/developer-console-homepage.png
new file mode 100644
index 00000000..c703449a
Binary files /dev/null and b/api-reference/authorization/images/developer-console-homepage.png differ
diff --git a/api-reference/authorization/images/eka-sign-up-options.png b/api-reference/authorization/images/eka-sign-up-options.png
new file mode 100644
index 00000000..49d2d3e3
Binary files /dev/null and b/api-reference/authorization/images/eka-sign-up-options.png differ
diff --git a/api-reference/authorization/images/enter-email.png b/api-reference/authorization/images/enter-email.png
new file mode 100644
index 00000000..e4c63a13
Binary files /dev/null and b/api-reference/authorization/images/enter-email.png differ
diff --git a/api-reference/authorization/images/hub-home.png b/api-reference/authorization/images/hub-home.png
new file mode 100644
index 00000000..029dc5df
Binary files /dev/null and b/api-reference/authorization/images/hub-home.png differ
diff --git a/api-reference/authorization/images/invite-flow/copy-invite-link.png b/api-reference/authorization/images/invite-flow/copy-invite-link.png
new file mode 100644
index 00000000..e90e684d
Binary files /dev/null and b/api-reference/authorization/images/invite-flow/copy-invite-link.png differ
diff --git a/api-reference/authorization/images/invite-flow/create-invite.png b/api-reference/authorization/images/invite-flow/create-invite.png
new file mode 100644
index 00000000..0eb27575
Binary files /dev/null and b/api-reference/authorization/images/invite-flow/create-invite.png differ
diff --git a/api-reference/authorization/images/invite-flow/invite-left-side-panel.png b/api-reference/authorization/images/invite-flow/invite-left-side-panel.png
new file mode 100644
index 00000000..9ab325c7
Binary files /dev/null and b/api-reference/authorization/images/invite-flow/invite-left-side-panel.png differ
diff --git a/api-reference/authorization/images/invite-flow/setup-profile.png b/api-reference/authorization/images/invite-flow/setup-profile.png
new file mode 100644
index 00000000..783998f2
Binary files /dev/null and b/api-reference/authorization/images/invite-flow/setup-profile.png differ
diff --git a/api-reference/authorization/images/save-client-secret.png b/api-reference/authorization/images/save-client-secret.png
new file mode 100644
index 00000000..0c547484
Binary files /dev/null and b/api-reference/authorization/images/save-client-secret.png differ
diff --git a/api-reference/authorization/images/save-long-lived-token.png b/api-reference/authorization/images/save-long-lived-token.png
new file mode 100644
index 00000000..db6c1c71
Binary files /dev/null and b/api-reference/authorization/images/save-long-lived-token.png differ
diff --git a/api-reference/authorization/images/setup-workspace.png b/api-reference/authorization/images/setup-workspace.png
new file mode 100644
index 00000000..8f97167d
Binary files /dev/null and b/api-reference/authorization/images/setup-workspace.png differ
diff --git a/api-reference/authorization/images/verify-otp.png b/api-reference/authorization/images/verify-otp.png
new file mode 100644
index 00000000..04c1ef0d
Binary files /dev/null and b/api-reference/authorization/images/verify-otp.png differ
diff --git a/api-reference/authorization/invite-flow.mdx b/api-reference/authorization/invite-flow.mdx
new file mode 100644
index 00000000..250524f9
--- /dev/null
+++ b/api-reference/authorization/invite-flow.mdx
@@ -0,0 +1,129 @@
+## Overview
+
+The **Invite Flow** allows workspace admins to onboard users into thier workspace using an invite link generated from the **Eka Developer Console**.
+
+## Creating an Invite Link
+
+<Steps>
+    <Step title="Open the Eka Developer Console">
+        <a href="https://console.eka.care" target="_blank">Click here to visit Eka Developer Console</a>.
+        <Note>
+        You must be an Admin to create invites.
+        </Note>
+    </Step>
+
+    <Step title="Navigate to Invites">
+        From the left sidebar, click on <strong>Invites</strong>.
+
+        <img
+        src="images/invite-flow/invite-left-side-panel.png"
+        alt="Developer Console with Invites highlighted"
+        data-zoomable
+        />
+    </Step>
+
+    <Step title="Create Invite Link">
+        Click on <strong>Create Invite Link</strong>. Once created, an invite link is generated.
+
+        <img
+        src="images/invite-flow/create-invite.png"
+        alt="Developer Console with Invites highlighted"
+        data-zoomable
+        />
+
+        <img
+        src="images/invite-flow/copy-invite-link.png"
+        alt="Developer Console with Invites highlighted"
+        data-zoomable
+        />
+
+        <Note>
+            Copy the link before leaving the page as it will not be shown again.
+        </Note>
+
+        <Note>
+            Invite links grant access to a specific product and workspace.
+            Do <strong>not</strong> share an invite link with anyone other than the intended recipient.
+        </Note>
+    </Step>
+</Steps>
+
+---
+
+## Consuming an Invite Link
+
+Once generated, the invite link can be shared with the user via email, chat, or any external channel.
+
+Once an invite link is created and shared, the invited user can join the workspace by opening the link.
+The system ensures the user is authenticated before granting workspace access.
+
+---
+
+## Invite Authentication Flow
+
+<Steps>
+    <Step title="Open the Invite Link">
+        The user clicks the invite link shared with them and the user is redirected to the authentication flow.
+    </Step>
+
+    <Step title="Choose Sign-Up or Login Method">
+        On the authentication screen, the user can choose their preferred method to continue.
+
+        Eka supports multiple options such as:
+        - Google
+        - Apple
+        - Email Address
+        - Username
+
+        In this guide, we’ll walk through the flow using <strong>Email Address</strong>.
+
+        ![Eka sign-up options screen](images/eka-sign-up-options.png)
+    </Step>
+
+    <Step title="Enter Email Address">
+        The user enters their email address and clicks <strong>Submit</strong>.
+
+        ![Eka enter email](images/enter-email.png)
+    </Step>
+
+
+    <Step title="Verify Email Using OTP">
+        A one-time password (OTP) is sent to the user’s email address.
+
+        The user enters the OTP and clicks <strong>Confirm</strong> to continue authentication.
+
+        <img
+            src="images/verify-otp.png"
+            alt="OTP verification screen"
+            data-zoomable
+        />
+    </Step>
+
+    <Step title="Set Up Profile Details (New Users Only)">
+        Users are prompted to set up their profile.
+
+        <img
+            src="images/invite-flow/setup-profile.png"
+            alt="OTP verification screen"
+            data-zoomable
+        />
+
+        After entering the profile details, click <strong>Next</strong> to continue.
+
+    </Step>
+
+    <Step title="Invite Validation and Consumption">
+        After successful authentication and profile setup, invite is consumed and workspace access is granted to the user.
+    </Step>
+
+    <Step title="Redirect to Product">
+        Once the invite is successfully consumed, the user is redirected automatically.
+
+        The redirection is based on the invite configuration and includes:
+        - The <strong>target product</strong> (for example, EMR)
+        - The <strong>specific workspace</strong> for which the invite was created
+
+        This ensures the user lands directly in the correct product context
+        without requiring any additional product selection.
+    </Step>
+</Steps>
\ No newline at end of file
diff --git a/api-reference/authorization/refresh-token-v2.mdx b/api-reference/authorization/refresh-token-v2.mdx
index 14ac26b8..3e3e0bd8 100644
--- a/api-reference/authorization/refresh-token-v2.mdx
+++ b/api-reference/authorization/refresh-token-v2.mdx
@@ -1,4 +1,4 @@
 ---
 openapi: post /connect-auth/v1/account/refresh-token
-title: Connect Refresh V2
+title: Connect Refresh
 ---
diff --git a/api-reference/authorization/refresh-token.mdx b/api-reference/authorization/refresh-token.mdx
deleted file mode 100644
index 41a0b5bc..00000000
--- a/api-reference/authorization/refresh-token.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
----
-openapi: post /connect-auth/v1/account/refresh
-title: Connect Refresh
----
diff --git a/api-reference/authorization/sdks/go-sdk.mdx b/api-reference/authorization/sdks/go-sdk.mdx
new file mode 100644
index 00000000..4796eae6
--- /dev/null
+++ b/api-reference/authorization/sdks/go-sdk.mdx
@@ -0,0 +1,111 @@
+---
+title: 'Go SDK'
+description: 'A GO SDK for interacting with Eka Care APIs.'
+---
+
+## Prerequisites
+
+- Go 1.24+ (matches the SDK’s go.mod)
+- Eka Care developer account and credentials (client_id and client_secret)
+
+## Installation
+
+```bash
+go get github.com/eka-care/eka-sdk-go
+```
+
+Install a specific version (recommended for reproducible builds):
+
+```bash
+go get github.com/eka-care/eka-sdk-go@latest
+# or pin to a specific release
+go get github.com/eka-care/eka-sdk-go@vX.Y.Z
+```
+
+## Authentication and Setup
+
+The SDK supports configuration via environment variables (recommended) or explicit options in code.
+
+### Recommended: Environment variables
+
+Set the following variables in your environment or a .env file:
+
+```bash
+# Required
+export EKA_ENVIRONMENT=production   # or development
+export EKA_CLIENT_ID=your-client-id
+export EKA_CLIENT_SECRET=your-client-secret
+```
+
+Then initialize the client from environment variables:
+
+```go
+client := ekasdk.NewFromEnv()
+```
+
+### Alternative: Explicit configuration (not recommended for production)
+
+```go
+client := ekasdk.New(
+	ekasdk.WithEnvironment(ekasdk.EnvironmentProduction),
+	ekasdk.WithClientID("your-client-id"),
+	ekasdk.WithClientSecret("your-client-secret"),
+)
+```
+
+## Quickstart
+
+Authenticate and call an ABDM API (login init via PHR address):
+
+```go
+package main
+
+import (
+	"context"
+	"log"
+
+	ekasdk "github.com/eka-care/eka-sdk-go"
+	"github.com/eka-care/eka-sdk-go/internal/interfaces"
+	"github.com/eka-care/eka-sdk-go/services/abdm/abha/login"
+)
+
+func auth() {
+	ctx := context.Background()
+
+	// Create SDK client from environment variables
+	client := ekasdk.NewFromEnv()
+
+	// Authenticate with Eka platform
+	if err := client.Login(ctx); err != nil {
+		log.Fatalf("Authentication failed: %v", err)
+	}
+}
+```
+
+## Configuration reference
+
+- EKA_CLIENT_ID: Client ID from the developer portal (required)
+- EKA_CLIENT_SECRET: Client secret from the developer portal (required)
+- EKA_ENVIRONMENT: production or development (required)
+
+Configuration priority (highest to lowest):
+- Environment variables
+- Explicit options via WithXxx() functions
+- Built-in defaults
+
+## Troubleshooting
+
+Typical auth/config errors when calling `client.Login(ctx)`:
+
+```text
+"client ID is required for authentication. Set EKA_CLIENT_ID environment variable or use WithClientID() option"
+"client secret is required for authentication. Set EKA_CLIENT_SECRET environment variable or use WithClientSecret() option"
+"failed to authenticate with provided credentials: invalid client credentials"
+```
+
+## Examples and resources
+
+- GitHub repository: https://github.com/eka-care/eka-sdk-go
+- Examples: https://github.com/eka-care/eka-sdk-go/tree/main/examples/quickstart
+- Issues & support: https://github.com/eka-care/eka-sdk-go/issues
+
diff --git a/api-reference/authorization/sdks/java-sdk.mdx b/api-reference/authorization/sdks/java-sdk.mdx
new file mode 100644
index 00000000..dd76089e
--- /dev/null
+++ b/api-reference/authorization/sdks/java-sdk.mdx
@@ -0,0 +1,130 @@
+---
+title: 'Java SDK'
+description: 'A Java Spring Boot SDK for interacting with Eka Care APIs.'
+---
+
+# Overview
+
+A Java Spring Boot SDK for processing medical documents through the Eka Care API. This SDK supports document submission, result polling, and FHIR data extraction.
+
+## Prerequisites
+
+- **JDK 17+** (verify with `java -version`)
+- **Maven** (verify with `mvn -version`)
+- **IDE**: IntelliJ IDEA, Eclipse, or VS Code with Java extensions
+- **Eka Care API Credentials**: Valid client ID and secret
+
+---
+
+## Project Structure
+
+```
+ekacare-sdk/
+├── src/main/java/com/example/ekacare/
+│   ├── sdk/EkaCareSDK.java
+│   ├── service/EkaCareService.java
+│   └── controller/DocumentController.java
+├── src/main/resources/application.properties
+└── pom.xml
+```
+
+---
+
+## Setup Instructions
+
+### Step 1: Create Spring Boot Project
+
+**Via Spring Initializr:**
+- Visit [start.spring.io](https://start.spring.io)
+- Select Maven, Java 17, Spring Boot 3.2.0
+- Add "Spring Web" dependency
+- Generate and extract
+
+**Via IntelliJ IDEA:**
+File → New → Project → Spring Initializr → Configure with Java 17 and Spring Boot 3.2.0
+
+### Step 2: Add SDK Files
+
+Copy files from the repository to respective directories:
+- `EkaCareSDK.java` → `src/main/java/com/example/ekacare/sdk/`
+- `EkaCareService.java` → `src/main/java/com/example/ekacare/service/`
+- `application.properties` → `src/main/resources/`
+- `pom.xml` → project root
+
+### Step 3: Configure Credentials
+
+Update `application.properties`:
+
+```properties
+ekacare.client.id=YOUR_CLIENT_ID_HERE
+ekacare.client.secret=YOUR_CLIENT_SECRET_HERE
+```
+
+### Step 4: Build
+
+```bash
+mvn clean install
+```
+
+---
+
+## Quick Start
+
+### Direct SDK Usage
+
+```java
+try (EkaCareSDK sdk = new EkaCareSDK("CLIENT_ID", "CLIENT_SECRET")) {
+    Map<String, Object> result = sdk.processAndWait(
+        "/path/to/document.jpg",
+        "smart",
+        10,  // poll interval (seconds)
+        300  // timeout (seconds)
+    );
+    Map<String, Object> data = (Map<String, Object>) result.get("data");
+    System.out.println("FHIR: " + data.get("fhir"));
+}
+```
+
+### Spring Boot Service
+
+```java
+@Component
+public class MyDocumentProcessor {
+    @Autowired
+    private EkaCareService ekaCareService;
+
+    public void process() throws InterruptedException {
+        Map<String, Object> result = ekaCareService
+            .processDocumentAndWait("/path/to/document.jpg", "smart");
+        System.out.println("Result: " + result);
+    }
+}
+```
+
+---
+
+## Example cURL Requests
+
+```bash
+# Submit document asynchronously
+curl -X POST http://localhost:8080/api/documents/process?task=smart \
+  -F "file=@/path/to/document.jpg"
+
+# Get processing result
+curl http://localhost:8080/api/documents/abc123/result
+
+# Synchronous processing (waits for completion)
+curl -X POST http://localhost:8080/api/documents/process-sync?task=smart \
+  -F "file=@/path/to/document.jpg"
+```
+
+---
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| File Not Found | Use absolute paths or verify relative path correctness |
+| Authorization (401) | Validate credentials in properties file |
+| Maven Build Fails | Run `mvn clean install -U` |
+| Port 8080 In Use | Change in `application.properties`: `server.port=8081` |
diff --git a/api-reference/authorization/sdks/python-sdk.mdx b/api-reference/authorization/sdks/python-sdk.mdx
new file mode 100644
index 00000000..f465ab11
--- /dev/null
+++ b/api-reference/authorization/sdks/python-sdk.mdx
@@ -0,0 +1,60 @@
+---
+title: 'Python SDK'
+description: 'A Python SDK for interacting with Eka Care APIs.'
+---
+
+You can install it as a python package as below
+
+```bash
+pip install ekacare
+```
+
+---
+## Quick Start
+### Authentication
+
+```python
+from ekacare import EkaCareClient
+
+# Initialize with client credentials
+client = EkaCareClient(
+    client_id="your_client_id",
+    client_secret="your_client_secret"
+)
+
+# Or initialize with an existing access token
+client = EkaCareClient(
+    client_id="your_client_id",
+    client_secret="your_client_secret",
+    access_token="your_access_token"
+)
+
+# Manually get an access token
+token_response = client.auth.login()
+access_token = token_response["access_token"]
+```
+---
+
+## Error Handling
+
+The SDK uses custom exceptions to handle errors:
+
+```python
+from ekacare import EkaCareClient, EkaCareAPIError, EkaCareAuthError
+
+client = EkaCareClient(
+    client_id="your_client_id",
+    client_secret="your_client_secret"
+)
+
+try:
+    documents = client.records.list_documents()
+except EkaCareAuthError as e:
+    print(f"Authentication error: {e}")
+except EkaCareAPIError as e:
+    print(f"API error: {e}")
+```
+
+## License
+
+This SDK is distributed under the MIT License.
\ No newline at end of file
diff --git a/api-reference/doc-tool/appointment-api/change-status.mdx b/api-reference/doc-tool/appointment-api/change-status.mdx
new file mode 100644
index 00000000..cf079d06
--- /dev/null
+++ b/api-reference/doc-tool/appointment-api/change-status.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /dr/v1/appointment/{appointment_id}/change-status
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/business-api/get-business-info.mdx b/api-reference/doc-tool/business-api/get-business-info.mdx
new file mode 100644
index 00000000..c79296cd
--- /dev/null
+++ b/api-reference/doc-tool/business-api/get-business-info.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /cdr/v1/get_business_info/
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/doc-tool.yaml b/api-reference/doc-tool/doc-tool.yaml
index 649d27be..4eea597c 100644
--- a/api-reference/doc-tool/doc-tool.yaml
+++ b/api-reference/doc-tool/doc-tool.yaml
@@ -1038,6 +1038,661 @@ paths:
                   code: "SERVER_ERROR"
                   message: "An unexpected error occurred on the server"
       deprecated: false
+  /cdr/v1/get_business_info/:
+    get:
+      tags:
+        - Doctor and clinic API
+      summary: Get Workspace Information
+      description: >-
+        
+        ### Overview
+        
+        The Get Workspace Information API retrieves basic information about a business including the business ID and business name. This API is designed to provide essential business details for authenticated requests.
+        
+        ### Endpoint
+        
+        **URL:** `{{HOST}}/cdr/v1/get_business_info`
+        
+        
+        **Method:** GET
+        
+        ### Request Parameters
+        
+        This endpoint does not require any parameters. The auth header contains business-id information which will be used to fetch the details.
+        
+        ### Response Parameters
+        
+        | Parameter | Type | Description |
+        
+        | --- | --- | --- |
+        
+        | status | string | Status of the response (success) |
+        
+        | bid | string | Unique identifier of the business |
+        
+        | business_name | string | Name of the business |
+
+      operationId: GetBusinessInformation
+      parameters:
+        - name: auth
+          in: header
+          description: >-
+            The auth token of the business. It is used to authenticate the client. This should be fetched from auth api.
+          required: true
+          style: simple
+          schema:
+            type: string
+            example: >-
+              eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJiX2lkIjoiMTIzNDU2IiwiY2xpZW50X2lkIjoiNzg5MCIsImV4dHJhX2ZpZWxkIjoiZXh0cmFfZmllbGRfZGF0YSJ9.q9KzBI6f4l3OyM_EkB5Quq0l9EEMFh5JS-fx3F_PHUM
+      responses:
+        '200':
+          description: OK
+          headers: { }
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  bid:
+                    type: string
+                    example: "789235904342534"
+                  business_name:
+                    type: string
+                    example: "Example business"
+              example:
+                status: "success"
+                bid: "789235904342534"
+                business_name: "Example business"
+        '401':
+          description: Unauthorized
+          headers: { }
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  message:
+                    type: string
+                    example: "Unauthorized"
+              example:
+                message: "Unauthorized"
+      deprecated: false
+  /cdr/v1/doctor/:
+    post:
+      tags:
+        - Doctor and clinic API
+      summary: Create Doctor Profile
+      description: >-
+
+        ### Overview
+
+        Create a new doctor profile for your business. This endpoint lets you register a doctor with their personal details, specializations, qualifications, and profile image.
+
+        
+        **Endpoint:** `{{HOST}}/cdr/v1/doctor`
+
+
+        **Method:** `POST`
+
+        ### Request Parameters
+
+
+        | Parameter | Type | Description | Required |
+
+        | --- | --- | --- | --- |
+
+        | firstname | string | Doctor's first name | Yes |
+
+        | lastname | string | Doctor's last name | Yes |
+
+        | gender | string | Doctor's gender (M/F/O) | Yes |
+
+        | dob | string | Doctor's date of birth (YYYY-MM-DD) | No |
+
+        | email | string | Doctor's email address | No |
+
+        | mobile | string | Doctor's mobile number (10 digits) | No |
+
+        | specialisations | array | List of doctor's specializations | No |
+
+        | qualifications | array | List of doctor's qualifications/degrees | No |
+
+        | about | string | Brief description about the doctor | No |
+
+        | profile_image_url | string | URL of the doctor's profile image | No |
+
+        | clinic_ids | array | List of Eka clinic IDs to assign to this doctor | No |
+
+        | partner_clinic_ids | array | List of partner clinic IDs to assign to this doctor | No |
+
+        | partner_id | string | Unique identifier provided by partner | No |
+
+
+        ### Response Parameters
+
+
+        | Parameter | Type   | Description                                   |
+
+        | --------- | ------ | --------------------------------------------- |
+
+        | status    | string | Status of the response (e.g., "success")      |
+
+        | ekaid     | string | Unique identifier for the created doctor      |
+
+
+
+
+        > **Note:**
+        The `specialisations` and `qualifications` fields accept predefined values, if wanted these can be left empty as they are optional fields. For the complete and up-to-date list, see this Google Sheet:  
+        [View Specializations & Qualifications List](https://docs.google.com/spreadsheets/d/1qRf_R-WHF1F9g3XYcJWHp5IqIWzJxXCaKh22wCCm4j4/edit?usp=sharing)
+       
+
+      operationId: CreateDoctorProfile
+      parameters:
+        - name: auth
+          in: header
+          description: >-
+            The auth token of the business. It is used to authenticate the client. This should be fetched from auth api.
+          required: true
+          style: simple
+          schema:
+            type: string
+            example: >-
+              eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJiX2lkIjoiMTIzNDU2IiwiY2xpZW50X2lkIjoiNzg5MCIsImV4dHJhX2ZpZWxkIjoiZXh0cmFfZmllbGRfZGF0YSJ9.q9KzBI6f4l3OyM_EkB5Quq0l9EEMFh5JS-fx3F_PHUM
+      requestBody:
+        description: 'Request body for creating a doctor profile'
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - firstname
+                - lastname
+                - gender
+              properties:
+                firstname:
+                  type: string
+                  description: Doctor's first name
+                  example: "Rajesh"
+                lastname:
+                  type: string
+                  description: Doctor's last name
+                  example: "Sharma"
+                mobile:
+                  type: string
+                  description: Doctor's mobile number (10 digits)
+                  example: "0000011111"
+                dob:
+                  type: string
+                  description: Doctor's date of birth (YYYY-MM-DD) default to 1990-01-01, if not provided.
+                  example: "1999-01-01"
+                email:
+                  type: string
+                  format: email
+                  description: Doctor's email address
+                  example: "dr.rajesh@example.com"
+                gender:
+                  type: string
+                  enum: ["M", "F", "O"]
+                  description: "Doctor's gender (M - Male, F - Female, O - Other)"
+                  example: "M"
+                specialisations:
+                  type: array
+                  items:
+                    type: string
+                  description: List of doctor's specializations. Refer to the Available Specializations section for valid values.
+                  example: ["Cardiology", "Internal Medicine"]
+                qualifications:
+                  type: array
+                  items:
+                    type: string
+                  description: List of doctor's qualifications/degrees. Refer to the Available Qualifications section for valid values.
+                  example: ["MBBS", "MD", "DM"]
+                about:
+                  type: string
+                  description: Brief description about the doctor
+                  example: "Dr. Rajesh Sharma is a renowned cardiologist with over 15 years of experience in interventional cardiology."
+                profile_image_url:
+                  type: string
+                  format: uri
+                  description: URL of the doctor's profile image
+                  example: "https://example.com/images/dr-rajesh.jpg"
+                clinic_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: "List of Eka clinic IDs to assign to this doctor"
+                  example: ["c-ab2c-34f2d-2gwd-2g2g"]
+                partner_clinic_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: "List of partner clinic IDs to assign to this doctor"
+                  example: ["Part_clinic_1"]
+                partner_id:
+                  type: string
+                  description: "Unique identifier provided by partner"
+                  example: "Part_doc"
+            example:
+              firstname: "Rajesh"
+              lastname: "Sharma"
+              mobile: "0000011111"
+              dob: "1999-01-01"
+              email: "dr.rajesh@example.com"
+              gender: "M"
+              specialisations: ["Cardiology", "Internal Medicine"]
+              qualifications: ["MBBS", "MD", "DM"]
+              about: "Dr. Rajesh Sharma is a renowned cardiologist with over 15 years of experience in interventional cardiology."
+              profile_image_url: "https://example.com/images/dr-rajesh.jpg"
+              clinic_ids: ["c-ab2c-34f2d-2gwd-2g2g"]
+              partner_clinic_ids: ["Part_clinic_1"]
+              partner_id : "Part_doc"
+      responses:
+        '201':
+          description: Created - Doctor successfully created
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  ekaid:
+                    type: string
+                    description: Unique identifier for the created doctor
+                    example: "do1769174683513"
+        '400':
+          description: Bad Request - Invalid or missing required parameters
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  '<field>':
+                    type: array
+                    items:
+                      type: string
+                      example: "This field is required."
+                  message:
+                    type: array
+                    items:
+                      type: string
+                      example: "Only one of partner_clinic_ids or clinic_ids should be provided, not both."
+  /cdr/v1/clinic/:
+    post:
+      tags:
+        - Doctor and clinic API
+      summary: Create Clinic
+      description: >-
+        ### Overview
+
+        The Create Clinic API allows you to register a new clinic for your business, including its name, address, pincode, contact number, city, state, and assigned doctors.
+
+
+        **Endpoint:** `{{HOST}}/cdr/v1/clinic`
+
+
+        **Method:** POST
+
+        ### Request Parameters
+
+
+        | Parameter   | Type    | Description                                   | Required |
+
+        | ----------- | ------- | --------------------------------------------- | -------- |
+
+        | name        | string  | Name of the clinic                            | Yes      |
+
+        | address     | string  | Address of the clinic                         | Yes      |
+
+        | partner_id  | string  | Unique id of the clinic in partner's system.  | No      |
+
+        | pincode     | string  | Pincode of the clinic                         | No       |
+
+        | contact     | string  | Contact number                                | No       |
+
+        | doctor_ids  | array   | List of doctor Eka IDs to assign to this clinic| No      |
+
+        | partner_doctor_ids  | array   | List of partner doctor IDs to assign to this clinic| No      |
+
+        | city        | string  | City name                                     | No       |
+
+        | state       | string  | State name                                    | No       |
+
+        ### Response Parameters
+
+
+        | Parameter   | Type    | Description                                   |
+
+        | ----------- | ------- | --------------------------------------------- |
+
+        | status      | string  | Status of the response (e.g., "success")      |
+
+        | ekaid       | string  | Unique identifier for the created clinic      |
+
+
+      operationId: CreateClinic
+      parameters:
+        - name: auth
+          in: header
+          description: >-
+            The auth token of the business. It is used to authenticate the client. This should be fetched from auth api.
+          required: true
+          style: simple
+          schema:
+            type: string
+            example: >-
+              eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJiX2lkIjoiMTIzNDU2IiwiY2xpZW50X2lkIjoiNzg5MCIsImV4dHJhX2ZpZWxkIjoiZXh0cmFfZmllbGRfZGF0YSJ9.q9KzBI6f4l3OyM_EkB5Quq0l9EEMFh5JS-fx3F_PHUM
+      requestBody:
+        description: 'Request body for creating a clinic'
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - name
+                - address
+              properties:
+                name:
+                  type: string
+                  description: Name of the clinic
+                  example: "Sunrise Clinic"
+                address:
+                  type: string
+                  description: Address of the clinic
+                  example: "123 Main Street, Block A"
+                partner_id:
+                  type: string
+                  description: Unique identifier of the clinic in the partner’s system
+                  example: "Clinic_321_Indore"
+                pincode:
+                  type: string
+                  description: Pincode of the clinic
+                  example: "560001"
+                contact:
+                  type: string
+                  pattern: "^\\d{10,11}$"
+                  description: Contact number (10 or 11 digits)
+                  example: "9876543210"
+                doctor_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of doctor Eka IDs to assign to this clinic
+                  example: ["171266028552522", "171266028552523"]
+                partner_doctor_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of partner doctor IDs to assign to this clinic
+                  example: ["Part_Doc_1","Part_Doc_2"]
+                city:
+                  type: string
+                  description: City name
+                  example: "Bangalore"
+                state:
+                  type: string
+                  description: State name
+                  example: "Karnataka"
+            example:
+              name: "Sunrise Clinic"
+              address: "123 Main Street, Block A"
+              partner_id: "Clinic_321_Indore"
+              pincode: "560001"
+              contact: "9876543210"
+              doctor_ids: ["171266028552522", "171266028552523"]
+              partner_doctor_ids: ["Part_Doc_1","Part_Doc_2"]
+              city: "Bangalore"
+              state: "Karnataka"
+      responses:
+        '201':
+          description: Created - Clinic successfully created
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  ekaid:
+                    type: string
+                    description: Unique identifier for the created doctor
+                    example: "do1769174683513"
+        '400':
+          description: Bad Request - Invalid or missing required parameters
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  '<field>':
+                    type: array
+                    items:
+                      type: string
+                      example: "This field is required."
+                  message:
+                    type: array
+                    items:
+                      type: string
+                      example: "Only one of doctor_ids or partner_doctor_ids should be provided, not both."
+  /cdr/v1/ekauser/:
+    post:
+      tags:
+        - HIP Users API
+      summary: Create Eka User
+      description: >-
+
+        ### Overview
+
+        Create a new Eka User (HIP User) for your business. This endpoint lets you register a user with their personal details and assign them to specific doctors and clinics.
+
+        
+        **Endpoint:** `{{HOST}}/cdr/v1/ekauser`
+
+
+        **Method:** `POST`
+
+        ### Request Parameters
+
+
+        | Parameter    | Type    | Description                                           | Required |
+
+        |--------------|---------|-------------------------------------------------------|----------|
+        
+        | firstname    | string  | User's first name                                     | Yes      |
+        
+        | lastname     | string  | User's last name                                      | Yes      |
+        
+        | mobile       | string  | User's mobile number (10 digits)                      | Yes*     |
+        
+        | email        | string  | User's email address                                  | Yes*     |
+
+        | auth_userid  | string  | auth_userid is used for the SSO authentication        | Yes*     |
+        
+        | gender       | string  | User's gender (M/F/O)                                 | Yes      |
+        
+        | dob          | string  | User's date of birth (YYYY-MM-DD)                     | Yes      |
+        
+        | is_admin     | boolean | Whether the user is an admin                          | No       |
+        
+        | seat_type    | string  | Seat type (b - basic, p - premium). Default: b        | No       |
+        
+        | persona      | string  | User persona (S - Staff, D - Doctor). Default: D      | No       |
+        
+        | doctor_ids   | array   | List of doctor Eka IDs to assign to this user         | No       |
+        
+        | partner_doctor_ids   | array   | List of partner doctor IDs to assign to this user         | No       |
+
+        | clinic_ids   | array   | List of clinic Eka IDs to assign to this user         | No       |
+
+        | partner_clinic_ids   | array   | List of partner clinic IDs to assign to this user         | No       |
+
+        > **Note:** Either `mobile` or `email` or `auth_userid` is required. At least one must be provided.
+
+
+
+        ### Response Parameters
+
+
+        | Parameter | Type   | Description                                   |
+
+        | --------- | ------ | --------------------------------------------- |
+
+        | status    | string | Status of the response (e.g., "success")      |
+
+        | ekaid     | string | Unique identifier for the created Eka User    |
+
+
+      operationId: CreateEkaUser
+      parameters:
+        - name: auth
+          in: header
+          description: >-
+            The auth token of the business. It is used to authenticate the client. This should be fetched from auth api.
+          required: true
+          style: simple
+          schema:
+            type: string
+            example: >-
+              eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJiX2lkIjoiMTIzNDU2IiwiY2xpZW50X2lkIjoiNzg5MCIsImV4dHJhX2ZpZWxkIjoiZXh0cmFfZmllbGRfZGF0YSJ9.q9KzBI6f4l3OyM_EkB5Quq0l9EEMFh5JS-fx3F_PHUM
+      requestBody:
+        description: 'Request body for creating an Eka User'
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - firstname
+                - lastname
+                - gender
+                - dob
+              properties:
+                firstname:
+                  type: string
+                  description: User's first name
+                  example: "Amit"
+                lastname:
+                  type: string
+                  description: User's last name
+                  example: "Kumar"
+                mobile:
+                  type: string
+                  description: User's mobile number (10 digits). Either mobile or email or auth_userid is required.
+                  example: "0000011111"
+                email:
+                  type: string
+                  format: email
+                  description: User's email address. Either mobile or email or auth_userid is required.
+                  example: "amit.kumar@example.com"
+                auth_userid:
+                  type: string
+                  description: auth_userid used for SSO authentication. Either mobile or email or auth_userid is required
+                  example: "Prateek_@_123"
+                gender:
+                  type: string
+                  enum: ["M", "F", "O"]
+                  description: "User's gender (M - Male, F - Female, O - Other)"
+                  example: "M"
+                dob:
+                  type: string
+                  format: date
+                  description: User's date of birth in YYYY-MM-DD format
+                  example: "1990-05-15"
+                is_admin:
+                  type: boolean
+                  description: Whether the user has admin privileges
+                  default: false
+                  example: false
+                seat_type:
+                  type: string
+                  enum: ["b", "p"]
+                  description: "Seat type (b - basic, p - premium). Default: b"
+                  example: "b"
+                persona:
+                  type: string
+                  enum: ["S", "D"]
+                  description: "User persona (S - Staff, D - Doctor). Default: D"
+                  example: "D"
+                doctor_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of doctor Eka IDs to assign to this user
+                  example: ["171266028552522", "171266028552523"]
+                partner_doctor_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of partner doctor IDs to assign to this user
+                  example: ["Part_doc_1", "Part_doc_2"]
+                clinic_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of clinic Eka IDs to assign to this user
+                  example: ["c-314086a34253rd", "c-415197b45364se"]
+                partner_clinic_ids:
+                  type: array
+                  items:
+                    type: string
+                  description: List of partner clinic IDs to assign to this user
+                  example: ["Part_clinic_1", "Part_clinic_2"]
+            example:
+              firstname: "Amit"
+              lastname: "Kumar"
+              mobile: "9876543210"
+              email: "amit.kumar@example.com"
+              auth_userid: "Prateek_@_123"
+              gender: "M"
+              dob: "1990-05-15"
+              is_admin: false
+              seat_type: "b"
+              persona: "D"
+              doctor_ids: ["171266028552522", "171266028552523"]
+              clinic_ids: ["c-314086a34253rd", "c-415197b45364se"]
+              partner_doctor_ids: ["Part_doc_1", "Part_doc_2"]
+              partner_clinic_ids: ["Part_clinic_1", "Part_clinic_2"]
+      responses:
+        '201':
+          description: Created - Eka User successfully created
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  ekaid:
+                    type: string
+                    description: Unique identifier for the created Eka User
+                    example: "176917697553584"
+        '400':
+          description: Bad Request - Invalid or missing required parameters
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  '<field>':
+                    type: array
+                    items:
+                      type: string
+                      example: "This field is required."
+                  message:
+                    type: array
+                    items:
+                      type: string
+                      example: "Only one of doctor_ids or partner_doctor_ids should be provided, not both."
+      deprecated: false
   /dr/v1/business/clinic/{clinic_id}:
     get:
       tags:
@@ -2077,6 +2732,9 @@ paths:
               properties:
                 partner_appointment_id:
                   type: string
+                token:
+                  type: integer
+                  description: 'A unique number given to each patient to indicate their position in the queue.'
                 appointment_details:
                   type: object
                   properties:
@@ -2238,6 +2896,7 @@ paths:
               partner_clinic_id: "642783"
               partner_doctor_id: "8423994"
               partner_patient_id: "6742984"
+              token: 2
               appointment_details:
                 start_time: 1730189586
                 end_time: 1730189586
@@ -2409,14 +3068,38 @@ paths:
               - **50** → when filtering by (`doctor_id`, `start_date`, `end_date`) OR (`clinic_id`, `start_date`, `end_date`) OR (`doctor_id`, `clinic_id`, `start_date`, `end_date`).  
               - **30** → when filtering only by (`start_date`, `end_date`).  
 
-        ### Appointment Status Codes
-          - BK    : Booked  
-          - OG    : Ongoing  
-          - CM    : Completed with Prescription  
-          - CMNP  : Completed without a Prescription  
-          - CN    : Cancelled  
-          - CND   : Cancelled by Doctor  
-          - CNS   : Cancelled by Staff
+        ### Appointment_statuses:
+
+              Booked / Queue States:
+                - BK (Booked) : Appointment created/confirmed.
+                - CK (Checked-in) : Booked appointment added to the Queue (Checked-in).
+                - RV (Reserved) : Appointment marked as Reserved, when patient said they will come for the appointment on the follow-up appointment message.
+                - IN (Initiated) : Appointment marked as Initiated, when patient received follow-up appointment message.
+                - PA  (Parked) : Appointment moved to Parked state.
+
+              Ongoing States:
+                - OG (Ongoing): Consultation is in progress.
+
+              Completion Statuses:
+                - CM (Completed): Appointment completed with a prescription created.
+                - CMNP (Completed No Prescription) : Appointment marked Exit from Queue / Completed without a prescription.
+                - AB (Aborted) : Appointment was started (Start Visit) but not completed. Automatically marked AB at 12:00 AM next day.
+                - NS (No Show) : Appointment was added to Queue but not started/completed. Automatically marked NS at 12:00 AM next day.
+                - NSD (No Show Doctor) : No-show tagged specifically from a doctor’s action (if implemented).
+                - NSS (No Show Staff) : No-show tagged specifically from a staff action (if implemented).
+
+              Cancellation Statuses:
+                - CN (Cancelled) : Appointment cancelled via API.
+                - CND (Cancelled Doctor) : Cancelled from the doctor’s account in the tool.
+                - CNS (Cancelled Staff) : Cancelled from the staff’s account in the tool.
+                - PC (Provisional Cancelled) : Appointment marked as provisional cancellation, when patient said they will not come for the appointment on the follow-up appointment message.
+                - PNR (Payment Not Received) : Appointment marked as PNR, when patient tried paying for a pre-paid appointment but the payment failed.
+
+              Reschedule Statuses:
+                - RE : Rescheduled via API.
+                - RES : Rescheduled from staff account.
+                - RED : Rescheduled from doctor account.
+
       operationId: GetBusinessAppointments
       parameters:
         - name: Authorization
@@ -3091,14 +3774,39 @@ paths:
         appointment status, and related services.
         
         
-        Appointment_statuses:
-          - BK    : Booked
-          - OG    : Ongoing
-          - CM	  : Completed with Prescription
-          - CMNP  : Completed without a Prescription
-          - CN    : Cancelled
-          - CND   : Cancelled by Doctor
-          - CNS   : Cancelled by Staff
+        
+        ### Appointment_statuses:
+
+              Booked / Queue States:
+                - BK (Booked) : Appointment created/confirmed.
+                - CK (Checked-in) : Booked appointment added to the Queue (Checked-in).
+                - RV (Reserved) : Appointment marked as Reserved, when patient said they will come for the appointment on the follow-up appointment message.
+                - IN (Initiated) : Appointment marked as Initiated, when patient received follow-up appointment message.
+                - PA  (Parked) : Appointment moved to Parked state.
+
+              Ongoing States:
+                - OG (Ongoing): Consultation is in progress.
+
+              Completion Statuses:
+                - CM (Completed): Appointment completed with a prescription created.
+                - CMNP (Completed No Prescription) : Appointment marked Exit from Queue / Completed without a prescription.
+                - AB (Aborted) : Appointment was started (Start Visit) but not completed. Automatically marked AB at 12:00 AM next day.
+                - NS (No Show) : Appointment was added to Queue but not started/completed. Automatically marked NS at 12:00 AM next day.
+                - NSD (No Show Doctor) : No-show tagged specifically from a doctor’s action (if implemented).
+                - NSS (No Show Staff) : No-show tagged specifically from a staff action (if implemented).
+
+              Cancellation Statuses:
+                - CN (Cancelled) : Appointment cancelled via API.
+                - CND (Cancelled Doctor) : Cancelled from the doctor’s account in the tool.
+                - CNS (Cancelled Staff) : Cancelled from the staff’s account in the tool.
+                - PC (Provisional Cancelled) : Appointment marked as provisional cancellation, when patient said they will not come for the appointment on the follow-up appointment message.
+                - PNR (Payment Not Received) : Appointment marked as PNR, when patient tried paying for a pre-paid appointment but the payment failed.
+
+              Reschedule Statuses:
+                - RE : Rescheduled via API.
+                - RES : Rescheduled from staff account.
+                - RED : Rescheduled from doctor account.
+
 
       operationId: GetappointmentDetails
       parameters:
@@ -3469,6 +4177,9 @@ paths:
                 end_time:
                   type: integer
                   description: 'End time of new appointment in epoch. To be used in order to reschedule appointment.'
+                token:
+                  type: integer
+                  description: 'A unique number given to each patient to indicate their position in the queue.'
                 video_connect:
                   type: object
                   properties:
@@ -3593,7 +4304,7 @@ paths:
                   city: "Bangalore"
                   pincode: 560049
                 partner_patient_id: "6742984"
-
+              token: 2
               video_connect:
                   vendor: 100ms
                   url: "https://xyz.live/meeting/nfo-necy-cwg"
@@ -3746,6 +4457,9 @@ paths:
             schema:
               type: object
               properties:
+                token:
+                  type: integer
+                  description: 'A unique number given to each patient to indicate their position in the queue.' 
                 appointment_details:
                   type: object
                   properties:
@@ -4597,8 +5311,199 @@ paths:
                         type: string
               example:
                 error:
-                  code: "CANCEL_NOT_ALLOWED"
-                  message: "You do not have permission to cancel this appointment"
+                  code: "CANCEL_NOT_ALLOWED"
+                  message: "You do not have permission to cancel this appointment"
+        '400':
+          description: Bad Request
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error:
+                    type: object
+                    properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+              example:
+                error:
+                  code: "INVALID_REQUEST"
+                  message: "The request is invalid or missing required parameters"
+        '500':
+          description: Internal Server Error
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error:
+                    type: object
+                    properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+              example:
+                error:
+                  code: "SERVER_ERROR"
+                  message: "An unexpected error occurred on the server"
+      deprecated: false
+  /dr/v1/appointment/{appointment_id}/reschedule:
+    put:
+      tags:
+        - Appointment API
+      summary: Reschedule Appointment
+      description: >-
+
+        ### Overview
+
+
+        This API endpoint is used to reschedule an existing appointment.
+
+      operationId: RescheduleAppointment
+      parameters:
+        - name: auth
+          in: header
+          description: ''
+          required: true
+          style: simple
+          schema:
+            type: string
+            example: 'auth'
+        - name: appointment_id
+          in: path
+          description: ''
+          required: true
+          style: simple
+          schema:
+            type: string
+        - name: partner_id
+          in: query
+          description: 'If set to 1 then appointment_id in path parameter should be partner_appointment_id else eka apppointment_id'
+          required: true
+          style: form
+          explode: true
+          schema:
+            type: string
+            example: '1'
+      requestBody:
+        description: ''
+        content:
+          application/json:
+            schema:
+              type: object
+              properties:
+                start_time:
+                  type: integer
+                end_time:
+                  type: integer
+              oneOf:
+                - title: PartnerIds
+                  properties:
+                    partner_clinic_id:
+                      type: string
+                      description: 'Identifier for the partner’s clinic.'
+                    partner_doctor_id:
+                      type: string
+                      description: 'Identifier for the partner’s doctor.'
+                
+                - title: EkaIds
+                  properties:
+                    clinic_id:
+                      type: string
+                      description: 'Identifier for the clinic in Eka.'
+                    doc_id:
+                      type: string
+                      description: 'Identifier for the doctor in Eka.'
+            example:
+              start_time: 1730189586
+              end_time: 1730189586
+              partner_clinic_id: "54672347823"
+              partner_doctor_id: "58hjbfiugfqw8778"
+      responses:
+        '204':
+          description: OK
+          headers:
+            Date:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: Thu, 16 Apr 2020 08:47:12 GMT
+            Transfer-Encoding:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: chunked
+            Connection:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: keep-alive
+            Server:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: nginx/1.10.3 (Ubuntu)
+            Vary:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: Accept-Encoding
+            Strict-Transport-Security:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: max-age=15768000
+            Content-Encoding:
+              content:
+                text/plain:
+                  schema:
+                    type: string
+                  example: gzip
+        '404':
+          description: Not Found
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error:
+                    type: object
+                    properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+              example:
+                error:
+                  code: "APPOINTMENT_NOT_FOUND"
+                  message: "The specified appointment ID does not exist"
+        '403':
+          description: Forbidden
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error:
+                    type: object
+                    properties:
+                      code:
+                        type: string
+                      message:
+                        type: string
+              example:
+                error:
+                  code: "RESCHEDULE_NOT_ALLOWED"
+                  message: "You do not have permission to reschedule this appointment"
         '400':
           description: Bad Request
           content:
@@ -4636,19 +5541,20 @@ paths:
                   code: "SERVER_ERROR"
                   message: "An unexpected error occurred on the server"
       deprecated: false
-  /dr/v1/appointment/{appointment_id}/reschedule:
-    put:
+  
+  /dr/v1/appointment/{appointment_id}/change-status:
+    post:
       tags:
         - Appointment API
-      summary: Reschedule Appointment
+      summary: No-Show Appointment
       description: >-
 
         ### Overview
 
 
-        This API endpoint is used to reschedule an existing appointment.
+        This API endpoint is used to update an existing appointment to No-Show state.
 
-      operationId: RescheduleAppointment
+      operationId: ChangeStatusAppointment
       parameters:
         - name: auth
           in: header
@@ -4665,6 +5571,7 @@ paths:
           style: simple
           schema:
             type: string
+        
         - name: partner_id
           in: query
           description: 'If set to 1 then appointment_id in path parameter should be partner_appointment_id else eka apppointment_id'
@@ -4681,35 +5588,11 @@ paths:
             schema:
               type: object
               properties:
-                start_time:
-                  type: integer
-                end_time:
-                  type: integer
-              oneOf:
-                - title: PartnerIds
-                  properties:
-                    partner_clinic_id:
-                      type: string
-                      description: 'Identifier for the partner’s clinic.'
-                    partner_doctor_id:
-                      type: string
-                      description: 'Identifier for the partner’s doctor.'
-                
-                - title: EkaIds
-                  properties:
-                    clinic_id:
-                      type: string
-                      description: 'Identifier for the clinic in Eka.'
-                    doc_id:
-                      type: string
-                      description: 'Identifier for the doctor in Eka.'
-            example:
-              start_time: 1730189586
-              end_time: 1730189586
-              partner_clinic_id: "54672347823"
-              partner_doctor_id: "58hjbfiugfqw8778"
+                status:
+                  type: string   
+                  example: 'NS'  
       responses:
-        '204':
+        '200':
           description: OK
           headers:
             Date:
@@ -4754,42 +5637,6 @@ paths:
                   schema:
                     type: string
                   example: gzip
-        '404':
-          description: Not Found
-          content:
-            application/json:
-              schema:
-                type: object
-                properties:
-                  error:
-                    type: object
-                    properties:
-                      code:
-                        type: string
-                      message:
-                        type: string
-              example:
-                error:
-                  code: "APPOINTMENT_NOT_FOUND"
-                  message: "The specified appointment ID does not exist"
-        '403':
-          description: Forbidden
-          content:
-            application/json:
-              schema:
-                type: object
-                properties:
-                  error:
-                    type: object
-                    properties:
-                      code:
-                        type: string
-                      message:
-                        type: string
-              example:
-                error:
-                  code: "RESCHEDULE_NOT_ALLOWED"
-                  message: "You do not have permission to reschedule this appointment"
         '400':
           description: Bad Request
           content:
@@ -4808,24 +5655,7 @@ paths:
                 error:
                   code: "INVALID_REQUEST"
                   message: "The request is invalid or missing required parameters"
-        '500':
-          description: Internal Server Error
-          content:
-            application/json:
-              schema:
-                type: object
-                properties:
-                  error:
-                    type: object
-                    properties:
-                      code:
-                        type: string
-                      message:
-                        type: string
-              example:
-                error:
-                  code: "SERVER_ERROR"
-                  message: "An unexpected error occurred on the server"
+        
       deprecated: false
   /dr/v1/appointment/patient/{patient_id}:
     get:
@@ -5756,7 +6586,265 @@ paths:
                         conf_id: "25e4acd4eb5fbc0b8523d8de315555a9ee7b5700b0b89a07879daff1be1510e6"
 
       deprecated: false
-  
+  /cdr/v1/hipusers/{hip_user_id}:
+    get:
+      tags:
+        - HIP Users API
+      summary: Get HIP User Details by ID
+      description: >
+        This API retrieves detailed information about a specific HIP user
+        registered under a business. The response includes the user's personal
+        details, assigned doctors, and associated clinics.
+
+        > _Use this API to get complete profile details of a single HIP user by their Eka user ID._
+      operationId: GetHIPUserById
+      parameters:
+        - name: auth
+          in: header
+          required: true
+          description: >
+            The authentication token for the business. It is used to verify the business making the request. The token can be fetched from the Auth API.
+          schema:
+            type: string
+          example: >
+            eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJkb2Mtd2ViIiwiYi1pZCI6IjcxNzYzMzgwMzI2NzY4MjQiLCJjYyI6eyJlc2MiOjAsInBleCI6MTc5NDc4NzIwMCwicHN0IjoidHJ1ZSIsInN0eSI6InAifSwiZG9iIjoiMTk2My0wNS0wMyIsImV4cCI6MTc2Mzk4MDc5MSwiZm4iOiJNYW5vaGFyYW4iLCJnZW4iOiJNIiwiaWF0IjoxNzYzOTc4OTkxLCJpZHAiOiJtb2IiLCJpc3MiOiJlbXIuZWthLmNhcmUiLCJqdGkiOiI5NzlhMmM5Yy03ODkwLTQ5NDUtYWU2YS1kZjQzNGQxNjMyOTQiLCJsbiI6Ik1vaGFuIiwib2lkIjoiMTc2MzM4MDMyNjkyMDU3IiwicHJpIjp0cnVlLCJwcyI6IkFEIiwiciI6IklOIiwicyI6IkRyIiwidXVpZCI6IjgyNmEzZDU3LWVkMmUtNDNjYi1iODg0LTc0OGQyOTcwMzI1NyIsInctaWQiOiI3MTc2MzM4MDMyNjc2ODI0Iiwidy1uIjoiTWFudXNocmVlIEhvc3BpdGFsIn0.zFZtvgcNVV0iEEvmmjmCOh79HRHsAcvrc6jff71E7Xo
+        - name: hip_user_id
+          in: path
+          required: true
+          description: The unique Eka Care ID of the HIP user.
+          schema:
+            type: string
+          example: "176338032692057"
+      responses:
+        '200':
+          description: OK
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  user:
+                    type: object
+                    properties:
+                      id:
+                        type: string
+                        example: "176338032692057"
+                      firstname:
+                        type: string
+                        example: "Manoharan"
+                      lastname:
+                        type: string
+                        example: "Mohan"
+                      mobile:
+                        type: string
+                        example: "9840254450"
+                      email:
+                        type: string
+                        example: "criticcaredr@gmail.com"
+                      is_admin:
+                        type: boolean
+                        example: true
+                      seat_type:
+                        type: string
+                        description: >
+                          Indicates the type of seat or subscription plan assigned to the HIP user.
+                          - **p** → Premium user (full access to advanced features)
+                          - **b** → Basic user (access to standard features only)
+                        example: "p"
+                      doctors:
+                        type: array
+                        items:
+                          type: object
+                          properties:
+                            id:
+                              type: string
+                              example: "do1763380327031"
+                            firstname:
+                              type: string
+                              example: "Manoharan"
+                            lastname:
+                              type: string
+                              example: "Mohan"
+                      clinics:
+                        type: array
+                        items:
+                          type: object
+                          properties:
+                            id:
+                              type: string
+                              example: "c-1506ace382e94bf5ba9751fb"
+                            name:
+                              type: string
+                              example: "Manushree Hospital"
+                      partner_id:
+                        type: string
+                        nullable: true
+                        example: null
+        '403':
+          description: Forbidden
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "error"
+                  message:
+                    type: string
+                    example: "You do not have permission to access this HIP user"
+        '404':
+          description: Not Found
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error:
+                    type: object
+                    properties:
+                      code:
+                        type: string
+                        example: "NOT_FOUND"
+                      message:
+                        type: string
+                        example: "User not found. Please check the provided ID."
+
+        '500':
+          description: Internal Server Error
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "error"
+                  message:
+                    type: string
+                    example: "An unexpected error occurred on the server"
+  /cdr/v1/hipusers/:
+    get:
+      tags:
+        - HIP Users API
+      summary: Get All HIP Users of a Business
+      description: >
+        This API retrieves the list of all HIP users associated with a business.
+        The response includes each user's details along with their linked doctors
+        and clinics.
+
+        > _Use this API to fetch all HIP users for a business account in one call._
+      operationId: GetAllHIPUsers
+      parameters:
+        - name: auth
+          in: header
+          required: true
+          description: >
+            The authentication token for the business. It is used to verify the business making the request. The token can be fetched from the Auth API.
+          schema:
+            type: string
+          example: >
+            eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJkb2Mtd2ViIiwiYi1pZCI6IjcxNzYzMzgwMzI2NzY4MjQiLCJjYyI6eyJlc2MiOjAsInBleCI6MTc5NDc4NzIwMCwicHN0IjoidHJ1ZSIsInN0eSI6InAifSwiZG9iIjoiMTk2My0wNS0wMyIsImV4cCI6MTc2Mzk4MDc5MSwiZm4iOiJNYW5vaGFyYW4iLCJnZW4iOiJNIiwiaWF0IjoxNzYzOTc4OTkxLCJpZHAiOiJtb2IiLCJpc3MiOiJlbXIuZWthLmNhcmUiLCJqdGkiOiI5NzlhMmM5Yy03ODkwLTQ5NDUtYWU2YS1kZjQzNGQxNjMyOTQiLCJsbiI6Ik1vaGFuIiwib2lkIjoiMTc2MzM4MDMyNjkyMDU3IiwicHJpIjp0cnVlLCJwcyI6IkFEIiwiciI6IklOIiwicyI6IkRyIiwidXVpZCI6IjgyNmEzZDU3LWVkMmUtNDNjYi1iODg0LTc0OGQyOTcwMzI1NyIsInctaWQiOiI3MTc2MzM4MDMyNjc2ODI0Iiwidy1uIjoiTWFudXNocmVlIEhvc3BpdGFsIn0.zFZtvgcNVV0iEEvmmjmCOh79HRHsAcvrc6jff71E7Xo
+      responses:
+        '200':
+          description: OK
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "success"
+                  users:
+                    type: array
+                    items:
+                      type: object
+                      properties:
+                        id:
+                          type: string
+                          example: "176338032692057"
+                        firstname:
+                          type: string
+                          example: "Manoharan"
+                        lastname:
+                          type: string
+                          example: "Mohan"
+                        mobile:
+                          type: string
+                          example: "9840254450"
+                        email:
+                          type: string
+                          example: "criticcaredr@gmail.com"
+                        is_admin:
+                          type: boolean
+                          example: true
+                        seat_type:
+                          type: string
+                          description: >
+                            Indicates the type of seat or subscription plan assigned to the HIP user.
+                            - **p** → Premium user (full access to advanced features)
+                            - **b** → Basic user (access to standard features only)
+                          example: "p"
+                        doctors:
+                          type: array
+                          items:
+                            type: object
+                            properties:
+                              id:
+                                type: string
+                                example: "do1763380327031"
+                              firstname:
+                                type: string
+                                example: "Manoharan"
+                              lastname:
+                                type: string
+                                example: "Mohan"
+                        clinics:
+                          type: array
+                          items:
+                            type: object
+                            properties:
+                              id:
+                                type: string
+                                example: "c-1506ace382e94bf5ba9751fb"
+                              name:
+                                type: string
+                                example: "Manushree Hospital"
+                        partner_id:
+                          type: string
+                          nullable: true
+                          example: null
+        '403':
+          description: Forbidden
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "error"
+                  message:
+                    type: string
+                    example: "You do not have permission to access HIP users for this business"
+        '500':
+          description: Internal Server Error
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  status:
+                    type: string
+                    example: "error"
+                  message:
+                    type: string
+                    example: "An unexpected error occurred on the server"
+
 components:
   schemas:
     AuthLoginRequest:
diff --git a/api-reference/doc-tool/ip-allowlisting-for-clients.mdx b/api-reference/doc-tool/ip-allowlisting-for-clients.mdx
new file mode 100644
index 00000000..0429f758
--- /dev/null
+++ b/api-reference/doc-tool/ip-allowlisting-for-clients.mdx
@@ -0,0 +1,24 @@
+---
+title: IP Allowlisting for Clients
+description: Allowlisting and endpoint information to access Eka Care EMR 
+---
+
+Ensure your network/firewall is configured to allow inbound connections from the below URLs for seamless integration with Eka Care EMR.
+
+## Production
+- **Allowed URLs:**
+  - `*.eka.care`
+
+## Staging
+- **Allowed URLs:**
+  - `*.dev.eka.care`
+
+## S3 Bucket URLs
+
+- `*.s3.ap-south-1.amazonaws.com`
+
+
+---
+
+> eka.care and dev.eka.care URL's are hosted on AWS Cloudfront, Make sure you have allowlisted [AWS CloudFront IP Addresses.](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LocationsOfEdgeServers.html)
+
diff --git a/api-reference/doc-tool/ip-allowlisting-for-clients.yaml b/api-reference/doc-tool/ip-allowlisting-for-clients.yaml
new file mode 100644
index 00000000..8b0343b5
--- /dev/null
+++ b/api-reference/doc-tool/ip-allowlisting-for-clients.yaml
@@ -0,0 +1,76 @@
+openapi: 3.0.0
+info:
+  title: Doctor Tool IP Allowlisting Information
+  description: Allowlisting and endpoint information to access Eka Care EMR
+  version: 1.0.0
+  contact:
+    name: Eka Care Support
+    url: https://eka.care/
+    email: support@eka.care
+
+servers:
+  - url: https://api.eka.care
+    description: Production server - Allowed URL pattern *.eka.care
+  - url: https://api.dev.eka.care
+    description: Staging server - Allowed URL pattern *.dev.eka.care
+
+tags:
+  - name: Network Configuration
+    description: IP allowlisting and network configuration requirements
+
+paths:
+  /network-info:
+    get:
+      tags:
+        - Network Configuration
+      summary: Get Network Configuration Requirements
+      description: |
+        Ensure your network/firewall is configured to allow inbound connections from the below URLs for seamless integration with Eka Care EMR.
+        
+        ## Production Environment
+        - **Allowed URLs:** `*.eka.care`
+        
+        ## Staging Environment
+        - **Allowed URLs:** `*.dev.eka.care`
+        
+        ## S3 Bucket URLs
+        - `*.s3.ap-south-1.amazonaws.com`
+        
+        ## Important Notes
+        - eka.care and dev.eka.care URLs are hosted on AWS CloudFront
+        - Make sure you have allowlisted [AWS CloudFront IP Addresses](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LocationsOfEdgeServers.html)
+      responses:
+        200:
+          description: Network configuration information
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  production:
+                    type: object
+                    properties:
+                      urls:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.eka.care"]
+                      s3_buckets:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.s3.ap-south-1.amazonaws.com"]
+                  staging:
+                    type: object
+                    properties:
+                      urls:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.dev.eka.care"]
+                      s3_buckets:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.s3.ap-south-1.amazonaws.com"]
+
diff --git a/api-reference/doc-tool/onboarding-apis/onboard-clinic.mdx b/api-reference/doc-tool/onboarding-apis/onboard-clinic.mdx
new file mode 100644
index 00000000..c4a49408
--- /dev/null
+++ b/api-reference/doc-tool/onboarding-apis/onboard-clinic.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /cdr/v1/clinic/
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/onboarding-apis/onboard-doctor.mdx b/api-reference/doc-tool/onboarding-apis/onboard-doctor.mdx
new file mode 100644
index 00000000..0278d061
--- /dev/null
+++ b/api-reference/doc-tool/onboarding-apis/onboard-doctor.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /cdr/v1/doctor/
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/onboarding-apis/onboard-ekauser.mdx b/api-reference/doc-tool/onboarding-apis/onboard-ekauser.mdx
new file mode 100644
index 00000000..20eb3aa3
--- /dev/null
+++ b/api-reference/doc-tool/onboarding-apis/onboard-ekauser.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /cdr/v1/ekauser/
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/post_webhooks/google-review-webhook.mdx b/api-reference/doc-tool/post_webhooks/google-review-webhook.mdx
new file mode 100644
index 00000000..4bcb3b0d
--- /dev/null
+++ b/api-reference/doc-tool/post_webhooks/google-review-webhook.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /registered_url_for_google_review_events
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/post_webhooks/mcert-webhook.mdx b/api-reference/doc-tool/post_webhooks/mcert-webhook.mdx
new file mode 100644
index 00000000..58205ad4
--- /dev/null
+++ b/api-reference/doc-tool/post_webhooks/mcert-webhook.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /registered_url_for_consent_form
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/post_webhooks/post_webhook.yaml b/api-reference/doc-tool/post_webhooks/post_webhook.yaml
index 42409609..5c0de81a 100644
--- a/api-reference/doc-tool/post_webhooks/post_webhook.yaml
+++ b/api-reference/doc-tool/post_webhooks/post_webhook.yaml
@@ -1096,6 +1096,363 @@ paths:
           description: "Successfully received the schedule event"
           headers: {}
       deprecated: false
+  /registered_url_for_google_review_events:
+    post:
+      tags:
+        - Doctor Webhooks
+      summary: Google Review Events
+      description: >-
+        When a Google review request event occurs, a webhook is sent to the registered endpoint containing the Doctor ID, Google review link, and Patient ID.
+
+        The receiving system can use these details to update or manage Google review information as needed.
+      operationId: GoogleReviewRequestWebhook
+      parameters: []
+      requestBody:
+        description: ''
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - event
+                - event_time
+                - timestamp
+                - client_id
+                - business_id
+                - data
+              properties:
+                event:
+                  type: string
+                  enum:
+                    - "google_review.request"
+                  example: "google_review.request"
+                  description: "Type of event"
+                event_time:
+                  type: integer
+                  example: 1730189586
+                  description: "Event occurred timestamp"
+                timestamp:
+                  type: integer
+                  example: 1730189586
+                  description: "Timestamp of the event"
+                client_id:
+                  type: string
+                  example: "67978400352a61001d64e9fb"
+                  description: "Client ID for the schedule"
+                business_id:
+                  type: string
+                  example: "174159057718553"
+                  description: "Business ID for the schedule"
+                data:
+                  type: object
+                  required:
+                    - doctor_id
+                    - google_review_link
+                    - patient_id
+                  properties:
+                    doctor_id:
+                      type: string
+                      example: "174159057723920"
+                      description: "Identifier for the respective doctor in Eka"
+                    google_review_link:
+                      type: string
+                      example : "https://g.page/r/CRVNub8JgYWLEA0/review"
+                      description: "Google review link"
+                    patient_id:
+                      type: string
+                      example: "174159057723925"
+                      description: "Identified for the respective patient in Eka"
+                    appointment_id:
+                      type: string
+                      example: "api-abb67007-1e53-4f0f-b428-a4bc025468a4"
+                      description: "Unique identifier for the appointment."
+                    clinic_id:
+                      type: string
+                      example: "67978400352a61001d64e9fb"
+                      description: "Unique identifier of the clinic"
+      deprecated: false
+
+  /registered_url_for_consent_form:
+    post:
+      tags:
+        - Doctor Webhooks
+      summary: Consent Form Events
+      description: >-
+        When a consent form or medical certificate is created or updated, a webhook is sent to the registered endpoint containing the Doctor Id, Patient Id, Consent form url, **type(represents whether it is a medical certificate or consent form)** etc.
+
+        The receiving system can use these details as per their need.
+        
+      operationId: McertEventsWebhook
+      parameters: []
+      requestBody:
+        description: ''
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - event
+                - event_time
+                - timestamp
+                - client_id
+                - business_id
+                - data
+              properties:
+                event:
+                  type: string
+                  enum:
+                    - "mcert.created"
+                    - "mcert.updated"
+                  example: "mcert.created"
+                  description: "Type of event"
+                event_time:
+                  type: integer
+                  example: 1730189586
+                  description: "Event occurred timestamp"
+                timestamp:
+                  type: integer
+                  example: 1730189586
+                  description: "Timestamp of the event"
+                client_id:
+                  type: string
+                  example: "67978400352a61001d64e9fb"
+                  description: "Client ID for the schedule"
+                business_id:
+                  type: string
+                  example: "174159057718553"
+                  description: "Business ID for the schedule"
+                data:
+                  type: object
+                  required:
+                    - docid
+                    - id
+                    - owner
+                    - patientid
+                    - sendurlpdf
+                    - url
+                    - type
+                  properties:
+                    docid:
+                      type: string
+                      example: "174159057723920"
+                      description: "Identifier for the respective doctor in Eka"
+                    id:
+                      type: string
+                      example : "eaaf7c24-ebcd-4340-975a-851d6e31478f"
+                      description: "Unique identifier for the consent form"
+                    owner:
+                      type: string
+                      example: "174159057723925"
+                      description: "Business Id"
+                    patientid:
+                      type: string
+                      example: "175465638609726"
+                      description: "Unique identifier for the patient."
+                    sendurlpdf:
+                      type: string
+                      example: "https://mcertificate.dev.eka.care/b-161467756044203/eaaf7c24-ebcd-4340-975a-851d6e31478f.pdf"
+                      description: "Consent form url which is sent on whatsapp"
+                    url:
+                      type: string
+                      example: "https://mcertificate.dev.eka.care/b-161467756044203/eaaf7c24-ebcd-4340-975a-851d6e31478f.pdf"
+                      description: "Consent form url"
+                    type:
+                      type: string
+                      example: "mcert"
+                      description: "Type of document. \nPossible values: **mcert** (for medical certificate), **consent** (for consent form)."
+      deprecated: false
+  
+  /registered_url_for_receipt_events:
+    post:
+      tags:
+        - Receipt Webhooks
+      summary: Receipt Events
+      description: >-
+        When a Receipt is created, updated or deleted, a webhook is sent to the registered endpoint containing the Doctor Id, Patient Id, Clinic Id etc.
+
+        The receiving system can use these details as per their need.
+        
+      operationId: McertEventsWebhook
+      parameters: []
+      requestBody:
+        description: ''
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - event
+                - event_time
+                - timestamp
+                - client_id
+                - business_id
+                - data
+              properties:
+                event:
+                  type: string
+                  enum:
+                    - "receipt.created"
+                    - "receipt.updated"
+                    - "receipt.deleted"
+                  example: "receipt.created"
+                  description: "Type of event"
+                event_time:
+                  type: integer
+                  example: 1730189586
+                  description: "Event occurred timestamp"
+                timestamp:
+                  type: integer
+                  example: 1730189586
+                  description: "Timestamp of the event"
+                client_id:
+                  type: string
+                  example: "67978400352a61001d64e9fb"
+                  description: "Client ID for the schedule"
+                business_id:
+                  type: string
+                  example: "174159057718553"
+                  description: "Business ID for the schedule"
+                data:
+                  type: object
+                  required:
+                    - receipt_id
+                    - aid
+                    - doctor_oid
+                    - clinic_id
+                    - patient_oid
+                    - created_at
+                    - updated_at
+                    - receipt_url
+                    - receipt_status
+                    - receipt_amount
+                    - additional_discount_value
+                    - additional_discount_type
+                    - additional_discount_amount
+                    - net_amount
+                    - name
+                    - mobile
+                    - sku_discount_amount
+                    - amount_due
+                    - archive
+                    - receipt_number
+                    - flavour
+                    - remarks
+                    - ref_trx_id
+                    - payment_id
+                    - payment_link
+                    - amount_paid
+                    - actor
+                  properties:
+                    receipt_id:
+                      type: integer
+                      example: 2579
+                      description: "Unique identifier for the receipt"
+                    aid:
+                      type: string
+                      example: "d-75f3dcf1-5de3-40fc-8ccd-f42c8d54e8e8"
+                      description: "Appointment Id"
+                    doctor_oid:
+                      type: string
+                      example: "161467756044203"
+                      description: "Unique identifier for the doctor"
+                    clinic_id:
+                      type: string
+                      example: "60b0ee0c0b5804795509aefb"
+                      description: "Clinic identifier"
+                    patient_oid:
+                      type: string
+                      example: "176345969121476"
+                      description: "Unique identifier for the patient"
+                    created_at:
+                      type: integer
+                      example: 1763476917560
+                      description: "Timestamp when the receipt was created (in milliseconds)"
+                    updated_at:
+                      type: integer
+                      example: 1763476917560
+                      description: "Timestamp when the receipt was last updated (in milliseconds)"
+                    receipt_number:
+                      type: string
+                      example: null
+                      description: "Human-readable receipt number"
+                    receipt_url:
+                      type: string
+                      example: "https://doc-receipt.s3.ap-south-1.amazonaws.com/v2/b-161467756044203/161467756044203/60b0ee0c0b5804795509aefb/1763476916985.pdf"
+                      description: "URL to download/view the receipt"
+                    receipt_status:
+                      type: string
+                      example: "SUCCESS"
+                      description: "Status of the receipt"
+                    receipt_amount:
+                      type: number
+                      example: 120
+                      description: "Total amount on the receipt"
+                    additional_discount_value:
+                      type: number
+                      example: 10
+                      description: "Value of any additional discount"
+                    additional_discount_type:
+                      type: string
+                      example: "AMOUNT"
+                      description: "Type of additional discount"
+                    additional_discount_amount:
+                      type: number
+                      example: 10
+                      description: "Amount reduced due to additional discount"
+                    net_amount:
+                      type: number
+                      example: 120
+                      description: "Net payable amount after discounts"
+                    name:
+                      type: string
+                      example: "gc baby normal"
+                      description: "Name of the patient"
+                    mobile:
+                      type: string
+                      example: "+919008888888"
+                      description: "Patient's mobile number"
+                    flavour:
+                      type: string
+                      example: null
+                      description: "Flavour or type of receipt/service"
+                    sku_discount_amount:
+                      type: number
+                      example: 10
+                      description: "Discount amount applied per SKU/item"
+                    amount_due:
+                      type: number
+                      example: 10
+                      description: "Remaining amount to be paid"
+                    archive:
+                      type: integer
+                      example: 0
+                      description: "Whether the receipt is archived (0 or 1)"
+                    remarks:
+                      type: string
+                      example: ""
+                      description: "Additional remarks about the transaction"
+                    ref_trx_id:
+                      type: string
+                      example: ""
+                      description: "Reference transaction ID"
+                    payment_id:
+                      type: string
+                      example: "ret-dfwef-dsfsd-fwefdsf"
+                      description: "Unique identifier for the payment"
+                    payment_link:
+                      type: string
+                      example: "https://example.link.com"
+                      description: "URL for payment completion"
+                    amount_paid:
+                      type: number
+                      example: 10
+                      description: "Amount already paid"
+                    actor:
+                      type: string
+                      example: "doctor"
+                      description: "Who performed the action or update"
+      deprecated: false
+  
   
   /registered_url_for_appointment_tele_dr_joined_webhook_events:
     post:
diff --git a/api-reference/doc-tool/post_webhooks/receipt-webhook.mdx b/api-reference/doc-tool/post_webhooks/receipt-webhook.mdx
new file mode 100644
index 00000000..db331b5d
--- /dev/null
+++ b/api-reference/doc-tool/post_webhooks/receipt-webhook.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /registered_url_for_receipt_events
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/user-apis/get-all-users.mdx b/api-reference/doc-tool/user-apis/get-all-users.mdx
new file mode 100644
index 00000000..579e42f9
--- /dev/null
+++ b/api-reference/doc-tool/user-apis/get-all-users.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /cdr/v1/hipusers/
+---
\ No newline at end of file
diff --git a/api-reference/doc-tool/user-apis/get-user-by-id.mdx b/api-reference/doc-tool/user-apis/get-user-by-id.mdx
new file mode 100644
index 00000000..7d1c0cfd
--- /dev/null
+++ b/api-reference/doc-tool/user-apis/get-user-by-id.mdx
@@ -0,0 +1,3 @@
+---
+openapi: get /cdr/v1/hipusers/{hip_user_id}
+---
\ No newline at end of file
diff --git a/api-reference/general-tools/medical/lab-report/classification-webhook.mdx b/api-reference/general-tools/medical/lab-report/classification-webhook.mdx
new file mode 100644
index 00000000..2af1f91a
--- /dev/null
+++ b/api-reference/general-tools/medical/lab-report/classification-webhook.mdx
@@ -0,0 +1,48 @@
+Webhook event is sent when classification of document processing completes.
+### Request
+**Headers:**
+
+- `Eka-Webhook-Signature`: `<Eka Webhook Signature>`  [Refer: Webhook Signature](/api-reference/connect/webhooks/webhook-signature)
+- `Content-Type`: `application/json`
+
+**Body:**
+
+```json
+{
+        "event": "rec.classification",
+        "service": "rec",
+        "event_time": 1759234802,
+        "transaction_id": "4d39628e-7916-47d7-bc35-a00cb986942b",
+        "data": {
+             "status": "parsing_complete",
+             "document_id": "ed66604d-9d62-4f71-a5fb-b78a490148a0",
+             "document_classification": "lab_report"
+        }
+}
+```
+### Field Descriptions
+
+- **`data`**: Contains additional details related to the event.
+    - **`status`**: Current parsing state (parsing_initiated, parsing_complete, parsing_error).
+    - **`document_id`**: ID of the document that was parsed.
+    - **`document_classification`**: Document classification category (enum)
+            - Possible values:
+                - `lab_report` - Laboratory test report
+                - `prescription` - Medical prescription
+                - `medical_insurance` - Medical insurance document
+                - `scan_interpretation` - Radiology/scan interpretation report
+                - `scan` - Medical scan/imaging
+                - `discharge_summary` - Hospital discharge summary
+                - `cowin_vaccine_certificate` - COVID-19 vaccination certificate
+                - `other_medical_document` - Other medical-related document
+                - `medical_invoice` - Medical bill/invoice
+                - `id_card` - Identification card
+                - `body_part` - Body part image
+                - `other_insurance` - Other insurance document
+                - `other_invoice` - Non-medical invoice
+                - `other_graphical` - Other graphical content
+                - `non_medical_document` - Non-medical document
+Note: The status field is an enum with following possible values:
+ - parsing_complete
+ - parsing_error
+ - parsing_initiated
\ No newline at end of file
diff --git a/api-reference/general-tools/medical/lab-report/delete-document.mdx b/api-reference/general-tools/medical/lab-report/delete-document.mdx
index 1802d114..25f71379 100644
--- a/api-reference/general-tools/medical/lab-report/delete-document.mdx
+++ b/api-reference/general-tools/medical/lab-report/delete-document.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Delete Document"
-openapi: delete /mr/api/v1/docs/{document_id}
+openapi: delete /mr/api/v1/docs/{id}
 ---
 
 API to delete a uploaded document from using a `document_id` 
\ No newline at end of file
diff --git a/api-reference/general-tools/medical/lab-report/smart-report-webhook.mdx b/api-reference/general-tools/medical/lab-report/smart-report-webhook.mdx
index 153227e3..c0b89367 100644
--- a/api-reference/general-tools/medical/lab-report/smart-report-webhook.mdx
+++ b/api-reference/general-tools/medical/lab-report/smart-report-webhook.mdx
@@ -17,9 +17,6 @@ Webhook event is sent when Smart Report processing completes.
              "status": "parsing_complete",
              "document_id": "ed66604d-9d62-4f71-a5fb-b78a490148a0",
              "identifier": "ekacare-sr-82b9b563-6c83-48e6-a89e-c2621db5599a",
-             "data": {
-                  "fhir": "<fhir data base64 encoded>"
-             }
         }
 }
 ```
diff --git a/SDKs/web-sdk/self-assessment-sdk.mdx b/api-reference/health-ai/assessment/SDKs/assessment-ts-sdk.mdx
similarity index 79%
rename from SDKs/web-sdk/self-assessment-sdk.mdx
rename to api-reference/health-ai/assessment/SDKs/assessment-ts-sdk.mdx
index 7ce6e173..5318c087 100644
--- a/SDKs/web-sdk/self-assessment-sdk.mdx
+++ b/api-reference/health-ai/assessment/SDKs/assessment-ts-sdk.mdx
@@ -1,10 +1,9 @@
 ---
-title: Self Assessment SDK
-description: "Complete implementation guide for the Self Assessment SDK"
+title: TS SDK
+description: "Complete implementation guide for the Assessment TS SDK"
 ---
 
-# Self Assessment SDK Implementation
-
+# Assessment TS SDK Implementation
 This guide provides everything you need to integrate the Self Assessment SDK into your application.
 
 ## Overview
@@ -58,17 +57,83 @@ Initializes and runs a Self Assessment application.
 - `container_id` (string, required): The HTML element ID where the assessment will be rendered
 - `auth_token` (string, required): JWT authentication token for API access
 - `refresh_token` (string, required): Token used to refresh the auth token when it expires
-- `params` (object, optional): Additional parameters for the assessment (e.g., age, gender)
-- `practice_info` (object, optional): Information about the practice and patient
+- `params` (object, required): Patient parameters for the assessment
+  - `age` (number, required): Patient's age
+  - `gender` (string, required): Patient's gender (e.g., "M", "F", "O")
+- `practice_info` (object, required): Practice and patient identification. See [Practice Info Configuration](#practice-info-configuration) below
 - `transaction_id` (string, optional): Unique transaction identifier
 - `onEndCallback` (function, optional): Callback function called when assessment ends
 - `onSaRedirectCallback` (function, optional): Callback function called when assessment redirects
 - `onSaSubmitCallback` (function, optional): Callback function called when assessment is submitted
 - `onSaInitCallback` (function, optional): Callback function called when assessment is initialized
 
-**Example:**
+#### Practice Info Configuration
+
+The `practice_info` object is required and has two different use cases:
+
+<AccordionGroup>
+  <Accordion title="Patient-Initiated Assessment">
+    When a patient is taking the assessment for themselves:
+    
+    **Required fields (at least one must be provided):**
+    - `patient_uuid` (string): Unique identifier for the patient
+    - `unique_identifier` (string): Alternative unique identifier for the patient
+    
+    ```javascript
+    practice_info: {
+      patient_uuid: "9531778f-030c-11223344-38488c",
+      unique_identifier: "17345678765"
+    }
+    ```
+    
+    <Note>You can provide either `patient_uuid`, `unique_identifier`, or both.</Note>
+  </Accordion>
+
+  <Accordion title="Doctor-Initiated Assessment">
+    When a doctor is conducting the assessment for a patient:
+    
+    **Required fields:**
+    - At least one patient identifier:
+      - `patient_uuid` (string): Unique identifier for the patient
+      - `unique_identifier` (string): Alternative unique identifier for the patient
+    - `practitioner_uuid` (string): Unique identifier for the doctor/practitioner
+    
+    ```javascript
+    practice_info: {
+      practitioner_uuid: "161461111111111",
+      patient_uuid: "9531778f-030c-11223344-38488c",
+      unique_identifier: "17345678765"
+    }
+    ```
+    
+    <Note>When `practitioner_uuid` is included, the assessment is associated with the doctor's practice.</Note>
+  </Accordion>
+</AccordionGroup>
+
+**Examples:**
 
 ```javascript
+// Patient-initiated assessment
+window.runSaApp({
+  workflow_id: 4014,
+  container_id: "sa-container",
+  auth_token: "your-jwt-token",
+  refresh_token: "your-refresh-token",
+  params: {
+    age: 25,
+    gender: "M",
+  },
+  practice_info: {
+    patient_uuid: "9531778f-030c-11223344-38488c",
+    unique_identifier: "17345678765",
+  },
+  transaction_id: "appt_1234",
+  onSaInitCallback: (params) => {
+    console.log("Assessment initialized:", params);
+  },
+});
+
+// Doctor-initiated assessment
 window.runSaApp({
   workflow_id: 4014,
   container_id: "sa-container",
@@ -408,15 +473,15 @@ interface TRunSaApp {
   container_id: string;
   auth_token: string;
   refresh_token: string;
-  params?: {
-    age?: number;
-    gender?: string;
+  params: {
+    age: number;
+    gender: string;
     [key: string]: any;
   };
-  practice_info?: {
-    practitioner_uuid: string;
-    patient_uuid: string;
-    unique_identifier: string;
+  practice_info: {
+    patient_uuid?: string;
+    unique_identifier?: string;
+    practitioner_uuid?: string;
   };
   transaction_id?: string;
   onEndCallback?: (params: {
@@ -561,3 +626,30 @@ window.getWorkflowList().then((response) => {
   console.log("Available workflows:", response.workflows);
 });
 ```
+
+#### 4. Missing Required Parameters
+
+**Problem**: Assessment fails to initialize due to missing parameters.
+
+**Solution**:
+
+- Ensure `params` object includes both `age` and `gender`
+- Verify `practice_info` contains at least one patient identifier (`patient_uuid` or `unique_identifier`)
+- For doctor-initiated assessments, include `practitioner_uuid`
+
+```javascript
+// Correct: All required fields present
+window.runSaApp({
+  workflow_id: 4014,
+  container_id: "sa-container",
+  auth_token: "your-jwt-token",
+  refresh_token: "your-refresh-token",
+  params: {
+    age: 25,
+    gender: "M"
+  },
+  practice_info: {
+    patient_uuid: "9531778f-030c-11223344-38488c"
+  }
+});
+```
diff --git a/api-reference/health-ai/assessment/SDKs/ekapython-sdk.mdx b/api-reference/health-ai/assessment/SDKs/ekapython-sdk.mdx
index 4c1e9a6e..c0a90a22 100644
--- a/api-reference/health-ai/assessment/SDKs/ekapython-sdk.mdx
+++ b/api-reference/health-ai/assessment/SDKs/ekapython-sdk.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Eka Python SDK"
+title: "Python SDK"
 description: "Eka Python SDK for assessment"
 ---
 
diff --git a/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.yml b/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.yml
index 6e9e0e0d..d3db7acd 100644
--- a/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.yml
+++ b/api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment.yml
@@ -61,7 +61,7 @@ paths:
                 unique_identifier:
                   type: string
                   description: >-
-                    A unique patient identifier to identify the patient's profile to associate as assessment with, if applicable.
+                    Unique patient OID to identify the patient for which they are taking the assessment.
                 transaction_id:
                   type: string
                   description: >-
@@ -69,6 +69,7 @@ paths:
               required:
                 - user_info
                 - workflow_id
+                - unique_identifier
               example:
                 user_info:
                   dob: "2001-03-14"
diff --git a/api-reference/health-ai/assessment/assessment-flow/overview.mdx b/api-reference/health-ai/assessment/assessment-flow/overview.mdx
new file mode 100644
index 00000000..2be849f8
--- /dev/null
+++ b/api-reference/health-ai/assessment/assessment-flow/overview.mdx
@@ -0,0 +1,48 @@
+---
+title: "Overview"
+---
+
+Welcome to our comprehensive Assessment Platform, designed to provide users with tailored insights into their health. Our platform features three primary types of assessments:
+
+## 1. Risk Assessments
+Risk Assessments evaluate the likelihood of a user developing specific health conditions, such as diabetes or hypertension. By analyzing key factors, users receive a clear understanding of their risk levels.
+
+## 2. Symptom Checker
+Our Symptom Checker takes user-reported symptoms as input and, through a series of targeted questions, helps triage and identify probable diagnoses. This AI-driven tool is designed to streamline the assessment process and provide users with valuable insights.
+
+
+> Each assessment in our platform is associated with a unique **Workflow ID**. This identifier is crucial for initializing and conducting assessments seamlessly. 
+For more details on the Workflow IDs, please refer to the next topic [Assessment Workflows](./assessment-workflows) or contact support.
+
+
+These are the steps to get perform assessment using Eka Care APIs.
+    
+<Steps>
+  <Step title="Initialization">
+    This step is used to [initialize](./initialization/initialize-assessment) the assessment. This API returns a unique assessmentid which will be used in the next steps.
+  </Step>
+  <Step title="Start Assessment">
+    This step is used to [start the assessment](./continue/start-assessment). It will return the first question of the assessment.
+  </Step>
+  <Step title="Continue Assessment">
+    This step is used to [continue the assessment](./continue/continue-assessment). It will return the next question of the assessment. You need to send the answer of the previous question in the request body. Continue this step until you get the last question.
+  </Step>
+  <Step title="Submit Assessment">
+    This step is used to [submit the assessment](./submit/submit-assessment). You need to send the answer of the last question in the request body. It will return the result and summary of the assessment.
+  </Step>
+</Steps>
+
+<Warning>
+  **Restrictions on Assessments:**<br/>
+
+  **Age restrictions:**<br/>
+  - `12-130 years` for Symptom Checker and Risk Assessment.  
+  - `0-130 years` for Customized Assessments  
+
+  **Gender restrictions:**  
+  - `M, F` supported for Symptom Checker and Risk Assessment.
+  - `M, F, O` supported for Customized Assessments
+</Warning>
+
+
+You will get multiple error codes in case of any failure. You can refer to the [error codes](/api-reference/health-ai/assessment/error-codes) for more details.
diff --git a/api-reference/health-ai/assessment/overview.mdx b/api-reference/health-ai/assessment/overview.mdx
index 2be849f8..153fd7a7 100644
--- a/api-reference/health-ai/assessment/overview.mdx
+++ b/api-reference/health-ai/assessment/overview.mdx
@@ -2,47 +2,60 @@
 title: "Overview"
 ---
 
-Welcome to our comprehensive Assessment Platform, designed to provide users with tailored insights into their health. Our platform features three primary types of assessments:
+# Assessment Platform Overview
 
-## 1. Risk Assessments
-Risk Assessments evaluate the likelihood of a user developing specific health conditions, such as diabetes or hypertension. By analyzing key factors, users receive a clear understanding of their risk levels.
+Eka Care's Assessment Platform empowers healthcare providers with AI-driven health assessments. Simply configure your workflow, and our platform will guide patients through intelligent questionnaires to provide tailored health insights.
 
-## 2. Symptom Checker
-Our Symptom Checker takes user-reported symptoms as input and, through a series of targeted questions, helps triage and identify probable diagnoses. This AI-driven tool is designed to streamline the assessment process and provide users with valuable insights.
+## 🎯 What is the Assessment Platform?
 
+The Assessment Platform is an AI-powered health assessment tool that evaluates patients through dynamic, intelligent questionnaires. It supports symptom check, risk and general assessments.
 
-> Each assessment in our platform is associated with a unique **Workflow ID**. This identifier is crucial for initializing and conducting assessments seamlessly. 
-For more details on the Workflow IDs, please refer to the next topic [Assessment Workflows](./assessment-workflows) or contact support.
+## 🛠️ Integration Products
 
+The Assessment Platform offers **3 different ways** to integrate health assessments into your workflow:
 
-These are the steps to get perform assessment using Eka Care APIs.
-    
-<Steps>
-  <Step title="Initialization">
-    This step is used to [initialize](./initialization/initialize-assessment) the assessment. This API returns a unique assessmentid which will be used in the next steps.
-  </Step>
-  <Step title="Start Assessment">
-    This step is used to [start the assessment](./continue/start-assessment). It will return the first question of the assessment.
-  </Step>
-  <Step title="Continue Assessment">
-    This step is used to [continue the assessment](./continue/continue-assessment). It will return the next question of the assessment. You need to send the answer of the previous question in the request body. Continue this step until you get the last question.
-  </Step>
-  <Step title="Submit Assessment">
-    This step is used to [submit the assessment](./submit/submit-assessment). You need to send the answer of the last question in the request body. It will return the result and summary of the assessment.
-  </Step>
-</Steps>
+### 1. 🎨 **Web SDK** 
+*Pre-built UI components for web applications*
 
-<Warning>
-  **Restrictions on Assessments:**<br/>
+**What it is**: Ready-to-use JavaScript SDK with built-in UI components  
+**Who it's for**: Web applications wanting quick integration with minimal coding   
 
-  **Age restrictions:**<br/>
-  - `12-130 years` for Symptom Checker and Risk Assessment.  
-  - `0-130 years` for Customized Assessments  
+**How it works**: 
+- Include SDK script → Initialize with config → Render assessment UI
+- Pre-built responsive UI
+- Handles all API calls automatically
 
-  **Gender restrictions:**  
-  - `M, F` supported for Symptom Checker and Risk Assessment.
-  - `M, F, O` supported for Customized Assessments
-</Warning>
+**Get Started**: [Web SDK Documentation](https://developer.eka.care/api-reference/health-ai/assessment/SDKs/assessment-ts-sdk)
+
+---
+
+### 2. 📦 **Backend SDKs** 
+*Pre-built libraries for server-side integration*
+
+**What it is**: Ready-to-use code libraries for backend services  
+**Who it's for**: Applications needing server-side assessment management  
+
+**Available SDKs**:
+- [Python SDK](https://developer.eka.care/api-reference/health-ai/assessment/SDKs/ekapython-sdk) - For Python/Django/Flask applications
+
+**How it works**: 
+- Import SDK → Call simple methods → Get assessment results
+- Handles authentication and response formatting automatically
+
+---
+
+### 3. 🌐 **REST APIs** 
+*Direct API access for custom integrations*
+
+**What it is**: Raw HTTP endpoints that you call directly  
+**Who it's for**: Advanced developers, microservices, or any programming language not covered by SDKs  
+
+**How it works**: 
+1. Initialize assessment → Start assessment → Continue with responses → Submit final answer
+2. Full control over the process
+3. Works with any programming language
+
+**Get Started**: [API Documentation](https://developer.eka.care/api-reference/health-ai/assessment/assessment-flow/overview)
 
 
-You will get multiple error codes in case of any failure. You can refer to the [error codes](/api-reference/health-ai/assessment/error-codes) for more details.
+**Ready to integrate intelligent health assessments?** Choose your integration method above and start building!
\ No newline at end of file
diff --git a/api-reference/health-ai/ekascribe/FHIR/Eka-FHIR-structure.mdx b/api-reference/health-ai/ekascribe/FHIR/Eka-FHIR-structure.mdx
new file mode 100644
index 00000000..1949757f
--- /dev/null
+++ b/api-reference/health-ai/ekascribe/FHIR/Eka-FHIR-structure.mdx
@@ -0,0 +1,264 @@
+---
+title: "Eka FHIR Structure"
+description: "FHIR resource mappings for Eka Care medical data"
+---
+
+# Eka FHIR Resource Mappings
+
+This document provides the FHIR (Fast Healthcare Interoperability Resources) mappings used by Eka Care for structured medical data. Each section details how Eka properties map to standard FHIR resources.
+
+---
+
+## Symptoms
+
+**FHIR Resource:** `Observation`
+
+Symptoms observed during patient consultations are stored using the FHIR Observation resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| symptoms.name, code | Observation.code | [Manifestation or Symptom](https://www.hl7.org/fhir/valueset-manifestation-or-symptom.html) | SNOMED, Eka codes |
+| symptoms.category | Observation.category | [Observation Category](https://terminology.hl7.org/5.1.0/CodeSystem-observation-category.html) | SNOMED: 418799008, MDB: s-8068301606 |
+| symptoms.status | Observation.status | [Observation Status](https://www.hl7.org/fhir/valueset-observation-status.html) | Voice2RX: `preliminary`, Rx: `final` |
+| symptoms.since | Observation.effective | - | effectiveDateTime \| effectivePeriod |
+| symptom.notes | Observation.note | [Annotation](https://www.hl7.org/fhir/datatypes.html#Annotation) | String text |
+| symptom.is-recorded-for | Observation.subject | - | Patient Reference |
+| symptoms.severity | Observation.value | [CodeableConcept](https://www.hl7.org/fhir/datatypes.html#CodeableConcept) | ValueCodeableConcept |
+| symptoms.laterality | Observation.bodySite | [Body Site](https://www.hl7.org/fhir/valueset-body-site.html#expansion) | CodeableConcept.coding.code |
+
+---
+
+## Conditions / Diagnoses
+
+**FHIR Resource:** `Condition`
+
+Medical conditions and diagnoses are stored using the FHIR Condition resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| condition.name, code | Condition.code | - | SNOMED |
+| condition.current_status | Condition.clinicalStatus | [Condition Clinical](https://build.fhir.org/valueset-condition-clinical.html) | Ruled-out: `inactive`, Confirmed: `active`, Suspected: `unknown` |
+| condition.verification | Condition.verificationStatus | [Verification Status](https://build.fhir.org/valueset-condition-ver-status.html) | Ruled-out: `refuted`, Confirmed: `confirmed`, Suspected: `unconfirmed` |
+| condition.severity | Condition.severity | [Condition Severity](https://build.fhir.org/valueset-condition-severity.html) | SNOMED: 24484000 (severe), 6736007 (moderate), 255604002 (mild) |
+| condition.category | Condition.category | [Condition Category](https://build.fhir.org/valueset-condition-category.html) | FHIR: `encounter-diagnosis` |
+| condition.since | Condition.onset | - | datetime \| period \| age \| string |
+| condition.is-recorded-for | Condition.subject | - | Patient |
+| condition.first-time-on | Condition.recordedDate | - | - |
+| condition.evidence | Condition.evidence | - | Evidence pointing to condition |
+| condition.where | Condition.bodyStructure | - | Has bodysite + other details |
+| condition.stage | Condition.stage | - | e.g., cancer stages |
+| condition.notes | Condition.note | - | Strings |
+| condition.laterality | Condition.bodySite | [Body Site](https://www.hl7.org/fhir/valueset-body-site.html#expansion) | CodeableConcept.coding.code |
+
+---
+
+## Medical History
+
+**FHIR Resource:** `Condition`
+
+Past medical history is also stored using the FHIR Condition resource with different category.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| condition.name, code | Condition.code | - | SNOMED |
+| condition.current_status | Condition.clinicalStatus | [Condition Clinical](https://build.fhir.org/valueset-condition-clinical.html) | Ruled-out: `inactive`, Confirmed: `active`, Suspected: `unknown` |
+| condition.verification | Condition.verificationStatus | [Verification Status](https://build.fhir.org/valueset-condition-ver-status.html) | Ruled-out: `refuted`, Confirmed: `confirmed`, Suspected: `unconfirmed` |
+| condition.severity | Condition.severity | [Condition Severity](https://build.fhir.org/valueset-condition-severity.html) | SNOMED codes for severity |
+| condition.category | Condition.category | [Condition Category](https://build.fhir.org/valueset-condition-category.html) | `problem-list-item` |
+| condition.since | Condition.onset | - | datetime \| period \| age \| string |
+| condition.is-recorded-for | Condition.subject | - | Patient |
+| condition.first-time-on | Condition.recordedDate | - | - |
+| condition.stage | Condition.stage | - | e.g., cancer stages |
+| condition.notes | Condition.note | - | Strings |
+
+---
+
+## Advices
+
+**FHIR Resource:** `CarePlan`
+
+Doctor's advice to patients is stored using the FHIR CarePlan resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| advice.status | CarePlan.status | - | `active` |
+| advice.intent | CarePlan.intent | [Care Plan Intent](https://build.fhir.org/valueset-care-plan-intent.html) | `plan` |
+| advice.category | CarePlan.category | - | Custom: SNOMED for advice |
+| advice.for | CarePlan.subject | - | Patient |
+| advice.details | CarePlan.activity.performedActivity | [CodeableReference](https://build.fhir.org/references.html#CodeableReference) | CodeableReference.concept.text |
+| advice.details | CarePlan.description | [CarePlan Description](https://build.fhir.org/careplan-definitions.html#CarePlan.description) | - |
+
+---
+
+## Notes
+
+**FHIR Resource:** `CarePlan`
+
+Clinical notes are stored using the FHIR CarePlan resource with different intent.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| notes.status | CarePlan.status | - | `active` |
+| notes.intent | CarePlan.intent | [Care Plan Intent](https://build.fhir.org/valueset-care-plan-intent.html) | `proposal` |
+| notes.category | CarePlan.category | - | Custom: for notes |
+| notes.for | CarePlan.subject | - | Patient |
+| notes.details | CarePlan.description | [CodeableReference](https://build.fhir.org/references.html#CodeableReference) | CodeableReference.concept.text |
+
+---
+
+## Examinations
+
+**FHIR Resource:** `Observation`
+
+Physical examination findings are stored using the FHIR Observation resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| exam.name, code | Observation.code | [Manifestation or Symptom](https://www.hl7.org/fhir/valueset-manifestation-or-symptom.html) | SNOMED, Eka codes |
+| exam.category | Observation.category | [Observation Category](https://terminology.hl7.org/5.1.0/CodeSystem-observation-category.html) | `exam` |
+| exam.status | Observation.status | [Observation Status](https://www.hl7.org/fhir/valueset-observation-status.html) | `preliminary` \| `final` \| `unknown` |
+| exam.since | Observation.effective | - | effectiveDateTime \| effectivePeriod |
+| exam.notes | Observation.note | [Annotation](https://www.hl7.org/fhir/datatypes.html#Annotation) | String |
+| exam.is-recorded-for | Observation.subject | - | Patient |
+| exam.location | Observation.bodySite | [Body Site](https://www.hl7.org/fhir/valueset-body-site.html#expansion) | - |
+
+---
+
+## Follow-Up
+
+**FHIR Resource:** `Appointment`
+
+Follow-up appointments suggested by doctors are stored using the FHIR Appointment resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| followup.status | Appointment.status | [Appointment Status](https://build.fhir.org/valueset-appointmentstatus.html) | `proposed` |
+| followup.type | Appointment.appointmentType | [Appointment Type](https://terminology.hl7.org/6.0.2/ValueSet-v2-0276.html) | `FOLLOWUP` |
+| followup.created | Appointment.created | - | - |
+| followup.start | Appointment.start | - | Instant |
+
+---
+
+## Family History
+
+**FHIR Resource:** `FamilyMemberHistory`
+
+Family medical history is stored using the FHIR FamilyMemberHistory resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| dataentry.status | FamilyMemberHistory.status | [History Status](https://build.fhir.org/valueset-history-status.html) | `completed` |
+| relation | FamilyMemberHistory.relationship | [Family Member](https://terminology.hl7.org/6.0.2/ValueSet-v3-FamilyMember.html) | - |
+| relative.name | FamilyMemberHistory.name | - | String |
+| remarks | FamilyMemberHistory.note | - | - |
+| clinical.status | FamilyMemberHistory.condition.outcome | - | CodeableConcept.coding.code |
+
+---
+
+## Vitals ( Trackers )
+
+**FHIR Resource:** `Observation`
+
+Patient vitals and health trackers are stored using the FHIR Observation resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| vitals.name, code | Observation.code | [Manifestation or Symptom](https://www.hl7.org/fhir/valueset-manifestation-or-symptom.html) | SNOMED, Eka codes |
+| vitals.category | Observation.category | [Observation Category](https://terminology.hl7.org/5.1.0/CodeSystem-observation-category.html) | SNOMED: s-8068301606, FHIR: `vital-signs` |
+| vitals.status | Observation.status | [Observation Status](https://www.hl7.org/fhir/valueset-observation-status.html) | Voice2RX: `preliminary`, Rx: `final` |
+| vitals.since | Observation.effective | - | effectiveDateTime \| effectivePeriod |
+| vitals.notes | Observation.note | [Annotation](https://www.hl7.org/fhir/datatypes.html#Annotation) | String text |
+| vitals.value | Observation.value | [CodeableConcept](https://www.hl7.org/fhir/datatypes.html#CodeableConcept) | ValueCodeableConcept |
+| vitals.components | Observation.component | - | For vitals like BP with multiple values |
+
+---
+
+## Medications
+
+**FHIR Resource:** `MedicationRequest`
+
+Medication prescriptions are stored using the FHIR MedicationRequest resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|--------------|---------------|-----------|-----------------|
+| medication.name, medication.id | MedicationRequest.medicationCodeableConcept | [Medication Codes](https://www.hl7.org/fhir/valueset-medication-codes.html) | Name : Ibuprofen 200mg; code: MDB/SNOMED |
+| medication.status | MedicationRequest.status | [MedicationRequest Status](https://www.hl7.org/fhir/valueset-medicationrequest-status.html) | `active` |
+| medication.intent | MedicationRequest.intent | [MedicationRequest Intent](https://www.hl7.org/fhir/valueset-medicationrequest-intent.html) | `order` |
+| patient.id, patient.profile.personal.name | MedicationRequest.subject | [Reference](https://www.hl7.org/fhir/references.html) | Patient reference |
+| doctor.id, doctor.profile.personal.name | MedicationRequest.requester | [Reference](https://www.hl7.org/fhir/references.html) | Practitioner reference |
+| date | MedicationRequest.authoredOn | [dateTime](https://www.hl7.org/fhir/datatypes.html#dateTime) | ISO 8601 format |
+| medication.instruction | MedicationRequest.dosageInstruction.text | [Dosage](https://www.hl7.org/fhir/dosage.html) | String |
+| medication.dose.value, dose.unit, dose.id, dose.custom | MedicationRequest.dosageInstruction.doseAndRate.doseQuantity | [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity) | value, unit, code |
+| medication.dose-rate-type | MedicationRequest.dosageInstruction.doseAndRate.type | [Dose Rate Type](https://www.hl7.org/fhir/valueset-dose-rate-type.html) | `ordered` |
+| medication.frequency.id, frequency.value, frequency.custom | MedicationRequest.dosageInstruction.additionalInstruction | [Additional Instruction](https://www.hl7.org/fhir/valueset-additional-instruction-codes.html) | CodeableConcept |
+| medication.frequency.frequency, frequency.period, frequency.period_unit, duration, duration-unit, when | MedicationRequest.dosageInstruction.timing.repeat | [Timing](https://www.hl7.org/fhir/datatypes.html#Timing) | frequency, period, periodUnit |
+| calculated | MedicationRequest.dispenseRequest.quantity | [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity) | frequency × duration × dose |
+---
+
+## Lab Tests / Imaging / Surgical Procedures
+**FHIR Resource:** `ServiceRequest`
+
+Lab tests, imaging requests ( radiology) and surgical procedure are stored using the FHIR ServiceRequest resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|-------------|---------------|-----------|-----------------|
+| status | ServiceRequest.status | [Request Status](https://www.hl7.org/fhir/valueset-request-status.html) | `active` |
+| intent | ServiceRequest.intent | [Request Intent](https://www.hl7.org/fhir/valueset-request-intent.html) | `order` |
+| category | ServiceRequest.category | [Service Request Category](https://www.hl7.org/fhir/valueset-servicerequest-category.html) | Supported categories are imaging, lab_test, surgical_procedure |
+| labTests.id, labTests.name | ServiceRequest.code | [Procedure Codes](https://www.hl7.org/fhir/valueset-procedure-code.html) | CodeableConcept from `http://eka.care/mdb`, `http://loinc.org`, `https://parchi.eka.care/local` |
+| patient_oid, patient_name | ServiceRequest.subject | [Reference](https://www.hl7.org/fhir/references.html) | Reference to Patient resource |
+| visitid | ServiceRequest.encounter | [Reference](https://www.hl7.org/fhir/references.html) | Reference to Encounter resource |
+| doctor_oid, doctor_name | ServiceRequest.requester | [Reference](https://www.hl7.org/fhir/references.html) | Reference to Practitioner resource |
+| date | ServiceRequest.authoredOn | [dateTime](https://www.hl7.org/fhir/datatypes.html#dateTime) | ISO 8601 format |
+| remark/notes | ServiceRequest.note | [Annotation](https://www.hl7.org/fhir/datatypes.html#Annotation) | Text note |
+
+---
+
+## DrugAllergy / FoodAllergy Intolerance
+**FHIR Resource:** `AllergyIntolerance`
+
+Food and medication allergies are stored using the FHIR AllergyIntolerance resource.
+
+| Eka Property | FHIR Resource | FHIR Link | Decision to Use |
+|-------------|---------------|-----------|-----------------|
+| doctor_oid, doctor_name | AllergyIntolerance.asserter | [Reference](https://www.hl7.org/fhir/references.html) | Reference to Practitioner resource |
+| category | AllergyIntolerance.category | [Allergy Category](https://www.hl7.org/fhir/valueset-allergy-intolerance-category.html) | `food` or `medication` |
+| clinicalStatus | AllergyIntolerance.clinicalStatus | [Clinical Status](https://www.hl7.org/fhir/valueset-allergyintolerance-clinical.html) | code: `active`, display: `Active` |
+| drugAllergy.id, foodOtherAllergy.id | AllergyIntolerance.code | [Allergy Codes](https://www.hl7.org/fhir/valueset-allergyintolerance-code.html) | CodeableConcept from `http://snomed.info/sct`, `http://eka.care/mdb`, `https://parchi.eka.care/local` |
+| criticality | AllergyIntolerance.criticality | [Allergy Criticality](https://www.hl7.org/fhir/valueset-allergy-intolerance-criticality.html) | `high` |
+| notes | AllergyIntolerance.note | [Annotation](https://www.hl7.org/fhir/datatypes.html#Annotation) | Text note |
+| patient_oid, patient_name | AllergyIntolerance.patient | [Reference](https://www.hl7.org/fhir/references.html) | Reference to Patient resource |
+| type | AllergyIntolerance.type | [Allergy Type](https://www.hl7.org/fhir/valueset-allergy-intolerance-type.html) | `allergy` |
+| recordedDate | AllergyIntolerance.recordedDate | [dateTime](https://www.hl7.org/fhir/datatypes.html#dateTime) | ISO 8601 format (current time) |
+| verificationStatus | AllergyIntolerance.verificationStatus | [Verification Status](https://www.hl7.org/fhir/valueset-allergyintolerance-verification.html) | code: `confirmed`, display: `Confirmed` |
+---
+
+# Summary Table
+
+| Data Type | FHIR Resource | Category/Type |
+|-----------|---------------|---------------|
+| Symptoms | Observation | signs-and-symptoms |
+| Conditions/Diagnoses | Condition | encounter-diagnosis |
+| Medical History | Condition | problem-list-item |
+| Advices | CarePlan | intent: plan |
+| Notes | CarePlan | intent: proposal |
+| Examinations | Observation | exam |
+| Follow-Up | Appointment | FOLLOWUP |
+| Family History | FamilyMemberHistory | - |
+| Vitals | Observation | vital-signs |
+| Medications | MedicationRequest | intent: order |
+| Lab Tests/Imaging/Surgical Procedures | ServiceRequest | imaging/lab_test/surgical_procedure |
+| Food and drug Allergies | AllergyIntolerance | food/medication |
+
+---
+
+## Complete FHIR Bundle Example
+
+<a href="/api-reference/health-ai/ekascribe/FHIR/fhir-bundle-example" target="_blank">
+  <Card
+    title="View Complete FHIR Bundle JSON"
+    icon="code"
+  >
+    Click here to view the full 3000+ line JSON example of a comprehensive FHIR Bundle including all mapped resources. (Opens in new tab)
+  </Card>
+</a>
diff --git a/api-reference/health-ai/ekascribe/FHIR/fhir-bundle-example.mdx b/api-reference/health-ai/ekascribe/FHIR/fhir-bundle-example.mdx
new file mode 100644
index 00000000..de33ef2e
--- /dev/null
+++ b/api-reference/health-ai/ekascribe/FHIR/fhir-bundle-example.mdx
@@ -0,0 +1,3020 @@
+---
+title: "Complete FHIR Bundle Example"
+description: "Full JSON example of the Eka FHIR Bundle"
+mode: "wide"
+---
+
+```json
+{
+  "entry": [
+    {
+      "request": {
+        "method": "PUT",
+        "url": "AllergyIntolerance/6a0841ca-46bf-5169-ba94-df396b21e999"
+      },
+      "resource": {
+        "id": "6a0841ca-46bf-5169-ba94-df396b21e999",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "mh-53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          "food"
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "active",
+              "display": "Active",
+              "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-45652c55c95428ea51e58155fee07af5",
+              "display": "Banana intolerance",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "criticality": "high",
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-45652c55c95428ea51e58155fee07af5"
+          }
+        ],
+        "note": [
+          {
+            "text": "Causes itching"
+          }
+        ],
+        "patient": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "recordedDate": "2025-12-12T16:04:14.452266+00:00",
+        "type": "allergy",
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "confirmed",
+              "display": "Confirmed",
+              "system": "http://terminology.hl7.org/CodeSystem/allergyintolerance-verification"
+            }
+          ]
+        },
+        "resourceType": "AllergyIntolerance"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Appointment/1a6610b4-a69e-57cc-9d0f-3f940c9449a8"
+      },
+      "resource": {
+        "id": "1a6610b4-a69e-57cc-9d0f-3f940c9449a8",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "appointmentType": {
+          "coding": [
+            {
+              "code": "FOLLOWUP",
+              "display": "Follow-up",
+              "system": "http://terminology.hl7.org/CodeSystem/v2-0276"
+            }
+          ]
+        },
+        "created": "2025-12-12T10:34:14.410092+00:00",
+        "description": "Follow up advised in 3-5 days after test results are available",
+        "end": "2025-12-15T00:00:00+00:00",
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#appointment"
+          }
+        ],
+        "participant": [
+          {
+            "actor": {
+              "display": "dummy_patient",
+              "reference": "Patient/dummy_patient_oid"
+            },
+            "status": "accepted"
+          }
+        ],
+        "start": "2025-12-15T00:00:00+00:00",
+        "status": "proposed",
+        "resourceType": "Appointment"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/7d38dfba-9bdb-5834-9eee-f8aa545aa5cb"
+      },
+      "resource": {
+        "id": "7d38dfba-9bdb-5834-9eee-f8aa545aa5cb",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "encounter-diagnosis",
+                "display": "Encounter Diagnosis",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "inactive",
+              "display": "inactive",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-97f95df7ab182ac40f0e48c5d1dfbbbb",
+              "display": "Acid reflux",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-97f95df7ab182ac40f0e48c5d1dfbbbb"
+          }
+        ],
+        "note": [
+          {
+            "text": "Working diagnosis based on symptoms and examination"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "suspected",
+              "display": "suspected",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/d51b2db3-6060-565b-a918-bd0a4e140c31"
+      },
+      "resource": {
+        "id": "d51b2db3-6060-565b-a918-bd0a4e140c31",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "encounter-diagnosis",
+                "display": "Encounter Diagnosis",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "inactive",
+              "display": "inactive",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-4ab621252040a372c8667a885de40f6f",
+              "display": "Gastritis",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-4ab621252040a372c8667a885de40f6f"
+          }
+        ],
+        "note": [
+          {
+            "text": "Working diagnosis based on symptoms and examination"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "suspected",
+              "display": "suspected",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/baa81103-658c-58dc-9986-c4fc1ab220a2"
+      },
+      "resource": {
+        "id": "baa81103-658c-58dc-9986-c4fc1ab220a2",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "encounter-diagnosis",
+                "display": "Encounter Diagnosis",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "inactive",
+              "display": "inactive",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-308ec5a00860dfcb2af8a5f156506860",
+              "display": "Dyspepsia",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-308ec5a00860dfcb2af8a5f156506860"
+          }
+        ],
+        "note": [
+          {
+            "text": "Working diagnosis based on symptoms and examination, related to intermittent abdominal pain"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "suspected",
+              "display": "suspected",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/a4dc0582-3010-57e2-b5fc-5530622ba8fa"
+      },
+      "resource": {
+        "id": "a4dc0582-3010-57e2-b5fc-5530622ba8fa",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "problem-list-item",
+                "display": "Problem List Item",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "active",
+              "display": "active",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-37f54c55ea395e99dae2a324bd47688c",
+              "display": "Gastric issue",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-37f54c55ea395e99dae2a324bd47688c"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "confirmed",
+              "display": "confirmed",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/84261bbe-790c-54bf-ac2a-bc4d9c7439bd"
+      },
+      "resource": {
+        "id": "84261bbe-790c-54bf-ac2a-bc4d9c7439bd",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "problem-list-item",
+                "display": "Problem List Item",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "active",
+              "display": "active",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-3c47e65837e019511242d1b65943954e",
+              "display": "Allergic rhinitis",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-3c47e65837e019511242d1b65943954e"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "confirmed",
+              "display": "confirmed",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Condition/e49ff164-dc27-5486-b7d8-479e69cec534"
+      },
+      "resource": {
+        "id": "e49ff164-dc27-5486-b7d8-479e69cec534",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "asserter": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "problem-list-item",
+                "display": "Problem List Item",
+                "system": "http://terminology.hl7.org/CodeSystem/condition-category"
+              }
+            ]
+          }
+        ],
+        "clinicalStatus": {
+          "coding": [
+            {
+              "code": "inactive",
+              "display": "inactive",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "code": {
+          "coding": [
+            {
+              "code": "locale-4307395708f2c5e132701afcfea5f46f",
+              "display": "Migraine",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "evidence": [
+          {
+            "code": [
+              {
+                "coding": [
+                  {
+                    "code": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2",
+                    "system": "https://www.eka.care/prescriptions"
+                  }
+                ]
+              }
+            ]
+          }
+        ],
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-4307395708f2c5e132701afcfea5f46f"
+          }
+        ],
+        "note": [
+          {
+            "text": "Occasional episodes in the past, currently not active"
+          }
+        ],
+        "recordedDate": "2025-12-12T10:34:14.410092+00:00",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "verificationStatus": {
+          "coding": [
+            {
+              "code": "refuted",
+              "display": "refuted",
+              "system": "http://terminology.hl7.org/CodeSystem/condition-clinical"
+            }
+          ]
+        },
+        "resourceType": "Condition"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/3a230b5a-ef2b-5d76-9e18-90f321000e8a"
+      },
+      "resource": {
+        "id": "3a230b5a-ef2b-5d76-9e18-90f321000e8a",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.472747+00:00",
+        "description": "Follow the medication schedule strictly",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-42d19e7fdb84acc68a988baaf186ca9f"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/54b505c4-52f2-5481-9fe7-60bc90ab40a9"
+      },
+      "resource": {
+        "id": "54b505c4-52f2-5481-9fe7-60bc90ab40a9",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.473296+00:00",
+        "description": "Complete the recommended tests",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-4fe34c1270db070636da3398a0f30cb3"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/9ef7c35a-f898-5fc2-90b2-431a025ae8e2"
+      },
+      "resource": {
+        "id": "9ef7c35a-f898-5fc2-90b2-431a025ae8e2",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.473802+00:00",
+        "description": "Avoid known food triggers",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-0b2381ce17f4ec7f8e58615651b1ffb4"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/c26f4429-1671-5920-90ff-23c185f15e54"
+      },
+      "resource": {
+        "id": "c26f4429-1671-5920-90ff-23c185f15e54",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.474302+00:00",
+        "description": "Monitor symptoms",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-6b2a6f4cf15428f0a06d5c5ed61db097"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/1e84f116-3b97-50b3-9ef6-09a16295203b"
+      },
+      "resource": {
+        "id": "1e84f116-3b97-50b3-9ef6-09a16295203b",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.474796+00:00",
+        "description": "Avoid spicy and oily food",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-dabbd37531374f42436a91b6b835cf6d"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/bd4b3fd2-7941-5ada-9256-a21ab6a9583f"
+      },
+      "resource": {
+        "id": "bd4b3fd2-7941-5ada-9256-a21ab6a9583f",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.475298+00:00",
+        "description": "Have early and light dinners",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-6f9ecff5eaa8bf922b6f69433b298201"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/87753a7f-be1a-58ca-af6d-f31aff262a0a"
+      },
+      "resource": {
+        "id": "87753a7f-be1a-58ca-af6d-f31aff262a0a",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.475791+00:00",
+        "description": "Avoid tea or coffee on an empty stomach",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-91ecff0e501c7f9f488654b5d16eb09b"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/62b3a87e-010a-5bb3-bdf8-8d5834e7620b"
+      },
+      "resource": {
+        "id": "62b3a87e-010a-5bb3-bdf8-8d5834e7620b",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.476309+00:00",
+        "description": "Drink adequate water",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-db441d1f6e4785b2b1e16723ad2c3836"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/8963b4b5-ddc7-5e10-acb5-8fc75139bc24"
+      },
+      "resource": {
+        "id": "8963b4b5-ddc7-5e10-acb5-8fc75139bc24",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.476850+00:00",
+        "description": "Manage stress",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-749454cfdd89100fa35c70d6dbb27956"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/43e405f2-cf6a-5e98-b8bf-56441494e3b6"
+      },
+      "resource": {
+        "id": "43e405f2-cf6a-5e98-b8bf-56441494e3b6",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.477343+00:00",
+        "description": "Get 7-8 hours of sleep",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-cd08f4f60267c6792d6b8efbdd423bf2"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/2c61e7a0-61a1-569c-a0ab-e4d620aaaba1"
+      },
+      "resource": {
+        "id": "2c61e7a0-61a1-569c-a0ab-e4d620aaaba1",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "386464006",
+                "display": "Medical advice",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.477831+00:00",
+        "description": "Avoid banana for now, reintroduce gradually if symptoms settle",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-4544e3b00dc19d63c2eb90e57c67af33"
+          }
+        ],
+        "intent": "plan",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "CarePlan/1ae0ac1b-5a7a-5578-a50a-e7a71c81ef6e"
+      },
+      "resource": {
+        "id": "1ae0ac1b-5a7a-5578-a50a-e7a71c81ef6e",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "371530004",
+                "display": "Clinical note",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "created": "2025-12-12T16:04:14.478328+00:00",
+        "description": "The patient is advised dietary and lifestyle modifications including avoiding spicy and oily food, having early and light dinners, avoiding tea or coffee on an empty stomach, drinking adequate water, managing stress, getting 7-8 hours of sleep, and working properly. The patient is also advised to avoid banana for now due to mild allergies and reintroduce gradually if symptoms settle. Fasting for 8 to 10 hours is required for imaging tests. No known red flag symptoms at present.",
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#b3e20a60-9a63-4db0-98bf-d2047f4d7643"
+          }
+        ],
+        "intent": "proposal",
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "CarePlan"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/46a3c331-dc6e-5371-9a61-7747654b4379"
+      },
+      "resource": {
+        "id": "46a3c331-dc6e-5371-9a61-7747654b4379",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "108252007",
+                "display": "Laboratory procedure",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-e53edc51a4a40d10ae24cce03b46e3a0",
+              "display": "Complete blood count",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-e53edc51a4a40d10ae24cce03b46e3a0"
+          }
+        ],
+        "intent": "order",
+        "note": [
+          {
+            "text": "To rule out infection"
+          }
+        ],
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/bed2f3a8-2a10-5fb8-baeb-611674d697a5"
+      },
+      "resource": {
+        "id": "bed2f3a8-2a10-5fb8-baeb-611674d697a5",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "108252007",
+                "display": "Laboratory procedure",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-b1594238c0f99d3191650dc0e14d3a32",
+              "display": "Fasting blood sugar",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-b1594238c0f99d3191650dc0e14d3a32"
+          }
+        ],
+        "intent": "order",
+        "note": [
+          {
+            "text": "To rule out sugar imbalance"
+          }
+        ],
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/fbcc5bc7-b79c-567c-8598-21e927ba67ef"
+      },
+      "resource": {
+        "id": "fbcc5bc7-b79c-567c-8598-21e927ba67ef",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "108252007",
+                "display": "Laboratory procedure",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-adecb0c53f640a31ed2c1ea3e67ff02e",
+              "display": "Liver function test",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-adecb0c53f640a31ed2c1ea3e67ff02e"
+          }
+        ],
+        "intent": "order",
+        "note": [
+          {
+            "text": "To rule out liver related issues"
+          }
+        ],
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/579b1c10-6c6c-5b55-963a-707bd53e9c5e"
+      },
+      "resource": {
+        "id": "579b1c10-6c6c-5b55-963a-707bd53e9c5e",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "108252007",
+                "display": "Laboratory procedure",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-487b7e9702affe76e2a3c1bdff7b06b4",
+              "display": "Urine routine and microscopy",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-487b7e9702affe76e2a3c1bdff7b06b4"
+          }
+        ],
+        "intent": "order",
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/bb9e687e-9f67-5088-b071-bf13bea65208"
+      },
+      "resource": {
+        "id": "bb9e687e-9f67-5088-b071-bf13bea65208",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "363679005",
+                "display": "Imaging",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-3fed2664e046e71b0a5619610a2d302b",
+              "display": "Chest X-ray PA view",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-3fed2664e046e71b0a5619610a2d302b"
+          }
+        ],
+        "intent": "order",
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/0ac5af5a-38d0-5bcb-b3da-7dd3cafcfccb"
+      },
+      "resource": {
+        "id": "0ac5af5a-38d0-5bcb-b3da-7dd3cafcfccb",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "363679005",
+                "display": "Imaging",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-66fd7fb2a1ae6c2e0d989200d0aa27fb",
+              "display": "Ultrasound of abdomen and pelvis",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-66fd7fb2a1ae6c2e0d989200d0aa27fb"
+          }
+        ],
+        "intent": "order",
+        "note": [
+          {
+            "text": "To assess the abdominal organs and evaluate the cause of discomfort"
+          }
+        ],
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "ServiceRequest/08d590cc-cc16-5f79-959f-8c20e79b4046"
+      },
+      "resource": {
+        "id": "08d590cc-cc16-5f79-959f-8c20e79b4046",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410092+00:00",
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "387713003",
+                "display": "Surgical procedure",
+                "system": "http://snomed.info/sct"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-7adcac021efc5fe6525924f9213709e4",
+              "display": "Diagnostic endoscopy",
+              "system": "https://www.eka.care/local"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-7adcac021efc5fe6525924f9213709e4"
+          }
+        ],
+        "intent": "order",
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "ServiceRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/788869c9-bdc5-5b2a-9ff3-8dcf3e4206d1"
+      },
+      "resource": {
+        "id": "788869c9-bdc5-5b2a-9ff3-8dcf3e4206d1",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-f8a79ef309a886ba94602ec9429dd5b1",
+              "display": "Abdominal pain",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-f8a79ef309a886ba94602ec9429dd5b1"
+          }
+        ],
+        "note": [
+          {
+            "text": "Intermittent"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/f795b0e4-4de5-5e87-ba17-c1eb6070a19d"
+      },
+      "resource": {
+        "id": "f795b0e4-4de5-5e87-ba17-c1eb6070a19d",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-d8ac2007dfc6d117ded6a46e77603358",
+              "display": "Burning sensation",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-d8ac2007dfc6d117ded6a46e77603358"
+          }
+        ],
+        "note": [
+          {
+            "text": "In the upper abdomen"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/a846136a-f3a7-57e6-bb18-7e852ee4ab2e"
+      },
+      "resource": {
+        "id": "a846136a-f3a7-57e6-bb18-7e852ee4ab2e",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-c82b6bd3c496e89f5da5ccbe73fa11c1",
+              "display": "Sour taste",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-c82b6bd3c496e89f5da5ccbe73fa11c1"
+          }
+        ],
+        "note": [
+          {
+            "text": "Early morning"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/a9abe391-4555-529b-86ec-f6f5b266d30f"
+      },
+      "resource": {
+        "id": "a9abe391-4555-529b-86ec-f6f5b266d30f",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-380f43098d377b1705af989748de525f",
+              "display": "Headache",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-380f43098d377b1705af989748de525f"
+          }
+        ],
+        "note": [
+          {
+            "text": "Occasional"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/b2fe71a2-dfad-5169-ac59-413688daa446"
+      },
+      "resource": {
+        "id": "b2fe71a2-dfad-5169-ac59-413688daa446",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-83dbceb6d763ebb17cc387eccf42d052",
+              "display": "Nasal congestion",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-83dbceb6d763ebb17cc387eccf42d052"
+          }
+        ],
+        "note": [
+          {
+            "text": "Slightly present"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/c2154b8d-3304-5243-b72d-34e777e2c6d8"
+      },
+      "resource": {
+        "id": "c2154b8d-3304-5243-b72d-34e777e2c6d8",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "symptom",
+                "display": "symptom",
+                "system": "https://www.custom.code"
+              }
+            ]
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-a9df378813d31194b7d07d81646dd4c2",
+              "display": "Bloating",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-a9df378813d31194b7d07d81646dd4c2"
+          }
+        ],
+        "note": [
+          {
+            "text": "After meal"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/c24a52f6-da61-5d81-a7c4-68ce793c3356"
+      },
+      "resource": {
+        "id": "c24a52f6-da61-5d81-a7c4-68ce793c3356",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "vital-signs",
+                "display": "Vital Signs",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "Vital Signs"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "v-1365277675",
+              "display": "Blood pressure",
+              "system": "https://www.custom.code/technical"
+            }
+          ]
+        },
+        "component": [
+          {
+            "code": {
+              "coding": [
+                {
+                  "code": "lb-8296133834",
+                  "display": "Diastolic Blood Pressure",
+                  "system": "https://www.custom.code/technical"
+                },
+                {
+                  "code": "75367002",
+                  "display": "Diastolic Blood Pressure",
+                  "system": "http://snomed.info/sct"
+                }
+              ]
+            },
+            "valueQuantity": {
+              "code": "lu-736638821",
+              "system": "https://www.eka.care/mdb/technical",
+              "unit": "mmHg",
+              "value": 128
+            }
+          },
+          {
+            "code": {
+              "coding": [
+                {
+                  "code": "lb-9242267093",
+                  "display": "Systolic Blood Pressure",
+                  "system": "https://www.custom.code/technical"
+                },
+                {
+                  "code": "75367002",
+                  "display": "Systolic Blood Pressure",
+                  "system": "http://snomed.info/sct"
+                }
+              ]
+            },
+            "valueQuantity": {
+              "code": "lu-736638821",
+              "system": "https://www.eka.care/mdb/technical",
+              "unit": "mmHg",
+              "value": 84
+            }
+          }
+        ],
+        "effectiveDateTime": "2025-12-12T10:34:14.410092+00:00",
+        "encounter": {
+          "reference": "Encounter/53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#v-1365277675"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/d92330a9-ff09-5542-a9e7-a41d70b26aa4"
+      },
+      "resource": {
+        "id": "d92330a9-ff09-5542-a9e7-a41d70b26aa4",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "vital-signs",
+                "display": "Vital Signs",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "Vital Signs"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "lb-1201285132",
+              "display": "Pulse rate",
+              "system": "https://www.custom.code/technical"
+            },
+            {
+              "code": "78564009",
+              "display": "Pulse rate",
+              "system": "http://snomed.info/sct"
+            }
+          ]
+        },
+        "effectiveDateTime": "2025-12-12T10:34:14.410092+00:00",
+        "encounter": {
+          "reference": "Encounter/53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#lb-1201285132"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "valueQuantity": {
+          "system": "https://www.eka.care/mdb/technical",
+          "unit": "bpm",
+          "value": 82.0
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/c101b5ef-333d-538b-bd60-cdbd23b3f708"
+      },
+      "resource": {
+        "id": "c101b5ef-333d-538b-bd60-cdbd23b3f708",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "vital-signs",
+                "display": "Vital Signs",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "Vital Signs"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "lb-199711567",
+              "display": "Temperature",
+              "system": "https://www.custom.code/technical"
+            },
+            {
+              "code": "386725007",
+              "display": "Temperature",
+              "system": "http://snomed.info/sct"
+            }
+          ]
+        },
+        "effectiveDateTime": "2025-12-12T10:34:14.410092+00:00",
+        "encounter": {
+          "reference": "Encounter/53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#lb-199711567"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "valueQuantity": {
+          "system": "https://www.eka.care/mdb/technical",
+          "unit": "°F",
+          "value": 98.4
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/6a73a85d-f99e-57e0-aae1-7cdd3a2e4864"
+      },
+      "resource": {
+        "id": "6a73a85d-f99e-57e0-aae1-7cdd3a2e4864",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "vital-signs",
+                "display": "Vital Signs",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "Vital Signs"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "lb-1771358750",
+              "display": "Oxygen saturation",
+              "system": "https://www.custom.code/technical"
+            }
+          ]
+        },
+        "effectiveDateTime": "2025-12-12T10:34:14.410092+00:00",
+        "encounter": {
+          "reference": "Encounter/53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#lb-1771358750"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "valueQuantity": {
+          "system": "https://www.eka.care/mdb/technical",
+          "unit": "%",
+          "value": 98.0
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/b2ac8bfa-f26c-516f-b8b1-3f1badac1362"
+      },
+      "resource": {
+        "id": "b2ac8bfa-f26c-516f-b8b1-3f1badac1362",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "exam",
+                "display": "exam",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "exam"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-10cc52cdcf768e0de5c5cb8f2c7c392c",
+              "display": "Abdominal examination",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-10cc52cdcf768e0de5c5cb8f2c7c392c"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/a98e36a8-231c-5033-a77b-5c1b0601d84c"
+      },
+      "resource": {
+        "id": "a98e36a8-231c-5033-a77b-5c1b0601d84c",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "exam",
+                "display": "exam",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "exam"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-a203eeec31398c30560cda36f182c1e9",
+              "display": "Nasal examination",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-a203eeec31398c30560cda36f182c1e9"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "Observation/70fa9d39-88f8-55a0-a440-220f791c0a21"
+      },
+      "resource": {
+        "id": "70fa9d39-88f8-55a0-a440-220f791c0a21",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "category": [
+          {
+            "coding": [
+              {
+                "code": "exam",
+                "display": "exam",
+                "system": "http://terminology.hl7.org/CodeSystem/observation-category"
+              }
+            ],
+            "text": "exam"
+          }
+        ],
+        "code": {
+          "coding": [
+            {
+              "code": "locale-ff872e79afb817c097203685d3f3010e",
+              "display": "Systematic examination",
+              "system": "https://www.eka.care"
+            }
+          ]
+        },
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-ff872e79afb817c097203685d3f3010e"
+          }
+        ],
+        "performer": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "status": "final",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "Observation"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "MedicationRequest/71747c56-19dc-58e5-ab73-bb45b37f0a44"
+      },
+      "resource": {
+        "id": "71747c56-19dc-58e5-ab73-bb45b37f0a44",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410000+00:00",
+        "dispenseRequest": {
+          "quantity": {
+            "system": "https://www.eka.care/mdb",
+            "unit": "tablet",
+            "value": 10
+          }
+        },
+        "dosageInstruction": [
+          {
+            "additionalInstruction": [
+              {
+                "coding": [
+                  {
+                    "display": "1-0-0",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              }
+            ],
+            "doseAndRate": [
+              {
+                "doseQuantity": {
+                  "system": "https://www.eka.care/mdb",
+                  "unit": "tablet",
+                  "value": 1
+                },
+                "type": {
+                  "coding": [
+                    {
+                      "code": "ordered",
+                      "display": "Ordered",
+                      "system": "http://terminology.hl7.org/CodeSystem/dose-rate-type"
+                    }
+                  ]
+                }
+              }
+            ],
+            "text": "To reduce stomach acid",
+            "timing": {
+              "code": {
+                "coding": [
+                  {
+                    "display": "on empty stomach",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              },
+              "repeat": {
+                "duration": 10,
+                "durationUnit": "d",
+                "frequency": 1,
+                "period": 1,
+                "periodUnit": "d",
+                "when": [
+                  "MORN"
+                ]
+              }
+            }
+          }
+        ],
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "use": "official",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-34e44334caaf5b59d3330526f322661b"
+          }
+        ],
+        "intent": "order",
+        "medicationCodeableConcept": {
+          "coding": [
+            {
+              "code": "locale-34e44334caaf5b59d3330526f322661b",
+              "display": "Pantoprazole 40 mg",
+              "system": "https://www.eka.care/mdb"
+            }
+          ]
+        },
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/None"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "MedicationRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "MedicationRequest/1f8fcdc1-e658-5530-a120-b19965076740"
+      },
+      "resource": {
+        "id": "1f8fcdc1-e658-5530-a120-b19965076740",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410000+00:00",
+        "dispenseRequest": {
+          "quantity": {
+            "system": "https://www.eka.care/mdb",
+            "unit": "tablet",
+            "value": 10
+          }
+        },
+        "dosageInstruction": [
+          {
+            "additionalInstruction": [
+              {
+                "coding": [
+                  {
+                    "display": "0-1-1",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              }
+            ],
+            "doseAndRate": [
+              {
+                "doseQuantity": {
+                  "system": "https://www.eka.care/mdb",
+                  "unit": "tablet",
+                  "value": 1
+                },
+                "type": {
+                  "coding": [
+                    {
+                      "code": "ordered",
+                      "display": "Ordered",
+                      "system": "http://terminology.hl7.org/CodeSystem/dose-rate-type"
+                    }
+                  ]
+                }
+              }
+            ],
+            "text": "For abdominal cramps",
+            "timing": {
+              "code": {
+                "coding": [
+                  {
+                    "code": "tpr1$ta5",
+                    "display": "after meal",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              },
+              "repeat": {
+                "duration": 5,
+                "durationUnit": "d",
+                "frequency": 2,
+                "period": 1,
+                "periodUnit": "d",
+                "when": [
+                  "AFT",
+                  "NIGHT"
+                ]
+              }
+            }
+          }
+        ],
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "use": "official",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-36c66e1c0745cce3d9d00b24e90a3cef"
+          }
+        ],
+        "intent": "order",
+        "medicationCodeableConcept": {
+          "coding": [
+            {
+              "code": "locale-36c66e1c0745cce3d9d00b24e90a3cef",
+              "display": "Dicyclomine 10 mg",
+              "system": "https://www.eka.care/mdb"
+            }
+          ]
+        },
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/None"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "MedicationRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "PUT",
+        "url": "MedicationRequest/fa49c610-f4d3-519e-89e2-1814ee6f1f72"
+      },
+      "resource": {
+        "id": "fa49c610-f4d3-519e-89e2-1814ee6f1f72",
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "authoredOn": "2025-12-12T10:34:14.410000+00:00",
+        "dispenseRequest": {
+          "quantity": {
+            "system": "https://www.eka.care/mdb",
+            "unit": "ml",
+            "value": 140
+          }
+        },
+        "dosageInstruction": [
+          {
+            "additionalInstruction": [
+              {
+                "coding": [
+                  {
+                    "display": "0-1-1",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              }
+            ],
+            "doseAndRate": [
+              {
+                "doseQuantity": {
+                  "system": "https://www.eka.care/mdb",
+                  "unit": "ml",
+                  "value": 10
+                },
+                "type": {
+                  "coding": [
+                    {
+                      "code": "ordered",
+                      "display": "Ordered",
+                      "system": "http://terminology.hl7.org/CodeSystem/dose-rate-type"
+                    }
+                  ]
+                }
+              }
+            ],
+            "text": "For quick relief from burning and acidity",
+            "timing": {
+              "code": {
+                "coding": [
+                  {
+                    "code": "tpr1$ta5",
+                    "display": "after meal",
+                    "system": "https://www.eka.care/"
+                  }
+                ]
+              },
+              "repeat": {
+                "duration": 7,
+                "durationUnit": "d",
+                "frequency": 2,
+                "period": 1,
+                "periodUnit": "d",
+                "when": [
+                  "AFT",
+                  "NIGHT"
+                ]
+              }
+            }
+          }
+        ],
+        "encounter": {
+          "reference": "Encounter/edfad957-7379-5416-a97c-45982d9cb531"
+        },
+        "identifier": [
+          {
+            "system": "https://www.eka.care",
+            "use": "official",
+            "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2#locale-7547a072463fc3e549f4a6f85f5acfbb"
+          }
+        ],
+        "intent": "order",
+        "medicationCodeableConcept": {
+          "coding": [
+            {
+              "code": "locale-7547a072463fc3e549f4a6f85f5acfbb",
+              "display": "Antacid syrup",
+              "system": "https://www.eka.care/mdb"
+            }
+          ]
+        },
+        "requester": {
+          "display": "dummy doctor",
+          "reference": "Practitioner/None"
+        },
+        "status": "active",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "resourceType": "MedicationRequest"
+      }
+    },
+    {
+      "request": {
+        "method": "POST",
+        "url": "Composition"
+      },
+      "resource": {
+        "extension": [
+          {
+            "url": "https://www.eka.care/care_context_id",
+            "valueString": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+          }
+        ],
+        "author": [
+          {
+            "display": "dummy doctor",
+            "reference": "Practitioner/"
+          }
+        ],
+        "date": "2025-12-12T10:34:14.410092+00:00",
+        "identifier": {
+          "system": "https://www.eka.care",
+          "value": "53c5592a-9e86-4dfs53aabcdda--vicky-12-dec-test-2"
+        },
+        "section": [
+          {
+            "entry": [
+              {
+                "reference": "AllergyIntolerance/6a0841ca-46bf-5169-ba94-df396b21e999"
+              }
+            ],
+            "title": "AllergyIntolerance"
+          },
+          {
+            "entry": [
+              {
+                "reference": "Appointment/1a6610b4-a69e-57cc-9d0f-3f940c9449a8"
+              }
+            ],
+            "title": "Appointment"
+          },
+          {
+            "entry": [
+              {
+                "reference": "Condition/7d38dfba-9bdb-5834-9eee-f8aa545aa5cb"
+              },
+              {
+                "reference": "Condition/d51b2db3-6060-565b-a918-bd0a4e140c31"
+              },
+              {
+                "reference": "Condition/baa81103-658c-58dc-9986-c4fc1ab220a2"
+              },
+              {
+                "reference": "Condition/a4dc0582-3010-57e2-b5fc-5530622ba8fa"
+              },
+              {
+                "reference": "Condition/84261bbe-790c-54bf-ac2a-bc4d9c7439bd"
+              },
+              {
+                "reference": "Condition/e49ff164-dc27-5486-b7d8-479e69cec534"
+              }
+            ],
+            "title": "Condition"
+          },
+          {
+            "entry": [
+              {
+                "reference": "CarePlan/3a230b5a-ef2b-5d76-9e18-90f321000e8a"
+              },
+              {
+                "reference": "CarePlan/54b505c4-52f2-5481-9fe7-60bc90ab40a9"
+              },
+              {
+                "reference": "CarePlan/9ef7c35a-f898-5fc2-90b2-431a025ae8e2"
+              },
+              {
+                "reference": "CarePlan/c26f4429-1671-5920-90ff-23c185f15e54"
+              },
+              {
+                "reference": "CarePlan/1e84f116-3b97-50b3-9ef6-09a16295203b"
+              },
+              {
+                "reference": "CarePlan/bd4b3fd2-7941-5ada-9256-a21ab6a9583f"
+              },
+              {
+                "reference": "CarePlan/87753a7f-be1a-58ca-af6d-f31aff262a0a"
+              },
+              {
+                "reference": "CarePlan/62b3a87e-010a-5bb3-bdf8-8d5834e7620b"
+              },
+              {
+                "reference": "CarePlan/8963b4b5-ddc7-5e10-acb5-8fc75139bc24"
+              },
+              {
+                "reference": "CarePlan/43e405f2-cf6a-5e98-b8bf-56441494e3b6"
+              },
+              {
+                "reference": "CarePlan/2c61e7a0-61a1-569c-a0ab-e4d620aaaba1"
+              },
+              {
+                "reference": "CarePlan/1ae0ac1b-5a7a-5578-a50a-e7a71c81ef6e"
+              }
+            ],
+            "title": "CarePlan"
+          },
+          {
+            "entry": [
+              {
+                "reference": "ServiceRequest/46a3c331-dc6e-5371-9a61-7747654b4379"
+              },
+              {
+                "reference": "ServiceRequest/bed2f3a8-2a10-5fb8-baeb-611674d697a5"
+              },
+              {
+                "reference": "ServiceRequest/fbcc5bc7-b79c-567c-8598-21e927ba67ef"
+              },
+              {
+                "reference": "ServiceRequest/579b1c10-6c6c-5b55-963a-707bd53e9c5e"
+              },
+              {
+                "reference": "ServiceRequest/bb9e687e-9f67-5088-b071-bf13bea65208"
+              },
+              {
+                "reference": "ServiceRequest/0ac5af5a-38d0-5bcb-b3da-7dd3cafcfccb"
+              },
+              {
+                "reference": "ServiceRequest/08d590cc-cc16-5f79-959f-8c20e79b4046"
+              }
+            ],
+            "title": "ServiceRequest"
+          },
+          {
+            "entry": [
+              {
+                "reference": "Observation/788869c9-bdc5-5b2a-9ff3-8dcf3e4206d1"
+              },
+              {
+                "reference": "Observation/f795b0e4-4de5-5e87-ba17-c1eb6070a19d"
+              },
+              {
+                "reference": "Observation/a846136a-f3a7-57e6-bb18-7e852ee4ab2e"
+              },
+              {
+                "reference": "Observation/a9abe391-4555-529b-86ec-f6f5b266d30f"
+              },
+              {
+                "reference": "Observation/b2fe71a2-dfad-5169-ac59-413688daa446"
+              },
+              {
+                "reference": "Observation/c2154b8d-3304-5243-b72d-34e777e2c6d8"
+              },
+              {
+                "reference": "Observation/c24a52f6-da61-5d81-a7c4-68ce793c3356"
+              },
+              {
+                "reference": "Observation/d92330a9-ff09-5542-a9e7-a41d70b26aa4"
+              },
+              {
+                "reference": "Observation/c101b5ef-333d-538b-bd60-cdbd23b3f708"
+              },
+              {
+                "reference": "Observation/6a73a85d-f99e-57e0-aae1-7cdd3a2e4864"
+              },
+              {
+                "reference": "Observation/b2ac8bfa-f26c-516f-b8b1-3f1badac1362"
+              },
+              {
+                "reference": "Observation/a98e36a8-231c-5033-a77b-5c1b0601d84c"
+              },
+              {
+                "reference": "Observation/70fa9d39-88f8-55a0-a440-220f791c0a21"
+              }
+            ],
+            "title": "Observation"
+          },
+          {
+            "entry": [
+              {
+                "reference": "MedicationRequest/71747c56-19dc-58e5-ab73-bb45b37f0a44"
+              },
+              {
+                "reference": "MedicationRequest/1f8fcdc1-e658-5530-a120-b19965076740"
+              },
+              {
+                "reference": "MedicationRequest/fa49c610-f4d3-519e-89e2-1814ee6f1f72"
+              }
+            ],
+            "title": "MedicationRequest"
+          }
+        ],
+        "status": "preliminary",
+        "subject": {
+          "display": "dummy_patient",
+          "reference": "Patient/dummy_patient_oid"
+        },
+        "title": "Prescription",
+        "type": {
+          "coding": [
+            {
+              "code": "440545006",
+              "display": "Prescription record",
+              "system": "http://snomed.info/sct"
+            }
+          ]
+        },
+        "resourceType": "Composition"
+      }
+    }
+  ],
+  "type": "batch",
+  "resourceType": "Bundle"
+}
+```
diff --git a/api-reference/health-ai/ekascribe/SDKs/TS-sdk.mdx b/api-reference/health-ai/ekascribe/SDKs/TS-sdk.mdx
index 07c71a15..cfb784f5 100644
--- a/api-reference/health-ai/ekascribe/SDKs/TS-sdk.mdx
+++ b/api-reference/health-ai/ekascribe/SDKs/TS-sdk.mdx
@@ -30,24 +30,26 @@ yarn add @eka-care/ekascribe-ts-sdk
 
 ### 1. Get Ekascribe Instance
 
-It will give you the main class instance, use this instance to access all methods
+Get the SDK instance once and use it everywhere in your application to call all methods.
 
 ```ts
-getEkaScribeInstance({
+// Create a config variable to manage tokens
+const sdkConfig = {
   access_token: '<your_access_token>',
-});
-```
+};
 
-```ts
-const ekaScribe = getEkaScribeInstance({ access_token: 'old_token' });
+// Get instance and use it throughout your application
+const ekascribe = getEkaScribeInstance(sdkConfig);
 ```
 
+**Important:** Use this same `ekascribe` instance for all SDK method calls.
+
 ### 2. Fetch configurations list
 
 Get supported input languages, output formats, and consultation modes.
 
 ```ts
-ekascribe.getEkascribeConfig();
+const config = await ekascribe.getEkascribeConfig();
 ```
 
 - #### Sample Response:
@@ -89,18 +91,47 @@ ekascribe.getEkascribeConfig();
 }
 ```
 
-### 3. Init transaction
+### 3. Fetch user's favorite templates
 
-Use this method to init a transaction before starting recording.
+Get the list of templates marked as favorites by the user (configured via `my_templates` in the config).
 
 ```ts
-await ekascribe.initTransaction({
+const myTemplates = await ekascribe.getConfigMyTemplates();
+```
+
+- #### Sample Response:
+
+```ts
+{
+  "data": {
+    "my_templates": [
+      {
+        "id": "template_123",
+        "name": "General Consultation"
+      },
+      {
+        "id": "template_456",
+        "name": "Cardiology Template"
+      }
+    ],
+  },
+  "message": "Configuration fetched successfully",
+  "code": 200
+}
+```
+
+**Note:** The `my_templates` field contains templates that were previously saved using the `updateConfig()` method (see Templates SDK Methods section).
+
+### 4. Init transaction
+
+Initialize a transaction before starting recording. This sets up the session with your configuration.
+
+```ts
+const response = await ekascribe.initTransaction({
   mode: 'consultation',
-  input_language: ['te', 'en'],
-  output_format_template: [{ template_id: 'eka_emr_template' }],
-  txn_id: 'abc-123',
-  auto_download: false,
-  model_training_consent: false,
+  input_language: ['en-IN'],
+  output_format_template: [{ template_id: 'your_template_id' }],
+  txn_id: 'unique-transaction-id',
   transfer: 'vaded' | 'non-vaded',
   model_type: 'pro' | 'lite',
   system_info: {
@@ -114,29 +145,120 @@ await ekascribe.initTransaction({
     biologicalSex: 'M',
   },
   version: '1.0.0',
-  flavour: 'web' | 'extension',
-});
+  additional_data: {},
+},
+  sharedWorkerUrl: 'worker-url', // optional - see Shared Worker Configuration below
+);
 ```
 
+**Key Parameters:**
+
+- `input_language`: Language code array (e.g., `['en-IN']`)
+- `output_format_template`: Array with `template_id` - depends on your end user's template selection
+- `system_info`: Optional - Pass your system configuration to backend
+- `patient_details`: Optional - Patient information
+- `version`: SDK version
+- `additional_data`: Optional - Pass any data you want to receive unchanged in the response
+- `transfer`: Audio mode. Use `vaded` for audio already processed with Voice Activity Detection (SDK does this by default); use `non-vaded` only if you are sending raw audio without VAD.
+- `model_type`: Transcription model choice. `pro` = most accurate; `lite` = lower latency, more performant.
+- `sharedWorkerUrl`: Optional - Custom URL for the shared worker script. See **Shared Worker Configuration** section below for usage details.
+
 - #### Sample Response:
 
 ```ts
 {
-  "status_code": 200,
-  "message": "Transaction initialized successfully",
-  "business_id": "biz_abc123def456",
-  "txn_id": "abc-123",
-  "oid": "org_789xyz",
-  "uuid": "user_uuid_456"
+  error_code?: ERROR_CODE,
+  status_code: 200,
+  message: "Transaction initialized successfully",
+  business_id: "biz_abc123def456",
+  txn_id: "abc-123",
+  oid: "org_789xyz",
+  uuid: "user_uuid_456"
 }
 ```
 
-### 4. Start recording
+**Error handling:**
+
+Possible Error Codes in `error_code`:
+
+- `txn_limit_exceeded`: Maximum number of transactions exceeded
+- `txn_init_failed`: Something went wrong. Retry with the same method call
+
+**Handling 401 Status Code:**
 
-Start recording with user-selected options.
+If you receive a `status_code: 401`, update the tokens in your config and reinitialize the instance:
 
 ```ts
-await ekascribe.startRecording();
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
+
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+
+// Now you can retry the method call
+const response = await ekascribe.initTransaction({ ... });
+```
+
+#### Shared Worker Configuration
+
+The SDK supports using a shared worker for efficient background audio file uploads. If you provide a `sharedWorkerUrl`, the SDK will use a shared worker for file uploads. If not provided, the SDK will use the main thread for file uploads.
+
+**Why use Shared Worker:**
+
+- **Better Performance**: Offloads file uploads to a background thread, keeping the main thread free for UI interactions
+- **Resource Efficiency**: A single shared worker instance can handle uploads across multiple tabs/windows
+- **Improved User Experience**: Prevents UI blocking during large file uploads
+
+**How to configure:**
+
+```ts
+// Step 1: Create a function to fetch and prepare the worker URL
+async function getSharedWorkerUrl() {
+  // Fetch the worker script from CDN (or your own hosting) - update the latest sdk version
+  const workerScriptResponse = await fetch(
+    'https://cdn.jsdelivr.net/npm/@eka-care/ekascribe-ts-sdk@2.0.48/dist/worker.bundle.js'
+  );
+  const workerScript = await workerScriptResponse.text();
+
+  // Create a blob from the worker script
+  const blob = new Blob([workerScript], { type: 'application/javascript' });
+
+  // Generate an object URL for the blob
+  const workerUrl = URL.createObjectURL(blob);
+
+  return workerUrl;
+}
+
+// Step 2: Use the worker URL in initTransaction
+const sharedWorkerUrl = await getSharedWorkerUrl();
+
+const response = await ekascribe.initTransaction(
+  {
+    mode: 'consultation',
+    input_language: ['en-IN'],
+    output_format_template: [{ template_id: 'your_template_id' }],
+    txn_id: 'unique-transaction-id',
+    transfer: 'vaded',
+    model_type: 'pro',
+    // ... other parameters
+  },
+  sharedWorkerUrl // Pass the custom worker URL;
+);
+```
+
+**Important notes:**
+
+- Make sure to use the correct SDK version in the CDN URL
+- The worker URL must be accessible from the same origin or have proper CORS headers
+- Remember to revoke the object URL when you're done: `URL.revokeObjectURL(workerUrl)`
+- If `sharedWorkerUrl` is not provided, the SDK will use the main thread for file uploads (no shared worker)
+
+### 5. Start recording
+
+Start recording audio after initializing the transaction.
+
+```ts
+const response = await ekascribe.startRecording();
 ```
 
 - #### Sample Response:
@@ -146,16 +268,19 @@ await ekascribe.startRecording();
   "status_code": 200,
   "message": "Recording started successfully",
   "txn_id": "abc-123",
+  // Possible error codes:
+  // - "microphone" -> microphone permission not granted
+  // - "vad_not_initialized" -> VAD failed to initialize; reinitialize and retry the same function call
   error_code?: ERROR_CODE
 }
 ```
 
-### 5. Pause recording
+### 6. Pause recording
 
-Use the method to pause voice recording
+Pause the ongoing voice recording.
 
 ```ts
-await ekascribe.pauseRecording();
+const response = await ekascribe.pauseRecording();
 ```
 
 - #### Sample Response:
@@ -169,12 +294,12 @@ await ekascribe.pauseRecording();
 }
 ```
 
-### 6. Resume recording
+### 7. Resume recording
 
-Use the method to resume voice recording
+Resume a paused recording.
 
 ```ts
-await ekascribe.resumeRecording();
+const response = await ekascribe.resumeRecording();
 ```
 
 - #### Sample Response:
@@ -188,12 +313,17 @@ await ekascribe.resumeRecording();
 }
 ```
 
-### 7. End recording
+### 8. End recording
 
-Use the method to end voice recording
+End the recording session. This method:
+
+- Stops the recording
+- Uploads all audio chunks to the server
+- Automatically retries failed uploads once
+- Calls the commit API to finalize the transaction
 
 ```ts
-await ekascribe.endRecording();
+const response = await ekascribe.endRecording();
 ```
 
 - #### Sample Response:
@@ -202,18 +332,157 @@ await ekascribe.endRecording();
 {
   "status_code": 200,
   "message": "Recording ended and files uploaded successfully",
-  failed_files?: ['1.mp3', '2.mp3']; // if there are any failed files
-  total_audio_files?: ['1.mp3', '2.mp3', '3.mp3', '4.mp3']; // list of all audio files generated
+  failed_files?: ['1.mp3', '2.mp3'], // Only present if some files failed to upload
+  total_audio_files?: ['1.mp3', '2.mp3', '3.mp3', '4.mp3'], // List of all audio files generated
   error_code?: ERROR_CODE;
 }
 ```
 
-### 8. Retry upload recording
+**Error handling:**
+
+Possible Error Codes in `error_code`:
+
+- `txn_stop_failed`: Call `endRecording` again.
+- `audio_upload_failed`: Use `retryUploadRecording` (step 9).
+- `txn_commit_failed`: Call `commitTransactionCall` (step 11).
+
+**Handling 401 Status Code:**
+
+If you receive a `status_code: 401`, update the tokens in your config and retry:
+
+```ts
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
+
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+
+// Now retry the method call
+const response = await ekascribe.endRecording();
+```
+
+### 9. Get output recorded prescription
+
+The SDK polls for you and resolves when processing finishes (default max wait: 2 minutes; override via `max_polling_time`, pass time in milliseconds).
+
+```ts
+// Waits up to 2 minutes by default; override as needed
+const res = await ekascribe.pollSessionOutput({
+  txn_id: 'transaction-id',
+  max_polling_time: 2 * 60 * 1000, // optional
+  template_id: 'template-id', // optional
+});
+```
+
+**Note:**
+
+1. On passing `template_id` in request params, the function will return output only for that specific template ID. If `template_id` is not passed, it will return all template responses generated for that `txn_id`.
+2. Use `onPartialResultCallback` (see Generic Callbacks section) before calling `pollSessionOutput` to receive real-time updates during polling, display partial transcription results, and improve user experience with processing progress indicators.
+
+Status codes to handle:
+
+- `200`: Success; all templates processed.
+- `202`: Templates are still processing; poll again (or let `pollSessionOutput` continue).
+- `206`: Partial success; some templates not processed fully.
+- `401`: Authentication token expired. Update the token.
+- `403`: Invalid Authentication token. Pass new token.
+- `500`: All template processing failed, or internal server error; stop and surface error.
+
+- #### Response type:
+
+```ts
+{
+  response?: {
+    data: {
+      output: TOutputSummary[];
+      template_results: {
+        integration: TOutputSummary[];
+        custom: TOutputSummary[];
+        transcript: TOutputSummary[];
+      };
+      audio_matrix?: {
+        quality: string;
+      };
+      additional_data?: {};
+      created_at?: string;
+    };
+    error?: {
+      code: string;
+      msg: string;
+    };
+  } | null;
+  status_code: number;
+  message?: string;
+}
+
+type TOutputSummary = {
+  template_id: string;
+  value?: JSON | Array | string;
+  type: string;
+  name: string;
+  status: 'success' | 'partial_success' | 'failure';
+  errors?: Array<{
+    type: 'warning' | 'error';
+    code?: string;
+    msg: string;
+  }>;
+  warnings?: Array<{
+    type: 'warning' | 'error';
+    code?: string;
+    msg: string;
+  }>;
+};
+```
+
+- #### Example Response:
+
+```ts
+{
+  status_code: 200,
+  response: {
+    data: {
+      output: [
+        {
+          template_id: "template_id_passed_in_initTransaction",
+          value: "Output Data for this template",
+          type: "custom",
+          name: "General Prescription",
+          status: "success"
+        }
+      ],
+      template_results: {
+        custom: [
+          {
+            template_id: "custom_template",
+            value: "Output prescription",
+            type: "custom",
+            name: "Custom Medication Template",
+            status: "partial_success",
+            warnings: [
+              {
+                type: "warning",
+                code: "FIELD_MISSING",
+                msg: "Dosage information not found"
+              }
+            ]
+          }
+        ]
+      },
+      audio_matrix: {
+        quality: "4.5"
+      },
+      created_at: "2024-11-19T10:30:00Z"
+    }
+  }
+}
+```
 
-Use this method to retry uploading failed audio files.
+### 10. Retry upload recording
+
+Retry uploading failed audio files after `endRecording`.
 
 ```ts
-await ekascribe.retryUploadRecording({ force_commit: true });
+const response = await ekascribe.retryUploadRecording({ force_commit: true });
 ```
 
 - #### Sample Response:
@@ -228,22 +497,37 @@ await ekascribe.retryUploadRecording({ force_commit: true });
 }
 ```
 
-`force_commit` behavior
+**`force_commit` behavior:**
+
+- `force_commit: true` - Model will initiate the processing if some files still fail after retry
+- `force_commit: false` - It will waits until all files are uploaded successfully before processing.
+
+**Handling 401 Status Code:**
+
+If you receive a `status_code: 401`, update the tokens in your config and retry:
+
+```ts
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
 
--- If `force_commit` is set to `true`, the SDK will call the commit API even if some audio files still fail to upload after retrying once.
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
 
--- If `force_commit` is set to `false`, the SDK will wait until **all audio files** are uploaded successfully before making the commit request.
+// Now retry the method call
+const response = await ekascribe.retryUploadRecording({ force_commit: true });
+```
 
-### 9. Patch recording session status
+### 11. Patch recording session status
 
-Use the method to cancel a recording session.
+Cancel or update the status of a recording session.
 
 ```ts
-await ekascribe.patchSessionStatus({
-  sessionId: 'abc-123',
-  processing_status: 'cancelled',
+const response = await ekascribe.patchSessionStatus({
+  sessionId: 'abc-123', // txn_id of the session you want to cancel
+  processing_status: 'cancelled', // pass exactly this value
   processing_error: {
     error: {
+      // Pass these exact values without changing them
       type: 'user_action',
       code: 'cancelled_by_user',
       msg: 'Session cancelled by user',
@@ -267,12 +551,27 @@ await ekascribe.patchSessionStatus({
 }
 ```
 
-### 10. Commit transaction
+**Handling 401 Status Code:**
+
+If you receive a `code: 401`, update the tokens in your config and retry:
+
+```ts
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
+
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+
+// Now retry the method call
+const response = await ekascribe.patchSessionStatus({ ... });
+```
+
+### 12. Commit transaction
 
-Use this method to commit a transaction that is not yet committed or returned a "commit failed" error in a previous step.
+Call this if `endRecording` returns `error_code: 'txn_commit_failed'` or the transaction is not yet committed.
 
 ```ts
-await ekascribe.commitTransactionCall();
+const response = await ekascribe.commitTransactionCall();
 ```
 
 - #### Response type:
@@ -285,12 +584,27 @@ await ekascribe.commitTransactionCall();
 };
 ```
 
-### 11. Stop transaction
+**Handling 401 Status Code:**
 
-Use this method to stop a transaction that has not yet been stopped or returned a "stop failed" error in a previous step.
+If you receive a `status_code: 401`, update the tokens in your config and retry:
 
 ```ts
-await ekascribe.stopTransactionCall();
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
+
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+
+// Now retry the method call
+const response = await ekascribe.commitTransactionCall();
+```
+
+### 13. Stop transaction
+
+Use this method to stop a transaction that has not yet been stopped or returned a `txn_stop_failed` error in a previous step.
+
+```ts
+const response = await ekascribe.stopTransactionCall();
 ```
 
 - #### Response type:
@@ -303,20 +617,27 @@ await ekascribe.stopTransactionCall();
 };
 ```
 
-### 12. Get output template prescriptions
+**Handling 401 Status Code:**
 
-Use this method to fetch the final generated prescription output for a session.
+If you receive a `status_code: 401`, update the tokens in your config and retry:
 
 ```ts
-await ekascribe.getTemplateOutput({ txn_id: 'abc-123' });
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
+
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+
+// Now retry the method call
+const response = await ekascribe.stopTransactionCall();
 ```
 
-### 13. Get previous sessions
+### 14. Get previous sessions
 
-Use this method to retrieve all the previous sessions for a specific doctor ID
+Fetch previous sessions. `txn_count` controls how many sessions the API returns.
 
 ```ts
-const sessions = await ekascribe.getSessionHistory({ txn_count: 10 });
+const sessions = await ekascribe.getSessionHistory({ txn_count: 10 }); // txn_count = number of sessions to fetch
 ```
 
 - #### Response type:
@@ -325,24 +646,175 @@ const sessions = await ekascribe.getSessionHistory({ txn_count: 10 });
 {
   data: [
     {
-      "created_at": "string",
-      "b_id": "string",
-      "user_status": "string",
-      "processing_status": "string",
-      "txn_id": "string",
-      "mode": "string",
-      "uuid": "string",
-      "oid": "string"
+      b_id: "7174661713699045", // business ID
+      created_at: "2025-12-10T10:28:00Z",
+      mode: "consultation",
+      oid: "174661713843153", // logged-in doctor's org ID
+      patient_details: {      // present only if sent in initTransaction
+        "age": 18,
+        "biologicalSex": "M",
+        "username": ""
+      },
+      // processing_status can be: success | system_failure | request_failure | cancelled | in-progress
+      processing_status: "in-progress",
+      txn_id: "sc-c2e9be8b-46e5-489a-9473-236ddb5b24fb",
+      // user_status can be: init | commit
+      user_status: "init",
+      uuid: "c44fd76d-8de1-4011-aa54-5ddcca140f0f" // logged-in doctor's user ID
     }
   ],
-  status: "string",
-  code: "number",
-  message: "string",
-  retrieved_count: "number"
+  status: "success",
+  code: 200,
+  message: "Sessions fetched",
+  retrieved_count: 1
+}
+```
+
+### 15. Convert response to other template post session
+
+Use this method to convert an existing transcription from a completed transaction into a different template format. This is useful when you want to reformat existing transcription data without re-recording.
+
+```ts
+const response = await ekascribe.postTransactionConvertToTemplate({
+  txn_id: 'transaction-id-123',
+  template_id: 'new-template-id',
+});
+```
+
+**Key Parameters:**
+
+- `txn_id`: The transaction ID of the completed session you want to convert
+- `template_id`: The ID of the template format you want to convert the transcription into
+
+- #### Sample Response:
+
+```ts
+{
+  status: 'success' | 'failed';
+  message: string;
+  txn_id: string;
+  template_id: string;
+  b_id: string;
+  code: number;
+  msg: string;
+  error?: {
+    code: string;
+    message: string;
+    display_message: string;
+  };
+}
+```
+
+**When to use:**
+
+- When you need to apply a different template to an existing transcription
+- To generate multiple template formats from the same recording session
+- After completing a session, when you want to see the output in a different template structure
+
+**Note:** After getting success response from this method, call `pollSessionOutput` (Point 9) to get the output for the new template_id.
+
+### 16. Convert transcription to template
+
+Use this method to convert a transcription text to a specific template format.
+
+```ts
+const response = await ekascribe.convertTranscriptionToTemplate({
+  txn_id: 'transaction-id-123',
+  template_id: 'target-template-id',
+  transcript: 'custom transcript text',
+});
+```
+
+**Key Parameters:**
+
+- `txn_id`: The transaction ID of the session
+- `template_id`: The ID of the template format you want to convert to
+- `transcript`: Custom transcript text to use for conversion
+
+- #### Sample Response:
+
+```ts
+{
+  status: 'success' | 'failed';
+  message: string;
+  txn_id: string;
+  template_id: string;
+  b_id: string;
+  code: number;
+  msg: string;
+  error?: { code: string; message: string; display_message: string };
+}
+```
+
+### 17. Update result summary
+
+Use this method to update/edit the result summary (template output) for a transaction.
+
+```ts
+const response = await ekascribe.updateResultSummary({
+  txnId: 'transaction-id-123',
+  data: [
+    {
+      'template-id': 'template-123',
+      data: 'Updated template output content', // Base64 Encoded data
+    },
+  ],
+});
+```
+
+**Key Parameters:**
+
+- `txnId`: The transaction ID
+- `data`: Array of objects containing `template-id` and the updated `data` base64 encoded data
+
+- #### Sample Response:
+
+```ts
+{
+  status: string;
+  message: string;
+  txn_id: string;
+  b_id: string;
+  code: number;
+  error?: { code: string; message: string; display_message: string };
 }
 ```
 
-### 14. Get All Templates
+### 18. Run system compatibility test
+
+Use this method to run a comprehensive system compatibility test to ensure the user's browser and device support all SDK features.
+
+```ts
+const summary = await ekascribe.runSystemCompatibilityTest(
+  (testResult) => {
+    // Callback receives individual test results
+    console.log('Test:', testResult.name, 'Result:', testResult.status);
+  },
+  sharedWorker // Optional: SharedWorker instance for testing worker compatibility
+);
+```
+
+- #### Sample Response:
+
+```ts
+{
+  // TCompatibilityTestSummary
+  microphone: { status: 'pass' | 'fail'; message?: string };
+  audioContext: { status: 'pass' | 'fail'; message?: string };
+  sharedWorker: { status: 'pass' | 'fail'; message?: string };
+  // ... other compatibility tests
+}
+```
+
+**When to use:**
+
+- Before starting a recording session to ensure user's system is compatible
+- To provide user feedback about missing permissions or unsupported features
+- During onboarding to identify potential issues
+
+## Templates SDK Methods
+
+### 1. Get All Templates
 
 Use this method to retrieve all available templates for the current user.
 
@@ -368,7 +840,7 @@ const templates = await ekascribe.getAllTemplates();
 }
 ```
 
-### 15. Create Template
+### 2. Create Template
 
 Use this method to create a new custom template.
 
@@ -392,7 +864,7 @@ const newTemplate = await ekascribe.createTemplate({
 }
 ```
 
-### 16. Edit Template
+### 3. Edit Template
 
 Use this method to update an existing template.
 
@@ -417,7 +889,7 @@ const updatedTemplate = await ekascribe.updateTemplate({
 }
 ```
 
-### 17. Delete Template
+### 4. Delete Template
 
 Use this method to delete an existing template.
 
@@ -437,7 +909,7 @@ const deleteResult = await ekascribe.deleteTemplate('template-123');
 }
 ```
 
-### 18. Generate Template with AI by giving a prompt
+### 5. Generate Template with AI by giving a prompt
 
 Use this method to generate a template using AI with a text prompt.
 
@@ -472,7 +944,7 @@ const aiTemplate = await ekascribe.aiGenerateTemplate(formData);
 }
 ```
 
-### 19. Add templates to list
+### 6. Add templates to list
 
 Use this method to mark templates as favourite templates.
 
@@ -496,7 +968,7 @@ const configUpdate = await ekascribe.updateConfig({
 }
 ```
 
-### 20. Get All Sections
+### 7. Get All Sections
 
 Use this method to retrieve all available template sections.
 
@@ -524,7 +996,7 @@ const sections = await ekascribe.getAllTemplateSections();
 }
 ```
 
-### 21. Create Section in a template
+### 8. Create Section in a template
 
 Use this method to create a new section that can be used in templates.
 
@@ -549,7 +1021,7 @@ const newSection = await ekascribe.createTemplateSection({
 }
 ```
 
-### 22. Edit Section in a template
+### 9. Edit Section in a template
 
 Use this method to update an existing template section.
 
@@ -575,7 +1047,7 @@ const updatedSection = await ekascribe.updateTemplateSection({
 }
 ```
 
-### 23. Delete Section from a template
+### 10. Delete Section from a template
 
 Use this method to delete a template section.
 
@@ -595,150 +1067,90 @@ const deleteResult = await ekascribe.deleteTemplateSection('section-123');
 }
 ```
 
-### 24. Convert a transaction into another template after prescription generation
-
-Use this method to convert an existing transaction's output to use a different template format.
-
-```ts
-const convertResult = await ekascribe.postTransactionConvertToTemplate({
-  txn_id: 'abc-123',
-  template_id: 'new-template-456',
-});
-```
-
-- #### Response type:
-
-```ts
-{
-  status: 'success' | 'failed';
-  message: string;
-  txn_id: string;
-  template_id: string;
-  b_id: string;
-  code: number;
-  msg: string;
-  error?: { code: string; message: string; display_message: string };
-}
-```
-
-### 25. Search past sessions by a patient name
-
-Use this method to search through previous sessions by patient name.
-
-```ts
-// First get session history
-const sessions = await ekascribe.getSessionHistory({ txn_count: 50 });
-
-// Then search by patient name
-const filteredSessions = await ekascribe.searchSessionsByPatientName({
-  sessions: sessions.data || [],
-  patientName: 'John Doe',
-});
-```
-
-- #### Response type:
+## Non-vaded flow: Upload raw audio to get output summary
 
-```ts
-// Returns filtered array of session history data
-[
-  {
-    created_at: 'string',
-    b_id: 'string',
-    user_status: 'string',
-    processing_status: 'string',
-    txn_id: 'string',
-    mode: 'string',
-    uuid: 'string',
-    oid: 'string',
-    patient_details: {
-      username: 'string',
-      oid: 'string',
-      age: number,
-      biologicalSex: 'M' | 'F' | 'O',
-      mobile: 'string',
-      email: 'string',
-    },
-  },
-];
-```
+Use this method to upload pre-recorded audio files directly and get transcription output without real-time recording. This is useful when you have existing audio files and want to process them.
 
-### 26. Upload audio file to get output summary
+**What this method does:**
 
-Use this method to upload audio files directly and get transcription output without real-time recording.
+- Gets a presigned URL from the server
+- Uploads audio files to S3 via presigned URL
+- Initializes a transaction with the uploaded files
+- Returns the transaction details
 
 ```ts
 const audioFiles = [file1, file2]; // File or Blob objects
 const audioFileNames = ['audio1.mp3', 'audio2.mp3'];
 
-const uploadResult = await ekascribe.uploadAudioWithPresignedUrl({
-  action: 'upload',
+const response = await ekascribe.uploadAudioWithPresignedUrl({
+  action: 'ekascribe-v2', // Pass this exact value without changing
   audioFiles,
   audioFileNames,
   mode: 'consultation',
-  txn_id: 'upload-session-123',
-  input_language: ['en'],
-  output_format_template: [{ template_id: 'eka_emr_template' }],
-  transfer: 'non-vaded',
-  auto_download: false,
-  model_training_consent: false,
+  txn_id: 'unique-transaction-id',
+  input_language: ['en-IN'],
+  output_format_template: [{ template_id: 'your_template_id' }],
+  transfer: 'non-vaded', // Use 'non-vaded' for raw audio files
+  model_type: 'pro' | 'lite',
   system_info: {
     platform: 'web',
     language: 'en',
     time_zone: 'Asia/Kolkata',
   },
-  model_type: 'pro',
+  patient_details: {
+    username: 'John Doe',
+    age: 35,
+    biologicalSex: 'M',
+  },
+  version: '1.0.0',
+  additional_data: {},
 });
 ```
 
-- #### Response type:
+**Key Parameters:**
+
+- `action`: Pass `ekascribe-v2` exactly as shown
+- `audioFiles`: Array of File or Blob objects
+- `audioFileNames`: Array of file names corresponding to audio files
+- `transfer`: Use `non-vaded` for raw audio files (not processed with VAD)
+- Other parameters: Same as `initTransaction` (see step 3)
+
+- #### Sample Response:
 
 ```ts
 {
-  error_code?: ERROR_CODE;
-  status_code: number;
-  message: string;
-  business_id?: string;
-  txn_id?: string;
-  oid?: string;
-  uuid?: string;
+  error_code?: ERROR_CODE,
+  status_code: 200,
+  message: 'Recording uploaded successfully.',
 }
 ```
 
-### 27. Edit output summary
+**Error handling:**
 
-Use this method to edit the generated output summary for a completed transaction.
+Possible Error Codes in `error_code`:
 
-```ts
-const editResult = await ekascribe.updateResultSummary({
-  txnId: 'abc-123',
-  data: [
-    {
-      'template-id': 'eka_emr_template',
-      data: 'Updated prescription content here',
-    },
-  ],
-});
-```
+- `get_presigned_url_failed`: Failed to get presigned URL from server, retry with the same method
+- `audio_upload_failed`: Failed to upload audio files to S3, retry with the same method
+- `txn_limit_exceeded`: Maximum number of transactions exceeded
+- `txn_init_failed`: Failed to initialize transaction after upload, retry with the same method
 
-- #### Response type:
+**Handling 401 Status Code:**
+
+If you receive a `status_code: 401`, update the tokens in your config and retry:
 
 ```ts
-{
-  status: string;
-  message: string;
-  txn_id: string;
-  b_id: string;
-  code: number;
-  error?: { code: string; message: string; display_message: string };
-}
-```
+// Update tokens in your config variable
+sdkConfig.access_token = '<new_access_token>';
 
-## Utility Methods
+// Update tokens in the instance
+ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
 
-```ts
-const ekaScribe = getEkaScribeInstance({ access_token: 'old_token' });
+// Now retry the method call
+const response = await ekascribe.uploadAudioWithPresignedUrl({ ... });
 ```
 
+## Utility Methods
+
 ### 1. Get total uploaded files
 
 Use this method to retrieve all the audio files generated for a specific session.
@@ -815,86 +1227,181 @@ ekaScribe.destroyVad();
 
 ### 8. Update Authentication Tokens
 
-Use this method to update the access token without reinitializing the entire SDK instance.
+Use this method to update the access token when it expires (e.g., when you receive a 401 error).
 
 ```ts
-ekaScribe.updateAuthTokens({ access_token: 'new_token' });
+ekascribe.updateAuthTokens({ access_token: 'new_access_token' });
 ```
 
-## Generic Callbacks
+**When to use:**
 
-```ts
-const ekaScribe = getEkaScribeInstance({ access_token: 'your_token' });
-```
+- When any API method returns `status_code: 401`
+- When `eventCallback` returns `error.code: 401` in `file_upload_status`
+- Before token expiration to prevent upload failures
 
-### 1. Event callback
+## Generic Callbacks
 
-This is a comprehensive callback that provides information about SDK operations, including success events, errors, progress updates, and system status. Use this callback to monitor all SDK activities and handle events globally in your application.
+### 1. Event callback
 
-```ts
-ekaScribe.onEventCallback((eventData) => {
-  console.log('Event callback triggered:', eventData);
+This callback provides information about SDK operations. Use it to monitor file uploads, transaction status, AWS configuration, and authentication errors.
+
+```ts
+ekascribe.onEventCallback((eventData) => {
+  console.log('Event callback:', eventData);
+
+  // Handle different callback types
+  switch (eventData.callback_type) {
+    case 'file_upload_status':
+      // Track audio chunk upload progress
+      console.log(`Uploaded ${eventData.data?.success}/${eventData.data?.total} chunks`);
+      break;
+    case 'transaction_status':
+      // Monitor transaction lifecycle (init, stop, commit, cancel)
+      console.log('Transaction update:', eventData.message);
+      break;
+    case 'aws_configure_status':
+      // AWS S3 configuration status
+      console.log('AWS config:', eventData.status);
+      break;
+    case 'authentication_status':
+      // API authentication errors
+      console.error('Auth error:', eventData.message);
+      break;
+  }
 });
 ```
 
-- #### Sample Callback Data:
+- #### Callback Structure:
 
 ```ts
 {
-  callback_type: 'AUDIO_UPLOAD' | 'TRANSACTION_STATUS' | 'VAD_STATUS' | 'RECORDING_STATUS',
-  status: 'success' | 'error' | 'progress' | 'info',
-  message: 'Audio file uploaded successfully',
+  callback_type: 'file_upload_status' | 'transaction_status' | 'aws_configure_status' | 'authentication_status',
+  status: 'success' | 'error' | 'info',
+  message: string,
+  timestamp: string, // ISO timestamp
   error?: {
-    code: 500,
-    msg: 'Upload failed',
-    details: { fileName: 'audio_chunk_1.mp3' }
+    code: number,
+    msg: string,
+    details: any
   },
   data?: {
-    success: 3,
-    total: 4,
-    is_uploaded: true,
-    fileName: 'audio_chunk_1.mp3',
-    request: { txn_id: 'abc-123' },
-    response: { status: 'uploaded' }
-  },
-  timestamp: '2024-01-15T10:30:45.123Z',
-  metadata?: {
-    txn_id: 'abc-123',
-    chunk_index: 1
+    success?: number,      // Number of successfully uploaded chunks
+    total?: number,        // Total number of chunks
+    is_uploaded?: boolean, // Whether current chunk uploaded successfully
+    fileName?: string,     // Current file name
+    chunkData?: Uint8Array[], // Audio chunk data for current audiofile
+    request?: any,         // API request details
+    response?: any         // API response details
   }
 }
 ```
 
+- #### Callback Types Explained:
+
+**`file_upload_status`** - Track audio chunk upload progress
+
+Use this to monitor upload progress of audio chunks:
+
+- `status: 'info'` - Audio chunk info
+
+  - `data.success`: Count of successfully uploaded chunks
+  - `data.total`: Total chunks generated
+  - `data.fileName`: Current chunk file name
+  - `data.chunkData`: Audio data for current chunk
+
+- `status: 'success'` - Chunk uploaded successfully
+
+  - `data.success`: Updated successful upload count
+  - `data.total`: Total chunks
+  - `data.is_uploaded`: true
+
+- `status: 'error'` - Chunk upload failed
+
+  - `error.code`: HTTP error code
+  - `error.msg`: Error message
+  - `error.details`: Additional error details
+
+- Status codes to handle:
+
+  If `error.code === 401`, it means your access token has expired. Update tokens immediately:
+
+  ```ts
+  ekascribe.onEventCallback((eventData) => {
+    if (eventData.callback_type === 'file_upload_status' && eventData.status === 'error') {
+      if (eventData.error?.code === 401) {
+        // Token expired - update it
+        sdkConfig.access_token = '<new_access_token>';
+        ekascribe.updateAuthTokens({ access_token: sdkConfig.access_token });
+      }
+    }
+  });
+  ```
+
 ### 2. User speech callback
 
-This callback will return a boolean indicating whether the user is speaking or not.
+Triggered by Voice Activity Detection (VAD) when user starts or stops speaking.
 
 ```ts
-ekaScribe.onUserSpeechCallback((isSpeech) => {
-  console.log(isSpeech ? 'User is speaking' : 'User is not speaking');
+ekascribe.onUserSpeechCallback((isSpeech) => {
+  if (isSpeech) {
+    console.log('User started speaking');
+  } else {
+    console.log('User stopped speaking');
+  }
 });
 ```
 
-### 3. VAD Callback to check if a frame is valid speech or not
-
-This callback provides information about voice activity detection frames and audio processing status.
-
-```ts
-ekaScribe.onVadFramesCallback((vadData) => {
-  console.log('VAD frame processed:', vadData);
+### 3. Partial result callback
+
+This callback provides real-time partial results while polling for the final output. Use it to display intermediate transcription and template results to users before processing is complete.
+
+```ts
+ekascribe.onPartialResultCallback((partialData) => {
+  console.log('Partial result received:', partialData);
+
+  // Handle different poll statuses
+  switch (partialData.poll_status) {
+    case 'in-progress':
+      // Processing is still ongoing, display partial results
+      console.log('Processing...', partialData.response);
+      break;
+    case 'success':
+      // Final result received
+      console.log('Processing complete:', partialData.response);
+      break;
+    case 'failed':
+      // Processing failed
+      console.error('Processing failed:', partialData.message);
+      break;
+    case 'timeout':
+      // Polling timed out
+      console.warn('Polling timeout:', partialData.message);
+      break;
+  }
 });
 ```
 
-- #### Sample Callback Data:
+- #### Callback Structure:
 
 ```ts
 {
-  status_code: 200,
-  message: 'Audio captured. | No audio captured.',
-  error_code?: 'speech_detected' | 'no_audio_capture'
+  txn_id: string; // Transaction ID
+  response: TGetStatusApiResponse | null; // The response structure is the same as returned by `pollSessionOutput` method
+  status_code: number; // HTTP status code
+  message: string; // Status message
+  poll_status: 'in-progress' | 'success' | 'failed' | 'timeout'; // Current polling state
 }
 ```
 
+**When to use:**
+
+- Set this callback before calling `pollSessionOutput` to receive real-time updates
+- Display partial transcription results to improve user experience
+- Show processing progress indicators
+- Handle intermediate template results
+
+**Note:** This callback is triggered multiple times during polling - once for each poll attempt until processing completes or times out.
+
 ### Error codes
 
 | Error Code            | Description                                                 |
@@ -911,5 +1418,4 @@ ekaScribe.onVadFramesCallback((vadData) => {
 | `no_audio_capture`    | No audio was captured during the recording session          |
 | `txn_status_mismatch` | Invalid operation due to mismatched transaction status      |
 
-
 Refer [Ekascribe](https://github.com/eka-care/v2rx-extension) for SDK implementations.
diff --git a/api-reference/health-ai/ekascribe/SDKs/android-sdk.mdx b/api-reference/health-ai/ekascribe/SDKs/android-sdk.mdx
index a553a42b..dde90259 100644
--- a/api-reference/health-ai/ekascribe/SDKs/android-sdk.mdx
+++ b/api-reference/health-ai/ekascribe/SDKs/android-sdk.mdx
@@ -1,329 +1,369 @@
-[![](https://jitpack.io/v/eka-care/eka-v2rx-android.svg)](https://jitpack.io/#eka-care/eka-v2rx-android/latest)
-
-## Table of Contents
-
-1. [Overview](#overview)
-2. [Prerequisites](#prerequisites)
-3. [Installation](#installation)
-4. [Initialization](#initialization)
-    - [Set up logging callbacks for SDK events](#set-up-logging-callbacks-for-sdk-events)
-5. [Basic Usage](#basic-usage)
-    - [Starting a Voice Session](#starting-a-voice-session)
-    - [Stopping a Voice Session](#stopping-a-voice-session)
-    - [Checking Session Status](#checking-session-status)
-6. [Working with Sessions](#working-with-sessions)
-    - [Retrieving Session History](#retrieving-session-history)
-    - [Sample Structured Rx Data](#sample-structured-rx-data)
-    - [Sample Clinical Notes Output](#sample-clinical-notes-output)
-7. [Advanced Features](#advanced-features)
-    - [Retrying a Session](#retrying-a-session)
-8. [Cleanup](#cleanup)
-9. [Links](#links)
+# EkaScribe SDK Documentation
+
+EkaScribe SDK (Voice2Rx) is an Android SDK for voice-based medical transcription and documentation.
+It provides real-time voice recording, transcription, and intelligent medical documentation
+generation with support for multiple languages and output formats.
+
+**Version:** 3.0.7
+
+**Minimum Android SDK:** 23 (Android 6.0)
 
 ---
 
-## Overview
+## 1. Installation
 
-Voice2Rx is an Android SDK that allows voice transcription and structured prescription data generation for healthcare applications.
+### Add Maven Repository
 
-## Prerequisites
+Add the JitPack repository to your project's `settings.gradle.kts` (or `build.gradle`):
 
-Before integrating the Voice2Rx SDK, ensure that your Android project meets the following requirements:
+```kotlin
+dependencyResolutionManagement {
+    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
+    repositories {
+        google()
+        mavenCentral()
+        // Add below line to fetch SDK from Jitpack
+        maven { url = uri("<https://jitpack.io>") }
+    }
+}
 
-- Android API level 24 or higher
-- Kotlin 1.9.0 or higher
-- Microphone permission in your AndroidManifest.xml:
-    
-    ```xml
-    
-    <uses-permission android:name="android.permission.RECORD_AUDIO" />
-    <uses-permission android:name="android.permission.INTERNET" />
-    ```
-    
-- Runtime permission handling for microphone access
+```
 
-## Installation
+### Add Dependencies
 
-Add the following dependency to your `app/build.gradle.kts` file:
+Add the EkaScribe SDK and required networking dependency to your app's `build.gradle.kts`:
 
 ```kotlin
-implementation("com.github.eka-care:eka-v2rx-android:2.0.3")
+dependencies {
+    implementation("com.github.eka-care:Eka-Scribe-Android:${LATEST_VERSION}")
+}
+
+```
+
+### Required Permissions
+
+Add the following permissions to your `AndroidManifest.xml`:
+
+```xml
+<uses-permission android:name="android.permission.RECORD_AUDIO" />
+<uses-permission android:name="android.permission.INTERNET" />
+<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
 ```
 
-## Initialization
+**Note:** You must request `RECORD_AUDIO` permission at runtime for Android 6.0 and above.
+
+---
+
+## 2. Initialization
 
-To initialize the SDK, you need to implement the `IOkHttpSetup` interface and provide the necessary configuration:
+Initialize the SDK in your `Application` class or main `Activity`.
+
+### Step 1: Implement Lifecycle Callbacks
+
+Create a class that implements `Voice2RxLifecycleCallbacks` to handle session events.
 
 ```kotlin
-// Create object implementing IOkHttpSetup interface to provide auth tokens
-class EkaAuthConfigImpl : EkaAuthConfig {
-    override suspend fun refreshToken(): String {
-        // return new auth token after refresh
-    }
+import com.eka.voice2rx_sdk.sdkinit.Voice2RxLifecycleCallbacks
+import com.eka.voice2rx_sdk.common.models.EkaScribeError
 
-    override fun sessionExpired() {
-				// callback function for session expired
+class MyVoice2RxCallbacks : Voice2RxLifecycleCallbacks {
+    override fun onStartSession(sessionId: String) {
+        // Recording started
     }
-}
 
-// Initialize the SDK
-Voice2Rx.init(
-    context = context,
-    config = Voice2RxInitConfig(
-        voice2RxLifecycle = object : Voice2RxLifecycleCallbacks {
-            override fun onStartSession(sessionId: String) {
+    override fun onStopSession(sessionId: String, recordedFiles: Int) {
+        // Get result when ready after stopping the session
+        CoroutineScope(Dispatchers.IO).launch {
+            Voice2Rx.pollEkaScribeResult(sessionId = sessionId).onSuccess {
+                Log.d(TAG, it.templates.toString())
+            }.onFailure {
+                Log.d(TAG, "error : ${it.message.toString()}")
             }
+        }
+    }
 
-            override fun onStopSession(
-                sessionId: String,
-                recordedFiles: Int
-            ) {
-            }
+    override fun onPauseSession(sessionId: String) {
+        // Recording paused
+    }
 
-            override fun onPauseSession(sessionId: String) {
-            }
+    override fun onResumeSession(sessionId: String) {
+        // Recording resumed
+    }
 
-            override fun onResumeSession(sessionId: String) {
-            }
+    override fun onError(error: EkaScribeError) {
+        // Handle error
+    }
+}
 
-            override fun onError(
-                sessionId: String,
-                error: VoiceError
-            ) {
-            }
-        },
-        authorizationToken = // provide eka auth token,
-        ekaAuthConfig = EkaAuthConfigImpl(),
-    )
-)
 ```
 
-### Set up logging callbacks for SDK events
+### Step 2: Implement TokenStorage
+
+The networking module requires a `TokenStorage` implementation to handle authentication tokens.
 
 ```kotlin
-Voice2Rx.setEventLogger(
-    object : LogInterceptor {
-        override fun logEvent(eventLog: EventLog) {
-            when(eventLog) {
-                is EventLog.Error -> {
+import com.eka.networking.token.TokenStorage
 
-                }
-                is EventLog.Warning -> {
+class MyTokenStorage : TokenStorage {
+    override fun getAccessToken(): String {
+        return "access_token"
+    }
 
-                }
-                is EventLog.Info -> {
+    override fun getRefreshToken(): String {
+        return "refresh_token"
+    }
 
-                }
-            }
-        }
+    override fun saveTokens(accessToken: String, refreshToken: String) {
+        // save tokens
     }
+
+    override fun onSessionExpired() {
+        // SessionExpired refresh token expired
+    }
+}
+```
+
+### Step 3: Configure and Initialize
+
+Initialize `Voice2Rx` with `Voice2RxInitConfig` and `NetworkConfig`.
+
+```kotlin
+import com.eka.voice2rx_sdk.sdkinit.Voice2Rx
+import com.eka.voice2rx_sdk.sdkinit.Voice2RxInitConfig
+import com.eka.networking.client.NetworkConfig
+import com.eka.networking.client.AuthConfig
+
+// 1. Configure Network
+val networkConfig = NetworkConfig(
+    appId = "your-app-id",
+    baseUrl = "<https://api.eka.care/>",
+    appVersionName = BuildConfig.VERSION_NAME,
+    appVersionCode = BuildConfig.VERSION_CODE,
+    isDebugApp = false // false in production environment,
+    apiCallTimeOutInSec = 30L,
+    headers = mapOf(), // Optional headers
+    tokenStorage = MyTokenStorage()
 )
+
+// 2. Configure SDK
+val config = Voice2RxInitConfig(
+    voice2RxLifecycle = MyVoice2RxCallbacks(),
+    networkConfig = networkConfig,
+)
+
+// 3. Initialize
+Voice2Rx.init(config, context)
+
 ```
 
-## Basic Usage
+---
+
+## 3. Core API Reference
+
+All main functions are available via the `Voice2Rx` singleton object.
+
+### Recording Control
+
+### `startVoice2Rx`
+
+Starts a new voice recording session.
+
+```kotlin
+fun startVoice2Rx(
+    mode: String = Voice2RxType.CONSULTATION.value, // "consultation" or "dictation"
+    patientDetails: PatientDetails? = null,
+    outputFormats: List<Template>, // Max 2 formats
+    languages: List<String>,       // Max 2 languages
+    modelType: String,             // e.g., "pro"
+    onError: (EkaScribeError) -> Unit,
+    onStart: (String) -> Unit
+)
 
-### Starting a Voice Session
+```
 
-To start a voice recording session:
+**Example:**
 
 ```kotlin
-// Start a voice session in DICTATION or CONSULTATION mode
+// Define output templates using Template(templateId, templateName)
+val outputFormats = listOf(
+    Template(templateId = "19288d2f-81a9-46a6-b804-9651242a9b3e", templateName = "SOAP Note")
+)
+
+val languages = listOf("en-IN")
+
 Voice2Rx.startVoice2Rx(
-    mode = Voice2RxType.DICTATION,
-    onError = {}
+    mode = Voice2RxType.DICTATION.value,
+    outputFormats = outputFormats,
+    languages = languages,
+    modelType = "pro" // or lite for faster results,
+    onError = { error -> Log.e("SDK", "Error: ${error.errorDetails.message}") },
+    onStart = { sessionId -> Log.d("SDK", "Started: $sessionId") }
 )
-// The onStart callback (defined in init) will be triggered when the session begins
+
 ```
 
-### Stopping a Voice Session
+### `pauseVoice2Rx`
 
-To stop a voice recording session:
+Pauses the current recording.
+
+```kotlin
+Voice2Rx.pauseVoice2Rx()
+
+```
+
+### `resumeVoice2Rx`
+
+Resumes a paused recording.
+
+```kotlin
+Voice2Rx.resumeVoice2Rx()
+
+```
+
+### `stopVoice2Rx`
+
+Stops the recording and triggers processing.
 
 ```kotlin
-// Stop the current voice session
 Voice2Rx.stopVoice2Rx()
-// The onStop callback will be triggered with the sessionId
+
 ```
 
-### Checking Session Status
+### `isCurrentlyRecording`
 
-To check if a recording session is currently active:
+Checks if a recording is in progress.
 
 ```kotlin
-// Returns true if a recording session is in progress
 val isRecording = Voice2Rx.isCurrentlyRecording()
+
 ```
 
-## Working with Sessions
+### Data & Results
 
-### Retrieving Session History
+### `getSessionOutput`
 
-To access previous recording sessions:
+Retrieves the transcription/generated output for a session.
 
 ```kotlin
-// Get all recording sessions
-val sessions = Voice2Rx.getSessions()
+suspend fun getSessionOutput(sessionId: String): Result<SessionResult>
+
+```
+
+### `pollEkaScribeResult`
+
+Polls for results, useful for waiting until processing completes.
 
-// Access a specific session (example using the first session)
-val session = sessions.firstOrNull()
-val sessionProcessingStatus = Voice2Rx.getVoice2RxSessionStatus(sessionId = session.sessionId)
-val sessionOutput = Voice2Rx.getVoiceSessionData(sessionId = session.sessionId)
+```kotlin
+suspend fun pollEkaScribeResult(sessionId: String): Result<SessionResult>
 
 ```
 
-### Sample Structured Rx Data
-
-The SDK returns structured prescription data in JSON format:
-
-```json
-{
-  "prescription": {
-    "advices": [
-      {
-        "id": "locale-4f1e59b7c71003546b7bb5aadb89280b",
-        "parsedText": "Take bedrest for at least 7 days",
-        "text": "Take bedrest for at least 7 days"
-      },
-      {
-        "id": "locale-b3ca8e9447de58b3738549ec3c8db922",
-        "parsedText": "Do exercise with physiotherapist",
-        "text": "Do exercise with physiotherapist"
-      }
-    ],
-    "followup": {
-      "date": "2025-03-09T00:00:00.000000Z"
-    },
-    "labTests": [
-      {
-        "common_name": "Blood sugar test",
-        "id": "locale-5686e09a70ffcbc355b372f57b744752",
-        "name": "Blood sugar test"
-      },
-      {
-        "common_name": "Liver function test",
-        "id": "locale-9b501b45359316407782679ce7eeabac",
-        "name": "Liver function test"
-      },
-      {
-        "common_name": "X-ray",
-        "id": "locale-3c51a99d9bbfefde7ba517f3316899f2",
-        "name": "X-ray"
-      }
-    ],
-    "language": "EN",
-    "medications": [
-      {
-        "duration": {
-          "custom": "3 Days",
-          "unit": "Days",
-          "value": 3
-        },
-        "frequency": {
-          "custom": "1-1-1",
-          "dose": [
-            "1",
-            "1",
-            "1"
-          ],
-          "frequency": "3",
-          "pattern_id": "fp-1",
-          "period": 1,
-          "period_unit": "day"
-        },
-        "id": "locale-a0fdc63d09d1d255b00796ade40bb3c6",
-        "name": "Molo 650 tablet",
-        "original_name": "mdolo 650 tablet",
-        "linked": {
-          "eka_id": "b-4974923412"
-        }
-      }
-    ],
-    "symptoms": [
-      {
-        "id": "locale-f532fde6e2a357af72b9de6aa1f0e65e",
-        "name": "Fever",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-6a44898c82426d50cb083373d59b155a",
-        "name": "Headache",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-867fc9a3c94474b3c77ee9a0b5aae022",
-        "name": "Leg pain",
-        "status": "preliminary"
-      },
-      {
-        "id": "locale-a7033cb31b1991cc8f4c9c751a8452b6",
-        "name": "Neck pain",
-        "status": "preliminary"
-      }
-    ]
-  }
-}
+### `getHistoryVoice2Rx`
+
+Fetches session history.
+
+```kotlin
+suspend fun getHistoryVoice2Rx(count: Int? = null): Voice2RxHistoryResponse?
 
 ```
 
-### Sample Clinical Notes Output
+### `getFullRecordingFile`
+
+Gets the audio file for a session.
+
+```kotlin
+fun getFullRecordingFile(sessionId: String): Result<File>
 
-The SDK can also generate a formatted markdown output:
+```
 
-```markdown
-**Chief Complaints**
-- Fever
-- Headache
-- Leg pain
-- Neck pain
+### Session Info & Monitoring
 
-**Assessment**
-- Symptomatic fever with multiple body pains
+### `getSessionUploadInfoAsFlow`
 
-**Plan**
-- Medications:
-  - Mdolo 650 tablet - TID for 3 days
-- Investigations advised:
-  - Blood test
-  - Blood sugar test
-  - Liver function test
-  - X-ray
-- Physiotherapy referral
+Observe the upload stage of a session (Uploading, Processing, Completed).
 
-**Patient Instructions**
-- Take complete bed rest for 7 days
-- Follow up after 15 days with all investigation reports
-- Continue physiotherapy sessions
-- Take prescribed medications as directed
+```kotlin
+suspend fun getSessionUploadInfoAsFlow(sessionId: String): Flow<VoiceTransactionStage>?
 
 ```
 
-## Advanced Features
+### `getVoiceActivityFlow`
+
+Flow for real-time voice activity (speech detection, amplitude).
+
+```kotlin
+fun getVoiceActivityFlow(): Flow<VoiceActivityData>?
+
+```
 
-### Retrying a Session
+### `getAudioQualityFlow`
 
-To retry processing a session:
+Flow for real-time audio quality metrics (STOI, PESQ, SI-SDR).
 
 ```kotlin
-Voice2Rx.retrySession(
-    context = context,
-    sessionId = sessionId,
-    onResponse = { responseState ->
-        // Handle the retry response
-        // Indicates whether retry was successful or not
-    }
-)
+fun getAudioQualityFlow(): Flow<AudioQualityMetrics?>?
+
+```
+
+### Configuration & Templates
+
+### `getTemplates`
+
+Get available output templates.
+
+```kotlin
+suspend fun getTemplates(): Result<List<TemplateItem>>?
+
+```
+
+### `getUserConfigs`
+
+Get user configuration including supported languages and modes.
+
+```kotlin
+suspend fun getUserConfigs(): Result<UserConfigs>
+
 ```
 
-## Cleanup
+### `updateUserConfigs`
 
-When you're done using the SDK, free up resources:
+Update user preferences (selected language, mode, etc.).
 
 ```kotlin
-// Release all resources
-Voice2Rx.dispose()
+suspend fun updateUserConfigs(selectedUserPreferences: SelectedUserPreferences): Result<Boolean>
 
 ```
 
-## Links
+---
+
+## 4. Error Handling
+
+Errors are returned via `EkaScribeError`.
+
+**Common Error Codes:**
+
+- `SUPPORTED_OUTPUT_FORMATS_COUNT_EXCEEDED`: Max 2 output formats allowed.
+- `SUPPORTED_LANGUAGES_COUNT_EXCEEDED`: Max 2 languages allowed.
+- `LANGUAGE_LIST_CAN_NOT_BE_EMPTY`
+- `OUTPUT_FORMAT_LIST_CAN_NOT_BE_EMPTY`
+
+**Data Class:**
+
+```kotlin
+data class EkaScribeError(
+    val sessionId: String,
+    val errorDetails: EkaScribeErrorDetails, // Contains 'message', 'displayMessage', 'code'
+    val voiceError: VoiceError
+)
+
+```
+
+## 5. Cleanup
+
+Call `releaseResources()` when the SDK is no longer needed (e.g., in `onDestroy` of your host
+Activity/Application).
+
+```kotlin
+Voice2Rx.releaseResources()
 
-- [GitHub Repository](https://github.com/eka-care/eka-v2rx-android)
\ No newline at end of file
+```
\ No newline at end of file
diff --git a/api-reference/health-ai/ekascribe/SDKs/ios-sdk.mdx b/api-reference/health-ai/ekascribe/SDKs/ios-sdk.mdx
index f89ac9fc..5cbe3c6e 100644
--- a/api-reference/health-ai/ekascribe/SDKs/ios-sdk.mdx
+++ b/api-reference/health-ai/ekascribe/SDKs/ios-sdk.mdx
@@ -1 +1,931 @@
-## Coming Soon
\ No newline at end of file
+# EkaScribe iOS SDK
+
+A Swift package for voice-to-prescription functionality with audio recording and real-time transcription capabilities for medical consultation applications.
+
+## Overview
+
+EkaScribe empowers healthcare applications with advanced voice recording and transcription capabilities. It provides a seamless integration for medical consultation workflows, enabling doctors to record patient interactions and automatically generate prescriptions through AI-powered voice analysis.
+
+### Getting Started
+
+1. **Install** the package via Swift Package Manager
+2. **Configure** authentication and doctor information at app launch
+3. **Initialize** `VoiceToRxViewModel` in your view
+4. **Start recording** with your desired templates and languages
+5. **Handle results** when processing completes
+
+The SDK requires **iOS 17.0+** and provides a simple, straightforward API for voice-to-prescription functionality.
+
+### Key Features
+
+- 🎙️ **Voice Activity Detection (VAD)** - Intelligent audio recording with automatic speech detection
+- 🔄 **Real-time Transcription** - Live audio-to-text conversion during consultations
+- 🏥 **Medical Context Aware** - Specialized for healthcare terminology and prescription generation
+- 📊 **Session Management** - Complete recording session lifecycle management
+- ☁️ **Cloud Integration** - Automatic audio upload and processing
+- 📝 **Template Support** - Customizable output formats (SOAP notes, prescriptions, etc.)
+
+## Table of Contents
+
+- [Requirements](#requirements)
+- [Installation](#installation)
+- [Integration Guide](#integration-guide)
+- [Core Components](#core-components)
+- [Configuration](#configuration)
+- [Recording Management](#recording-management)
+- [Template Management](#template-management)
+- [Session History](#session-history)
+- [Result Management](#result-management)
+- [Error Handling](#error-handling)
+- [API Reference](#api-reference)
+
+## Requirements
+
+> **⚠️ Important**: This SDK requires iOS 17.0 or later.
+
+- **iOS**: 17.0+
+- **Swift**: 5.9+
+- **Xcode**: 15.0+
+- **Sdk Version**: 1.3.5+
+
+### System Permissions
+
+Add the following permissions to your app's `Info.plist`:
+
+```xml
+<key>NSMicrophoneUsageDescription</key>
+<string>This app needs microphone access to record medical consultations</string>
+<key>NSLocalNetworkUsageDescription</key>
+<string>This app needs network access to upload and process audio recordings</string>
+```
+
+## Installation
+
+### Swift Package Manager
+
+Add EkaScribe to your project using Swift Package Manager:
+
+1. In Xcode, select **File → Add Package Dependencies**
+2. Enter the repository URL:
+   ```
+   https://github.com/eka-care/EkaVoiceToRx.git
+   ```
+   Or use SSH:
+   ```
+   git@github.com:eka-care/EkaVoiceToRx.git
+   ```
+3. Choose the version or branch
+4. Add to your target
+
+### Package.swift
+
+```swift
+dependencies: [
+    .package(url: "https://github.com/eka-care/EkaVoiceToRx.git", from: "1.3.5")
+]
+```
+
+### Import Statement
+
+After adding the package, import it in your Swift files:
+
+```swift
+import EkaVoiceToRx
+```
+
+## Integration Guide
+
+Follow these steps to integrate the SDK into your app:
+
+### Step 1: Configure Authentication and Doctor Information
+
+Set up authentication tokens and doctor information when your app launches. This should be done once at app startup:
+
+```swift
+import SwiftUI
+import EkaVoiceToRx
+
+@main
+struct YourApp: App {
+    init() {
+        configureEkaScribe()
+    }
+    
+    var body: some Scene {
+        WindowGroup {
+            ContentView()
+        }
+    }
+    
+    private func configureEkaScribe() {
+        // 1. Set authentication tokens (required)
+        AuthTokenHolder.shared.authToken = "your_auth_token"
+        AuthTokenHolder.shared.refreshToken = "your_refresh_token"
+        AuthTokenHolder.shared.bid = "your_business_id"
+        
+        // 2. Configure doctor/user information (required)
+        let config = V2RxInitConfigurations.shared
+        config.clientId = "your_client_id"
+        config.ownerName = "Dr. Smith"
+        config.ownerOID = "doctor_oid_123"
+        config.ownerUUID = "doctor_uuid_456"
+    }
+}
+```
+
+**Important**: Make sure to set authentication tokens and doctor information before making any SDK calls.
+
+### Step 2: Initialize the View Model
+
+Create a `VoiceToRxViewModel` instance in your SwiftUI view or UIKit view controller:
+
+**SwiftUI:**
+```swift
+@StateObject private var viewModel = VoiceToRxViewModel(
+    voiceToRxInitConfig: .shared,
+    voiceToRxDelegate: nil
+)
+```
+
+**UIKit:**
+```swift
+private let viewModel = VoiceToRxViewModel(
+    voiceToRxInitConfig: .shared,
+    voiceToRxDelegate: nil
+)
+```
+
+### Step 3: Start Recording
+
+Start a recording session with your desired configuration:
+
+#### Parameters
+
+The `startRecording()` method accepts the following parameters:
+
+- **conversationType** (`VoiceConversationType`): The type of conversation (see [Conversation Types](#conversation-types))
+
+- **inputLanguage** (`[InputLanguageType]`): Array of supported languages (see [Input Languages](#input-languages))
+
+- **templates** (`[OutputFormatTemplate]`): Array of output format templates (see [Template Management](#template-management))
+
+- **modelType** (`ModelType`): The AI model to use for processing (see [Model Types](#model-types))
+
+```swift
+// Your implementation
+private func startRecording() async {
+    do {
+        // 1. Fetch available templates (recommended)
+        // See Template Management section for details on getTemplates API
+        // VoiceToRxRepo.shared.getTemplates { result in ... }
+        
+        // 2. Configure templates
+        let outputFormat: [OutputFormatTemplate] = [
+            OutputFormatTemplate(
+                templateID: "template-id-here",
+                templateType: .defaultType,
+                templateName: "SOAP Notes"
+            )
+        ]
+        
+        // 3. Set patient information (if applicable)
+        V2RxInitConfigurations.shared.subOwnerOID = patientOID
+        V2RxInitConfigurations.shared.subOwnerName = patientName
+        
+        // 4. Calling SDK function
+        try await viewModel.startRecording(
+            conversationType: VoiceConversationType.conversation,
+            inputLanguage: [InputLanguageType.english, InputLanguageType.hindi],
+            templates: outputFormat,
+            modelType: ModelType.lite
+        )
+        
+        // Successfully started recording
+    } catch {
+        // Handle errors
+        await MainActor.run {
+            handleRecordingError(error)
+        }
+    }
+}
+```
+
+**Note**: It's recommended to use the `getTemplates()` API first to fetch available templates before creating the `OutputFormatTemplate` array. See the [Template Management](#template-management) section for details.
+
+## Core Components
+
+### VoiceToRxViewModel
+
+The central view model that manages the entire voice recording and processing workflow.
+
+```swift
+public class VoiceToRxViewModel: ObservableObject {
+    @Published public var screenState: RecordConsultationState
+    
+    public init(
+        voiceToRxInitConfig: V2RxInitConfigurations,
+        voiceToRxDelegate: VoiceToRxDelegate?
+    )
+}
+```
+
+#### Recording States
+
+The `screenState` property tracks the current state of the recording session:
+
+```swift
+public enum RecordConsultationState {
+    case retry                          // Ready to retry after error
+    case startRecording                 // Initial state, ready to start
+    case listening(conversationType: VoiceConversationType) // Currently recording
+    case paused                         // Recording paused
+    case processing                     // Processing audio/generating prescription
+    case resultDisplay(success: Bool, value: String?)  // Results available
+    case deletedRecording              // Recording deleted
+}
+```
+
+#### Conversation Types
+
+```swift
+public enum VoiceConversationType: String, CaseIterable {
+    case conversation = "consultation"  // Doctor-patient conversation
+    case dictation                     // Direct prescription dictation
+}
+```
+
+#### Model Types
+
+```swift
+public enum ModelType {
+    case pro      // High accuracy model
+    case lite     // Faster, lighter model
+}
+```
+
+#### Input Languages
+
+```swift
+public enum InputLanguageType {
+    case english
+    case hindi
+    case tamil
+    case telugu
+    case kannada
+    case malayalam
+    case bengali
+    case gujarati
+    case marathi
+    case punjabi
+    case urdu
+    case odia
+    case assamese
+}
+```
+
+## Configuration
+
+### App-Level Setup
+
+Configure the SDK when your app launches. This should be done once at app startup:
+
+```swift
+import SwiftUI
+import EkaVoiceToRx
+
+@main
+struct YourApp: App {
+    init() {
+        configureEkaScribe()
+    }
+    
+    var body: some Scene {
+        WindowGroup {
+            ContentView()
+        }
+    }
+    
+    private func configureEkaScribe() {
+        // 1. Set authentication tokens (required)
+        AuthTokenHolder.shared.authToken = KeychainHelper.fetchAuthToken()
+        AuthTokenHolder.shared.refreshToken = KeychainHelper.fetchRefreshToken()
+        AuthTokenHolder.shared.bid = JWTDecoder.shared.businessId
+        
+        // 2. Configure doctor/user information (required)
+        let config = V2RxInitConfigurations.shared
+        config.clientId = "your_client_id"
+        config.ownerName = "Dr. Smith"
+        config.ownerOID = "doctor_oid_123"
+        config.ownerUUID = "doctor_uuid_456"
+        
+        // 3. Set up data container (optional - only if using SwiftData)
+        // config.modelContainer = SwiftDataRepoContext.modelContext.container
+    }
+}
+```
+
+**Important**: Make sure to set authentication tokens and doctor information before making any SDK calls.
+
+### Session-Specific Configuration
+
+Before starting a recording session, configure patient-specific information. This should be done each time you start a new recording:
+
+```swift
+// Set patient information for the current session (required before recording)
+V2RxInitConfigurations.shared.subOwnerOID = selectedPatientOid
+V2RxInitConfigurations.shared.subOwnerName = patientName
+
+// Optional: Set appointment ID for context
+V2RxInitConfigurations.shared.appointmentID = appointmentID
+```
+
+**Note**: Patient information can be set to empty strings if not applicable:
+```swift
+V2RxInitConfigurations.shared.subOwnerOID = ""
+V2RxInitConfigurations.shared.subOwnerName = ""
+```
+
+### Configuration Properties
+
+```swift
+public class V2RxInitConfigurations {
+    public static let shared: V2RxInitConfigurations
+    
+    // Doctor/User Information
+    public var ownerName: String?          // Doctor name
+    public var ownerOID: String?            // Doctor OID
+    public var ownerUUID: String?            // Doctor UUID
+    public var clientId: String?             // Client identifier
+    
+    // Patient Information (set per session)
+    public var subOwnerOID: String?         // Patient OID
+    public var subOwnerName: String?        // Patient name
+    
+    // Optional Context
+    public var appointmentID: String?       // Appointment identifier
+    
+    // Data Storage
+    public var modelContainer: ModelContainer?  // SwiftData container (optional)
+}
+```
+
+### Authentication
+
+Set authentication tokens before making any SDK calls:
+
+```swift
+AuthTokenHolder.shared.authToken = "your_auth_token"
+AuthTokenHolder.shared.refreshToken = "your_refresh_token"
+AuthTokenHolder.shared.bid = "your_business_id"
+```
+
+## Recording Management
+
+### Starting Recording
+
+#### Parameters
+
+The `startRecording()` method accepts the following parameters:
+
+- **conversationType** (`VoiceConversationType`): The type of conversation (see [Conversation Types](#conversation-types))
+
+- **inputLanguage** (`[InputLanguageType]`): Array of supported languages (see [Input Languages](#input-languages))
+
+- **templates** (`[OutputFormatTemplate]`): Array of output format templates (see [Template Management](#template-management))
+
+- **modelType** (`ModelType`): The AI model to use for processing (see [Model Types](#model-types))
+
+```swift
+// Start recording
+try await viewModel.startRecording(
+conversationType: VoiceConversationType.conversation,
+inputLanguage: [InputLanguageType.english, InputLanguageType.hindi],
+templates: templates,
+modelType: ModelType.lite
+ )
+```
+
+**Note**: It's recommended to use the `getTemplates()` API first to fetch available templates before creating the `OutputFormatTemplate` array. See the [Template Management](#template-management) section for details.
+
+### Pausing and Resuming
+
+```swift
+// Pause recording
+viewModel.pauseRecording()
+
+// Resume recording
+do {
+    try viewModel.resumeRecording()
+} catch {
+    // Handle resume error
+    print("Failed to resume: \(error.localizedDescription)")
+}
+```
+
+### Stopping Recording
+
+```swift
+// Stop recording and process
+Task {
+    do {
+        try await viewModel.stopRecording()
+        // The viewModel will transition to .processing, then .resultDisplay
+    } catch {
+        // Handle error
+        print("Failed to stop recording: \(error.localizedDescription)")
+    }
+}
+```
+
+### Handling Results
+
+Monitor the `screenState` for result availability. Results are automatically provided when processing completes:
+
+```swift
+case .resultDisplay(success: let success, value: let value):
+    if success {
+        // Get the result text (base64 encoded)
+        let base64EncodedText = value ?? ""
+        
+        // Decode base64 to get the actual result
+        guard let decodedData = Data(base64Encoded: base64EncodedText),
+              let resultText = String(data: decodedData, encoding: .utf8) else {
+            showError("Failed to decode result")
+            return
+        }
+        
+        // Get the session ID for future reference
+        let sessionID = viewModel.sessionID?.uuidString ?? ""
+        // Display results to user
+        showResults(resultText, sessionID: sessionID)
+    } else {
+        // Handle error
+        showError("Failed to process recording")
+    }
+```
+
+**Note**: The `value` parameter contains base64-encoded formatted output based on your selected template. You need to decode it before displaying to users. For more detailed results including multiple template outputs, use `VoiceToRxRepo.shared.fetchResultStatusResponse()`.
+
+## Template Management
+
+### Fetching Available Templates
+
+Use `VoiceToRxRepo` to fetch available templates:
+
+```swift
+import EkaVoiceToRx
+
+VoiceToRxRepo.shared.getTemplates { result in
+    switch result {
+    case .success(let response):
+        let templates = response.items
+        // Use templates
+        break
+    case .failure(let error):
+        print("Failed to fetch templates: \(error.localizedDescription)")
+        break
+    }
+}
+```
+
+### Updating Favorite Templates
+
+Update user's favorite templates configuration:
+
+```swift
+let templateIDs = ["template-id-1", "template-id-2"]
+
+VoiceToRxRepo.shared.updateConfig(
+    templates: templateIDs
+) { result in
+    switch result {
+    case .success:
+        print("Templates updated successfully")
+    case .failure(let error):
+        print("Failed to update: \(error.localizedDescription)")
+    }
+}
+```
+
+### Using Templates in Recording
+
+Pass templates when starting a recording:
+
+```swift
+// Your implementation
+private func startRecordingWithTemplates() async {
+    do {
+        // 1. Fetch available templates first (recommended)
+        // VoiceToRxRepo.shared.getTemplates { result in ... }
+        
+        // 2. Configure templates
+        let templates: [OutputFormatTemplate] = [
+            OutputFormatTemplate(
+                templateID: "template-id",
+                templateType: .defaultType,
+                templateName: "Template Name"
+            )
+        ]
+        
+        // 3. Calling SDK function
+        try await viewModel.startRecording(
+            conversationType: VoiceConversationType.conversation,
+            inputLanguage: [InputLanguageType.english],
+            templates: templates,
+            modelType: ModelType.pro
+        )
+    } catch {
+        // Handle error
+        await MainActor.run {
+            handleError(error)
+        }
+    }
+}
+```
+
+## Session History
+
+### Fetching Session History
+
+Retrieve past recording sessions:
+
+```swift
+VoiceToRxRepo.shared.getEkaScribeHistory { result in
+    switch result {
+    case .success(let response):
+        let sessions = response.data
+        // Display sessions
+        break
+    case .failure(let error):
+        print("Failed to fetch history: \(error.localizedDescription)")
+        break
+    }
+}
+```
+## Result Management
+
+### Fetching Full Result Response
+
+Get the complete result response with selected template outputs:
+
+```swift
+VoiceToRxRepo.shared.fetchResultStatusResponse(sessionID: sessionID) { result in
+    switch result {
+    case .success(let response):
+        // Note: All values in the response are base64 encoded and need to be decoded before display
+        // response.data.templateResults.custom - custom template results (base64 encoded)
+        // response.data.templateResults.transcript - transcript results (base64 encoded)
+        // response.data.output - general output (base64 encoded)
+        // response.data.audioMatrix - audio quality metrics
+        
+        // Example: Decoding a result value
+        if let encodedValue = response.data?.templateResults?.custom?.first?.value,
+           let decodedData = Data(base64Encoded: encodedValue),
+           let decodedText = String(data: decodedData, encoding: .utf8) {
+            // Use decodedText for display
+            print("Decoded result: \(decodedText)")
+        }
+        break
+    case .failure(let error):
+        print("Failed to fetch response: \(error.localizedDescription)")
+        break
+    }
+}
+```
+**Note**: The `value` parameter returned by `fetchResultStatus` is base64 encoded and must be decoded before displaying to users.
+
+### Switching Templates
+
+Switch the output format for an existing session:
+
+```swift
+VoiceToRxRepo.shared.switchTemplate(
+    templateID: newTemplateID,
+    sessionID: sessionID
+) { result in
+    switch result {
+    case .success(let response):
+        // Updated response with new template output
+        break
+    case .failure(let error):
+        print("Failed to switch template: \(error.localizedDescription)")
+        break
+    }
+}
+```
+
+### Updating Results
+
+Update edited content back to the server:
+
+```swift
+let request = UpdateResultRequest(
+    // Configure request with updated content
+)
+
+VoiceToRxRepo.shared.updateResult(
+    sessionID: sessionID,
+    request: request
+) { result, errorStatus in
+    switch result {
+    case .success:
+        print("Result updated successfully")
+    case .failure(let error):
+        print("Failed to update: \(error.localizedDescription)")
+    }
+}
+```
+
+## Error Handling
+
+### Common Errors
+
+The SDK provides specific error types:
+
+```swift
+public enum EkaScribeError: Error {
+    case freeSessionLimitReached
+    case microphonePermissionDenied
+    case microphoneIsInUse
+    case vadDetectorFailed
+    case noSessionId
+    case audioSessionSetupFailed
+}
+```
+
+### Error Handling Example
+
+Here's a complete example of handling errors when starting a recording:
+
+```swift
+// Your implementation
+private func handleRecording() async {
+    do {
+        let templates: [OutputFormatTemplate] = [
+            // Your templates
+        ]
+        
+        // Calling SDK function
+        try await viewModel.startRecording(
+            conversationType: VoiceConversationType.conversation,
+            inputLanguage: [InputLanguageType.english, InputLanguageType.hindi],
+            templates: templates,
+            modelType: ModelType.lite
+        )
+        
+        // Successfully started recording
+    } catch let error as EkaScribeError {
+        // Handle SDK-specific errors
+        await MainActor.run {
+            switch error {
+            case .freeSessionLimitReached:
+                // Show upgrade prompt
+                showUpgradeAlert()
+            case .microphonePermissionDenied:
+                // Show permission alert
+                showPermissionAlert()
+            case .microphoneIsInUse:
+                // Show microphone in use alert
+                showMicrophoneInUseAlert()
+            default:
+                // Handle other SDK-specific errors
+                showGenericError(error.localizedDescription)
+            }
+        }
+    } catch {
+        // Handle generic errors (network, API, etc.)
+        await MainActor.run {
+            showGenericError(error.localizedDescription)
+        }
+    }
+}
+```
+
+## API Reference
+
+### VoiceToRxViewModel
+
+#### Properties
+
+```swift
+@Published public var screenState: RecordConsultationState
+```
+
+#### Methods
+
+```swift
+// Core recording methods
+public func startRecording(
+    conversationType: VoiceConversationType,
+    inputLanguage: [InputLanguageType],
+    templates: [OutputFormatTemplate],
+    modelType: ModelType
+) async throws
+
+public func stopRecording() async throws
+public func pauseRecording()
+public func resumeRecording() throws
+
+// Session management
+public func deleteRecording(id: UUID)
+public func clearSession()
+public func retryIfNeeded()
+```
+
+### VoiceToRxRepo
+
+#### Template Management
+
+```swift
+public func getTemplates(completion: @escaping (Result<TemplateResponse, Error>) -> Void)
+public func updateConfig(templates: [String], completion: @escaping (Result<Void, Error>) -> Void)
+```
+
+#### Session History
+
+```swift
+public func getEkaScribeHistory(completion: @escaping (Result<ScribeHistoryResponse, Error>) -> Void)
+```
+
+#### Result Management
+
+```swift
+public func fetchResultStatusResponse(
+    sessionID: String,
+    completion: @escaping (Result<VoiceToRxStatusResponse, Error>) -> Void
+)
+// Note: All response values are base64 encoded. Decode before displaying.
+
+public func switchTemplate(
+    templateID: String,
+    sessionID: String,
+    completion: @escaping (Result<VoiceToRxStatusResponse, Error>) -> Void
+)
+
+public func updateResult(
+    sessionID: String,
+    request: UpdateResultRequest,
+    completion: @escaping (Result<Void, ErrorStatus>) -> Void
+)
+```
+
+### Configuration Classes
+
+#### V2RxInitConfigurations
+
+```swift
+public class V2RxInitConfigurations {
+    public static let shared: V2RxInitConfigurations
+    
+    public var modelContainer: ModelContainer?
+    public var clientId: String?
+    public var ownerName: String?
+    public var ownerOID: String?
+    public var ownerUUID: String?
+    public var subOwnerOID: String?
+    public var subOwnerName: String?
+    public var appointmentID: String?
+}
+```
+
+#### AuthTokenHolder
+
+```swift
+public class AuthTokenHolder {
+    public static let shared: AuthTokenHolder
+    
+    public var authToken: String?
+    public var refreshToken: String?
+    public var bid: String?
+}
+```
+
+### Data Models
+
+#### OutputFormatTemplate
+
+```swift
+public struct OutputFormatTemplate {
+    public let templateID: String
+    public let templateType: TemplateType
+    public let templateName: String
+    
+    public init(
+        templateID: String,
+        templateType: TemplateType,
+        templateName: String
+    )
+}
+```
+
+#### VoiceToRxStatusResponse
+
+```swift
+public struct VoiceToRxStatusResponse {
+    public let data: VoiceToRxStatusData?
+}
+
+public struct VoiceToRxStatusData {
+    public let templateResults: TemplateResults?
+    public let output: [VoiceToRxOutput]?
+    public let audioMatrix: AudioMatrix?
+}
+
+public struct TemplateResults {
+    public let custom: [VoiceToRxOutput]?
+    public let transcript: [VoiceToRxOutput]?
+}
+```
+
+## Best Practices
+
+### Memory Management
+
+```swift
+class RecordingViewController: UIViewController {
+    private var viewModel: VoiceToRxViewModel?
+    
+    deinit {
+        // Clean up resources
+        viewModel?.clearSession()
+    }
+    
+    override func viewWillDisappear(_ animated: Bool) {
+        super.viewWillDisappear(animated)
+        
+        // Pause recording when leaving screen
+        if case .listening = viewModel?.screenState {
+            viewModel?.pauseRecording()
+        }
+    }
+}
+```
+
+### State Management
+
+Always observe `screenState` changes to keep your UI in sync:
+
+```swift
+.onChange(of: viewModel.screenState) { oldState, newState in
+    // Update UI based on state
+    handleStateChange(newState)
+}
+```
+
+### Error Handling
+
+Always handle errors from async operations using try-catch:
+
+```swift
+// Your implementation
+private func startRecording() async {
+    do {
+        let templates: [OutputFormatTemplate] = [
+            // Your templates
+        ]
+        
+        // Calling SDK function
+        try await viewModel.startRecording(
+            conversationType: VoiceConversationType.conversation,
+            inputLanguage: [InputLanguageType.english, InputLanguageType.hindi],
+            templates: templates,
+            modelType: ModelType.lite
+        )
+        
+        // Successfully started recording
+    } catch {
+        // Handle error appropriately
+        await MainActor.run {
+            showError(error)
+        }
+    }
+}
+```
+
+## Troubleshooting
+
+### Microphone Permission Issues
+
+If microphone permission is denied:
+
+1. Check `Info.plist` has `NSMicrophoneUsageDescription`
+2. Request permission programmatically if needed
+3. Guide users to Settings if permission was previously denied
+
+### Session Creation Failures
+
+If sessions fail to create:
+
+1. Verify `ownerOID` is set in `V2RxInitConfigurations.shared`
+2. Check `AuthTokenHolder.shared.authToken` is valid
+3. Ensure network connectivity
+4. Check for free session limit if applicable
+
+### Result Not Available
+
+If results are not available after processing:
+
+1. Check `screenState` transitions to `.resultDisplay`
+2. Verify session ID is available: `viewModel.sessionID`
+3. Use `VoiceToRxRepo.shared.fetchResultStatusResponse` to get full response
+4. Check network connectivity for result retrieval
diff --git a/api-reference/health-ai/ekascribe/System-Requirements.mdx b/api-reference/health-ai/ekascribe/System-Requirements.mdx
new file mode 100644
index 00000000..1fc3ab34
--- /dev/null
+++ b/api-reference/health-ai/ekascribe/System-Requirements.mdx
@@ -0,0 +1,18 @@
+
+
+Before integrating EkaScribe, ensure your system meets the following requirements:
+
+#### Platform Requirements
+- **Google Chrome (Web)**: Version 100+
+- **Android App**: Android OS version 10+
+- **iOS App**: iOS version 14+
+
+#### Network Requirements
+- **Internet Speed**: Minimum 1 Mbps (recommended: 5+ Mbps)
+
+#### Hardware Requirements
+- **Microphone/Audio Capture Device**: Required
+
+> **Note**: EkaScribe uses audio from doctor-patient interactions. Using a quality external microphone improves audio quality and transcription accuracy.
+
+---
\ No newline at end of file
diff --git a/api-reference/health-ai/ekascribe/ekascribe-v2/ekascribe.yaml b/api-reference/health-ai/ekascribe/ekascribe-v2/ekascribe.yaml
index 980d1808..436bdc69 100644
--- a/api-reference/health-ai/ekascribe/ekascribe-v2/ekascribe.yaml
+++ b/api-reference/health-ai/ekascribe/ekascribe-v2/ekascribe.yaml
@@ -102,12 +102,31 @@ paths:
                       - "bn"
                       - "mr"
                       - "pa"
+                      - "or"
                   example: ["en-IN"]
+                
+                output_language:
+                  type: string
+                  description: Output language for the transcription result
+                  enum:
+                    - "en-IN"
+                    - "en-US"
+                    - "hi"
+                    - "gu"
+                    - "kn"
+                    - "ml"
+                    - "ta"
+                    - "te"
+                    - "bn"
+                    - "mr"
+                    - "pa"
+                    - "or"
+                  example: "en-IN"
                 speciality:
                   type: string
                   description: Medical speciality context for better transcription accuracy
                   example: "general_medicine"
-                
+
                 output_format_template:
                   type: array
                   description: Array of template configurations for output format
@@ -140,8 +159,9 @@ paths:
                 visitid: "09e4f00f-d665-4212-b77c-b2dd5f22bd92_1742560488782"
               mode: "dictation"
               input_language: ["en-IN"]
+              output_language: "en-IN"
               speciality: "general_medicine"
-              output_format_template: [{"template_id": "eka_emr_template", "language_output": "en-IN", "codification_needed": false}]
+              output_format_template: [{"template_id": "eka_emr_template", "codification_needed": false}]
               transfer: "non-vaded"
               batch_s3_url: "s3://m-pp-voice2rx/250307/R-S3-195D5131-D014-56A8-ACCF-2F8F2D230DEC/"
       security:
diff --git a/api-reference/health-ai/ekascribe/ekascribe-v2/init.mdx b/api-reference/health-ai/ekascribe/ekascribe-v2/init.mdx
index dcf2ae57..85d0e79a 100644
--- a/api-reference/health-ai/ekascribe/ekascribe-v2/init.mdx
+++ b/api-reference/health-ai/ekascribe/ekascribe-v2/init.mdx
@@ -36,3 +36,23 @@ Eka Care supports transcription in multiple languages. Specify the appropriate l
 | `bn` | Bengali |
 | `mr` | Marathi |
 | `pa` | Punjabi |
+| `or` | Oriya |
+
+## Supported Output Languages
+
+Eka Care supports generating transcription output in multiple languages, but only one can be selected at a time. Specify the appropriate language ID in the `output_language` parameter.
+
+| Language ID | Language Name |
+|-------------|---------------|
+| `en-IN` | English (India) |
+| `en-US` | English (United States) |
+| `hi` | Hindi |
+| `gu` | Gujarati |
+| `kn` | Kannada |
+| `ml` | Malayalam |
+| `ta` | Tamil |
+| `te` | Telugu |
+| `bn` | Bengali |
+| `mr` | Marathi |
+| `pa` | Punjabi |
+| `or` | Oriya |
diff --git a/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.mdx b/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.mdx
new file mode 100644
index 00000000..bd18cda8
--- /dev/null
+++ b/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.mdx
@@ -0,0 +1,34 @@
+---
+title: IP Allowlisting for Clients
+description: Allowlisting and endpoint information for Eka Scribe APIs & Audio transcription
+---
+
+Ensure your network/firewall is configured to allow inbound connections from the below URLs for seamless integration with Eka Scribe & audio transcription APIs.
+
+## Production
+- **Allowed URLs:**
+  - `*.eka.care`
+
+## Staging
+- **Allowed URLs:**
+  - `*.dev.eka.care`
+
+## S3 Bucket URLs
+
+### Production
+```
+https://m-prod-voice-record.s3.ap-south-1.amazonaws.com
+https://m-prod-voice2rx-batch.s3.ap-south-1.amazonaws.com
+https://m-prod-ekascribe-batch.s3.amazonaws.com
+```
+
+### Staging
+```
+https://m-dev-voice-record.s3.ap-south-1.amazonaws.com
+https://m-dev-voice2rx-batch.s3.ap-south-1.amazonaws.com
+```
+
+---
+
+> eka.care is hosted on AWS Cloudfront, Make sure you have allowlisted [AWS CloudFront IP Addresses.](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LocationsOfEdgeServers.html)
+
diff --git a/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.yaml b/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.yaml
new file mode 100644
index 00000000..d32f1b51
--- /dev/null
+++ b/api-reference/health-ai/ekascribe/ip-allowlisting-for-clients.yaml
@@ -0,0 +1,88 @@
+openapi: 3.0.0
+info:
+  title: EkaScribe IP Allowlisting Information
+  description: Allowlisting and endpoint information for Eka Scribe APIs & Audio transcription
+  version: 1.0.0
+  contact:
+    name: Eka Care Support
+    url: https://eka.care/
+    email: support@eka.care
+
+servers:
+  - url: https://api.eka.care
+    description: Production server - Allowed URL pattern *.eka.care
+  - url: https://api.dev.eka.care
+    description: Staging server - Allowed URL pattern *.dev.eka.care
+
+tags:
+  - name: Network Configuration
+    description: IP allowlisting and network configuration requirements
+
+paths:
+  /network-info:
+    get:
+      tags:
+        - Network Configuration
+      summary: Get Network Configuration Requirements
+      description: |
+        Ensure your network/firewall is configured to allow inbound connections from the below URLs for seamless integration with Eka Scribe & audio transcription APIs.
+        
+        ## Production Environment
+        - **Allowed URLs:** `*.eka.care`
+        
+        ## Staging Environment
+        - **Allowed URLs:** `*.dev.eka.care`
+        
+        ## S3 Bucket URLs
+        
+        ### Production
+        - `https://m-prod-voice-record.s3.ap-south-1.amazonaws.com`
+        - `https://m-prod-voice2rx-batch.s3.ap-south-1.amazonaws.com`
+        - `https://m-prod-ekascribe-batch.s3.amazonaws.com`
+        
+        ### Staging
+        - `https://m-dev-voice-record.s3.ap-south-1.amazonaws.com`
+        - `https://m-dev-voice2rx-batch.s3.ap-south-1.amazonaws.com`
+        
+        ## Important Notes
+        - eka.care is hosted on AWS CloudFront
+        - Make sure you have allowlisted [AWS CloudFront IP Addresses](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/LocationsOfEdgeServers.html)
+      responses:
+        200:
+          description: Network configuration information
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  production:
+                    type: object
+                    properties:
+                      urls:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.eka.care"]
+                      s3_buckets:
+                        type: array
+                        items:
+                          type: string
+                        example:
+                          - "https://m-prod-voice-record.s3.ap-south-1.amazonaws.com"
+                          - "https://m-prod-voice2rx-batch.s3.ap-south-1.amazonaws.com"
+                          - "https://m-prod-ekascribe-batch.s3.amazonaws.com"
+                  staging:
+                    type: object
+                    properties:
+                      urls:
+                        type: array
+                        items:
+                          type: string
+                        example: ["*.dev.eka.care"]
+                      s3_buckets:
+                        type: array
+                        items:
+                          type: string
+                        example:
+                          - "https://m-dev-voice-record.s3.ap-south-1.amazonaws.com"
+                          - "https://m-dev-voice2rx-batch.s3.ap-south-1.amazonaws.com"
diff --git a/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.mdx b/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.mdx
deleted file mode 100644
index 71071b78..00000000
--- a/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: IP Whitelisting for Clients
-description: Whitelisting and endpoint information for Eka Scribe APIs & Audio transcription
----
-
-# IP Whitelisting & Endpoint Information
-
-## Production
-- **Allowed URLs:**
-  - `*.eka.care`
-- **Allowed IPs:**
-  - 13.127.159.148/32
-  - 52.66.111.19/32
-  - 15.206.223.155/32
-  - 3.6.124.126/32
-
-## Staging
-- **Allowed URLs:**
-  - `*.dev.eka.care`
-- **Allowed IPs:**
-  - 3.6.115.57/32
-  - 13.204.33.30/32
-  - 43.204.151.111/32
-
-## S3 Bucket URLs
-
-### Production
-```
-https://m-prod-voice-record.s3.ap-south-1.amazonaws.com
-https://m-prod-voice2rx-batch.s3.ap-south-1.amazonaws.com
-```
-
-### Staging
-```
-https://m-dev-voice-record.s3.ap-south-1.amazonaws.com
-https://m-dev-voice2rx-batch.s3.ap-south-1.amazonaws.com
-```
-
----
-
-> Ensure your network/firewall is configured to allow outbound connections to the above IPs and URLs for seamless integration with Eka Scribe & audio transcription APIs.
diff --git a/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.yaml b/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.yaml
deleted file mode 100644
index 146df3dc..00000000
--- a/api-reference/health-ai/ekascribe/ip-whitelisting-for-clients.yaml
+++ /dev/null
@@ -1,25 +0,0 @@
-# Whitelisting and Endpoint Information for Eka Care Audio Transcription
-
-whitelisting:
-  production:
-    urls:
-      - "*.eka.care"
-    ips:
-      - 13.127.159.148/32
-      - 52.66.111.19/32
-      - 15.206.223.155/32
-      - 3.6.124.126/32
-  staging:
-    urls:
-      - "*.dev.eka.care"
-    ips:
-      - 3.6.115.57/32
-      - 13.204.33.30/32
-      - 43.204.151.111/32
-s3_buckets:
-  production:
-    - https://m-prod-voice-record.s3.ap-south-1.amazonaws.com
-    - https://m-prod-voice2rx-batch.s3.ap-south-1.amazonaws.com
-  staging:
-    - https://m-dev-voice-record.s3.ap-south-1.amazonaws.com
-    - https://m-dev-voice2rx-batch.s3.ap-south-1.amazonaws.com
diff --git a/api-reference/health-ai/ekascribe/overview.mdx b/api-reference/health-ai/ekascribe/overview.mdx
index f8ee0e61..b14f8395 100644
--- a/api-reference/health-ai/ekascribe/overview.mdx
+++ b/api-reference/health-ai/ekascribe/overview.mdx
@@ -99,3 +99,22 @@ Instead of polling for results, you can register a webhook to receive automatic
 - Reduced API calls
 
 ---
+
+## 💻 System Requirements
+
+Before integrating EkaScribe, ensure your system meets the following requirements:
+
+#### Platform Requirements
+- **Google Chrome (Web)**: Version 100+
+- **Android App**: Android OS version 10+
+- **iOS App**: iOS version 14+
+
+#### Network Requirements
+- **Internet Speed**: Minimum 1 Mbps (recommended: 5+ Mbps)
+
+#### Hardware Requirements
+- **Microphone/Audio Capture Device**: Required
+
+> **Note**: EkaScribe uses audio from doctor-patient interactions. Using a quality external microphone improves audio quality and transcription accuracy.
+
+---
diff --git a/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch.mdx b/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch.mdx
index 64c35cd8..582d04ad 100644
--- a/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch.mdx
+++ b/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch.mdx
@@ -1,5 +1,12 @@
 ---
 openapi: POST /abdm/v1/hip/care-context/data/on-fetch
 title: Push care context data to HIU
-description: The HIP holding the user data is responsible for sharing the data with the HIU after validating the consent approved by the user.
+description: >
+  Use this API to push encrypted FHIR data to the HIU after receiving the [`abha.hip_data_fetch`](/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch) webhook.
+
+
+  The HIP is responsible for preparing ABDM-compliant FHIR bundles, encrypting them using the key information received in the webhook, and pushing the data through this API. Use the `transaction_id` from the webhook payload to correlate the request.
+
+
+  This API is only needed if you are **not** storing health data on Eka servers.
 ---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/care-contexts/ecdh-decrypt.mdx b/api-reference/user-app/abdm-connect/care-contexts/ecdh-decrypt.mdx
new file mode 100644
index 00000000..c6827019
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/care-contexts/ecdh-decrypt.mdx
@@ -0,0 +1,24 @@
+---
+openapi: POST /abdm/v1/ecdh/decrypt
+title: Decrypt Data
+description: >
+  Decrypt data using ECDH key exchange.
+
+
+  This API decrypts health data received from external HIPs/HIUs via ABDM. A shared secret is derived from the receiver's private key and the sender's public key. The IV and salt are computed from the XOR of sender and receiver nonces, and the data is decrypted using AES-256-GCM.
+
+
+  **Algorithm details:**
+
+  - **Key Agreement:** ECDH on Curve25519 (Weierstrass form)
+
+  - **Key Derivation:** HKDF-SHA256
+
+  - **Symmetric Encryption:** AES-256-GCM
+
+  - **Nonce Handling:** IV and salt are derived from XOR of sender and receiver nonces
+
+
+  For more details, refer to the [ABDM Encryption and Decryption Guide](https://sandbox.abdm.gov.in/sandbox/v3/new-documentation?doc=EncryptionandDecryptions).
+
+---
diff --git a/api-reference/user-app/abdm-connect/care-contexts/ecdh-encrypt.mdx b/api-reference/user-app/abdm-connect/care-contexts/ecdh-encrypt.mdx
new file mode 100644
index 00000000..129d9179
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/care-contexts/ecdh-encrypt.mdx
@@ -0,0 +1,27 @@
+---
+openapi: POST /abdm/v1/ecdh/encrypt
+title: Encrypt Data
+description: >
+  Encrypt data using ECDH key exchange.
+
+
+  This API encrypts plaintext health data using ECDH shared secret derivation. A shared secret is derived from the sender's private key and the receiver's public key. The IV and salt are computed from the XOR of sender and receiver nonces, and the data is encrypted using AES-256-GCM.
+
+
+  **Algorithm details:**
+
+  - **Key Agreement:** ECDH on Curve25519 (Weierstrass form)
+
+  - **Key Derivation:** HKDF-SHA256
+
+  - **Symmetric Encryption:** AES-256-GCM
+
+  - **Nonce Handling:** IV and salt are derived from XOR of sender and receiver nonces
+
+
+  The response includes the base64-encoded encrypted data and the public key material to share with the receiver.
+
+
+  For more details, refer to the [ABDM Encryption and Decryption Guide](https://sandbox.abdm.gov.in/sandbox/v3/new-documentation?doc=EncryptionandDecryptions).
+
+---
diff --git a/api-reference/user-app/abdm-connect/care-contexts/ecdh-keys.mdx b/api-reference/user-app/abdm-connect/care-contexts/ecdh-keys.mdx
new file mode 100644
index 00000000..30154f42
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/care-contexts/ecdh-keys.mdx
@@ -0,0 +1,27 @@
+---
+openapi: GET /abdm/v1/ecdh/keys
+title: Generate ECDH Key Pair
+description: >
+  Generate an ECDH key pair with nonce for encryption/decryption operations.
+
+
+  This API generates a new ECDH key pair on Curve25519 (Weierstrass form) along with a random 32-byte nonce. The key pair and nonce are used for encrypting and decrypting health data exchanged via ABDM.
+
+
+  **Algorithm details:**
+
+  - **Key Agreement:** ECDH on Curve25519 (Weierstrass form)
+
+  - **Key Derivation:** HKDF-SHA256
+
+  - **Symmetric Encryption:** AES-256-GCM
+
+  - **Nonce Handling:** IV and salt are derived from XOR of sender and receiver nonces
+
+
+  Store the private key securely on your side. The public key and nonce are shared with the counterparty (HIP/HIU) during data exchange.
+
+
+  For more details, refer to the [ABDM Encryption and Decryption Guide](https://sandbox.abdm.gov.in/sandbox/v3/new-documentation?doc=EncryptionandDecryptions).
+
+---
diff --git a/api-reference/user-app/abdm-connect/care-contexts/getting-started.mdx b/api-reference/user-app/abdm-connect/care-contexts/getting-started.mdx
index 7b4ae75e..1a40359c 100644
--- a/api-reference/user-app/abdm-connect/care-contexts/getting-started.mdx
+++ b/api-reference/user-app/abdm-connect/care-contexts/getting-started.mdx
@@ -4,6 +4,33 @@ title: Overview
 
 A Care Context represents a logical grouping of health records. Each HMIS, LMIS, or PHR system should determine how to organize data into one or more care contexts for a user. For example, a hospital system might create a care context for each hospital visit, a lab test is a care-context for LMIS, or user-uploaded records in a PHR app.
 
+# Care Context Linking and Data Sharing
+
+Enables health data exchange between Health Information Providers (HIPs) and Health Information Users (HIUs).
+
+<Steps>
+  <Step title="Link Care Contexts (HIP)">
+    The HIP links a care context to the patient's ABHA address using the [Care Context Link API](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking). This registers the care context with ABDM so it can be discovered and requested by HIUs.
+
+    You can optionally include the FHIR data as a base64-encoded string in the `data` field of the Link API request. If provided, Eka stores the data on its servers and handles data sharing automatically when an HIU requests it — you will **not** need to handle the `abha.hip_data_fetch` webhook.
+  </Step>
+  <Step title="Receive Linking Confirmation">
+    Listen for the [`abha.link_care_context`](/api-reference/user-app/abdm-connect/webhooks/link-care-context) webhook to confirm whether the care context was successfully linked (`LINKED`) or failed (`ERRORED`).
+  </Step>
+  <Step title="Handle Data Fetch Requests">
+    When an HIU requests data for a linked care context (after the user grants consent), you receive the [`abha.hip_data_fetch`](/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch) webhook. This webhook is sent only if you are **not** storing the data on Eka servers and need to provide it yourself.
+  </Step>
+  <Step title="Push Encrypted Data">
+    Prepare the ABDM-compliant FHIR bundle for the requested care contexts, encrypt it using the key information from the webhook, and push it via the [Care Context Data On-Fetch API](/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch).
+  </Step>
+</Steps>
+
+<Note>
+If you store health data on Eka servers — either by passing base64-encoded FHIR data in the `data` field of the [Link API](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking), or via the [Upload API](/api-reference/user-app/records/obtain-authorization) — Eka handles data sharing automatically and you will **not** receive the `abha.hip_data_fetch` webhook.
+</Note>
+
+---
+
 # Listing Care Contexts
 <Note>
 This feature is useful for displaying a list of care contexts to a doctor (HMIS) or within a PHR app.
@@ -25,9 +52,9 @@ Listing linked Care Contexts involves two steps, as an ABHA address could have t
 
 Care contexts can be linked to an ABHA in various ways, depending on the document type.
 
-## HIP Inititated Linking
+## HIP Initiated Linking
 
-Use the [Link](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking) API to create the care context
+Use the [Link](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking) API to create the care context. Once linked, you will receive the [`abha.link_care_context`](/api-reference/user-app/abdm-connect/webhooks/link-care-context) webhook with the linking status.
 
 ## Upload a Medical Record
 
diff --git a/api-reference/user-app/abdm-connect/care-contexts/hiu-keys.mdx b/api-reference/user-app/abdm-connect/care-contexts/hiu-keys.mdx
new file mode 100644
index 00000000..2f98de10
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/care-contexts/hiu-keys.mdx
@@ -0,0 +1,16 @@
+---
+openapi: PATCH /abdm/v1/hiu/keyset
+title: Update public keyset
+description: >
+  API to update the HIU's public keyset.
+
+
+  The client must generate a key pair, store the private key securely on their side, and push the public key and nonce to Eka using this API. This keyset can be updated at any time.
+
+
+  When requesting health data from external HIPs via ABDM, Eka shares this public key and nonce with the HIP. The client can then use their stored private key along with the public key shared by the external HIP to decrypt the health data received on the [Data Push Webhook](/api-reference/user-app/abdm-connect/webhooks/hiu-data-push).
+
+
+  For details on key generation, encryption, and decryption, refer to the [ABDM Encryption and Decryption Guide](https://sandbox.abdm.gov.in/sandbox/v3/new-documentation?doc=EncryptionandDecryptions).
+
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking.mdx b/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking.mdx
index d6792000..4db1e437 100644
--- a/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking.mdx
+++ b/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking.mdx
@@ -1,4 +1,13 @@
 ---
 openapi: POST /abdm/v1/care-contexts/link
 title: Care context linking
+description: >
+  Use this API to link a care context to the patient's ABHA address. A care context represents a visit, test, or any logical grouping of health records.
+
+
+  After calling this API, listen for the [`abha.link_care_context`](/api-reference/user-app/abdm-connect/webhooks/link-care-context) webhook to confirm whether the linking was successful. Once linked, other HIUs can request data for this care context through ABDM's consent flow.
+
+
+  You can optionally pass the FHIR data as a base64-encoded string in the `data` field. If provided, Eka stores it and handles data sharing automatically — you won't need to handle the `abha.hip_data_fetch` webhook. If not provided, you will receive the [`abha.hip_data_fetch`](/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch) webhook when an HIU requests the data.
+
 ---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/consents/getting-started.mdx b/api-reference/user-app/abdm-connect/consents/getting-started.mdx
index ed1f063c..2d32f4a8 100644
--- a/api-reference/user-app/abdm-connect/consents/getting-started.mdx
+++ b/api-reference/user-app/abdm-connect/consents/getting-started.mdx
@@ -2,33 +2,63 @@
 title: Overview
 ---
 
-A unique identifier assigned to each consent request.
+Milestone 3 covers two sides of the same flow: an HIU requesting access to a patient's health records, and the patient approving or denying that request. Once consent is approved, EKA handles all the intermediate ABDM gateway callbacks to fetch the data from the HIP.
 
-**Consent Artefacts**
+<Note>User authorization is required for all consent operations (approve, deny, revoke).</Note>
 
-Consent artefacts are generated upon the approval of consents.
-Multiple consent artefacts can exist for a single consent, each corresponding to different providers.
-These artefacts represent the linkage between a healthcare provider (HIP) and care contexts.
+---
 
-Upon receiving a consent request, users can approve or deny the request.
-Additionally, they can revoke consent given for older requests.
+## HIU: Requesting Health Data
 
-<Note> User Authorization will be required for all these operations.</Note>
+An HIU initiates the flow by creating a consent request. The patient receives it on their PHR app and acts on it.
 
-### Consent Management: Approve, Deny, or Revoke Requests
 <Steps>
-    <Step title="Approve Consent Request">
-        Use the [Consent Approval](/api-reference/user-app/abdm-connect/consents/consent-approve) endpoint to approve a
-        consent request. You will need to provide necessary consent, care contexts and hip details to process the approval.
-    </Step>
-    <Step title="Deny Consent Request">
-        Use the [Consent Deny](/api-reference/user-app/abdm-connect/consents/consent-deny) endpoint to deny a consent request.
-        Consent id and a proper reason with be required to deny the consent request.
-    </Step>
-    <Step title="Revoke Consent Request">
-        Use the [Consent Revoke](/api-reference/user-app/abdm-connect/consents/consent-revoke) endpoint to revoke an existing consent.
-        Consent Artefact Id will be need to revoke the consent for particular hip.
-    </Step>
+  <Step title="Create a consent request">
+    Use the [Create Consent](/api-reference/user-app/abdm-connect/consents/consent-create) API to raise a request for a patient's health records. The request specifies the patient's ABHA address, the purpose, the date range of records needed, and the HIPs to fetch from.
+  </Step>
+  <Step title="Patient approves the request">
+    The patient receives the request on their PHR app and approves it. Once approved, EKA handles all the ABDM gateway callbacks required to trigger data fetch from the HIP — no action needed on your side.
+  </Step>
+  <Step title="Receive the health data">
+    Once the HIP pushes the data, it is delivered to you in one of two ways depending on how your integration is set up:
+
+    **If you manage data on your side:**
+    You receive the `abha.hiu_data_push` webhook with the encrypted FHIR bundle and `key_information` needed to decrypt it. Set up your HIU public keyset using the [Update Keyset](/api-reference/user-app/abdm-connect/care-contexts/hiu-keys) API — EKA shares this with the HIP so they can encrypt the data for you.
+
+    [abha.hiu_data_push webhook →](/api-reference/user-app/abdm-connect/webhooks/hiu-data-push)
+
+    **If EKA stores the data:**
+    Call the [Retrieve Health Records](/api-reference/user-app/records/retrieve-health-records) API with the `care_context_id` as the identifier. Get the `care_context_id` from the [Consent Details](/api-reference/user-app/abdm-connect/consents/consent-details) API after approval.
+  </Step>
 </Steps>
 
+---
+
+## Patient / PHR App: Managing Consent
+
+From the patient's side, consent requests arrive and can be approved, denied, or revoked at any time.
+
+<Steps>
+  <Step title="List consent requests">
+    Use the [List Consents](/api-reference/user-app/abdm-connect/consents/consent-list) API to fetch all pending and past consent requests for the patient.
+  </Step>
+  <Step title="Approve a request">
+    Use the [Approve Consent](/api-reference/user-app/abdm-connect/consents/consent-approve) API. You need to provide the consent ID, the care contexts to share, and the HIP details.
+
+    On approval, ABDM generates consent artefacts — one per HIP involved. These artefacts authorize the HIU to fetch records from those HIPs.
+  </Step>
+  <Step title="Deny a request">
+    Use the [Deny Consent](/api-reference/user-app/abdm-connect/consents/consent-deny) API with the consent ID and a reason.
+  </Step>
+  <Step title="Revoke a granted consent">
+    Use the [Revoke Consent](/api-reference/user-app/abdm-connect/consents/consent-revoke) API with the consent artefact ID to revoke access for a specific HIP.
+  </Step>
+</Steps>
+
+---
+
+## Auto-Approval
+
+For recurring or trusted access patterns, you can configure auto-approval policies so patients don't need to manually approve every request.
 
+[Configure Auto-Approval →](/api-reference/user-app/abdm-connect/consents/auto-approval/update-auto-approval-policy)
diff --git a/api-reference/user-app/abdm-connect/enrollment/aadhaar/auto-login.mdx b/api-reference/user-app/abdm-connect/enrollment/aadhaar/auto-login.mdx
new file mode 100644
index 00000000..b0f46813
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/enrollment/aadhaar/auto-login.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /abdm/na/v1/registration/aadhaar/auto-login
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture.mdx b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture.mdx
new file mode 100644
index 00000000..a2b8ed29
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /abdm/na/v1/face-auth/capture
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init.mdx b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init.mdx
new file mode 100644
index 00000000..a08359d1
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /abdm/na/v1/face-auth/init
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify.mdx b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify.mdx
new file mode 100644
index 00000000..b771f0ba
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify.mdx
@@ -0,0 +1,3 @@
+---
+openapi: post /abdm/na/v1/face-auth/verify
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/enrollment/face-auth/intro.mdx b/api-reference/user-app/abdm-connect/enrollment/face-auth/intro.mdx
new file mode 100644
index 00000000..2464e285
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/enrollment/face-auth/intro.mdx
@@ -0,0 +1,62 @@
+---
+title: Overview
+description: Authenticate users via Aadhaar-based facial recognition
+---
+
+Face Authentication provides a secure and convenient way for users to verify their identity using Aadhaar-based facial recognition. This method allows users to authenticate themselves by scanning a QR code and completing face verification on their mobile device.
+
+## How It Works
+
+The Face Authentication flow consists of three sequential API calls:
+
+<Steps>
+  <Step title="Initialize Face Auth">
+    Call the [Init API](/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init) to start a face authentication session. This generates a unique transaction ID and a QR code that the user scans with their mobile device.
+  </Step>
+  <Step title="Poll for Status">
+    Use the [Capture API](/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture) to poll the authentication status. Continue polling until the status changes from `Pending` to `Verified`. This indicates the user has successfully completed face verification on their device.
+  </Step>
+  <Step title="Retrieve User Information">
+    Once verified, call the [Verify API](/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify) with the user's Aadhaar number to fetch the authenticated user's demographic information. This includes details like name, date of birth, gender, and address.
+  </Step>
+</Steps>
+
+## Flow Diagram
+
+```mermaid
+sequenceDiagram
+    participant Client
+    participant API
+    participant User
+    participant ABDM
+
+    Client->>API: POST /face-auth/init
+    API-->>Client: Transaction ID + QR Code
+    Client->>User: Display QR Code
+    User->>ABDM: Scan QR & Complete Face Auth
+
+    loop Poll until verified
+        Client->>API: POST /face-auth/capture (Transaction ID)
+        API-->>Client: Status (Pending/Verified)
+    end
+
+    Client->>API: POST /face-auth/verify (Transaction ID + Aadhaar)
+    API-->>Client: User Information
+    Client->>Client: Proceed to ABHA Creation
+```
+
+<CardGroup cols={3}>
+  <Card title="Init API" icon="play" href="/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init">
+    Start a face authentication session
+  </Card>
+  <Card title="Capture API" icon="rotate" href="/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture">
+    Poll authentication status
+  </Card>
+  <Card title="Verify API" icon="check" href="/api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify">
+    Retrieve verified user information
+  </Card>
+</CardGroup>
+
+## Next Steps
+
+After successfully retrieving user information through face authentication, users can proceed to create their ABHA address using the verified demographic details.
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started.mdx
new file mode 100644
index 00000000..b7ca076b
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started.mdx
@@ -0,0 +1,72 @@
+---
+title: "Overview"
+---
+
+This guide explains how to integrate with the **National Health Provider Registry (NHPR)** under the ABDM ecosystem. The integration is divided into three parts:
+
+1. **HPR APIs** — Create and manage Healthcare Professional IDs directly from your portal
+2. **HFR APIs** — Search, register, and link Health Facilities directly from your portal
+3. **Onboarding** — Register your HPR & HFR with ABDM and onboard them to the Eka system
+
+## 1. Healthcare Professional Registry (HPR)
+
+These APIs let you integrate HPR ID creation directly into your application, so healthcare professionals can register their digital identity without leaving your portal.
+
+<Steps>
+    <Step title="Aadhaar Authentication">
+        Initiate the process by sending an OTP to the professional's Aadhaar-linked mobile number. Verify the OTP to establish identity.
+    </Step>
+    <Step title="Verify Linked Mobile">
+        Verify that the mobile number provided by the user matches the one linked with their Aadhaar record. This ensures the contact details are authentic.
+    </Step>
+    <Step title="Check Existing HPR ID">
+        Check if an HPR ID already exists for the current transaction or Aadhaar profile. If it exists, you may skip creation; otherwise, proceed to generate a new ID.
+    </Step>
+    <Step title="Get ID Suggestions">
+        If no ID exists, retrieve a list of system-suggested HPR IDs (e.g., `dr.name@hpr`) based on the user's profile to help them choose a valid handle.
+    </Step>
+    <Step title="Create HPR ID">
+        Finalize the registration by creating the HPR ID using a chosen or available handle. This generates the professional's digital profile in the ABDM network.
+    </Step>
+</Steps>
+
+[HPR APIs →](/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp)
+
+## 2. Health Facility Registry (HFR)
+
+These APIs let you integrate facility management directly into your application, so you can search, register, and link health facilities from your portal.
+
+<Steps>
+    <Step title="Search Facility">
+        Check if the facility already exists in the registry before attempting to create a new one.
+    </Step>
+    <Step title="Onboard Facility">
+        Register a new facility in the ABDM registry. This requires submitting official details such as the facility name, physical address, and the authorizing doctor's OID.
+    </Step>
+    <Step title="Link Facility">
+        Once a facility is identified or onboarded, connect it to the ABDM Bridge software. This linkage allows the facility to exchange health data and participate in the digital health network securely.
+    </Step>
+</Steps>
+
+[HFR APIs →](/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility)
+
+## 3. Onboarding to Eka
+
+Once the HPR ID and HFR ID have been created and registered on the ABDM portal, the final step is to onboard the facility into the Eka system. This connects your ABDM-registered facility to the Eka Bridge, enabling health data exchange through EKA's ABDM Connect.
+
+<Steps>
+    <Step title="Create HPR ID">
+        Register as a Facility Manager or Healthcare Professional on the ABDM portal.
+    </Step>
+    <Step title="Register Facility (HFR ID)">
+        Log in with your HPR ID, add facility details, upload documents, and submit for approval. Once approved, you receive the HFR ID.
+    </Step>
+    <Step title="Software Linkage">
+        From the facility dashboard, select Software Linkage and use the Eka Bridge ID to register your facility under Eka Bridge.
+    </Step>
+    <Step title="Onboard to Eka">
+        Call the onboard API to register the facility in the Eka system, completing the integration.
+    </Step>
+</Steps>
+
+[Onboarding Guide →](/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview)
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/link-facility.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/link-facility.mdx
new file mode 100644
index 00000000..e34a3d95
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/link-facility.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hfr/link
+title: Link HFR
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/onboard-facility.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/onboard-facility.mdx
new file mode 100644
index 00000000..ec39aba1
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/onboard-facility.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hfr/onboard
+title: Onboard HFR
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility.mdx
new file mode 100644
index 00000000..f723161c
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility.mdx
@@ -0,0 +1,4 @@
+---
+openapi: get /abdm/nhpr/v1/hfr/search/{hfrId}
+title: Search HFR
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-available.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-available.mdx
new file mode 100644
index 00000000..af0501ec
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-available.mdx
@@ -0,0 +1,6 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/check/available
+title: Check If HPR is Available
+---
+
+
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-exist.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-exist.mdx
new file mode 100644
index 00000000..e362da25
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-exist.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/check/exist
+title: Get HPR Info
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/create-hpr.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/create-hpr.mdx
new file mode 100644
index 00000000..78ae8a24
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/create-hpr.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/create
+title: Create HPR
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp.mdx
new file mode 100644
index 00000000..0b194160
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/init
+title: Get Aadhaar OTP
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-mobile-otp.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-mobile-otp.mdx
new file mode 100644
index 00000000..197e1ab1
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-mobile-otp.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/mobile/init
+title: Get Mobile OTP
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/suggest-ids.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/suggest-ids.mdx
new file mode 100644
index 00000000..a7a00e90
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/suggest-ids.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/suggest
+title: Suggest IDs
+---
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-aadhar-otp.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-aadhar-otp.mdx
new file mode 100644
index 00000000..b3b7c508
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-aadhar-otp.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/verify
+title: Verify Aadhaar OTP
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile-otp.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile-otp.mdx
new file mode 100644
index 00000000..f2a7df00
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile-otp.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/mobile/verify
+title: Verify Mobile OTP
+---
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile.mdx
new file mode 100644
index 00000000..56d793c9
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/nhpr/v1/hpr/aadhaar/demo/verify
+title: Verify Mobile
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview.mdx
new file mode 100644
index 00000000..fd026bcb
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview.mdx
@@ -0,0 +1,32 @@
+---
+title: Facility Onboarding
+description: Onboard your ABDM-registered healthcare facility to the Eka system
+---
+
+After your healthcare facility has been registered on the ABDM portal with a valid HPR ID and HFR ID, you need to onboard it into the Eka system. This final step connects your facility to the Eka Bridge, enabling it to participate in health data exchange through EKA's ABDM Connect.
+
+<Note>
+You can create HPR and HFR IDs either through the [ABDM portal](https://nhpr.abdm.gov.in/nhpr/v4/login) or programmatically using the [HPR](/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp) and [HFR](/api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility) APIs.
+</Note>
+
+## Prerequisites
+
+<Steps>
+    <Step title="Create HPR ID">
+        Every facility needs at least one registered healthcare professional. Create an HPR ID via Aadhaar-based verification — either through the [ABDM portal](https://nhpr.abdm.gov.in/nhpr/v4/login) or using the [HPR APIs](/api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp).
+    </Step>
+    <Step title="Register Facility (HFR ID)">
+        Log in with the HPR ID on the ABDM portal. Add facility details (name, address, type), upload required documents, and submit for approval. Once approved, you receive the **HFR ID** — the facility's unique identifier in the ABDM network.
+    </Step>
+    <Step title="Software Linkage">
+        From the facility dashboard on the ABDM portal, navigate to **Software Linkage**. Enter the **Eka Bridge ID** to register your facility under the Eka Bridge. This authorizes Eka to act as the software provider for your facility's ABDM transactions.
+    </Step>
+</Steps>
+
+## Onboard to Eka
+
+Once all prerequisites are complete, call the onboard API to register the facility in the Eka system.
+
+<Card title="Onboard Facility API" icon="rocket" href="/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding">
+  **POST** `/abdm/v1/hip/onboard`
+</Card>
diff --git a/api-reference/user-app/abdm-connect/providers/onboarding.mdx b/api-reference/user-app/abdm-connect/nhpr-abdm/onboarding.mdx
similarity index 100%
rename from api-reference/user-app/abdm-connect/providers/onboarding.mdx
rename to api-reference/user-app/abdm-connect/nhpr-abdm/onboarding.mdx
diff --git a/api-reference/user-app/abdm-connect/overview.mdx b/api-reference/user-app/abdm-connect/overview.mdx
new file mode 100644
index 00000000..35bca97b
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/overview.mdx
@@ -0,0 +1,176 @@
+---
+title: "Overview"
+description: "Understand what ABDM is, who the key players are, and what you can build with EKA's ABDM Connect APIs and SDKs."
+---
+
+# ABDM Connect
+
+**Ayushman Bharat Digital Mission (ABDM)** is India's national digital health infrastructure. It creates a shared ecosystem where patients, hospitals, labs, insurers, and health apps can exchange health data securely, with patient consent driving every transaction.
+
+EKA's **ABDM Connect** is a plug-and-play API and SDK suite that handles the ABDM gateway complexity so you don't have to.
+
+## The ABDM Ecosystem
+
+### Core Registries
+
+ABDM is built on four registries. Every entity gets a unique, verifiable identity through one of these.
+
+<CardGroup cols={2}>
+  <Card title="ABHA" icon="id-card">
+    **Ayushman Bharat Health Account**
+
+    The patient's health identity. Can be a 14-digit **ABHA Number** (KYC-verified via Aadhaar) or an **ABHA Address** like `nisha@abdm`. All health transactions in ABDM are anchored to this.
+  </Card>
+  <Card title="HPR" icon="user-doctor">
+    **Healthcare Professionals Registry**
+
+    A national registry of licensed healthcare professionals. Each doctor, nurse, or practitioner gets a unique **HPR ID** for verified digital identity.
+  </Card>
+  <Card title="HFR" icon="hospital">
+    **Health Facility Registry**
+
+    A national registry of health facilities, both government and private. Each facility gets a unique **HFR ID** used for record linking and patient discovery.
+  </Card>
+  <Card title="Consent Manager" icon="shield-halved">
+    **Consent Manager**
+
+    Manages the consent flow between HIPs (who hold data) and HIUs (who want access). The ABDM Gateway itself acts as the Consent Manager.
+  </Card>
+</CardGroup>
+
+### Roles in the Ecosystem
+
+There are two roles in ABDM. A product can play both.
+
+<CardGroup cols={2}>
+  <Card title="HIP" icon="database">
+    **Health Information Provider**
+
+    Hospitals, labs, clinics, and pharmacies that generate and hold patient health records. After a visit or test, a HIP links the records to the patient's ABHA address so they're discoverable and shareable.
+
+    *Examples: hospital HMS, diagnostic lab system, pharmacy software*
+  </Card>
+  <Card title="HIU" icon="magnifying-glass-chart">
+    **Health Information User**
+
+    Any entity that requests access to a patient's health records with the patient's consent. After consent is granted, the HIU pulls FHIR records from the relevant HIPs.
+
+    *Examples: insurance company, specialist referral system, wellness platform*
+  </Card>
+</CardGroup>
+
+## ABDM Milestones
+
+ABDM defines four certification milestones for HMIS/LMIS integrations. EKA's ABDM Connect covers all four.
+
+<Steps>
+  <Step title="M1 — ABHA Identity">
+    Required by all integrations: HIP, HIU, and PHR apps.
+
+    Every patient needs an ABHA identity before any health data can be linked or shared.
+
+    - Create an **ABHA Number** (14-digit, KYC-verified via Aadhaar or mobile OTP)
+    - Create an **ABHA Address** like `nisha@abdm`
+    - Login and session management
+    - Profile viewing, updates, and deletion
+    - KYC verification
+    - ABHA card and QR code generation
+    - Verify a patient's ABHA at facility check-in via QR scan (the HIP side of Scan & Share)
+
+    [ABHA Creation & Login APIs →](/api-reference/user-app/abdm-connect/registration/intro)
+  </Step>
+  <Step title="M2 — Care Context Linking & Data Sharing">
+    Required by HIPs: hospitals, labs, clinics, pharmacies.
+
+    Health records are grouped into care contexts (one per visit, test, or document). M2 is about linking these to a patient's ABHA address and serving them when an HIU requests them.
+
+    - HIP pushes records to a patient's ABHA address after each visit or test
+    - Patients can discover and pull unlinked records from any ABDM-connected facility
+    - List all linked providers and care contexts for an ABHA address
+    - Serve FHIR data when an HIU requests it, or store records on EKA and let us handle it automatically
+
+    [Care Context APIs →](/api-reference/user-app/abdm-connect/care-contexts/getting-started)
+  </Step>
+  <Step title="M3 — Consent Management & Data Fetching">
+    Required by HIUs: any entity accessing patient records.
+
+    Patients must explicitly consent before an HIU can access their records. M3 covers the full consent lifecycle and the data fetch that follows.
+
+    - Patients receive and act on consent requests from HIUs
+    - Approve, deny, or revoke consent at any time
+    - Auto-approval policies for recurring access
+    - HIU fetches encrypted FHIR data from HIPs after consent
+    - Encryption key management for secure transfer
+
+    [Consent APIs →](/api-reference/user-app/abdm-connect/consents/getting-started)
+  </Step>
+  <Step title="M4 — HPR & HFR Registration">
+    Required by all HMIS/LMIS integrations.
+
+    Every healthcare professional and facility must be registered in ABDM's national registries before they can participate in digital health transactions. M4 covers creating HPR IDs for doctors and nurses, and onboarding health facilities with HFR IDs.
+
+    - Create **HPR ID** for healthcare professionals via Aadhaar-based verification
+    - Check if an HPR ID already exists and get system-suggested IDs
+    - Search, onboard, and link **health facilities** (HFR) to the ABDM network
+    - Software linkage to connect facilities with the EKA Bridge for data exchange
+
+    [HPR & HFR APIs →](/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started)
+  </Step>
+</Steps>
+
+## PHR App
+
+PHR (Personal Health Record) App is a separate ABDM integration track, distinct from the HMIS milestones above. A PHR app is the patient-facing side of the ABDM ecosystem: patients create their ABHA, view records from every provider they've visited, manage consent, and share their profile at health facilities.
+
+A PHR app typically acts as both a HIP (storing user-uploaded records) and a HIU (fetching records from other providers on the patient's behalf).
+
+PHR app integration covers:
+- ABHA address creation and patient login
+- Viewing all linked care contexts and health records
+- Managing incoming consent requests
+- **Scan & Share** — patient scans a QR at a health facility to share their ABHA profile for registration
+- **Health locker** — patient-controlled storage for self-uploaded documents
+- **Subscription notifications** — get notified when a provider links new records
+
+[Scan & Share APIs →](/api-reference/user-app/abdm-connect/scan-and-share/getting-started)
+
+## What Can You Build
+
+<CardGroup cols={2}>
+  <Card title="Hospital / Clinic Product (HMS)" icon="hospital-user">
+    If you run a hospital or clinic system, you need to be a HIP. After every visit or test, link the patient's records to their ABHA address. When a patient later grants consent to another entity (like an insurer), your system serves those records automatically.
+
+  </Card>
+  <Card title="Consumer Health App (PHR)" icon="heart-pulse">
+    If you're building a patient-facing app, you need the PHR track on top of the milestones. Patients can aggregate their entire health history from every facility they've ever visited, manage consent, and check in at facilities by scanning a QR code.
+
+  </Card>
+  <Card title="Insurance / Analytics Platform (HIU)" icon="file-waveform">
+    If you need to access a patient's health records from any ABDM-connected provider, you need to be an HIU. You request consent from the patient, and once granted, pull their FHIR records directly.
+
+  </Card>
+  <Card title="Integrated Health Platform" icon="layer-group">
+    Large hospital networks and health platforms often need to be HIP, HIU, and PHR at once. Your HMS links records (HIP), doctors can pull history from outside (HIU), and patients have a portal to manage everything (PHR).
+
+  </Card>
+</CardGroup>
+
+## Next Steps
+
+<CardGroup cols={2}>
+  <Card title="Onboarding & Credentials" icon="rocket" href="/api-reference/authorization/getting-started#overview">
+    Get your credentials and onboard into ABDM through EKA Connect.
+  </Card>
+  <Card title="M1: ABHA Creation & Login" icon="user-plus" href="/api-reference/user-app/abdm-connect/registration/intro">
+    Start here: ABHA creation, login, and profile management.
+  </Card>
+  <Card title="M2: Care Context APIs" icon="link" href="/api-reference/user-app/abdm-connect/care-contexts/getting-started">
+    Link health records to ABHA addresses and enable data sharing.
+  </Card>
+  <Card title="M3: Consent APIs" icon="shield-check" href="/api-reference/user-app/abdm-connect/consents/getting-started">
+    Implement consent management and controlled data access.
+  </Card>
+  <Card title="M4: HPR & HFR APIs" icon="user-doctor" href="/api-reference/user-app/abdm-connect/nhpr-abdm/getting-started">
+    Register healthcare professionals and onboard health facilities.
+  </Card>
+</CardGroup>
diff --git a/api-reference/user-app/abdm-connect/profile/search/search.mdx b/api-reference/user-app/abdm-connect/profile/search/search.mdx
new file mode 100644
index 00000000..fb422684
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/profile/search/search.mdx
@@ -0,0 +1,4 @@
+---
+openapi: post /abdm/v1/profile/search
+title: Search ABHA
+---
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/providers/onboarding-overview.mdx b/api-reference/user-app/abdm-connect/providers/onboarding-overview.mdx
deleted file mode 100644
index ee1312de..00000000
--- a/api-reference/user-app/abdm-connect/providers/onboarding-overview.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Health Facility Onboarding
----
-This API is used to onboard a healthcare facility into our system after it has been successfully registered on the ABDM portal and software linkage has been completed using the Eka Bridge ID.
-
-## Prerequisites for Facility Onboarding
-<Steps>
-    <Step title="Create HPR ID">
-       Visit https://nhpr.abdm.gov.in/createID to register as Facility Manager or Healthcare Professional
-    </Step>
-    <Step title="Register Facility (HFR ID)">
-        Log in with HPR ID and add facility details, upload documents, and submit for approval. Once approved, you get the HFR ID
-    </Step>
-    <Step title="Software Linkage">
-        Go to the facility dashboard, select Software Linkage, and use the Eka Bridge ID to register your facility under Eka Bridge.
-    </Step>
-</Steps>
-
diff --git a/api-reference/user-app/abdm-connect/registration.yml b/api-reference/user-app/abdm-connect/registration.yml
index 65ca6519..6cbfe972 100644
--- a/api-reference/user-app/abdm-connect/registration.yml
+++ b/api-reference/user-app/abdm-connect/registration.yml
@@ -9,6 +9,139 @@ servers:
 - description: Stage/Sandbox
   url: https://api.dev.eka.care
 paths:
+  /abdm/na/v1/face-auth/capture:
+    post:
+      description: Capture PID endpoint is used to capture face-auth pid.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/FaceAuthCapturePIDRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FaceAuthCapturePIDResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Capture Face
+  /abdm/na/v1/face-auth/init:
+    post:
+      description: Face Auth endpoint is used to init face-auth endpoint.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/FaceAuthInitFaceAuthResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Face Auth Init
+  /abdm/na/v1/face-auth/verify:
+    post:
+      description: Verify PID endpoint is used to verify face-auth pid.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/FaceAuthVerifyFaceAuthRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/VerifyResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Verify Face
   /abdm/na/v1/profile/login/init:
     post:
       description: Generates an OTP for login. Supports login via Aadhaar number,
@@ -149,6 +282,52 @@ paths:
       security:
       - authApiKey: []
       summary: Verify OTP
+  /abdm/na/v1/registration/aadhaar/auto-login:
+    post:
+      description: API for Auto login
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreateRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/CreateResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Auto Login
   /abdm/na/v1/registration/aadhaar/create-phr:
     post:
       description: This API is used to create a new ABHA address
@@ -397,8 +576,593 @@ paths:
       summary: Resend OTP
   /abdm/na/v1/registration/aadhaar/verify:
     post:
-      description: This endpoint is used to verify Aadhaar otp generated for registration
-        using Aadhaar.
+      description: This endpoint is used to verify Aadhaar otp generated for registration
+        using Aadhaar.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/VerifyRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/VerifyResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Verify OTP
+  /abdm/na/v1/registration/mobile/create-phr:
+    post:
+      description: This API is used to create a new ABHA address for the user.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/CreateRequestType2'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/CreateResponseType2'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Create
+  /abdm/na/v1/registration/mobile/init:
+    post:
+      description: This endpoint is used to initiate the registration process for
+        a mobile number.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/InitRequestType2'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/InitResponseType2'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Generate OTP
+  /abdm/na/v1/registration/mobile/resend:
+    post:
+      description: This endpoint is used to resend a mobile registration request.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ResendRequestType3'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ResendResponseType3'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Resend OTP
+  /abdm/na/v1/registration/mobile/verify:
+    post:
+      description: This endpoint allows  to verify a mobile otp.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/VerifyRequestType3'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/VerifyResponseType3'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Verify OTP
+  /abdm/na/v1/registration/phr/check:
+    post:
+      description: This API endpoint allows to check whether provided health id is
+        already present in system.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ExistRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ModelsDoesHealthIdExistResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Does Abha Address Exist
+  /abdm/na/v1/registration/suggest:
+    get:
+      description: This API endpoint is used to fetch some suggested abha id that
+        are available on the basis of user details.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      - description: Middle Name
+        in: query
+        name: mn
+        schema:
+          description: Middle Name
+          examples:
+          - Singh
+          type: string
+      - description: Last Name
+        in: query
+        name: ln
+        schema:
+          description: Last Name
+          examples:
+          - Kumar
+          type: string
+      - description: First Name
+        in: query
+        name: fn
+        schema:
+          description: First Name
+          examples:
+          - Raj
+          type: string
+      - description: Date of Birth (YYYY-MM-DD)
+        in: query
+        name: dob
+        schema:
+          description: Date of Birth (YYYY-MM-DD)
+          examples:
+          - "1990-05-15"
+          type: string
+      - description: Transaction id received in the previous api.
+        in: query
+        name: transactionId
+        schema:
+          description: Transaction id received in the previous api.
+          type: string
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ModelsSuggestHealthIdResponse'
+          description: OK
+      security:
+      - authApiKey: []
+      summary: Suggest Abha Address
+  /abdm/nhpr/v1/hfr/link:
+    post:
+      description: Link a facility to the ABDM Bridge
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NhprUpdateBridgeRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprUpdateBridgeRequest'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/nhpr/v1/hfr/onboard:
+    post:
+      description: Onboard Facility
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NhprUpdateBridgeRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprOnboardFacilityResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/nhpr/v1/hfr/search/{hfrId}:
+    get:
+      description: Search Facility
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      - description: Hfr ID
+        in: path
+        name: hfrId
+        required: true
+        schema:
+          description: Hfr ID
+          type: string
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmInternalNhprRepoModelsFacility'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/nhpr/v1/hpr/aadhaar/check/available:
+    post:
+      description: Check HPR ID Availability
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NhprDoesHprExistRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprDoesHprExistResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/nhpr/v1/hpr/aadhaar/check/exist:
+    post:
+      description: Check if HPR ID Exists
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NhprTransactionId'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEKAIsHPRIDExistsResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/nhpr/v1/hpr/aadhaar/create:
+    post:
+      description: Create HPR ID
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -419,7 +1183,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/VerifyRequest'
+              $ref: '#/components/schemas/NhprEKACreateHPRID'
       responses:
         4XX:
           content:
@@ -437,14 +1201,13 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/VerifyResponse'
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEKACreateHPRIDResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Verify OTP
-  /abdm/na/v1/registration/mobile/create-phr:
+  /abdm/nhpr/v1/hpr/aadhaar/demo/verify:
     post:
-      description: This API is used to create a new ABHA address for the user.
+      description: Verify Aadhaar Linked Mobile
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -465,7 +1228,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/CreateRequestType2'
+              $ref: '#/components/schemas/NhprMobileOTPRequest'
       responses:
         4XX:
           content:
@@ -483,15 +1246,13 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/CreateResponseType2'
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaVerifiedResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Create
-  /abdm/na/v1/registration/mobile/init:
+  /abdm/nhpr/v1/hpr/aadhaar/init:
     post:
-      description: This endpoint is used to initiate the registration process for
-        a mobile number.
+      description: Get Aadhar OTP
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -512,7 +1273,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/InitRequestType2'
+              $ref: '#/components/schemas/ModelsHPRIDAadhaarInitRequest'
       responses:
         4XX:
           content:
@@ -530,14 +1291,13 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/InitResponseType2'
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaAadhaarResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Generate OTP
-  /abdm/na/v1/registration/mobile/resend:
+  /abdm/nhpr/v1/hpr/aadhaar/mobile/init:
     post:
-      description: This endpoint is used to resend a mobile registration request.
+      description: Generate Mobile OTP
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -558,7 +1318,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/ResendRequestType3'
+              $ref: '#/components/schemas/NhprMobileOTPRequest'
       responses:
         4XX:
           content:
@@ -576,14 +1336,13 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ResendResponseType3'
+                $ref: '#/components/schemas/NhprEkaAadhaarResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Resend OTP
-  /abdm/na/v1/registration/mobile/verify:
+  /abdm/nhpr/v1/hpr/aadhaar/mobile/verify:
     post:
-      description: This endpoint allows  to verify a mobile otp.
+      description: Verify Mobile OTP
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -604,7 +1363,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/VerifyRequestType3'
+              $ref: '#/components/schemas/NhprMobileVerifyRequest'
       responses:
         4XX:
           content:
@@ -622,15 +1381,13 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/VerifyResponseType3'
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaAadhaarResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Verify OTP
-  /abdm/na/v1/registration/phr/check:
+  /abdm/nhpr/v1/hpr/aadhaar/suggest:
     post:
-      description: This API endpoint allows to check whether provided health id is
-        already present in system.
+      description: Get Suggested HPR IDs
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -651,7 +1408,7 @@ paths:
         content:
           application/json:
             schema:
-              $ref: '#/components/schemas/ExistRequest'
+              $ref: '#/components/schemas/NhprTransactionId'
       responses:
         4XX:
           content:
@@ -669,15 +1426,18 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ModelsDoesHealthIdExistResponse'
+                properties:
+                  data:
+                    items:
+                      type: string
+                    type: array
+                type: object
           description: OK
       security:
       - authApiKey: []
-      summary: Does Abha Address Exist
-  /abdm/na/v1/registration/suggest:
-    get:
-      description: This API endpoint is used to fetch some suggested abha id that
-        are available on the basis of user details.
+  /abdm/nhpr/v1/hpr/aadhaar/verify:
+    post:
+      description: Verify Aadhar OTP
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -694,44 +1454,11 @@ paths:
         name: X-Hip-Id
         schema:
           type: string
-      - description: Middle Name
-        in: query
-        name: mn
-        schema:
-          description: Middle Name
-          examples:
-          - Singh
-          type: string
-      - description: Last Name
-        in: query
-        name: ln
-        schema:
-          description: Last Name
-          examples:
-          - Kumar
-          type: string
-      - description: First Name
-        in: query
-        name: fn
-        schema:
-          description: First Name
-          examples:
-          - Raj
-          type: string
-      - description: Date of Birth (YYYY-MM-DD)
-        in: query
-        name: dob
-        schema:
-          description: Date of Birth (YYYY-MM-DD)
-          examples:
-          - "1990-05-15"
-          type: string
-      - description: Transaction id received in the previous api.
-        in: query
-        name: transactionId
-        schema:
-          description: Transaction id received in the previous api.
-          type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/NhprEKAAadhaarVerifyRequest'
       responses:
         4XX:
           content:
@@ -749,11 +1476,10 @@ paths:
           content:
             application/json:
               schema:
-                $ref: '#/components/schemas/ModelsSuggestHealthIdResponse'
+                $ref: '#/components/schemas/HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaAadhaarResponse'
           description: OK
       security:
       - authApiKey: []
-      summary: Suggest Abha Address
   /abdm/uhi/v1/blood-bank/search:
     post:
       description: Search for Blood Bank District Wise
@@ -1158,7 +1884,7 @@ paths:
           description: OK
       security:
       - authApiKey: []
-  /abdm/uhi/v1/physical-consultation/booking/status:
+  /abdm/uhi/v1/physical-consultation/booking/order-status:
     get:
       description: Retrieve the current status of a physical consultation booking.
       parameters:
@@ -2561,6 +3287,88 @@ paths:
           description: No Content
       security:
       - authApiKey: []
+  /abdm/v1/ecdh/decrypt:
+    post:
+      description: Decrypt data using ECDH key exchange.
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ModelsDecryptPayload'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ModelsDecryptResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/v1/ecdh/encrypt:
+    post:
+      description: Encrypt data using ECDH key exchange.
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ModelsEncryptPayload'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ModelsEncryptResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/v1/ecdh/keys:
+    get:
+      description: Generate ECDH key pair with nonce for encryption/decryption operations.
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ModelsKeyPairWithNonce'
+          description: OK
+      security:
+      - authApiKey: []
   /abdm/v1/hip/care-context/data/on-fetch:
     post:
       description: API for HIP to push care context FHIR data to HIU
@@ -2605,22 +3413,6 @@ paths:
   /abdm/v1/hip/onboard:
     post:
       description: Onboard facility
-      parameters:
-      - description: Eka User ID (OID)
-        in: header
-        name: X-Pt-Id
-        schema:
-          type: string
-      - description: Partner User ID
-        in: header
-        name: X-Partner-Pt-Id
-        schema:
-          type: string
-      - description: Partner HIP ID
-        in: header
-        name: X-Hip-Id
-        schema:
-          type: string
       requestBody:
         content:
           application/json:
@@ -2729,6 +3521,31 @@ paths:
           description: Accepted
       security:
       - authApiKey: []
+  /abdm/v1/hiu/keyset:
+    patch:
+      description: API to update client public keyset
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/RecordsUpdateKeysetRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          description: OK
+      security:
+      - authApiKey: []
   /abdm/v1/profile:
     delete:
       description: This endpoint removes the specified ABHA profile along with all
@@ -3411,9 +4228,106 @@ paths:
           description: OK
       security:
       - authApiKey: []
-  /abdm/v1/profile/scan-and-pay/transaction-details/{request_id}:
-    get:
-      description: Retrieve open orders by request ID.
+  /abdm/v1/profile/scan-and-pay/transaction-details/{request_id}:
+    get:
+      description: Retrieve open orders by request ID.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      - description: Request ID
+        in: path
+        name: request_id
+        required: true
+        schema:
+          description: Request ID
+          type: string
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                properties:
+                  data:
+                    $ref: '#/components/schemas/ScanAndPayAcknowledgement'
+                  request_id:
+                    type: string
+                  status:
+                    enum:
+                    - REQUESTED_OPEN_ORDER
+                    - ' PROCESSING_OPEN_ORDER'
+                    - ' REQUESTED_PATIENT_SELECT'
+                    - ' PROCESSING_PATIENT_SELECT'
+                    - ' PROCESSING_PATIENT_NOTIFY'
+                    - ' REQUESTING_PATIENT_NOTIFY'
+                    - ' ERROR'
+                    examples:
+                    - PROCESSING_PATIENT_NOTIFY
+                    type:
+                    - "null"
+                    - string
+                type: object
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/v1/profile/search:
+    post:
+      description: Search KYCed ABHA profiles using mobile number
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ProfileDiscoverAbhaRequest'
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/ProfileSearchKycAbhaResponse'
+          description: OK
+      security:
+      - authApiKey: []
+  /abdm/v1/profile/share:
+    post:
+      description: Fetch the token from a hospital. <Note> Get the hip_id and counter_id
+        by reading the QR code of the Hospital/Clinic.</Note> <Note>Use the device
+        location for the location data</Note>
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -3430,13 +4344,17 @@ paths:
         name: X-Hip-Id
         schema:
           type: string
-      - description: Request ID
-        in: path
-        name: request_id
-        required: true
+      - description: OID is used to Identify the user.
+        in: query
+        name: oid
         schema:
-          description: Request ID
+          description: OID is used to Identify the user.
           type: string
+      requestBody:
+        content:
+          application/json:
+            schema:
+              $ref: '#/components/schemas/ScanandshareRequest'
       responses:
         4XX:
           content:
@@ -3454,26 +4372,7 @@ paths:
           content:
             application/json:
               schema:
-                properties:
-                  data:
-                    $ref: '#/components/schemas/ScanAndPayAcknowledgement'
-                  request_id:
-                    type: string
-                  status:
-                    enum:
-                    - REQUESTED_OPEN_ORDER
-                    - ' PROCESSING_OPEN_ORDER'
-                    - ' REQUESTED_PATIENT_SELECT'
-                    - ' PROCESSING_PATIENT_SELECT'
-                    - ' PROCESSING_PATIENT_NOTIFY'
-                    - ' REQUESTING_PATIENT_NOTIFY'
-                    - ' ERROR'
-                    examples:
-                    - PROCESSING_PATIENT_NOTIFY
-                    type:
-                    - "null"
-                    - string
-                type: object
+                $ref: '#/components/schemas/HipQRScanShareProfileResponseV2'
           description: OK
       security:
       - authApiKey: []
@@ -3656,12 +4555,12 @@ paths:
         name: X-Hip-Id
         schema:
           type: string
-      - description: Consent/Subscription/Authorization ID
+      - description: Consent/Subscription ID
         in: query
         name: id
         required: true
         schema:
-          description: Consent/Subscription/Authorization ID
+          description: Consent/Subscription ID
           type: string
       - description: Request type
         in: query
@@ -3671,7 +4570,6 @@ paths:
           enum:
           - consent
           - subscription
-          - authorization
           type: string
       - description: Status of the request
         in: query
@@ -3714,7 +4612,7 @@ paths:
       - authApiKey: []
   /abdm/v1/requests:
     get:
-      description: API to list all the Subscriptions / Authorization and Consent requests
+      description: API to list all the Subscriptions and Consent requests
       parameters:
       - description: Eka User ID (OID)
         in: header
@@ -3838,6 +4736,46 @@ paths:
           description: OK
       security:
       - authApiKey: []
+  /abdm/v1/session/status:
+    get:
+      description: Status of the user by the session.
+      parameters:
+      - description: Eka User ID (OID)
+        in: header
+        name: X-Pt-Id
+        schema:
+          type: string
+      - description: Partner User ID
+        in: header
+        name: X-Partner-Pt-Id
+        schema:
+          type: string
+      - description: Partner HIP ID
+        in: header
+        name: X-Hip-Id
+        schema:
+          type: string
+      responses:
+        4XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        5XX:
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/GenericError'
+          description: ""
+        "200":
+          content:
+            application/json:
+              schema:
+                $ref: '#/components/schemas/AuthLoggedInStatusResponse'
+          description: OK
+      security:
+      - authApiKey: []
   /abdm/v1/session/verify:
     post:
       description: Verify mobile OTP and get user session token
@@ -4029,6 +4967,10 @@ components:
       type: object
     ApproveRequest:
       properties:
+        access_mode:
+          enum:
+          - view
+          type: string
         consent_artefacts:
           description: List of consent artefacts.
           items:
@@ -4036,6 +4978,17 @@ components:
           type:
           - array
           - "null"
+        duration:
+          $ref: '#/components/schemas/CommonsDuration'
+        erase_at:
+          format: date-time
+          type: string
+        hi_types:
+          items:
+            type: string
+          type:
+          - array
+          - "null"
         id:
           description: Unique identifier of a consent, also called the consent ID.
           type: string
@@ -4072,6 +5025,13 @@ components:
         statelgd:
           type: string
       type: object
+    AuthLoggedInStatusResponse:
+      properties:
+        kyc_verified:
+          type: boolean
+        logged_in:
+          type: boolean
+      type: object
     ChangeRequest:
       properties:
         new:
@@ -4721,6 +5681,38 @@ components:
           description: Indicates if the user has already set the consent PIN.
           type: boolean
       type: object
+    FaceAuthCapturePIDRequest:
+      properties:
+        txn_id:
+          type: string
+      type: object
+    FaceAuthCapturePIDResponse:
+      properties:
+        message:
+          type: string
+        status:
+          type: string
+        txn_id:
+          type: string
+      type: object
+    FaceAuthInitFaceAuthResponse:
+      properties:
+        hint:
+          type:
+          - "null"
+          - string
+        txn_id:
+          type: string
+        url:
+          type: string
+      type: object
+    FaceAuthVerifyFaceAuthRequest:
+      properties:
+        aadhaar:
+          type: string
+        txn_id:
+          type: string
+      type: object
     FormDataSettingsRequest:
       properties:
         oid:
@@ -4736,6 +5728,70 @@ components:
         source_error:
           $ref: '#/components/schemas/SourceErr'
       type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmInternalNhprRepoModelsFacility:
+      properties:
+        data:
+          $ref: '#/components/schemas/ModelsFacility'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprDoesHprExistResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprDoesHprExistResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEKACreateHPRIDResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprEKACreateHPRIDResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEKAIsHPRIDExistsResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprEKAIsHPRIDExistsResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaAadhaarResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprEkaAadhaarResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprEkaVerifiedResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprEkaVerifiedResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprOnboardFacilityResponse:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprOnboardFacilityResponse'
+        error: {}
+        success:
+          type: boolean
+      type: object
+    HandlerTypedAPIResponseGithubComEkaCareNdhmPkgNhprNhprUpdateBridgeRequest:
+      properties:
+        data:
+          $ref: '#/components/schemas/NhprUpdateBridgeRequest'
+        error: {}
+        success:
+          type: boolean
+      type: object
     HipLocation:
       properties:
         latitude:
@@ -4747,6 +5803,33 @@ components:
           - "null"
           - string
       type: object
+    HipQRScanShareProfileResponseV2:
+      properties:
+        address:
+          description: Address associated with the HIP.
+          type: string
+        created_at:
+          format: date-time
+          type: string
+        footer:
+          type: string
+        hip_id:
+          description: Health Information Provider (HIP) identifier
+          type: string
+        hip_name:
+          description: Name of the Health Information Provider (HIP)
+          type: string
+        request_id:
+          description: Unique identifier for the request
+          type: string
+        show_token_screen:
+          type: boolean
+        token_expiry:
+          format: date-time
+          type: string
+        token_number:
+          type: string
+      type: object
     InitRequest:
       properties:
         aadhaar_number:
@@ -4926,8 +6009,9 @@ components:
         care_context_id:
           type: string
         data:
-          description: ABDM compliant FHIR bundle (optional, required if not opting
-            for webhook based implementation)
+          description: Base64 encoded ABDM compliant FHIR bundle (optional, required
+            if not opting for webhook based implementation)
+          type: string
         display:
           type: string
         hi_type:
@@ -5346,6 +6430,30 @@ components:
         type:
           type: string
       type: object
+    ModelsDecryptPayload:
+      properties:
+        encrypted_data:
+          description: Base64-encoded encrypted data to decrypt
+          type: string
+        receiver_nonce:
+          description: Nonce associated with the receiver's key pair
+          type: string
+        receiver_private_key:
+          description: Base64-encoded private key of the receiver
+          type: string
+        sender_nonce:
+          description: Nonce associated with the sender's key pair
+          type: string
+        sender_public_key:
+          description: Base64-encoded public key of the sender
+          type: string
+      type: object
+    ModelsDecryptResponse:
+      properties:
+        decrypted_data:
+          description: Decrypted plaintext data
+          type: string
+      type: object
     ModelsDiscoverCareContextHmisConnect:
       properties:
         error:
@@ -5517,6 +6625,36 @@ components:
           description: Indicates whether the health ID exist.
           type: boolean
       type: object
+    ModelsEncryptPayload:
+      properties:
+        plain_text_data:
+          description: Plaintext data to encrypt
+          type: string
+        receiver_nonce:
+          description: Nonce associated with the receiver's key pair
+          type: string
+        receiver_public_key:
+          description: Base64-encoded public key of the receiver
+          type: string
+        sender_nonce:
+          description: Nonce associated with the sender's key pair
+          type: string
+        sender_private_key:
+          description: Base64-encoded private key of the sender
+          type: string
+        sender_public_key:
+          description: Base64-encoded public key of the sender
+          type: string
+      type: object
+    ModelsEncryptResponse:
+      properties:
+        encrypted_data:
+          description: Base64-encoded encrypted data
+          type: string
+        key_to_share:
+          description: Public key material to share with the receiver
+          type: string
+      type: object
     ModelsError:
       properties:
         code:
@@ -5526,6 +6664,49 @@ components:
           description: Detailed error message
           type: string
       type: object
+    ModelsFacility:
+      properties:
+        address:
+          type: string
+        districtLGDCode:
+          type: string
+        districtName:
+          type: string
+        facilityId:
+          type: string
+        facilityName:
+          type: string
+        facilityStatus:
+          type: string
+        facilityType:
+          type: string
+        facilityTypeCode:
+          type: string
+        latitude:
+          type: string
+        longitude:
+          type: string
+        ownership:
+          type: string
+        ownershipCode:
+          type: string
+        pincode:
+          type: string
+        stateLGDCode:
+          type: string
+        stateName:
+          type: string
+        subDistrictLGDCode:
+          type: string
+        subDistrictName:
+          type: string
+        systemOfMedicine:
+          type: string
+        systemOfMedicineCode:
+          type: string
+        villageCityTownLGDCode: {}
+        villageCityTownName: {}
+      type: object
     ModelsGetConfirmResponse:
       properties:
         doctor_info:
@@ -5557,6 +6738,11 @@ components:
           description: Unique transaction ID for the next API call
           type: string
       type: object
+    ModelsHPRIDAadhaarInitRequest:
+      properties:
+        aadhaar:
+          type: string
+      type: object
     ModelsInitBilling:
       properties:
         address:
@@ -5600,6 +6786,18 @@ components:
             the previous api response
           type: string
       type: object
+    ModelsKeyPairWithNonce:
+      properties:
+        nonce:
+          description: Random nonce generated for the key pair
+          type: string
+        private_key:
+          description: Base64-encoded ECDH private key
+          type: string
+        public_key:
+          description: Base64-encoded ECDH public key
+          type: string
+      type: object
     ModelsLinkOnConfirmHmisConnect:
       properties:
         error:
@@ -5943,6 +7141,233 @@ components:
         long:
           type: number
       type: object
+    NhprDoesHprExistRequest:
+      properties:
+        hprId:
+          type: string
+      type: object
+    NhprDoesHprExistResponse:
+      properties:
+        available:
+          type: boolean
+      type: object
+    NhprEKAAadhaarVerifyRequest:
+      properties:
+        otp:
+          type: string
+        txn_id:
+          type: string
+      type: object
+    NhprEKACreateHPRID:
+      properties:
+        council:
+          type: boolean
+        domain_name:
+          type: string
+        email:
+          type: string
+        first_name:
+          type: string
+        hp_category_code:
+          type: integer
+        hp_sub_category_code:
+          type: integer
+        hprId:
+          type: string
+        id_type:
+          type: string
+        last_name:
+          type: string
+        middle_name:
+          type: string
+        notify_user:
+          type: boolean
+        password:
+          type: string
+        pincode:
+          type: string
+        profile_photo:
+          type: string
+        role:
+          type: integer
+        source_type:
+          type: string
+        txnId:
+          type: string
+      type: object
+    NhprEKACreateHPRIDResponse:
+      properties:
+        auth_methods:
+          items:
+            type: string
+          type:
+          - array
+          - "null"
+        categories: {}
+        category_id:
+          type: integer
+        day_of_birth:
+          type: string
+        district_code:
+          type: string
+        district_name:
+          type: string
+        email:
+          type: string
+        first_name:
+          type: string
+        gender:
+          type: string
+        hpr_id_number:
+          type: string
+        hprId:
+          type: string
+        kyc_photo:
+          type: string
+        last_name:
+          type: string
+        middle_name:
+          type: string
+        mobile:
+          type: string
+        month_of_birth:
+          type: string
+        name:
+          type: string
+        new:
+          type: boolean
+        state_code:
+          type: string
+        state_name:
+          type: string
+        sub_category_id:
+          type: integer
+        year_of_birth:
+          type: string
+      type: object
+    NhprEKAIsHPRIDExistsResponse:
+      properties:
+        address:
+          type: string
+        category_id:
+          type: integer
+        day_of_birth:
+          type: string
+        district_code:
+          type: string
+        district_name:
+          type: string
+        first_name:
+          type: string
+        gender:
+          type: string
+        hpr_id:
+          type: string
+        hpr_id_number:
+          type: string
+        last_name:
+          type: string
+        middle_name:
+          type: string
+        mobile:
+          type:
+          - "null"
+          - string
+        month_of_birth:
+          type: string
+        name:
+          type: string
+        new:
+          type: boolean
+        pincode:
+          type: string
+        profile_photo:
+          type: string
+        state_code:
+          type: string
+        state_name:
+          type: string
+        sub_category_id:
+          type: integer
+        token:
+          type: string
+        txn_id:
+          type: string
+        year_of_birth:
+          type: string
+      type: object
+    NhprEkaAadhaarResponse:
+      properties:
+        hint:
+          type: string
+        mobile_num:
+          type: string
+        txn_id:
+          type: string
+      type: object
+    NhprEkaVerifiedResponse:
+      properties:
+        error_code:
+          type:
+          - "null"
+          - string
+        hpr:
+          properties:
+            hprId:
+              type: string
+          type: object
+        reason:
+          type:
+          - "null"
+          - string
+        suggested_hpr_ids:
+          items:
+            type: string
+          type:
+          - array
+          - "null"
+        txnId:
+          type: string
+        uidai_token:
+          type:
+          - "null"
+          - string
+        verified:
+          type: boolean
+      type: object
+    NhprMobileOTPRequest:
+      properties:
+        mobile_num:
+          type: string
+        txn_id:
+          type: string
+      type: object
+    NhprMobileVerifyRequest:
+      properties:
+        otp:
+          type: string
+        txnId:
+          type: string
+      type: object
+    NhprOnboardFacilityResponse:
+      properties:
+        facility_id:
+          type: string
+      type: object
+    NhprTransactionId:
+      properties:
+        mobile_num:
+          type: string
+        txn_id:
+          type: string
+      type: object
+    NhprUpdateBridgeRequest:
+      properties:
+        clinic_id:
+          type: string
+        hfr_id:
+          type: string
+      type: object
     PhrLoginOTPRequest:
       properties:
         identifier:
@@ -6040,13 +7465,56 @@ components:
           - Jharkhand
           type: string
       type: object
+    ProfileAbha:
+      properties:
+        abha_address:
+          type: string
+        abha_number:
+          examples:
+          - xx-xxxx-xxxx-1525
+          type: string
+        age:
+          type: integer
+        gender:
+          examples:
+          - M
+          type: string
+        index:
+          examples:
+          - 1
+          type: integer
+        internal:
+          examples:
+          - true
+          type: boolean
+        kyc_verified:
+          examples:
+          - "true"
+          type: string
+        name:
+          examples:
+          - John Doe
+          type: string
+      type: object
+    ProfileDiscoverAbhaRequest:
+      properties:
+        mobile:
+          type: string
+      required:
+      - mobile
+      type: object
     ProfileResponse:
       properties:
         abha_address:
-          description: ABHA address associated with the user.
+          description: Primary/preferred abha address.
           examples:
           - shyam@abdm
           type: string
+        abha_addresses:
+          description: List of abha addresses associated with aadhaar
+          items:
+            type: string
+          type: array
         abha_number:
           description: ABHA number assigned to the user.
           examples:
@@ -6114,6 +7582,15 @@ components:
           - "null"
           - integer
       type: object
+    ProfileSearchKycAbhaResponse:
+      properties:
+        profiles:
+          items:
+            $ref: '#/components/schemas/ProfileAbha'
+          type:
+          - array
+          - "null"
+      type: object
     ProviderHipDetail:
       properties:
         hip_id:
@@ -6258,6 +7735,18 @@ components:
         success:
           type: boolean
       type: object
+    RecordsUpdateKeysetRequest:
+      properties:
+        nonce:
+          description: Base64-encoded nonce for encryption key derivation
+          type: string
+        public_key:
+          description: Base64-encoded ECDH public key for encryption
+          type: string
+      required:
+      - public_key
+      - nonce
+      type: object
     RegistrationEkaIds:
       properties:
         min_token:
@@ -6515,6 +8004,24 @@ components:
       - hip_id
       - counter_id
       type: object
+    ScanandshareRequest:
+      properties:
+        counter_id:
+          description: Counter ID from QR Code
+          type: string
+        hip_id:
+          description: HIP ID from QR Code
+          type: string
+        location:
+          $ref: '#/components/schemas/HipLocation'
+          description: Location of the user
+        patient:
+          $ref: '#/components/schemas/ScanandsharePatient'
+          description: Patient details
+      required:
+      - counter_id
+      - hip_id
+      type: object
     ScanandshareResponse:
       properties:
         expiry:
@@ -6664,6 +8171,11 @@ components:
       type: object
     VerifyResponse:
       properties:
+        abha_profiles:
+          description: Abha profiles of the user.
+          items:
+            $ref: '#/components/schemas/VerifyAbhaProfile'
+          type: array
         eka:
           $ref: '#/components/schemas/RegistrationEkaIds'
           description: Eka IDs, will be present if SkipState is abha_end
@@ -6697,6 +8209,11 @@ components:
       type: object
     VerifyResponseType2:
       properties:
+        abha_profiles:
+          description: Abha profiles of the user.
+          items:
+            $ref: '#/components/schemas/VerifyAbhaProfile'
+          type: array
         eka:
           $ref: '#/components/schemas/RegistrationEkaIds'
         hint:
diff --git a/api-reference/user-app/abdm-connect/release-notes.mdx b/api-reference/user-app/abdm-connect/release-notes.mdx
deleted file mode 100644
index 65a9daab..00000000
--- a/api-reference/user-app/abdm-connect/release-notes.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: 'ABDM Connect Release Notes'
----
-
-## Sep 18th, 2024
-We have started reverting with NHA/ABDM error codes and messages in the API response in case of failures.
-Please refer to the [Error Code Mapping](/api-reference/user-app/abdm-connect/errors) for more details.
-
-
-## Aug 30th, 2024
-- [Refresh token Api](/api-reference/authorization/refresh-token-api)
-Refresh Token API.
-The ABHA Registration APIs will also send the refresh token alongside the access token in the API response.
-
-- [Update Profile](/api-reference/user-app/abdm-connect/profile/details/update-profile)
-Updated constraints for profile update API
-
-- [Error Code Mapping](/api-reference/user-app/abdm-connect/errors)
-Error Code to message mapping
-
-## Aug 28th, 2024
-- [Resend OTP APIs for Aadhaar Registration](/api-reference/user-app/abdm-connect/aadhaar/mobile-resend)
-Resend Aadhaar / Mobile OTPs for registration process
-
-## Aug 22nd, 2024
-- [Discover & Link Care Context](/api-reference/user-app/abdm-connect/care-contexts/discover/introduction)
-Discover unlinked care contexts and link them to ABHA
-- [ABHA Card Download](/api-reference/user-app/abdm-connect/profile/cards/abha-card)
-Download ABHA Card in PNG format
-- [Delete ABHA](/api-reference/user-app/abdm-connect/profile/details/delete)
-Deletes ABHA from the system
-
-## Aug 21st, 2024
-- [Linked Providers & Care Context](/api-reference/user-app/abdm-connect/care-contexts/providers/providers)    
-List the linked providers and linked care-contexts
-- [Provider Search & Details](/api-reference/user-app/abdm-connect/providers/provider)    
-Search Health Providers & fetch details of a health provider
-- [ABHA Profile Details, QR Code & Update Profile](/api-reference/user-app/abdm-connect/profile/cards/qr-code)    
-Abha Profile Management APIs and QR Code data API.
-- [Scan & Share](/api-reference/user-app/abdm-connect/profile/scan-and-share/scanandshare)   
-Scan & Share APIs to get Hospital/Clinic Appointment tokens
-
-
-## Aug 21st, 2024
-- [Consent Listing](/api-reference/user-app/abdm-connect/consents/list-requests)    
-List Consents based on grant status, approve/deny/revoke consents.
-- [Consent Pin Settings](/api-reference/user-app/abdm-connect/consents/pin/set)    
-Set, reset consent pins.
-
-## Aug, 12th 2024
-
-- [Registration APIs](/api-reference/user-app/abdm-connect/aadhaar/initiate-registration)    
-ABHA Registration using mobile / aadhaar OTPs
-
-## Oct, 4th 2024
-
-- [ABHA KYC APIs](/api-reference/user-app/abdm-connect/profile/kyc/kyc-init)
-ABHA Profile KYC using ABHA number
diff --git a/api-reference/user-app/abdm-connect/session/getting-started.mdx b/api-reference/user-app/abdm-connect/session/getting-started.mdx
index f8d06a9e..71a408de 100644
--- a/api-reference/user-app/abdm-connect/session/getting-started.mdx
+++ b/api-reference/user-app/abdm-connect/session/getting-started.mdx
@@ -4,18 +4,32 @@ title: Overview
 
 ## User Session
 
-
 Upon registration or creation of an ABHA, a user session is maintained with the ABHA Gateway.
 This session expires after a certain period. When the session expires, APIs requiring ABHA Gateway authentication will return a `491` HTTP response code.
 
-
 A ABHA Gateway Session creation requires a Mobile OTP (One-Time Password) Authentication.
 
 <Steps>
-    <Step title="Generate Mobile OTP">
-        Use the [Initiate Session: Generate Mobile OTP](/api-reference/user-app/abdm-connect/session/init) endpoint to start a new session by generating a mobile OTP. This session is linked to the provided ABHA address, and a `txn_id` (Transaction ID) will be returned for tracking and verification.
-    </Step>
-    <Step title="Verify Mobile OTP">
-        Use the [Verify Mobile OTP: Get User Session Token](/api-reference/user-app/abdm-connect/session/verify) endpoint to verify the OTP generated in the previous step. Provide the OTP and `txn_id` associated with the session to receive an access token for further authentication.
-    </Step>
-</Steps>
\ No newline at end of file
+  <Step title="Generate Mobile OTP">
+    Use the [Initiate Session: Generate Mobile OTP](/api-reference/user-app/abdm-connect/session/init) endpoint to start a new session by generating a mobile OTP.
+    This session is linked to the provided ABHA address, and a `txn_id` (Transaction ID) will be returned for tracking and verification.
+  </Step>
+
+  <Step title="Verify Mobile OTP">
+    Use the [Verify Mobile OTP: Get User Session Token](/api-reference/user-app/abdm-connect/session/verify) endpoint to verify the OTP generated in the previous step.
+    Provide the OTP and `txn_id` associated with the session to receive an access token for further authentication.
+  </Step>
+</Steps>
+
+---
+
+## Check User Session Status
+
+Before initiating OTP authentication, clients **should first check whether a valid ABHA Gateway session already exists**.
+
+Use the **Session Status API** to get the current authentication status of the user.
+
+- If a valid session exists, continue using the existing session token
+- If no valid session exists or the session has expired, users should call:
+  - **Generate Mobile OTP**
+  - **Verify Mobile OTP**
diff --git a/api-reference/user-app/abdm-connect/session/status.mdx b/api-reference/user-app/abdm-connect/session/status.mdx
new file mode 100644
index 00000000..39e700ce
--- /dev/null
+++ b/api-reference/user-app/abdm-connect/session/status.mdx
@@ -0,0 +1,6 @@
+---
+openapi: get /abdm/v1/session/status
+---
+
+
+X-Pt-Id is necessary to hit this API.
\ No newline at end of file
diff --git a/api-reference/user-app/abdm-connect/webhooks/abha-created.mdx b/api-reference/user-app/abdm-connect/webhooks/abha-created.mdx
index efcc2c5f..92ee7e23 100644
--- a/api-reference/user-app/abdm-connect/webhooks/abha-created.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/abha-created.mdx
@@ -1,3 +1,7 @@
+---
+title: ABHA Address Created
+---
+
 Webhook event is sent on successful ABHA Address creation.
 
 ### Request
diff --git a/api-reference/user-app/abdm-connect/webhooks/discover-care-context.mdx b/api-reference/user-app/abdm-connect/webhooks/discover-care-context.mdx
index fd1333aa..7156c813 100644
--- a/api-reference/user-app/abdm-connect/webhooks/discover-care-context.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/discover-care-context.mdx
@@ -1,5 +1,8 @@
-The webhook event is triggered whenever a user requests the discovery of unlinked care contexts. The HIP must use the provided user information to search for and identify matching unlinked
-care contexts within their system.
+---
+title: Discovery Request Received
+---
+
+This webhook is triggered when a user requests discovery of unlinked care contexts from your HIP. Use the provided user information (ABHA address, mobile number, name, demographics) to search for and return matching unlinked care contexts within your system.
 
 ### Request
 **Headers:**
diff --git a/api-reference/user-app/abdm-connect/webhooks/discover-link-confirm.mdx b/api-reference/user-app/abdm-connect/webhooks/discover-link-confirm.mdx
index d95ae005..3dac4d30 100644
--- a/api-reference/user-app/abdm-connect/webhooks/discover-link-confirm.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/discover-link-confirm.mdx
@@ -1,4 +1,8 @@
-The webhook event is triggered when a user attempts to verify the OTP. Upon receiving this webhook, the HIP should validate the OTP generated during the discover link init event. If the OTP is valid, the HIP should proceed to link the care context.
+---
+title: Link Confirmation - Verify OTP
+---
+
+This webhook is triggered when a user submits the OTP to confirm care context linking. Validate the OTP generated during the [Link Initiation](/api-reference/user-app/abdm-connect/webhooks/discover-link-init) step. If valid, proceed to link the care contexts.
 ### Request
 **Headers:**
 
diff --git a/api-reference/user-app/abdm-connect/webhooks/discover-link-init.mdx b/api-reference/user-app/abdm-connect/webhooks/discover-link-init.mdx
index adc59398..cd564835 100644
--- a/api-reference/user-app/abdm-connect/webhooks/discover-link-init.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/discover-link-init.mdx
@@ -1,5 +1,8 @@
-The webhook event is triggered whenever a user initiates the linking of unlinked care contexts. Upon receiving this webhook, the HIP should generate
-an OTP and save the care contexts for further processing.
+---
+title: Link Initiation - Generate OTP
+---
+
+This webhook is triggered when a user initiates linking of discovered care contexts. Upon receiving this webhook, generate an OTP, send it to the user, and save the care contexts for further processing.
 ### Request
 **Headers:**
 
diff --git a/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch.mdx b/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch.mdx
index ca337612..76c2ac50 100644
--- a/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/hip-data-fetch.mdx
@@ -1,4 +1,18 @@
-Webhook event is sent to fetch FHIR data for care contexts requested by HIU. HIP should prepare the ABDM compliant FHIR bundle for care contexts and push it to the HIU using the [Care context data on-fetch API](/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch)
+---
+title: Health Data Requested by HIU
+---
+
+This webhook is sent when an HIU requests health data for care contexts that you have previously linked using the [Care Context Link API](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking).
+
+<Note>
+You will only receive this webhook if you are **not** storing the health data on Eka servers. If you use Eka's Upload API to store records, Eka handles data sharing automatically.
+</Note>
+
+**What to do when you receive this webhook:**
+
+1. Prepare an ABDM-compliant FHIR bundle for each care context listed in the `care_contexts` array.
+2. Encrypt the FHIR data using the `key_information` provided in the webhook payload (ECDH-based encryption).
+3. Push the encrypted data to the HIU using the [Care Context Data On-Fetch API](/api-reference/user-app/abdm-connect/care-contexts/data-on-fetch). Use the `transaction_id` from this webhook in the on-fetch request.
 
 ### Request
 **Headers:**
@@ -28,14 +42,14 @@ Webhook event is sent to fetch FHIR data for care contexts requested by HIU. HIP
             "care_context_2"
         ],
         "key_information": {
-            "crypto_alg": "",
-            "curve": "",
+            "crypto_alg": "ECDH",
+            "curve": "Curve25519",
             "dh_public_key": {
-                "expiry": "",
-                "parameters": "",
-                "key_value": ""
+                "expiry": "2026-03-01T12:00:00.000Z",
+                "parameters": "Curve25519/32byte random key",
+                "key_value": "base64-encoded public key"
             },
-            "nonce": ""
+            "nonce": "base64-encoded 32-byte nonce"
         },
         "hi_types": [
             "OPConsultation",
diff --git a/api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share.mdx b/api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share.mdx
index 230cca9b..2947ac9b 100644
--- a/api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share.mdx
@@ -1,4 +1,8 @@
-Webhook callback is sent to client for OPD Token Generation
+---
+title: Scan and Share Token Received
+---
+
+Webhook callback is sent to the client when a patient shares their ABHA token via Scan and Share for OPD token generation.
 
 ### Request
 **Headers:**
diff --git a/api-reference/user-app/abdm-connect/webhooks/hiu-data-push.mdx b/api-reference/user-app/abdm-connect/webhooks/hiu-data-push.mdx
index f8ca2b5d..4e2d63b6 100644
--- a/api-reference/user-app/abdm-connect/webhooks/hiu-data-push.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/hiu-data-push.mdx
@@ -1,4 +1,8 @@
-Webhook event is sent on data push from HIP to HIU
+---
+title: Health Data Received from HIP
+---
+
+Webhook event is sent when an external HIP pushes encrypted health data to your HIU.
 
 The Health Information User (HIU) can initiate a consent request through the [Consent-API](/api-reference/user-app/abdm-connect/consents/consent-create) to get care context data. Once consent is validated, the Health Information Provider (HIP) sends the encrypted health data to the HIU.
 
diff --git a/api-reference/user-app/abdm-connect/webhooks/link-care-context.mdx b/api-reference/user-app/abdm-connect/webhooks/link-care-context.mdx
index 2786b291..bf2fe611 100644
--- a/api-reference/user-app/abdm-connect/webhooks/link-care-context.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/link-care-context.mdx
@@ -1,4 +1,12 @@
-Webhook event is sent for care context linking
+---
+title: Care Context Linking Status
+---
+
+This webhook is sent after you call the [Care Context Link API](/api-reference/user-app/abdm-connect/care-contexts/link/hip-linking) to notify you of the linking result. Check the `status` field to determine if the care context was successfully linked.
+
+**What to do next:**
+- If `status` is `LINKED` — the care context is now registered with ABDM. Other HIUs can request this data through ABDM's consent flow.
+- If `status` is `ERRORED` — check the `error` field for the failure reason and retry if needed.
 
 ### Request
 **Headers:**
diff --git a/api-reference/user-app/abdm-connect/webhooks/locker-created.mdx b/api-reference/user-app/abdm-connect/webhooks/locker-created.mdx
index f8ac8af9..68ad2a17 100644
--- a/api-reference/user-app/abdm-connect/webhooks/locker-created.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/locker-created.mdx
@@ -1,3 +1,7 @@
+---
+title: Locker Created
+---
+
 Webhook event is sent on successful locker creation.
 
 
diff --git a/api-reference/user-app/abdm-connect/webhooks/subscription-modify.mdx b/api-reference/user-app/abdm-connect/webhooks/subscription-modify.mdx
index 7ed3ea18..5f45b74d 100644
--- a/api-reference/user-app/abdm-connect/webhooks/subscription-modify.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/subscription-modify.mdx
@@ -1,3 +1,7 @@
+---
+title: Subscription Updated
+---
+
 Webhook event is triggered whenever there is an update to a subscription.
 ### Request
 **Headers:**
diff --git a/api-reference/user-app/abdm-connect/webhooks/subscription-notify.mdx b/api-reference/user-app/abdm-connect/webhooks/subscription-notify.mdx
index 83ee2328..e3022798 100644
--- a/api-reference/user-app/abdm-connect/webhooks/subscription-notify.mdx
+++ b/api-reference/user-app/abdm-connect/webhooks/subscription-notify.mdx
@@ -1,4 +1,8 @@
-Webhook event is sent when a new care context is linked to the ABHA
+---
+title: New Care Context Linked (Subscription)
+---
+
+Webhook event is sent when a new care context is linked to the ABHA address you have an active subscription for.
 
 ### Request
 **Headers:**
diff --git a/SDKs/ios/medical-records.mdx b/api-reference/user-app/records/SDKs/iOS-sdk.mdx
similarity index 100%
rename from SDKs/ios/medical-records.mdx
rename to api-reference/user-app/records/SDKs/iOS-sdk.mdx
diff --git a/api-reference/user-app/records/delete-document.mdx b/api-reference/user-app/records/delete-document.mdx
index 5a3fe8cb..9a7a6f91 100644
--- a/api-reference/user-app/records/delete-document.mdx
+++ b/api-reference/user-app/records/delete-document.mdx
@@ -1,3 +1,3 @@
 ---
-openapi: delete /mr/api/v1/docs/{document_id}
+openapi: delete /mr/api/v1/docs/{id}
 ---
diff --git a/api-reference/user-app/records/describe-record.mdx b/api-reference/user-app/records/describe-record.mdx
index efc9e099..67fa6894 100644
--- a/api-reference/user-app/records/describe-record.mdx
+++ b/api-reference/user-app/records/describe-record.mdx
@@ -1,3 +1,3 @@
 ---
-openapi: get /mr/api/v1/docs/{document_id}
+openapi: get /mr/api/v1/docs/{id}
 ---
diff --git a/api-reference/user-app/records/records.yaml b/api-reference/user-app/records/records.yaml
index 64087327..085eff6e 100644
--- a/api-reference/user-app/records/records.yaml
+++ b/api-reference/user-app/records/records.yaml
@@ -36,13 +36,6 @@ paths:
           schema:
             type: string
           description: Please include the nextPageToken from the API response to enable pagination.
-        - name: p_oid
-          in: query
-          schema:
-            type: string
-          required: false
-          deprecated: true
-          description: Include the patient identifier (p_oid) to fetch the list of records. Applicable only for EMR cases.
         - name: accept
           in: header
           required: true
@@ -165,13 +158,6 @@ paths:
       summary: "Step 1: Upload Record"
       description: Generate a presigned URL that allows you to securely upload a document to the server. This URL can be used to upload the document directly without needing additional authentication or authorization steps.
       parameters:
-        - in: query
-          name: p_oid
-          required: false
-          description: Include the patient identifier (p_oid) to upload the record. This is applicable only for EMR cases.
-          schema:
-            type: string
-          deprecated: true
         - name: X-Pt-Id
           in: header
           required: true
@@ -212,7 +198,7 @@ paths:
                 document_id: ‘$response.body#/batch_response/0/document_id’
               description: >
                 The `document_id` value returned in the response can be used as
-                the `document_id` parameter in `GET /mr/api/v1/docs/{document_id}`.
+                the `document_id` parameter in `GET /mr/api/v1/docs/{id}`.
         "400":
           description: Bad Request
           content:
@@ -238,25 +224,18 @@ paths:
       security:
         - auth: []
 
-  /mr/api/v1/docs/{document_id}:
+  /mr/api/v1/docs/{id}:
     patch:
       summary: Update Document
       description: This API is used to update the document.
       parameters:
-        - name: document_id
+        - name: id
           in: path
           required: true
           description: Document ID to update the document details.
           schema:
             type: string
             example: 2df9e795-d368-4ceb-be9d-b44281703827
-        - name: p_oid
-          in: query
-          schema:
-            type: string
-          required: false
-          description: Include the patient identifier (p_oid) to update a patient's record. Applicable only for EMR cases.
-          deprecated: true
         - name: X-Pt-Id
           in: header
           required: true
@@ -272,25 +251,6 @@ paths:
                 dt:
                   type: string
                   nullable: true
-                  description: |
-                    The following values are allowed:
-                    - `ps`: Prescription
-                    - `lr`: Lab Report
-                    - `ot`: Other
-                    - `ds`: Discharge Summary
-                    - `vc`: Vaccine Certificate
-                    - `in`: Insurance
-                    - `iv`: Invoice
-                    - `sc`: Scan
-                  enum:
-                    - ps
-                    - lr
-                    - ot
-                    - ds
-                    - vc
-                    - in
-                    - iv
-                    - sc
                   example: lr
                 ndhm:
                   type: boolean
@@ -348,19 +308,12 @@ paths:
       description: This API is used to delete a document using a document ID.
       parameters:
         - in: path
-          name: document_id
+          name: id
           required: true
           description: Document ID to delete the document.
           schema:
             type: string
             example: 2df9e795-d368-4ceb-be9d-b44281703827
-        - name: p_oid
-          in: query
-          schema:
-            type: string
-          required: false
-          description: Include the patient identifier (p_oid) to delete a patient's record. Applicable only for EMR cases.
-          deprecated: true
         - name: X-Pt-Id
           in: header
           schema:
@@ -382,19 +335,12 @@ paths:
       operationId: getDocument
       parameters:
         - in: path
-          name: document_id
+          name: id
           required: true
           description: Document ID to fetch the document details.
           schema:
             type: string
             example: 2df9e795-d368-4ceb-be9d-b44281703827
-        - in: query
-          name: p_oid
-          required: false
-          description: Include the patient identifier (p_oid) to fetch a patient's record, applicable only for EMR cases.
-          schema:
-            type: string
-          deprecated: true
         - name: X-Pt-Id
           in: header
           required: true
@@ -420,7 +366,6 @@ paths:
                       type: string
                   dt:
                     type: string
-                    enum: [lr, ps, ds, vc, in, iv, sc, ot]
                   smart_report:
                     type: object
                     properties:
@@ -791,11 +736,11 @@ paths:
       parameters:
         - in: query
           name: dt
-          required: true
           schema:
             $ref: "#/components/schemas/DocumentTypeQueryParamV2"
         - in: query
           name: task
+          required: true
           schema:
             $ref: "#/components/schemas/UploadTaskQueryParam"
         - in: query
@@ -942,50 +887,6 @@ paths:
       security:
         - auth: []
 
-  /mr/webhook/smart-report:
-    post:
-      tags:
-        - Webhooks
-      summary: Smart Report
-      description: >-
-        When the records get uploaded, a webhook event is sent to register to get the smart report of the record upload. If there are multiple records upload in upload docs API we need to register web hook for all the document id recevied in the reponse. Use the below request payload to register to webhook. You can find [here](https://ekacare.notion.site/726b13df13ea4409b0cd30c6f3a80315?v=dcd10c722d3149d880ae889b06f4820a) list of parsing capablities we have as of now.
-      requestBody:
-        required: true
-        content:
-          application/json:
-            schema:
-              type: object
-              properties:
-                event_type:
-                  type: string
-                  example: "smart-report"
-                timestamp:
-                  type: string
-                  example: "2023-07-30T18:07:24.000Z"
-                data:
-                  type: object
-                  properties:
-                    document_id:
-                      type: string
-                      description: This is document_id which you have recevied Obtain a Presigned URL for Document Upload response
-                    webook_url:
-                      type: string
-                      description: This url we will use to send the payload upon successful parsing of the record
-
-      responses:
-        "200":
-          description: Event registered successfully
-        "204":
-          description: Event created successfully
-        "400":
-          description: Bad request
-        "403":
-          description: Forbidden - Access Denied
-        "500":
-          description: Something went wrong
-      security:
-        - auth: []
-
   /mr/api/v1/cases/{id}:
     delete:
       tags:
@@ -1556,26 +1457,6 @@ components:
         - lr
     DocumentTypeQueryParam:
       type: string
-      description: |
-        Specifies the type of document being uploaded. 
-        The following values are allowed:
-        - `ps`: Prescription
-        - `lr`: Lab Report
-        - `ot`: Other
-        - `ds`: Discharge Summary
-        - `vc`: Vaccine Certificate
-        - `in`: Insurance
-        - `iv`: Invoice
-        - `sc`: Scan
-      enum:
-        - ps
-        - lr
-        - ot
-        - ds
-        - vc
-        - in
-        - iv
-        - sc
 
     UploadTaskQueryParam:
       type: string
@@ -1584,9 +1465,11 @@ components:
         The following values are allowed:
         - `smart`: Parse the document to smart report
         - `pii`: Parse Personal Identification Information from the document
+        - `classification`: Parse classification document
       enum:
         - smart
         - pii
+        - classification
 
     FileUploadRequest:
       type: object
@@ -1617,7 +1500,8 @@ components:
         tg:
           type: array
           uniqueItems: true
-          description: The tag array can contain a maximum of **10 tags**.
+          description:
+            Tags are treated as SET, and therefore their order is not preserved. The tag array can contain a maximum of **10 tags**.
             If more than 10 tags are provided in the request, only the **first 10 tags** will be considered.
           items:
             type: string
diff --git a/api-reference/user-app/records/smart-report.mdx b/api-reference/user-app/records/smart-report.mdx
deleted file mode 100644
index cdb8ecfe..00000000
--- a/api-reference/user-app/records/smart-report.mdx
+++ /dev/null
@@ -1,3 +0,0 @@
----
-openapi: post /mr/webhook/smart-report
----
\ No newline at end of file
diff --git a/api-reference/user-app/records/update-document.mdx b/api-reference/user-app/records/update-document.mdx
index fd727640..e38ebb04 100644
--- a/api-reference/user-app/records/update-document.mdx
+++ b/api-reference/user-app/records/update-document.mdx
@@ -1,5 +1,5 @@
 ---
-openapi: patch /mr/api/v1/docs/{document_id}
+openapi: patch /mr/api/v1/docs/{id}
 ---
 
 
diff --git a/docs.json b/docs.json
index 89f1238f..6a8f25fe 100644
--- a/docs.json
+++ b/docs.json
@@ -29,12 +29,54 @@
                         "tab": "Documentation",
                         "groups": [
                             {
-                                "group": "Eka Care Developer API guide",
+                                "group": "Eka Overview",
                                 "pages": [
-                                    "introduction",
-                                    "abdm-connect",
-                                    "getting-started",
-                                    "communication-flow-appointment-clinical-events"
+                                    "user-guides/get-started",
+                                    "user-guides/eka-products"
+                                ]
+                            },
+                            {
+                                "group": "Product Details",
+                                "pages": [
+                                    {
+                                        "group": "Health AI",
+                                        "pages": [
+                                            "integrations/health-ai/assessments",
+                                            "integrations/health-ai/ekascribe",
+                                            "integrations/health-ai/medassist"
+                                        ]
+                                    },
+                                    {
+                                        "group": "MCP",
+                                        "pages": [
+                                            "integrations/mcp/MCP-for-Indian-treatment-protocol-search",
+                                            "integrations/mcp/mcp-for-emr"
+                                        ]
+                                    },
+                                    {
+                                        "group": "General Tools",
+                                        "pages": [
+                                            "integrations/general-tools/medical-db",
+                                            "integrations/general-tools/medical-document-parsing"
+                                        ]
+                                    },
+                                    {
+                                        "group": "Interoperability",
+                                        "pages": [
+                                            "integrations/interoperability/abdm"
+                                        ]
+                                    },
+                                    {
+                                        "group": "Core-EMR",
+                                        "pages": [
+                                            "integrations/core-emr/patients",
+                                            "integrations/core-emr/doctor",
+                                            "integrations/core-emr/appointments",
+                                            "integrations/core-emr/clinic",
+                                            "integrations/core-emr/payments",
+                                            "integrations/core-emr/prescription"
+                                        ]
+                                    }
                                 ]
                             }
                         ]
@@ -44,14 +86,38 @@
                         "groups": [
                             {
                                 "group": "Authorization",
+                                "icon": "lock",
                                 "pages": [
                                     "api-reference/authorization/getting-started",
-                                    "api-reference/authorization/client-login",
-                                    "api-reference/authorization/refresh-token",
-                                    "api-reference/authorization/oidc-user-verify",
-                                    "api-reference/authorization/oidc-user-refresh",
-                                    "api-reference/authorization/refresh-token-v2",
-                                    "api-reference/authorization/delete-account"
+                                    {
+                                        "group": "APIs",
+                                        "pages": [
+                                            {
+                                                "group": "Core APIs",
+                                                "pages": [
+                                                    "api-reference/authorization/client-login",
+                                                    "api-reference/authorization/refresh-token-v2",
+                                                    "api-reference/authorization/delete-account"
+                                                ]
+                                            },
+                                            {
+                                                "group": "OIDC Partner APIs",
+                                                "pages": [
+                                                    "api-reference/authorization/oidc-user-verify",
+                                                    "api-reference/authorization/oidc-user-refresh"
+                                                ]
+                                            }
+                                        ]
+                                    },
+                                    {
+                                        "group": "SDKs",
+                                        "pages": [
+                                            "api-reference/authorization/sdks/python-sdk",
+                                            "api-reference/authorization/sdks/go-sdk",
+                                            "api-reference/authorization/sdks/java-sdk"
+                                        ]
+                                    },
+                                    "api-reference/authorization/invite-flow"
                                 ]
                             },
                             {
@@ -86,14 +152,29 @@
                                         "icon": "comments-question-check",
                                         "pages": [
                                             "api-reference/health-ai/assessment/overview",
-                                            "api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment",
-                                            "api-reference/health-ai/assessment/assessment-flow/continue/start-assessment",
-                                            "api-reference/health-ai/assessment/assessment-flow/continue/continue-assessment",
-                                            "api-reference/health-ai/assessment/assessment-flow/submit/submit-assessment",
-                                            "api-reference/health-ai/assessment/questionnaire_data",
-                                            "api-reference/health-ai/assessment/component-info/list-all-components",
-                                            "api-reference/health-ai/assessment/fetch-assessment-v2",
-                                            "api-reference/health-ai/assessment/fetch-assessments-by-id",
+                                            {
+                                                "group": "Assessment APIS",
+                                                "icon": "comments-question-check",
+                                                "pages": [
+                                                    "api-reference/health-ai/assessment/assessment-flow/overview",
+                                                    "api-reference/health-ai/assessment/assessment-flow/initialization/initialize-assessment",
+                                                    "api-reference/health-ai/assessment/assessment-flow/continue/start-assessment",
+                                                    "api-reference/health-ai/assessment/assessment-flow/continue/continue-assessment",
+                                                    "api-reference/health-ai/assessment/assessment-flow/submit/submit-assessment",
+                                                    "api-reference/health-ai/assessment/questionnaire_data",
+                                                    "api-reference/health-ai/assessment/component-info/list-all-components",
+                                                    "api-reference/health-ai/assessment/fetch-assessment-v2",
+                                                    "api-reference/health-ai/assessment/fetch-assessments-by-id"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Assessment SDKs",
+                                                "icon": "laptop-binary",
+                                                "pages": [
+                                                    "api-reference/health-ai/assessment/SDKs/ekapython-sdk",
+                                                    "api-reference/health-ai/assessment/SDKs/assessment-ts-sdk"
+                                                ]
+                                            },
                                             {
                                                 "group": "More about Assessment",
                                                 "icon": "memo-circle-info",
@@ -104,13 +185,6 @@
                                                     "api-reference/health-ai/assessment/assessment-flow/continue/continue-request-formats",
                                                     "api-reference/health-ai/assessment/assessment-flow/continue/continue-response-formats"
                                                 ]
-                                            },
-                                            {
-                                                "group": "Assessment SDKs",
-                                                "icon": "laptop-binary",
-                                                "pages": [
-                                                    "api-reference/health-ai/assessment/SDKs/ekapython-sdk"
-                                                ]
                                             }
                                         ]
                                     },
@@ -119,6 +193,7 @@
                                         "icon": "microphone-lines",
                                         "pages": [
                                             "api-reference/health-ai/ekascribe/overview",
+                                            "api-reference/health-ai/ekascribe/System-Requirements",
                                             {
                                                 "group": "EkaScribe APIs",
                                                 "icon": "microphone-lines",
@@ -150,6 +225,14 @@
                                                 ]
                                             },
                                             "api-reference/health-ai/ekascribe/audio-transcription",
+                                            {
+                                                "group": "IP Allowlisting",
+                                                "icon": "list-check",
+                                                "pages": [
+                                                    "api-reference/health-ai/ekascribe/ip-allowlisting-for-clients"
+                                                ]
+                                            },
+                                            "api-reference/health-ai/ekascribe/FHIR/Eka-FHIR-structure",
                                             "api-reference/health-ai/ekascribe/ip-whitelisting-for-clients"
                                         ]
                                     },
@@ -199,17 +282,31 @@
                                         "group": "Medical Document Parsing",
                                         "icon": "book-open-cover",
                                         "pages": [
-                                            "api-reference/general-tools/medical/lab-report/introduction",
-                                            "api-reference/general-tools/medical/lab-report/upload-report",
-                                            "api-reference/general-tools/medical/lab-report/retrieve-parsed-report",
-                                            "api-reference/general-tools/medical/lab-report/parsed-report-result",
-                                            "api-reference/general-tools/medical/lab-report/delete-document",
+                                            {
+                                                "group": "APIs",
+                                                "icon": "network-wired",
+                                                "pages": [
+                                                    "api-reference/general-tools/medical/lab-report/introduction",
+                                                    "api-reference/general-tools/medical/lab-report/upload-report",
+                                                    "api-reference/general-tools/medical/lab-report/parsed-report-result",
+                                                    "api-reference/general-tools/medical/lab-report/delete-document"
+                                                ]
+                                            },
+                                            {
+                                                "group": "SDKs",
+                                                "icon": "box-open",
+                                                "pages": [
+                                                    "SDKs/backend/report-parsing-sdk",
+                                                    "SDKs/backend/report-parsing-sdk-java"
+                                                ]
+                                            },
                                             {
                                                 "group": "Webhooks",
                                                 "icon": "webhook",
                                                 "pages": [
                                                     "api-reference/general-tools/medical/lab-report/smart-report-webhook",
-                                                    "api-reference/general-tools/medical/lab-report/pii-webhook"
+                                                    "api-reference/general-tools/medical/lab-report/pii-webhook",
+                                                    "api-reference/general-tools/medical/lab-report/classification-webhook"
                                                 ]
                                             }
                                         ]
@@ -234,7 +331,7 @@
                                         ]
                                     },
                                     {
-                                        "group": "Patient Directory API's",
+                                        "group": "Patient Directory APIs",
                                         "icon": "hospital-user",
                                         "pages": [
                                             {
@@ -279,6 +376,33 @@
                                             "api-reference/doc-tool/doctor-and-clinic-api/get-doc-service"
                                         ]
                                     },
+                                    {
+                                        "group": "Config management APIs",
+                                        "icon": "user-cog",
+                                        "pages": [
+                                            {
+                                                "group": "User APIs",
+                                                "pages": [
+                                                    "api-reference/doc-tool/user-apis/get-all-users",
+                                                    "api-reference/doc-tool/user-apis/get-user-by-id"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Workspace APIs",
+                                                "pages": [
+                                                    "api-reference/doc-tool/business-api/get-business-info"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Onboarding APIs",
+                                                "pages": [
+                                                    "api-reference/doc-tool/onboarding-apis/onboard-doctor",
+                                                    "api-reference/doc-tool/onboarding-apis/onboard-clinic",
+                                                    "api-reference/doc-tool/onboarding-apis/onboard-ekauser"
+                                                ]
+                                            }
+                                        ]
+                                    },
                                     {
                                         "group": "Appointment API",
                                         "icon": "calendar-check",
@@ -292,7 +416,8 @@
                                             "api-reference/doc-tool/appointment-api/parked-appointment",
                                             "api-reference/doc-tool/appointment-api/complete-appointment",
                                             "api-reference/doc-tool/appointment-api/cancel-appointment",
-                                            "api-reference/doc-tool/appointment-api/get-appointments-by-date"
+                                            "api-reference/doc-tool/appointment-api/get-appointments-by-date",
+                                            "api-reference/doc-tool/appointment-api/change-status"
                                         ]
                                     },
                                     {
@@ -342,10 +467,26 @@
                                                 "group": "Doctor",
                                                 "icon": "stethoscope",
                                                 "pages": [
-                                                    "api-reference/doc-tool/post_webhooks/doctor-webhook"
+                                                    "api-reference/doc-tool/post_webhooks/doctor-webhook",
+                                                    "api-reference/doc-tool/post_webhooks/google-review-webhook",
+                                                    "api-reference/doc-tool/post_webhooks/mcert-webhook"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Receipt",
+                                                "icon": "indian-rupee-sign",
+                                                "pages": [
+                                                    "api-reference/doc-tool/post_webhooks/receipt-webhook"
                                                 ]
                                             }
                                         ]
+                                    },
+                                    {
+                                        "group": "IP Allowlisting",
+                                        "icon": "list-check",
+                                        "pages": [
+                                            "api-reference/doc-tool/ip-allowlisting-for-clients"
+                                        ]
                                     }
                                 ]
                             },
@@ -353,319 +494,418 @@
                                 "group": "ABDM Connect",
                                 "icon": "connectdevelop",
                                 "pages": [
+                                    "api-reference/user-app/abdm-connect/overview",
                                     {
-                                        "group": "Create and Login",
-                                        "icon": "user-plus",
+                                        "group": "APIs",
+                                        "icon": "network-wired",
                                         "pages": [
-                                            "api-reference/user-app/abdm-connect/registration/intro",
                                             {
-                                                "group": "Create",
-                                                "icon": "plus",
+                                                "group": "ABHA Creation and Login",
+                                                "icon": "user-plus",
                                                 "pages": [
+                                                    "api-reference/user-app/abdm-connect/registration/intro",
                                                     {
-                                                        "group": "Aadhaar",
-                                                        "icon": "id-card",
+                                                        "group": "Create",
+                                                        "icon": "plus",
                                                         "pages": [
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/initiate-registration",
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/aadhaar-resend-otp",
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/verify-otp",
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-resend-otp",
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-verify",
-                                                            "api-reference/user-app/abdm-connect/enrollment/aadhaar/create-abha"
+                                                            {
+                                                                "group": "Aadhaar",
+                                                                "icon": "id-card",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/initiate-registration",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/aadhaar-resend-otp",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/verify-otp",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-resend-otp",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/mobile-verify",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/create-abha",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/aadhaar/auto-login"
+                                                                ]
+                                                            },
+                                                            {
+                                                                "group": "Mobile",
+                                                                "icon": "mobile",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/enrollment/mobile/init",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/mobile/resend",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/mobile/verify",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/mobile/create"
+                                                                ]
+                                                            },
+                                                            {
+                                                                "group": "Face Auth",
+                                                                "icon": "face-viewfinder",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/enrollment/face-auth/intro",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-init",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-capture",
+                                                                    "api-reference/user-app/abdm-connect/enrollment/face-auth/face-auth-verify"
+                                                                ]
+                                                            }
                                                         ]
                                                     },
                                                     {
-                                                        "group": "Mobile",
-                                                        "icon": "mobile",
+                                                        "group": "Login",
+                                                        "icon": "right-to-bracket",
                                                         "pages": [
-                                                            "api-reference/user-app/abdm-connect/enrollment/mobile/init",
-                                                            "api-reference/user-app/abdm-connect/enrollment/mobile/resend",
-                                                            "api-reference/user-app/abdm-connect/enrollment/mobile/verify",
-                                                            "api-reference/user-app/abdm-connect/enrollment/mobile/create"
+                                                            "api-reference/user-app/abdm-connect/login/init",
+                                                            "api-reference/user-app/abdm-connect/login/verify",
+                                                            "api-reference/user-app/abdm-connect/login/login"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Commons",
+                                                        "icon": "tape",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/commons/does-health-id-exist",
+                                                            "api-reference/user-app/abdm-connect/commons/pincode-details",
+                                                            "api-reference/user-app/abdm-connect/commons/suggest-abha-address"
                                                         ]
                                                     }
                                                 ]
                                             },
                                             {
-                                                "group": "Login",
-                                                "icon": "right-to-bracket",
+                                                "group": "Profile Management",
+                                                "icon": "user",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/login/init",
-                                                    "api-reference/user-app/abdm-connect/login/verify",
-                                                    "api-reference/user-app/abdm-connect/login/login"
+                                                    "api-reference/user-app/abdm-connect/profile/getting-started",
+                                                    "api-reference/user-app/abdm-connect/profile/search/search",
+                                                    "api-reference/user-app/abdm-connect/profile/cards/qr-code",
+                                                    "api-reference/user-app/abdm-connect/profile/cards/abha-card",
+                                                    "api-reference/user-app/abdm-connect/profile/details/profile-details",
+                                                    "api-reference/user-app/abdm-connect/profile/details/update-profile",
+                                                    "api-reference/user-app/abdm-connect/profile/details/delete",
+                                                    {
+                                                        "group": "KYC",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/profile/kyc/kyc-init",
+                                                            "api-reference/user-app/abdm-connect/profile/kyc/kyc-resend",
+                                                            "api-reference/user-app/abdm-connect/profile/kyc/kyc-verify"
+                                                        ]
+                                                    }
                                                 ]
                                             },
                                             {
-                                                "group": "Commons",
-                                                "icon": "tape",
+                                                "group": "Scan & Share",
+                                                "icon": "qrcode",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/commons/does-health-id-exist",
-                                                    "api-reference/user-app/abdm-connect/commons/pincode-details",
-                                                    "api-reference/user-app/abdm-connect/commons/suggest-abha-address"
-                                                ]
-                                            }
-                                        ]
-                                    },
-                                    {
-                                        "group": "User Session",
-                                        "icon": "user-shield",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/session/getting-started",
-                                            "api-reference/user-app/abdm-connect/session/init",
-                                            "api-reference/user-app/abdm-connect/session/verify"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Patient Requests",
-                                        "icon": "hospital-user",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/patient-requests/getting-started",
-                                            "api-reference/user-app/abdm-connect/patient-requests/list-requests",
-                                            "api-reference/user-app/abdm-connect/patient-requests/requests-get-details"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Consents",
-                                        "icon": "handshake",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/consents/getting-started",
-                                            {
-                                                "group": "HIU",
-                                                "pages": [
-                                                    "api-reference/user-app/abdm-connect/consents/consent-create",
-                                                    "api-reference/user-app/abdm-connect/consents/consent-list",
-                                                    "api-reference/user-app/abdm-connect/consents/consent-details"
+                                                    "api-reference/user-app/abdm-connect/scan-and-share/getting-started",
+                                                    {
+                                                        "group": "PHR",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share",
+                                                            "api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share-token"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "HIP",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/scan-and-share/scan-on-share"
+                                                        ]
+                                                    }
                                                 ]
                                             },
                                             {
-                                                "group": "PHR",
+                                                "group": "User Session",
+                                                "icon": "user-shield",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/consents/consent-approve",
-                                                    "api-reference/user-app/abdm-connect/consents/consent-deny",
-                                                    "api-reference/user-app/abdm-connect/consents/consent-revoke"
+                                                    "api-reference/user-app/abdm-connect/session/getting-started",
+                                                    "api-reference/user-app/abdm-connect/session/status",
+                                                    "api-reference/user-app/abdm-connect/session/init",
+                                                    "api-reference/user-app/abdm-connect/session/verify"
                                                 ]
                                             },
                                             {
-                                                "group": "Auto Approval",
-                                                "pages": [
-                                                    "api-reference/user-app/abdm-connect/consents/auto-approval/get-status",
-                                                    "api-reference/user-app/abdm-connect/consents/auto-approval/update-auto-approval-policy"
-                                                ]
-                                            }
-                                        ]
-                                    },
-                                    {
-                                        "group": "Care Contexts",
-                                        "icon": "notes-medical",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/care-contexts/getting-started",
-                                            {
-                                                "group": "Data",
-                                                "icon": "files",
+                                                "group": "Patient Requests",
+                                                "icon": "hospital-user",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/care-contexts/data-on-fetch",
-                                                    "api-reference/user-app/abdm-connect/care-contexts/data-on-push"
+                                                    "api-reference/user-app/abdm-connect/patient-requests/getting-started",
+                                                    "api-reference/user-app/abdm-connect/patient-requests/list-requests",
+                                                    "api-reference/user-app/abdm-connect/patient-requests/requests-get-details"
                                                 ]
                                             },
                                             {
                                                 "group": "Providers",
-                                                "icon": "hospitals",
+                                                "icon": "hospital",
                                                 "pages": [
                                                     {
-                                                        "group": "Linked Providers",
-                                                        "pages": [
-                                                            "api-reference/user-app/abdm-connect/care-contexts/providers/providers"
-                                                        ]
-                                                    },
-                                                    {
-                                                        "group": "Linked Care Contexts",
+                                                        "group": "Search",
                                                         "pages": [
-                                                            "api-reference/user-app/abdm-connect/care-contexts/records/records"
+                                                            "api-reference/user-app/abdm-connect/providers/getting-started",
+                                                            "api-reference/user-app/abdm-connect/providers/provider",
+                                                            "api-reference/user-app/abdm-connect/providers/search/providers"
                                                         ]
                                                     }
                                                 ]
                                             },
                                             {
-                                                "group": "Linking",
-                                                "icon": "link",
+                                                "group": "Care Contexts",
+                                                "icon": "notes-medical",
                                                 "pages": [
+                                                    "api-reference/user-app/abdm-connect/care-contexts/getting-started",
                                                     {
-                                                        "group": "HIP Inititated Linking",
+                                                        "group": "Data",
+                                                        "icon": "files",
                                                         "pages": [
-                                                            "api-reference/user-app/abdm-connect/care-contexts/link/hip-linking"
+                                                            {
+                                                                "group": "Encryption",
+                                                                "icon": "lock",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/ecdh-keys",
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/ecdh-encrypt",
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/ecdh-decrypt"
+                                                                ]
+                                                            },
+                                                            {
+                                                                "group": "Sharing",
+                                                                "icon": "share",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/hiu-keys",
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/data-on-fetch",
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/data-on-push"
+                                                                ]
+                                                            }
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Providers",
+                                                        "icon": "hospitals",
+                                                        "pages": [
+                                                            {
+                                                                "group": "Linked Providers",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/providers/providers"
+                                                                ]
+                                                            },
+                                                            {
+                                                                "group": "Linked Care Contexts",
+                                                                "pages": [
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/records/records"
+                                                                ]
+                                                            }
                                                         ]
                                                     },
                                                     {
-                                                        "group": "Discover and Link",
+                                                        "group": "Linking",
+                                                        "icon": "link",
                                                         "pages": [
-                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/introduction",
                                                             {
-                                                                "group": "PHR",
+                                                                "group": "HIP Inititated Linking",
                                                                 "pages": [
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/discover",
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/link-init",
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/link-confirm"
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/link/hip-linking"
                                                                 ]
                                                             },
                                                             {
-                                                                "group": "HIP",
+                                                                "group": "Discover and Link",
                                                                 "pages": [
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/on_discover",
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/link_on_init",
-                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/link_on_confirm"
+                                                                    "api-reference/user-app/abdm-connect/care-contexts/discover/introduction",
+                                                                    {
+                                                                        "group": "PHR",
+                                                                        "pages": [
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/discover",
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/link-init",
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/link-confirm"
+                                                                        ]
+                                                                    },
+                                                                    {
+                                                                        "group": "HIP",
+                                                                        "pages": [
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/on_discover",
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/link_on_init",
+                                                                            "api-reference/user-app/abdm-connect/care-contexts/discover/link_on_confirm"
+                                                                        ]
+                                                                    }
                                                                 ]
                                                             }
                                                         ]
                                                     }
                                                 ]
-                                            }
-                                        ]
-                                    },
-                                    {
-                                        "group": "Providers",
-                                        "icon": "hospital",
-                                        "pages": [
+                                            },
                                             {
-                                                "group": "Onboarding",
+                                                "group": "Consents",
+                                                "icon": "handshake",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/providers/onboarding-overview",
-                                                    "api-reference/user-app/abdm-connect/providers/onboarding"
+                                                    "api-reference/user-app/abdm-connect/consents/getting-started",
+                                                    {
+                                                        "group": "HIU",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/consents/consent-create",
+                                                            "api-reference/user-app/abdm-connect/consents/consent-list",
+                                                            "api-reference/user-app/abdm-connect/consents/consent-details"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "PHR",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/consents/consent-approve",
+                                                            "api-reference/user-app/abdm-connect/consents/consent-deny",
+                                                            "api-reference/user-app/abdm-connect/consents/consent-revoke"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Auto Approval",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/consents/auto-approval/get-status",
+                                                            "api-reference/user-app/abdm-connect/consents/auto-approval/update-auto-approval-policy"
+                                                        ]
+                                                    }
                                                 ]
                                             },
                                             {
-                                                "group": "Search",
+                                                "group": "Blood Bank",
+                                                "icon": "droplet",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/providers/getting-started",
-                                                    "api-reference/user-app/abdm-connect/providers/provider",
-                                                    "api-reference/user-app/abdm-connect/providers/search/providers"
+                                                    "api-reference/user-app/abdm-connect/blood-bank/getting-started",
+                                                    "api-reference/user-app/abdm-connect/blood-bank/state-district",
+                                                    "api-reference/user-app/abdm-connect/blood-bank/get-blood-banks"
                                                 ]
-                                            }
-                                        ]
-                                    },
-                                    {
-                                        "group": "Profile",
-                                        "icon": "user",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/profile/getting-started",
-                                            "api-reference/user-app/abdm-connect/profile/cards/qr-code",
-                                            "api-reference/user-app/abdm-connect/profile/cards/abha-card",
-                                            "api-reference/user-app/abdm-connect/profile/details/profile-details",
-                                            "api-reference/user-app/abdm-connect/profile/details/update-profile",
-                                            "api-reference/user-app/abdm-connect/profile/details/delete",
+                                            },
                                             {
-                                                "group": "KYC",
+                                                "group": "Registries",
+                                                "icon": "building-columns",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/profile/kyc/kyc-init",
-                                                    "api-reference/user-app/abdm-connect/profile/kyc/kyc-resend",
-                                                    "api-reference/user-app/abdm-connect/profile/kyc/kyc-verify"
+                                                    "api-reference/user-app/abdm-connect/nhpr-abdm/getting-started",
+                                                    {
+                                                        "group": "HPR (Professionals)",
+                                                        "icon": "user-doctor",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-aadhar-otp",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-aadhar-otp",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-exist",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/suggest-ids",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/create-hpr",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/get-mobile-otp",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/verify-mobile-otp",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hpr/check-hpr-available"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "HFR (Facilities)",
+                                                        "icon": "hospital",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hfr/search-facility",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hfr/onboard-facility",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/hfr/link-facility"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Onboarding",
+                                                        "icon": "plus",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/onboarding-overview",
+                                                            "api-reference/user-app/abdm-connect/nhpr-abdm/onboarding"
+                                                        ]
+                                                    }
                                                 ]
-                                            }
-                                        ]
-                                    },
-                                    {
-                                        "group": "Scan & Share",
-                                        "icon": "qrcode",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/scan-and-share/getting-started",
+                                            },
                                             {
-                                                "group": "PHR",
+                                                "group": "Scan & Pay",
+                                                "icon": "money-bill",
+                                                "tag": "Coming Soon",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share",
-                                                    "api-reference/user-app/abdm-connect/scan-and-share/phr-scan-share-token"
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/getting-started",
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/open-orders",
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/get-open-orders",
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/patient-select",
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/get-patient-select",
+                                                    "api-reference/user-app/abdm-connect/scan-and-pay/get-transaction-details"
                                                 ]
                                             },
                                             {
-                                                "group": "HIP",
+                                                "group": "Physical Consultation",
+                                                "icon": "calendar-check",
+                                                "tag": "Coming Soon",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/scan-and-share/scan-on-share"
+                                                    "api-reference/user-app/abdm-connect/phys-cons/search-doctors",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-doctors",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/search-slots",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-slots",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/init",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-init",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/confirm",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-confirm",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/order-status",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-order-status",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/cancel",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/get-cancel",
+                                                    "api-reference/user-app/abdm-connect/phys-cons/update"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Errors",
+                                                "icon": "circle-exclamation",
+                                                "pages": [
+                                                    "api-reference/user-app/abdm-connect/errors"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Webhooks",
+                                                "icon": "webhook",
+                                                "pages": [
+                                                    "api-reference/user-app/abdm-connect/webhooks/abha-created",
+                                                    "api-reference/user-app/abdm-connect/webhooks/link-care-context",
+                                                    "api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share",
+                                                    "api-reference/user-app/abdm-connect/webhooks/hip-data-fetch",
+                                                    "api-reference/user-app/abdm-connect/webhooks/hiu-data-push",
+                                                    {
+                                                        "group": "Care Contexts Discovery",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/webhooks/discover-care-context",
+                                                            "api-reference/user-app/abdm-connect/webhooks/discover-link-init",
+                                                            "api-reference/user-app/abdm-connect/webhooks/discover-link-confirm"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Physical Consultation",
+                                                        "tag": "Coming Soon",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/webhooks/search-doctors",
+                                                            "api-reference/user-app/abdm-connect/webhooks/search-slots",
+                                                            "api-reference/user-app/abdm-connect/webhooks/booking-init",
+                                                            "api-reference/user-app/abdm-connect/webhooks/booking-confirm",
+                                                            "api-reference/user-app/abdm-connect/webhooks/booking-status",
+                                                            "api-reference/user-app/abdm-connect/webhooks/booking-cancel"
+                                                        ]
+                                                    },
+                                                    {
+                                                        "group": "Locker",
+                                                        "pages": [
+                                                            "api-reference/user-app/abdm-connect/webhooks/locker-created",
+                                                            "api-reference/user-app/abdm-connect/webhooks/subscription-modify",
+                                                            "api-reference/user-app/abdm-connect/webhooks/subscription-notify"
+                                                        ]
+                                                    }
                                                 ]
                                             }
                                         ]
                                     },
                                     {
-                                        "group": "Scan & Pay",
-                                        "icon": "money-bill",
-                                        "tag": "Coming Soon",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/getting-started",
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/open-orders",
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/get-open-orders",
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/patient-select",
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/get-patient-select",
-                                            "api-reference/user-app/abdm-connect/scan-and-pay/get-transaction-details"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Blood Bank",
-                                        "icon": "droplet",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/blood-bank/getting-started",
-                                            "api-reference/user-app/abdm-connect/blood-bank/state-district",
-                                            "api-reference/user-app/abdm-connect/blood-bank/get-blood-banks"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Physical Consultation",
-                                        "icon": "calendar-check",
-                                        "tag": "Coming Soon",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/phys-cons/search-doctors",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-doctors",
-                                            "api-reference/user-app/abdm-connect/phys-cons/search-slots",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-slots",
-                                            "api-reference/user-app/abdm-connect/phys-cons/init",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-init",
-                                            "api-reference/user-app/abdm-connect/phys-cons/confirm",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-confirm",
-                                            "api-reference/user-app/abdm-connect/phys-cons/order-status",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-order-status",
-                                            "api-reference/user-app/abdm-connect/phys-cons/cancel",
-                                            "api-reference/user-app/abdm-connect/phys-cons/get-cancel",
-                                            "api-reference/user-app/abdm-connect/phys-cons/update"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Errors",
-                                        "icon": "circle-exclamation",
-                                        "pages": [
-                                            "api-reference/user-app/abdm-connect/errors"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Webhooks",
-                                        "icon": "webhook",
+                                        "group": "SDKs",
+                                        "icon": "box-open",
                                         "pages": [
-                                            "api-reference/user-app/abdm-connect/webhooks/abha-created",
-                                            "api-reference/user-app/abdm-connect/webhooks/link-care-context",
-                                            "api-reference/user-app/abdm-connect/webhooks/hip-scan-and-share",
-                                            "api-reference/user-app/abdm-connect/webhooks/hip-data-fetch",
-                                            "api-reference/user-app/abdm-connect/webhooks/hiu-data-push",
                                             {
-                                                "group": "Care Contexts Discovery",
+                                                "group": "Web SDKs",
+                                                "icon": "globe",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/webhooks/discover-care-context",
-                                                    "api-reference/user-app/abdm-connect/webhooks/discover-link-init",
-                                                    "api-reference/user-app/abdm-connect/webhooks/discover-link-confirm"
-                                                ]
-                                            },
-                                            {
-                                                "group": "Physical Consultation",
-                                                "tag": "Coming Soon",
-                                                "pages": [
-                                                    "api-reference/user-app/abdm-connect/webhooks/search-doctors",
-                                                    "api-reference/user-app/abdm-connect/webhooks/search-slots",
-                                                    "api-reference/user-app/abdm-connect/webhooks/booking-init",
-                                                    "api-reference/user-app/abdm-connect/webhooks/booking-confirm",
-                                                    "api-reference/user-app/abdm-connect/webhooks/booking-status",
-                                                    "api-reference/user-app/abdm-connect/webhooks/booking-cancel"
+                                                    {
+                                                        "group": "ABHA",
+                                                        "icon": "id-card",
+                                                        "pages": [
+                                                            "SDKs/web-sdk/abha-sdk/get-started",
+                                                            "SDKs/web-sdk/abha-sdk/abha-login-create",
+                                                            "SDKs/web-sdk/abha-sdk/abha-kyc",
+                                                            "SDKs/web-sdk/abha-sdk/abha-consent",
+                                                            "SDKs/web-sdk/abha-sdk/abha-s&s",
+                                                            "SDKs/web-sdk/abha-sdk/abha-sdk-theme"
+                                                        ]
+                                                    }
                                                 ]
                                             },
                                             {
-                                                "group": "Locker",
+                                                "group": "Backend SDK",
+                                                "icon": "code",
                                                 "pages": [
-                                                    "api-reference/user-app/abdm-connect/webhooks/locker-created",
-                                                    "api-reference/user-app/abdm-connect/webhooks/subscription-modify",
-                                                    "api-reference/user-app/abdm-connect/webhooks/subscription-notify"
+                                                    "SDKs/backend/go-sdk"
                                                 ]
                                             }
                                         ]
@@ -707,58 +947,76 @@
                                 "icon": "book-open-cover",
                                 "pages": [
                                     {
-                                        "group": "Create",
-                                        "icon": "upload",
+                                        "group": "APIs",
+                                        "icon": "network-wired",
                                         "pages": [
-                                            "api-reference/user-app/records/create-overview",
-                                            "api-reference/user-app/records/obtain-authorization",
-                                            "api-reference/user-app/records/upload-records"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Read",
-                                        "icon": "eye",
-                                        "pages": [
-                                            "api-reference/user-app/records/read-documents",
-                                            "api-reference/user-app/records/describe-record",
-                                            "api-reference/user-app/records/list-records",
-                                            "api-reference/user-app/records/retrieve-health-records",
-                                            "api-reference/user-app/records/send-refresh"
-                                        ]
-                                    },
-                                    {
-                                        "group": "Update",
-                                        "icon": "pencil",
-                                        "pages": [
-                                            "api-reference/user-app/records/update_overview",
-                                            "api-reference/user-app/records/update-document"
+                                            {
+                                                "group": "Add",
+                                                "icon": "upload",
+                                                "pages": [
+                                                    "api-reference/user-app/records/create-overview",
+                                                    "api-reference/user-app/records/obtain-authorization",
+                                                    "api-reference/user-app/records/upload-records"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Read",
+                                                "icon": "eye",
+                                                "pages": [
+                                                    "api-reference/user-app/records/read-documents",
+                                                    "api-reference/user-app/records/describe-record",
+                                                    "api-reference/user-app/records/list-records",
+                                                    "api-reference/user-app/records/retrieve-health-records",
+                                                    "api-reference/user-app/records/send-refresh"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Update",
+                                                "icon": "pencil",
+                                                "pages": [
+                                                    "api-reference/user-app/records/update_overview",
+                                                    "api-reference/user-app/records/update-document"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Delete",
+                                                "icon": "trash",
+                                                "pages": [
+                                                    "api-reference/user-app/records/delete_overview",
+                                                    "api-reference/user-app/records/delete-document"
+                                                ]
+                                            },
+                                            {
+                                                "group": "Cases",
+                                                "icon": "folder-open",
+                                                "pages": [
+                                                    "api-reference/user-app/records/create-case",
+                                                    "api-reference/user-app/records/update-case",
+                                                    "api-reference/user-app/records/list-case",
+                                                    "api-reference/user-app/records/delete-case"
+                                                ]
+                                            }
                                         ]
                                     },
                                     {
-                                        "group": "Delete",
-                                        "icon": "trash",
+                                        "group": "SDKs",
+                                        "icon": "box-open",
                                         "pages": [
-                                            "api-reference/user-app/records/delete_overview",
-                                            "api-reference/user-app/records/delete-document"
+                                            {
+                                                "group": "Mobile",
+                                                "icon": "mobile",
+                                                "pages": [
+                                                    "api-reference/user-app/records/SDKs/iOS-sdk"
+                                                ]
+                                            }
                                         ]
                                     },
                                     {
                                         "group": "Webhooks",
                                         "icon": "webhook",
                                         "pages": [
-                                            "api-reference/user-app/records/smart-report",
                                             "api-reference/user-app/records/record-refresh-webhook"
                                         ]
-                                    },
-                                    {
-                                        "group": "Cases",
-                                        "icon": "folder-open",
-                                        "pages": [
-                                            "api-reference/user-app/records/create-case",
-                                            "api-reference/user-app/records/update-case",
-                                            "api-reference/user-app/records/list-case",
-                                            "api-reference/user-app/records/delete-case"
-                                        ]
                                     }
                                 ]
                             },
@@ -852,8 +1110,9 @@
                                 "group": "Highlights",
                                 "pages": [
                                     "eka-medai/spotlight",
-                                    "eka-medai/datasets"
-                                ]
+                                    "eka-medai/datasets",
+                                    "eka-medai/models"
+                                ] 
                             }
                         ]
                     },
@@ -863,29 +1122,19 @@
                             {
                                 "group": "Android",
                                 "pages": [
-                                    "SDKs/android/voice-to-rx",
+                                    "SDKs/android/ekascribe",
                                     "SDKs/android/medical-records"
                                 ]
                             },
-                            {
-                                "group": "iOS",
-                                "pages": [
-                                    "SDKs/ios/medical-records",
-                                    "SDKs/ios/eka-scribe"
-                                ]
-                            },
                             {
                                 "group": "Web SDK",
                                 "pages": [
-                                    "SDKs/web-sdk/getting-started",
-                                    "SDKs/web-sdk/self-assessment-sdk",
-                                    "SDKs/web-sdk/abha-sdk"
+                                    "SDKs/web-sdk/getting-started"
                                 ]
                             },
                             {
                                 "group": "Backend",
                                 "pages": [
-                                    "SDKs/backend/go-sdk",
                                     "SDKs/backend/ekapython-sdk",
                                     "SDKs/backend/webhook-sdk"
                                 ]
@@ -898,6 +1147,43 @@
                             }
                         ]
                     },
+                    {
+                        "tab": "AI Tools",
+                        "groups": [
+                            {
+                                "group": "Echo Agent Kit",
+                                "icon": "robot",
+                                "pages": [
+                                    "ai-tools/agent-kit/introduction",
+                                    "ai-tools/agent-kit/quickstart",
+                                    "ai-tools/agent-kit/installation",
+                                    "ai-tools/agent-kit/configuration",
+                                    "ai-tools/agent-kit/agents",
+                                    "ai-tools/agent-kit/tools",
+                                    "ai-tools/agent-kit/llm-providers",
+                                    "ai-tools/agent-kit/streaming",
+                                    "ai-tools/agent-kit/mcp-integration",
+                                    "ai-tools/agent-kit/examples"
+                                ]
+                            },
+                            {
+                                "group": "Eka MCP Server",
+                                "icon": "server",
+                                "pages": [
+                                    "ai-tools/mcp-server/introduction",
+                                    "ai-tools/mcp-server/supported-tools",
+                                    "ai-tools/mcp-server/authentication",
+                                    {
+                                        "group": "Integrations",
+                                        "icon": "plug",
+                                        "pages": [
+                                            "ai-tools/mcp-server/integrations/custom-client"
+                                        ]
+                                    }
+                                ]
+                            }
+                        ]
+                    },
                     {
                         "tab": "CookBook",
                         "groups": [
@@ -913,12 +1199,6 @@
                         ]
                     }
                 ]
-            },
-            {
-                "anchor": "Developer Discord",
-                "href": "https://discord.gg/THgd5S22EK",
-                "icon": "discord",
-                "iconType": "brands"
             }
         ]
     },
@@ -931,12 +1211,19 @@
             {
                 "label": "Support",
                 "href": "https://discord.gg/THgd5S22EK"
+            },
+            {
+                "label": "Developer Discord",
+                "anchor": "Developer Discord",
+                "href": "https://discord.gg/THgd5S22EK",
+                "icon": "discord",
+                "iconType": "brands"
             }
         ],
         "primary": {
             "type": "button",
-            "label": "Dashboard",
-            "href": "https://eka.care"
+            "label": "Get Started",
+            "href": "https://console.eka.care"
         }
     },
     "footer": {
diff --git a/eka-medai/datasets.mdx b/eka-medai/datasets.mdx
index fa83d767..a5ac9f17 100644
--- a/eka-medai/datasets.mdx
+++ b/eka-medai/datasets.mdx
@@ -10,7 +10,33 @@ At Eka Care, we believe that advancing healthcare in India requires AI solutions
 
 ## Available Datasets
 
-### NidaanKosh
+
+### Eka-Medical-ASR Evaluation Dataset
+- A curated collection of 3,900+ English and Hindi medical speech recordings designed to benchmark and improve speech-to-text performance for Indian healthcare use cases.
+- Built with diverse accents and real clinical terminology, this dataset enables robust evaluation of AI-powered medical scribe and voice-enabled healthcare applications.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/datasets/details/eka_medical_asr_evaluation_dataset.html) | [HuggingFace](https://huggingface.co/datasets/ekacare/eka-medical-asr-evaluation-dataset) 
+---
+### Medical Records Parsing Validation Set
+- A curated dataset of 288 de-identified lab reports and prescriptions designed to evaluate AI systems that extract structured data from unstructured medical documents.
+- Expert-annotated with rubric-based LLM evaluation, it ensures clinically accurate benchmarking across diverse Indian healthcare document formats.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/datasets/details/eka_medical_records_parsing_validation_set.html) | [HuggingFace](https://huggingface.co/datasets/ekacare/medical_records_parsing_validation_set)
+---
+### EkaCare Medical History Summarisation
+- A curated set of 58 real-world medical cases designed to evaluate AI systems in generating concise, clinically relevant summaries of patient histories.
+- Expert-defined rubrics and reference summaries ensure objective assessment of key developments, historical context, and critical care insights from the most recent six months of medical data.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/datasets/details/ekacare_medical_history_summarisation.html) | [HuggingFace](https://huggingface.co/datasets/ekacare/ekacare_medical_history_summarisation)
+---
+### Clinical Note Generation Dataset
+- A multilingual dataset of 156+ transcribed doctor–patient conversations designed to evaluate AI systems that convert medical dialogues into structured, entity-level clinical records.
+- Expert-annotated ground truth JSON and rubric-based LLM evaluation ensure accurate benchmarking of structured note generation for EHR-ready medical documentation.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/datasets/details/eka_clinical_note_generation_dataset.html) | [HuggingFace](https://huggingface.co/datasets/ekacare/clinical_note_generation_dataset)
+---
+### Eka-IndicMTEB
+- A multilingual medical embedding benchmark with 2,532 doctor-verified queries across 8 Indic languages, aligned to SNOMED CT for concept-level evaluation.
+- Designed to benchmark and improve cross-lingual medical retrieval and semantic search systems across India’s diverse linguistic landscape.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/datasets/details/ekaindicmteb.html) | [HuggingFace](https://huggingface.co/datasets/ekacare/Eka-IndicMTEB)
+---
+### NidaanKosh 
 
 **A Comprehensive Laboratory Investigation Dataset of 100,000 Indian Subjects with 6.8 Million+ Readings**
 
@@ -74,4 +100,7 @@ We welcome collaboration opportunities with academic institutions, research orga
 
 ---
 
-*These datasets are provided for research and development purposes. For terms of use and licensing information, please refer to the documentation included with each dataset.*
\ No newline at end of file
+*These datasets are provided for research and development purposes. For terms of use and licensing information, please refer to the documentation included with each dataset.*
+
+
+
diff --git a/eka-medai/models.mdx b/eka-medai/models.mdx
new file mode 100644
index 00000000..6b3ac8ce
--- /dev/null
+++ b/eka-medai/models.mdx
@@ -0,0 +1,19 @@
+## EkaCare Models
+
+### Parrotlet-V-Lite-4B
+- A purpose-built vision LLM optimized for parsing Indian medical records, including lab reports, digital prescriptions, document classification, and PII extraction.
+- Deployable via Hugging Face, it enables structured data extraction from medical images and PDFs for healthcare AI and interoperability workflows.
+-  [AIKosh](https://aikosh.indiaai.gov.in/home/models/details/parrotlet_v_lite_4b.html) | [Hugging Face](https://huggingface.co/ekacare/parrotlet-v-lite-4b)
+
+---
+
+### Parrotlet-A-EN-5B
+- A healthcare-optimized ASR model for transcribing English medical speech in Indian clinical settings, combining a Whisper V3 encoder with a MedGemma3 4B decoder.
+- Designed for accurate short-form medical audio transcription, it enables high-fidelity speech-to-text conversion for scribe and voice-enabled healthcare applications.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/models/details/parrotlet_a_en_5b.html) | [Hugging Face](https://huggingface.co/ekacare/parrotlet-a-en-5b)
+
+---
+### Parrotlet-E
+- A state-of-the-art multilingual embedding model optimized for entity-level medical concept representation across 12 Indic languages and English.
+- Fine-tuned on 18M+ SNOMED CT and UMLS-aligned term pairs, it enables robust cross-lingual medical coding, semantic search, and retrieval with benchmark-leading performance on Eka-IndicMTEB.
+- [AIKosh](https://aikosh.indiaai.gov.in/home/models/details/parrotlet_e.html) | [Hugging Face](https://huggingface.co/ekacare/parrotlet-e)
diff --git a/eka-medai/spotlight.mdx b/eka-medai/spotlight.mdx
index cdb152b3..0855725d 100644
--- a/eka-medai/spotlight.mdx
+++ b/eka-medai/spotlight.mdx
@@ -3,12 +3,20 @@ title: Spotlight
 ---
 
 ## Blogs
+- [Introducing KARMA – OpenMedEvalKit](https://info.eka.care/services/introducing-karma-openmedevalkit-an-open-source-framework-for-medical-ai-evaluation)
+- [Parrotlet-E & Eka IndicMTEB](https://info.eka.care/services/introducing-parrotlet-e-and-eka-indicmteb-bridging-indias-multilingual-healthcare-gap)
+- [Beyond Traditional WER: Semantic WER for ASR](https://info.eka.care/services/beyond-traditional-wer-the-critical-need-for-semantic-wer-in-asr-for-indian-healthcare)
+- [Parrotlet-V Lite (4B) – Vision LLM ](https://info.eka.care/services/parrotlet-v-lite-4b-releasing-our-purpose-built-vision-llm-for-parsing-medical-records)
+- [Parrotlet-A EN (5B) – Medical ASR LLM](https://info.eka.care/services/parrotlet-a-en-5b-releasing-our-purpose-built-llm-for-english-asr-in-indian-healthcare)
+- [Advancing Healthcare AI Evaluation in India](https://info.eka.care/services/advancing-healthcare-ai-evaluation-in-india-ekacare-releases-four-evaluation-datasets)
 - [Lab-Ready and Prescription-Perfect: Eka Care's Small LLMs vs. Industry Giants](https://info.eka.care/services/lab-ready-and-prescription-perfect-ekas-small-llms-vs-industry-giants)
 - [Extracting Structured Information from Lab Reports: Challenges and Learnings](https://info.eka.care/services/eka-smart-report)
 - [Eka's heart rate monitor](https://www.eka.care/services/get-the-pulse)
 - [Leveraging semantic technologies in healthcare](https://info.eka.care/services/leveraging-ontologies-in-health-care)
 
+
 ## Publications / Reports
+- Sujal Chondhekar, Vasanth Murukuri, Rushabh Vasani, Sanika Goyal, Rajshree Badami, Anushree Rana, Sanjana SN, Karthik Pandia, Sulabh Katiyar, Neha Jagadeesh, Sankalp Gulati (2025):When De-noising Hurts: A Systematic Study of Speech Enhancement Effects on Modern Medical ASR Systems, [arxiv.org](https://arxiv.org/abs/2512.17562)
 - Rajshree, B., Sanjana, S.N., Vasani, R., Tuniki, V., Kapoor, N., & Gulati, S. (2024). Latent iron deficiency in Indian women and children: A descriptive analysis. *International Journal of Clinical Biochemistry and Research*, Volume 2024, Article 22074. [Link to Article](https://www.ijcbr.in/article-details/22074). DOI: 10.18231/j.ijcbr.2024.010
 - Shetty A, Narasimhamurthy SS, Nataraj KS, Prabhu SM, Jagadeesh N, Katre K, et al. Smartphone‑based health monitoring in India: Data collection and evaluation for pulse rate estimation. J Family Med Prim Care 2024
 - Neelesh Kapoor, Sanjana SN ; Balu PS ,Soumitra Sethia, Shuba DB. AI Horizons in Indian Healthcare: A Vision for Transformation and Equity. Indian Journal of Community Medicine [In print]
diff --git a/images/EkascribeProductBasedOnBusinessModelAndIntegrationDecision.png b/images/EkascribeProductBasedOnBusinessModelAndIntegrationDecision.png
new file mode 100644
index 00000000..736b7824
Binary files /dev/null and b/images/EkascribeProductBasedOnBusinessModelAndIntegrationDecision.png differ
diff --git a/images/OIDC.png b/images/OIDC.png
new file mode 100644
index 00000000..67d72fcf
Binary files /dev/null and b/images/OIDC.png differ
diff --git a/images/claude-prompt.png b/images/claude-prompt.png
new file mode 100644
index 00000000..e7c1e14e
Binary files /dev/null and b/images/claude-prompt.png differ
diff --git a/images/eka-remote-mcp.png b/images/eka-remote-mcp.png
new file mode 100644
index 00000000..3fd7236f
Binary files /dev/null and b/images/eka-remote-mcp.png differ
diff --git a/images/ekascribe-integration-flow.png b/images/ekascribe-integration-flow.png
new file mode 100644
index 00000000..f50c0085
Binary files /dev/null and b/images/ekascribe-integration-flow.png differ
diff --git a/integrations/core-emr/appointments.mdx b/integrations/core-emr/appointments.mdx
new file mode 100644
index 00000000..f5568e55
--- /dev/null
+++ b/integrations/core-emr/appointments.mdx
@@ -0,0 +1,56 @@
+---
+title: Appointment
+description: Scheduled patient–doctor interactions within Core EMR
+---
+
+## Appointment
+
+An **Appointment** represents a scheduled meeting between a **patient** and a **doctor**. Appointments are core operational entities used to organize consultations, procedures, and follow-up visits across healthcare settings.
+
+Each appointment captures key details such as identifiers, participant information, location, timing, and current status.
+
+Read more : ([API Reference - Appointment](/api-reference/doc-tool/Actors/actors)) section. 
+
+Read more : ([API Reference - communication-flow-appointment-clinical-events ](/communication-flow-appointment-clinical-events)) section. 
+
+---
+
+## Use Cases
+
+### Patient Consultation Scheduling
+Schedule in-person or virtual consultations between patients and doctors with defined time slots.
+
+### Walk-In and Emergency Bookings
+Record and manage walk-in or urgent appointments alongside scheduled visits.
+
+### Rescheduling and Cancellations
+Update appointment timings, reassign doctors, or cancel appointments while maintaining an audit trail.
+
+### Teleconsultation Coordination
+Link appointments to virtual consultation platforms for remote care delivery.
+
+### Clinic and Resource Planning
+Use appointment data to manage clinic capacity, room usage, and clinician availability.
+
+### Notifications and Reminders
+Trigger reminders and updates for patients and doctors to reduce no-shows and improve attendance.
+
+---
+
+## Notes & Considerations
+
+- **Status lifecycle**  
+  Appointments typically move through states such as scheduled, confirmed, completed, cancelled, or no-show.
+
+- **Participant linkage**  
+  Appointments should be correctly linked to patient and doctor profiles to ensure data consistency.
+
+- **Time and location accuracy**  
+  Ensure correct timezone, clinic location, or virtual meeting details are captured.
+
+- **Operational dependencies**
+
+Read more : ([API Reference - Appointment](/api-reference/doc-tool/Actors/actors)) section. 
+
+Read more : ([API Reference - communication-flow-appointment-clinical-events ](/communication-flow-appointment-clinical-events)) section. 
+
diff --git a/integrations/core-emr/clinic.mdx b/integrations/core-emr/clinic.mdx
new file mode 100644
index 00000000..5e7c9fe1
--- /dev/null
+++ b/integrations/core-emr/clinic.mdx
@@ -0,0 +1,65 @@
+---
+title: Clinic
+description: Healthcare facility profiles within Core EMR
+---
+
+## Clinic
+
+A **Clinic** is a healthcare facility where doctors provide medical services. Clinic profiles represent physical or virtual care locations and act as the operational anchor for appointments, doctors, and patient interactions.
+
+Each clinic record includes details such as **name**, **address**, **contact information**, **specialties**, and **operating hours**.
+
+Read more : ([API Reference - Clinic](/api-reference/doc-tool/doctor-and-clinic-api/getting-started)) section. 
+
+---
+
+## Use Cases
+
+### Clinic Setup and Management
+Create and manage clinic profiles during onboarding or administrative configuration.
+
+### Doctor–Clinic Association
+Associate doctors with one or more clinics, departments, or service locations.
+
+### Appointment Location Mapping
+Link appointments to clinics to manage patient flow, room allocation, and operational planning.
+
+### Operating Hours and Availability
+Define clinic working hours, holidays, and closures to control appointment scheduling.
+
+### Multi-Location Network Management
+Support hospital groups and clinic chains with centralized visibility across locations.
+
+### Reporting and Operations
+Enable clinic-level reporting for patient volumes, consultations, and service utilization.
+
+---
+
+## Notes & Considerations
+
+- **Accurate location data**  
+  Ensure address and contact details are kept up to date for patient communication and navigation.
+
+- **Specialty alignment**  
+  Clinics may support multiple specialties that influence doctor assignments and appointment types.
+
+- **Operating hours enforcement**  
+  Scheduling systems should respect clinic hours to prevent invalid bookings.
+
+- **Virtual clinics**  
+  Clinics may represent teleconsultation-only locations with virtual operating models.
+
+- **Scalability**  
+  Designed to support single clinics as well as large, multi-location healthcare networks.
+
+---
+
+## Ideal For
+
+- Clinics and hospitals  
+- Hospital management systems (HMS)  
+- Practice management platforms  
+- Telemedicine providers  
+
+
+Read more : ([API Reference - Clinic](/api-reference/doc-tool/doctor-and-clinic-api/getting-started)) section. 
\ No newline at end of file
diff --git a/integrations/core-emr/doctor.mdx b/integrations/core-emr/doctor.mdx
new file mode 100644
index 00000000..cc424fca
--- /dev/null
+++ b/integrations/core-emr/doctor.mdx
@@ -0,0 +1,64 @@
+---
+title: Doctor
+description: Medical professional profiles and availability within Core EMR
+---
+
+## Doctor
+
+A **Doctor** is a medical professional registered on the Eka platform. Doctor profiles represent clinicians who deliver care and services and are central to appointment scheduling, clinical documentation, and care delivery workflows.
+
+Doctor records store personal details, professional credentials, clinic associations, and availability information required for operational and clinical coordination.
+
+Read more : ([API Reference - Doctor](/api-reference/doc-tool/doctor-and-clinic-api/getting-started)) section. 
+
+---
+
+## Use Cases
+
+### Doctor Onboarding and Management
+Create and manage doctor profiles during onboarding, credentialing, or administrative setup.
+
+### Appointment Scheduling
+Link doctors to appointment slots, calendars, and patient bookings across clinics or facilities.
+
+### Clinic and Facility Association
+Associate doctors with one or more clinics, departments, or hospital locations.
+
+### Clinical Documentation Ownership
+Attribute prescriptions, clinical notes, assessments, and encounters to the correct doctor.
+
+### Availability and Roster Management
+Manage working hours, leave schedules, and consultation availability for accurate booking.
+
+### Reporting and Performance Insights
+Enable analytics on consultations, patient load, and operational performance.
+
+---
+
+## Notes & Considerations
+
+- **Credential accuracy**  
+  Ensure qualifications, registrations, and specialties are kept current and verified.
+
+- **Multi-clinic support**  
+  Doctors may be associated with multiple clinics or facilities with different schedules.
+
+- **Availability consistency**  
+  Changes to schedules should be reflected across all booking and scheduling systems.
+
+- **Access control**  
+  Doctor profiles may be tied to role-based permissions within clinical systems.
+
+- **Auditability**  
+  Updates to doctor records should be traceable for administrative and compliance purposes.
+
+---
+
+## Ideal For
+
+- Clinics and hospitals  
+- Practice management systems  
+- Telemedicine platforms  
+- Multi-location healthcare networks  
+
+Read more : ([API Reference - Doctor](/api-reference/doc-tool/doctor-and-clinic-api/getting-started)) section. z
\ No newline at end of file
diff --git a/integrations/core-emr/patients.mdx b/integrations/core-emr/patients.mdx
new file mode 100644
index 00000000..e9fc4844
--- /dev/null
+++ b/integrations/core-emr/patients.mdx
@@ -0,0 +1,64 @@
+---
+title: Patient
+description: Patient profiles and demographic records within Core EMR
+---
+
+## Patient
+
+A **Patient** is an individual who receives medical care and services within the healthcare system. Patient profiles act as the central record for storing and managing personal, demographic, and clinical information across all care interactions.
+
+Patient data forms the foundation for appointments, clinical documentation, prescriptions, billing, and longitudinal care tracking within the **Core EMR**.
+
+Read more : ([API Reference - Patients](/api-reference/doc-tool/patient-registration-api/getting-started)) section. 
+
+---
+
+## Use Cases
+
+### Patient Registration and Onboarding
+Create and manage patient profiles during walk-in registration, online booking, or digital onboarding flows.
+
+### Longitudinal Health Records
+Maintain a unified patient record that aggregates visits, diagnoses, prescriptions, lab results, and clinical notes over time.
+
+### Appointment and Visit Management
+Link patient profiles to appointments, encounters, and care episodes for seamless operational workflows.
+
+### Clinical Documentation
+Associate patient records with clinical notes, assessments, prescriptions, and diagnostic reports.
+
+### Care Continuity Across Facilities
+Enable consistent patient identification and data access across departments, clinics, or hospital locations.
+
+### Reporting and Analytics
+Support population-level insights, patient demographics analysis, and operational reporting.
+
+---
+
+## Notes & Considerations
+
+- **Single source of truth**  
+  Patient profiles should be the authoritative reference for all clinical and operational workflows.
+
+- **Data accuracy**  
+  Ensure demographic and contact information is kept up to date to avoid downstream errors.
+
+- **Privacy and consent**  
+  Patient data must be handled in compliance with applicable data protection and healthcare regulations.
+
+- **Identity management**  
+  Deduplication and verification processes are important to prevent multiple records for the same individual.
+
+- **Extensible records**  
+  Patient profiles can be enriched over time with additional clinical, administrative, and contextual data.
+
+---
+
+## Ideal For
+
+- Clinics and hospitals  
+- EMR and HMS platforms  
+- Digital health applications  
+- Care coordination systems  
+
+Read more : ([API Reference - Patients](/api-reference/doc-tool/patient-registration-api/getting-started)) section. 
\ No newline at end of file
diff --git a/integrations/core-emr/payments.mdx b/integrations/core-emr/payments.mdx
new file mode 100644
index 00000000..ded632fe
--- /dev/null
+++ b/integrations/core-emr/payments.mdx
@@ -0,0 +1,67 @@
+---
+title: Payments
+description: Financial transactions for patient services within Core EMR
+---
+
+## Payments & Transactions
+
+A **Payment** (or **Transaction**) represents a financial record created when a patient pays for a healthcare service. Payment records capture essential financial details required for billing, reconciliation, and reporting within the **Core EMR**.
+
+Each payment includes information such as the **amount**, **payment method**, **receipt ID**, and the **current payment status**.
+
+Read more : ([API Reference - Payments](/api-reference/doc-tool/payment-api/get-transaction-status)) section. 
+
+---
+
+## Use Cases
+
+### Patient Billing and Checkout
+Record patient payments at the time of consultation, procedures, diagnostics, or other services directly within the EMR workflow.
+
+### Multi-Mode Payment Tracking
+Support and track different payment methods such as cash, card, UPI, wallets, or bank transfers under a unified transaction model.
+
+### Receipt Generation and Reconciliation
+Generate receipt IDs and maintain transaction records to support accounting, audits, and financial reconciliation.
+
+### Partial and Split Payments
+Handle scenarios where payments are made in parts or across multiple payment methods for a single visit or invoice.
+
+### Refunds and Adjustments
+Track refunded, reversed, or adjusted payments while maintaining a complete financial audit trail.
+
+### Reporting and Financial Analytics
+Enable revenue tracking, daily collections, payment status summaries, and clinic-level financial reporting.
+
+### Integration with Practice Management Systems
+Integrate payment records with billing, invoicing, and accounting systems used by hospitals and clinics.
+
+---
+
+## Notes & Considerations
+
+- **Status-driven lifecycle**  
+  Payments typically move through states such as initiated, completed, failed, or refunded.
+
+- **Service linkage**  
+  Payments should be associated with visits, appointments, procedures, or invoices for accurate financial mapping.
+
+- **Auditability**  
+  All updates to payment records should be traceable to support audits and compliance.
+
+- **Gateway-agnostic**  
+  Core EMR records payment outcomes while actual processing may be handled by external payment gateways.
+
+- **Operational validation**  
+  Clinics should verify completed payments before closing encounters or issuing final documents.
+
+---
+
+## Ideal For
+
+- Clinics and hospitals  
+- Practice management systems  
+- Diagnostic centers  
+- Multi-location healthcare networks  
+
+Read more : ([API Reference - Payments](/api-reference/doc-tool/payment-api/get-transaction-status)) section. 
\ No newline at end of file
diff --git a/integrations/core-emr/prescription.mdx b/integrations/core-emr/prescription.mdx
new file mode 100644
index 00000000..c94e4d45
--- /dev/null
+++ b/integrations/core-emr/prescription.mdx
@@ -0,0 +1,65 @@
+---
+title: Prescription
+description: Medical prescriptions and treatment instructions within Core EMR
+---
+
+## Prescription
+
+A **Prescription** is a medical document issued by a **doctor** to a **patient** that outlines prescribed medications, dosage instructions, and other treatment recommendations. Prescriptions are a core clinical artifact used to guide medication usage and ongoing care.
+
+Within **Core EMR**, prescriptions are structured records that can be created, stored, shared, and referenced across clinical workflows.
+
+Read more : ([API Reference - Prescription](/api-reference/doc-tool/prescription-api/get-prescription-details)) section. 
+
+---
+
+## Use Cases
+
+### Clinical Prescribing
+Create and manage prescriptions during consultations for acute or chronic conditions.
+
+### Medication History Tracking
+Maintain a longitudinal record of prescribed medications across visits and providers.
+
+### Digital Prescription Sharing
+Generate digital prescriptions that can be shared with patients, pharmacies, or downstream systems.
+
+### Follow-Up and Continuity of Care
+Reference past prescriptions during follow-up visits to assess adherence and treatment outcomes.
+
+### Pharmacy and Fulfillment Integration
+Integrate prescription data with pharmacy systems for dispensing and fulfillment workflows.
+
+### Audit and Compliance
+Maintain prescription records for regulatory compliance, audits, and medico-legal requirements.
+
+---
+
+## Notes & Considerations
+
+- **Doctor authorization**  
+  Prescriptions must be issued by authorized medical professionals.
+
+- **Structured medication data**  
+  Use standardized drug names and dosage formats to avoid ambiguity.
+
+- **Patient safety**  
+  Prescriptions should be reviewed for contraindications, allergies, and interactions where applicable.
+
+- **Amendments and cancellations**  
+  Changes to prescriptions should be versioned or tracked for clarity and auditability.
+
+- **Clinical verification required**  
+  Prescriptions are part of clinical decision-making and must be validated by clinicians.
+
+---
+
+## Ideal For
+
+- Clinics and hospitals  
+- EMR and HMS platforms  
+- Telemedicine providers  
+- Pharmacy and medication management systems  
+
+
+Read more : ([API Reference - Prescription](/api-reference/doc-tool/prescription-api/get-prescription-details)) section. 
\ No newline at end of file
diff --git a/integrations/general-tools/medical-db.mdx b/integrations/general-tools/medical-db.mdx
new file mode 100644
index 00000000..14464643
--- /dev/null
+++ b/integrations/general-tools/medical-db.mdx
@@ -0,0 +1,49 @@
+---
+title: Medical DB
+description: Standardized medical reference database for structured clinical knowledge
+---
+
+## Medical DB
+
+The Medical DB is a standardized medical reference database that provides structured clinical knowledge, including drugs, laboratory tests, symptoms, and diagnosis information. This data enables reliable medical lookups to support prescription creation, clinical decision support, and health record enrichment.
+
+Read more : ([API Reference - Medical DB](/api-reference/medical-db/drugs-and-labs)) section. 
+
+---
+
+## Coverage
+
+The database includes structured information for:
+
+- Drugs  
+- Laboratory tests  
+- Symptoms  
+- Diagnoses  
+
+---
+
+## Use Cases
+
+- Prescription creation and validation  
+- Clinical decision support  
+- Health record enrichment and normalization  
+- Grounding LLM outputs in trusted medical data  
+
+---
+
+## Key Characteristics
+
+- Structured and standardized clinical data  
+- Reliable reference-grade medical information  
+- Optimized for AI and LLM consumption  
+- Informational only; does not replace clinical judgment  
+
+---
+
+## Scope & Limitations
+
+- Reference database only  
+- Not intended to provide medical advice  
+- Clinical verification required for critical decisions  
+
+Read more : ([API Reference - Medical DB](/api-reference/medical-db/drugs-and-labs)) section. 
\ No newline at end of file
diff --git a/integrations/general-tools/medical-document-parsing.mdx b/integrations/general-tools/medical-document-parsing.mdx
new file mode 100644
index 00000000..acaae11e
--- /dev/null
+++ b/integrations/general-tools/medical-document-parsing.mdx
@@ -0,0 +1,70 @@
+---
+title: Medical Document Parsing
+description: Extract structured clinical data from lab report documents
+---
+
+## Medical Document Parsing
+
+The **Medical Document Parsing API** allows you to upload lab report documents (PDF or image formats) and extract **structured clinical data** from unstructured files. It converts scanned or digital lab reports into machine-readable formats suitable for downstream clinical and analytical workflows.
+
+Read more : ([API Reference - Medical Document Parsing](/eka-medai/technologies/overview)) section. 
+
+---
+
+## What It Extracts
+
+Parsed results include:
+
+- Lab test names  
+- Measured values  
+- Units of measurement  
+- Normal reference ranges  
+- Associated clinical metadata  
+
+The output is available in:
+- **FHIR format**
+- **Enhanced JSON format**
+
+---
+
+## Use Cases
+
+- Digitizing scanned lab reports  
+- Enriching patient health records  
+- Enabling search and analytics on lab data  
+- Powering clinical workflows and decision support systems  
+
+---
+
+## How It Works
+
+1. **Upload Report**  
+   Upload a scanned lab report (PDF or image).  
+   You receive a `document_id` for the uploaded file.
+
+2. **Retrieve Parsed Report**  
+   Use the `document_id` to fetch structured results in:
+   - FHIR format, or
+   - Enhanced JSON format
+
+3. **Delete Report**  
+   Remove the uploaded document using its `document_id`.
+
+---
+
+## Key Characteristics
+
+- Supports both PDF and image-based lab reports  
+- Produces structured, machine-readable clinical data  
+- Designed for integration into clinical systems and AI workflows  
+- Informational extraction only; no clinical interpretation
+
+---
+
+## Scope & Limitations
+
+- Focused on laboratory report parsing  
+- Accuracy depends on document quality and scan clarity  
+- Parsed data should be clinically verified before use  
+
+Read more : ([API Reference - Medical Document Parsing](/eka-medai/technologies/overview)) section. 
\ No newline at end of file
diff --git a/integrations/health-ai/assessments.mdx b/integrations/health-ai/assessments.mdx
new file mode 100644
index 00000000..58d91848
--- /dev/null
+++ b/integrations/health-ai/assessments.mdx
@@ -0,0 +1,83 @@
+---
+title: Assessments
+description: Structured capture of patient-reported health data across care journeys
+---
+
+## Assessment Platform APIs
+
+The **Assessment Platform APIs** enable structured, standardized capture of **patient-reported health data** to support patient-facing, clinical, and enterprise workflows.
+
+Using configurable assessment flows and questionnaires, teams can integrate assessments at multiple touchpoints across the care journey while ensuring consistent data models for downstream systems, analytics, and decision support.
+
+Read more : ([API Reference - Assessments](/api-reference/health-ai/assessment/overview)) section. 
+
+---
+
+## Patient-Facing Use Cases
+
+### Symptom Assessment
+Guide patients through adaptive questionnaires to capture symptoms in a structured format for triage, clinician review, and decision support workflows.
+
+### General Health Assessment
+Collect baseline health, lifestyle, and habit data in a consistent schema to support longitudinal tracking and personalized experiences.
+
+### Patient Onboarding
+Embed structured health intake and medical history assessments into onboarding or signup flows, ensuring consistent data capture across systems.
+
+### Pre-Consultation Data Collection
+Capture structured patient information before a visit to help clinicians prepare in advance and reduce consultation time.
+
+### Follow-Up and Post-Care Assessments
+Trigger assessments after consultations, procedures, or discharge to collect recovery status, side effects, and outcome data.
+
+### Preventive Care and Wellness Programs
+Run periodic assessments to collect lifestyle and wellness data that can power reminders, nudges, and long-term health programs.
+
+---
+
+## Clinical Use Cases
+
+### Health Risk Screening
+Run standardized screening assessments to identify potential health risks and generate structured risk indicators for alerts, flags, or preventive care workflows.
+
+### Teleconsultation Support
+Integrate assessments into teleconsultation flows to ensure clinicians receive complete, structured patient inputs before or during virtual visits.
+
+### Chronic Condition Monitoring
+Run recurring assessments for chronic conditions to track symptom progression, adherence, and patient-reported outcomes over time.
+
+### Clinical Research and Data Collection
+Standardize patient-reported data collection for studies and pilots, enabling clean datasets for clinical analysis and reporting.
+
+---
+
+## Enterprise Use Cases
+
+### Backend Integration APIs and SDKs
+Integrate assessments directly into EMRs and enterprise systems with full control over assessment logic, UI, and data handling across the complete lifecycle.
+
+### Quick Web Integration (Web SDK)
+Launch assessments using ready-to-use UI components to reduce development effort while delivering structured responses to backend systems via APIs.
+
+### Population Health and Analytics
+Aggregate structured assessment responses across cohorts to support population-level insights, risk stratification, and reporting dashboards.
+
+---
+
+## Key Characteristics
+
+- Structured and standardized data models  
+- Configurable assessment flows and questionnaires  
+- Suitable for patient-facing, clinical, and enterprise use cases  
+- Designed for analytics, decision support, and interoperability  
+
+---
+
+## Scope & Limitations
+
+- Informational and data-capture focused  
+- Not a substitute for clinical judgment  
+- Validation required before clinical decision-making  
+
+
+Read more : ([API Reference - Assessments](/api-reference/health-ai/assessment/overview)) section. 
\ No newline at end of file
diff --git a/integrations/health-ai/ekascribe.mdx b/integrations/health-ai/ekascribe.mdx
new file mode 100644
index 00000000..2371a2bf
--- /dev/null
+++ b/integrations/health-ai/ekascribe.mdx
@@ -0,0 +1,77 @@
+---
+title: EkaScribe 
+description: Clinical and enterprise use cases for medical-grade speech-to-documentation APIs
+---
+
+## EkaScribe Use Cases
+
+**EkaScribe APIs** enable healthcare platforms, EMRs, and hospital systems to convert clinical audio into **accurate, structured medical documentation** using medical-grade speech recognition.
+
+With support for **multiple languages**, **specialty-aware templates**, and **flexible integration models**, EkaScribe fits seamlessly into both **real-time** and **asynchronous** clinical workflows.
+
+The following use cases highlight how EkaScribe can be leveraged across healthcare organizations and digital health platforms.
+
+Read more : ([API Reference - Ekascribe](/api-reference/health-ai/ekascribe/overview)) section. 
+
+---
+
+## Clinical Documentation Automation
+
+Automatically convert doctor–patient conversations into structured clinical notes, reducing manual documentation effort and improving clinician productivity across outpatient and inpatient settings.
+
+---
+
+## EMR and EHR Documentation
+
+Generate EMR-ready medical notes in predefined templates and formats that integrate directly into electronic medical record systems used by hospitals and clinics.
+
+---
+
+## Hospital and Clinic Chain Enablement
+
+Standardize documentation workflows across large hospital networks and clinic chains using consistent transcription models, templates, and output schemas.
+
+---
+
+## Specialty-Based Medical Notes
+
+Produce structured notes aligned with specific medical specialties by providing contextual information during transcription, improving accuracy and relevance of outputs.
+
+---
+
+## Multilingual Consultation Transcription
+
+Support consultations in multiple regional and international languages, enabling clinicians to document encounters naturally while maintaining standardized medical records.
+
+---
+
+## Teleconsultation and Virtual Care Support
+
+Integrate real-time or recorded transcription into telemedicine platforms to capture complete consultation records during virtual visits.
+
+---
+
+## Audio Dictation for Clinicians
+
+Enable voice-first documentation by allowing clinicians to dictate notes, observations, or summaries that are automatically converted into structured medical records.
+
+---
+
+## Post-Consultation Summaries and Reports
+
+Generate consultation summaries that can be reviewed by clinicians, shared with patients, or stored for follow-up and continuity of care.
+
+---
+
+## Scalable Transcription Pipelines
+
+Process large volumes of clinical audio using batch uploads, job tracking, and webhooks to support enterprise-scale documentation workflows.
+
+---
+
+## Healthcare Analytics and Compliance
+
+Leverage structured transcription outputs for reporting, audit trails, quality reviews, and compliance workflows across healthcare organizations.
+
+
+Read more : ([API Reference - Ekascribe](/api-reference/health-ai/ekascribe/overview)) section. 
\ No newline at end of file
diff --git a/integrations/health-ai/medassist.mdx b/integrations/health-ai/medassist.mdx
new file mode 100644
index 00000000..d0a7ff23
--- /dev/null
+++ b/integrations/health-ai/medassist.mdx
@@ -0,0 +1,97 @@
+---
+title: MedAssist
+description: Agentic medical assistant for real-time medical conversations using medical LLMs
+---
+
+## MedAssist Agent
+
+**MedAssist** is a medical assistant agentic capability that enables users to communicate with Eka’s state-of-the-art **medical LLM** for medical concerns and healthcare guidance.
+
+It supports real-time, multi-modal interactions and is designed for integration into consumer apps, clinical platforms, and enterprise healthcare systems.
+
+Read more : ([API Reference - Medassist](/api-reference/health-ai/medassist/overview)) section. 
+
+---
+
+## How It Works
+
+MedAssist operates using a **session-based architecture**:
+
+1. **Session Creation**  
+   Create a new session using your API key.
+
+2. **WebSocket Connection**  
+   Connect to the session via WebSocket to enable real-time, bidirectional communication.
+
+3. **Multi-Format Communication**  
+   Send and receive messages in multiple formats during an active session.
+
+---
+
+## Supported Content Types
+
+- **Text Messages**  
+  Direct text-based medical queries and follow-up questions.
+
+- **Audio Messages**  
+  Voice recordings for conversational medical interactions.
+
+- **File Uploads**  
+  Medical documents, images, lab reports, or clinical files for contextual understanding.
+
+---
+
+## Use Cases
+
+### Patient Medical Guidance
+Enable patients to ask medical questions and receive contextual, reference-backed responses for general healthcare guidance and next steps.
+
+### Symptom Exploration and Triage
+Guide users through symptom discussions to help structure inputs for triage, escalation, or clinician follow-up workflows.
+
+### Pre-Consultation Support
+Collect and structure patient concerns before a clinical visit, helping clinicians start consultations with better context.
+
+### Post-Consultation Clarifications
+Allow patients to ask follow-up questions after a visit to better understand instructions, medications, or care plans.
+
+### Medical Document Contextualization
+Use uploaded lab reports or medical documents to provide explanations and contextual insights in natural language.
+
+### Multimodal Conversational Interfaces
+Power chat- and voice-based medical assistants in mobile apps, web portals, or kiosks using a single agent interface.
+
+### Telehealth and Virtual Care Assistants
+Embed MedAssist into teleconsultation platforms to support patients before, during, or after virtual visits.
+
+---
+
+## Notes & Considerations
+
+- **Informational only**  
+  MedAssist provides medical information and guidance but does not replace professional medical advice.
+
+- **Session-scoped context**  
+  Conversation context is maintained within a session and should be persisted externally if needed.
+
+- **Verification recommended**  
+  Outputs should be reviewed by healthcare professionals before being used in clinical decision-making.
+
+- **Privacy and compliance**  
+  Ensure proper handling of patient data and compliance with applicable healthcare regulations.
+
+- **Network requirements**  
+  Real-time communication requires stable WebSocket connectivity.
+
+---
+
+## Ideal For
+
+- Consumer health apps  
+- Telemedicine platforms  
+- Hospital patient portals  
+- Digital health assistants  
+- Enterprise healthcare workflows  
+
+
+Read more : ([API Reference - Medassist](/api-reference/health-ai/medassist/overview)) section. 
\ No newline at end of file
diff --git a/integrations/interoperability/abdm.mdx b/integrations/interoperability/abdm.mdx
new file mode 100644
index 00000000..4f0420a1
--- /dev/null
+++ b/integrations/interoperability/abdm.mdx
@@ -0,0 +1,14 @@
+---
+title: ABDM
+description: Plug-and-play APIs to integrate healthcare systems with India's ABDM ecosystem
+---
+
+## ABDM Connect
+
+**Ayushman Bharat Digital Mission (ABDM)** is India's national digital health infrastructure. It creates a shared ecosystem where patients, hospitals, labs, insurers, and health apps can exchange health data securely, with patient consent driving every transaction.
+
+EKA's **ABDM Connect** is a plug-and-play API and SDK suite that handles the ABDM gateway complexity for you, covering ABHA creation, care context linking, consent management, and health record exchange across HIPs, HIUs, and PHR apps.
+
+<Card title="ABDM Connect Overview" icon="arrow-right" href="/api-reference/user-app/abdm-connect/overview">
+  Dive into the full ABDM Connect documentation, ecosystem roles, certification milestones , PHR app integration, and API references.
+</Card>
\ No newline at end of file
diff --git a/integrations/mcp/MCP-for-Indian-treatment-protocol-search.mdx b/integrations/mcp/MCP-for-Indian-treatment-protocol-search.mdx
new file mode 100644
index 00000000..d9b3e641
--- /dev/null
+++ b/integrations/mcp/MCP-for-Indian-treatment-protocol-search.mdx
@@ -0,0 +1,120 @@
+---
+title: MCP for Indian treatment protocol searchs
+description: India-specific drug, protocol, and pharmacology intelligence APIs
+---
+
+Read more : ([API Reference - MCP for Indian treatment protocol searchs](/SDKs/EkaCare-MCP)) section.
+
+
+## Core Functionality
+
+### 1. Indian Branded Drug Search
+
+Search over **500,000+ branded drugs** available in the Indian market.
+
+**Features**
+- Filter by:
+  - Drug name  
+  - Generic composition  
+  - Dosage form  
+  - Volume / strength
+- Supports **compound generics**  
+  - Example: `Glimepiride, Metformin`
+
+**Returns**
+- Drug name  
+- Generic name  
+- Manufacturer  
+- Product type  
+
+---
+
+### 2. Indian Treatment Protocol Search
+
+Access **180+ treatment protocols** from authoritative Indian healthcare bodies.
+
+**Coverage**
+- **175 medical conditions / tags**
+- Sources include:
+  - ICMR  
+  - RSSDI  
+  - NPCDCS  
+  - and other Indian guideline publishers
+
+**Workflow**
+1. Fetch supported tags / medical conditions  
+2. Get available publishers for a selected tag  
+3. Search protocols using:
+   - Tag  
+   - Publisher  
+   - Free-text query  
+
+**Technology**
+- Semantic search powered by **AWS Bedrock**
+
+---
+
+### 3. Indian Pharmacology Details
+
+Pharmacology information grounded in the **National Formulary of India (2011)**.
+
+**Capabilities**
+- Retrieve pharmacology details for **generic compositions**
+- Supports **compound drug searches**  
+  - Example: `Rifampicin + Isoniazid`
+
+---
+
+### 4. Protocol Publishers
+
+Dynamic discovery of supported publishers per medical condition.
+
+**Examples**
+- ICMR  
+- RSSDI  
+- NPCDCS  
+- Additional national and program-specific bodies  
+
+---
+
+## Key Capabilities
+
+- **LLM-optimized**
+  - Strict tool prompts guide LLMs on when and how to invoke APIs
+- **Intent confirmation**
+  - Explicit condition confirmation required before protocol search
+- **Hallucination reduction**
+  - Responses grounded in curated medical databases, not model inference
+- **India-specific**
+  - Tailored to Indian drug markets and healthcare workflows
+
+---
+
+## Limits
+
+- **Python version**
+  - Requires **Python ≥ 3.11**
+- **API credentials required**
+  - Obtain `client-id` and `client-secret` via  
+    `ekaconnect@eka.care`
+- **India-focused**
+  - Drug database and protocols are specific to Indian healthcare
+- **Protocol coverage**
+  - 175 conditions currently supported (coverage is expanding)
+- **No medical advice**
+  - Informational only; professionals must verify before clinical use
+
+---
+
+## Dependencies
+
+**Public Package:** `eka_mcp_server`
+
+```bash
+mcp[all]>=1.3.0
+httpx>=0.28.1
+pyjwt>=2.10.0
+pillow>=11.0.0
+```
+---
+Read more : ([API Reference - MCP for Indian treatment protocol searchs](/SDKs/EkaCare-MCP)) section.
diff --git a/integrations/mcp/mcp-for-emr.mdx b/integrations/mcp/mcp-for-emr.mdx
new file mode 100644
index 00000000..eb091cc5
--- /dev/null
+++ b/integrations/mcp/mcp-for-emr.mdx
@@ -0,0 +1,83 @@
+---
+title: MCP for EMR
+description: Self-hosted MCP server bridging Eka.care APIs with LLM applications
+---
+
+## Core Functionality
+
+A **self-hosted Model Context Protocol (MCP) server** that bridges **Eka.care healthcare APIs** with LLM-powered applications, enabling AI assistants to securely interact with clinical and operational data.
+
+Read more : ([API Reference - MCP for EMR](/ai-tools/mcp-server/introduction)) section. 
+
+### Supported Capabilities
+
+AI assistants can:
+
+- **Manage appointments**
+  - Create, update, and retrieve patient appointments
+- **Access patient records**
+  - Search, create, retrieve, and update patients within a workspace
+- **Manage doctor and clinic data**
+  - Access doctor profiles and clinic information
+
+---
+
+### Coming Soon
+
+Planned extensions to expand clinical workflows:
+
+- **Handle prescriptions**
+  - Generate and manage digital prescriptions
+- **Get prescription history**
+  - Retrieve patient medication history
+- **Process assessments**
+  - Handle and analyze self-assessment data
+
+---
+
+## Key Capabilities
+
+- **Three usage modes**
+  - MCP server
+  - Direct async Python library
+  - Sync wrapper (CrewAI-compatible)
+- **Modular architecture**
+  - Easily extend with new Eka.care API modules
+- **Authentication**
+  - Client ID / Client Secret with JWT token management for local connections  
+  - OIDC flow for remote server deployments  
+  - Optional API key support
+- **LLM-optimized**
+  - Structured, predictable responses designed for AI consumption
+- **Error transparency**
+  - Eka.care API errors are forwarded directly for easier debugging
+
+---
+
+## Limits
+
+- **Python version**
+  - Requires **Python ≥ 3.10**
+- **Self-hosted only**
+  - Designed for organizational and controlled deployments
+- **API-dependent**
+  - All functionality requires valid **Eka.care API credentials**
+
+---
+
+## Dependencies
+
+Core dependencies required to run the MCP server:
+
+```bash
+FastMCP          # MCP protocol implementation (git main branch)
+httpx            # Async HTTP client for API calls
+pydantic         # Data validation and settings management
+PyJWT            # Authentication token handling
+py-key-value-aio # Redis-based async storage for auth tokens
+python-dotenv    # Environment configuration
+```
+
+---
+
+Read more : ([API Reference - MCP for EMR](/ai-tools/mcp-server/introduction)) section. 
\ No newline at end of file
diff --git a/introduction.mdx b/introduction.mdx
index e839345a..b45686f7 100644
--- a/introduction.mdx
+++ b/introduction.mdx
@@ -38,8 +38,9 @@ Choosing Eka Connect is a smart decision because of its strong focus on security
 
 **Obtain the Client ID and Client Secret**
 
-- Contact Eka’s support team to request your Client ID and Client Secret via Email.
-- Email - ekaconnect@eka.care
+- Login to your Eka Care Control Panel at [Console](https://console.eka.care) and create client_id and client_secret
+- If you are a developer and are looking to create an app for our doctors and patients you can either follow the end to end OIDC guidelines to connect Eka Accounts with yours, Or you can ask for API Key from your respective healthcare providers workspace to get access using API Key. [Hub](https://hub.eka.care/account/account/apitoken/)
+- For any issue or detailed info you can reach out to us at ekaconnect@eka.care
 
 #### **2. Authentication**
 
@@ -66,7 +67,7 @@ Access Tokens don’t last forever, they will eventually expire for security rea
 
 Once you’ve authenticated and successfully integrated with EKA Connect, you can access various services and features designed to support healthcare integration. Here’s what’s available:
 
-#### **1. ABDM Connect**([Reference](abdm-connect))
+#### **1. ABDM Connect**([Reference](/api-reference/user-app/abdm-connect/overview))
 Introducing the **ABDM Connector**: A Comprehensive API Suite for Easy Integration.
 
 The ABDM Connector is designed as a powerful, plug-and-play API suite that simplifies the integration of various healthcare solutions into the Ayushman Bharat Digital Mission (ABDM) ecosystem. Whether you're looking to connect Electronic Health Records (EHR), hospital management systems, or other healthcare platforms, this connector facilitates seamless interoperability.
diff --git a/mcp/authentication.mdx b/mcp/authentication.mdx
new file mode 100644
index 00000000..e96bcc69
--- /dev/null
+++ b/mcp/authentication.mdx
@@ -0,0 +1,200 @@
+---
+title: Authentication
+description: Securely connect your AI assistant to Eka.care
+---
+
+## Overview
+
+Eka.care MCP supports two authentication methods to fit different integration needs:
+
+<CardGroup cols={2}>
+  <Card title="🔐 OIDC Flow (Recommended)" icon="shield-check">
+    **Best for:** Healthcare providers and clinics
+    
+    Auto-authenticate with your Eka.care account. No manual credential management needed.
+  </Card>
+  <Card title="🔑 Client Credentials" icon="key">
+    **Best for:** Third-party integrations
+    
+    Use API credentials (Client ID, Secret, API Key) for programmatic access.
+  </Card>
+</CardGroup>
+
+---
+
+## Method 1: OIDC Flow (Auto-Authentication)
+
+This is the **easiest and most secure** method. Your AI assistant authenticates using your Eka.care login, just like logging into the dashboard.
+
+### How It Works
+
+<Steps>
+  <Step title="You start your MCP client">
+    Claude Desktop or any MCP-compatible client
+  </Step>
+  <Step title="MCP initiates OIDC flow">
+    Opens a secure browser window
+  </Step>
+  <Step title="You log in to Eka.care">
+    Use your existing Eka.care credentials
+  </Step>
+  <Step title="Connection established">
+    Your AI assistant now has secure access
+  </Step>
+</Steps>
+
+<Frame>
+  <img src="/images/OIDC.png" alt="OIDC Authentication Flow" />
+  {/* Screenshot placeholder: Diagram showing OIDC flow steps */}
+</Frame>
+
+## Method 2: Client Credentials
+
+Use this method if you have API credentials (Client ID, Client Secret, API Key) from the Eka.care team.
+
+### How It Works
+
+Your MCP server authenticates directly with Eka.care APIs using:
+- **Client ID**: Your application identifier
+- **Client Secret**: Secret key for authentication
+- **API Key**: to connect to a specefic workspace from your client_id / client_secret
+
+### Setup Client Credentials
+
+**1. Get your credentials:**
+
+Get your client id and client secret from Eka developer [console](https://console.eka.care/api-keys/)
+- Client ID
+- Client Secret
+
+If you are a standalone devleoper and wish to access workspaces of Eka Users you can either implement OIDC ( Oauth ) flow or get API Key from users workspace [Hub](https://hub.eka.care/account/account/apitoken/)
+- API Key
+
+
+For any issues you can contact **ekaconnect@eka.care** and request:
+
+**2. Configure your `.env` file:**
+
+```bash .env
+# API Configuration
+EKA_API_BASE_URL=https://api.eka.care
+
+# Client Credentials
+EKA_CLIENT_ID=your_client_id_here
+EKA_CLIENT_SECRET=your_client_secret_here
+EKA_API_KEY=your_api_key_here
+
+# Server Settings (optional)
+EKA_MCP_SERVER_HOST=localhost
+EKA_MCP_SERVER_PORT=8000
+EKA_LOG_LEVEL=INFO
+```
+
+<Warning>
+**Security Best Practices:**
+- Never commit credentials to version control
+- Use `.gitignore` to exclude `.env` file
+- Rotate credentials periodically
+- Use different credentials for development and production
+</Warning>
+
+**3. Update Claude Desktop config:**
+
+```json claude_desktop_config.json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "/full/path/to/.venv/bin/python",
+      "args": ["-m", "eka_mcp_sdk.server"],
+      "env": {
+        "EKA_CLIENT_ID": "your_client_id_here",
+        "EKA_CLIENT_SECRET": "your_client_secret_here",
+        "EKA_API_KEY": "your_api_key_here",
+        "EKA_API_BASE_URL": "https://api.eka.care"
+      }
+    }
+  }
+}
+```
+
+**4. Test your connection:**
+
+```bash
+# Start the MCP server
+eka-mcp-server
+```
+
+You should see:
+```
+INFO: Authentication successful
+INFO: MCP Server running on http://localhost:8000
+```
+
+### Credential Management Tips
+
+<AccordionGroup>
+  <Accordion title="How to test credentials">
+    **Quick test with curl:**
+    ```bash
+    curl -X POST https://api.eka.care/api/v1/auth/token \
+      -H "Content-Type: application/json" \
+      -H "X-API-KEY: your_api_key" \
+      -d '{
+        "client_id": "your_client_id",
+        "client_secret": "your_client_secret",
+        "grant_type": "client_credentials"
+      }'
+    ```
+    
+    Should return an access token if credentials are valid.
+  </Accordion>
+
+  <Accordion title="Token expiration">
+    **Automatic refresh:** The MCP server automatically refreshes tokens before they expire.
+    
+    **Default expiration:** Tokens typically last 1 hour and are refreshed automatically.
+    
+    **No action needed:** You don't need to manually manage token lifecycle.
+  </Accordion>
+
+  <Accordion title="Multiple environments">
+    **Development:**
+    ```bash .env.development
+    EKA_CLIENT_ID=dev_client_id
+    EKA_CLIENT_SECRET=dev_client_secret
+    EKA_API_KEY=dev_api_key
+    EKA_API_BASE_URL=https://api-dev.eka.care
+    ```
+    
+    **Production:**
+    ```bash .env.production
+    EKA_CLIENT_ID=prod_client_id
+    EKA_CLIENT_SECRET=prod_client_secret
+    EKA_API_KEY=prod_api_key
+    EKA_API_BASE_URL=https://api.eka.care
+    ```
+  </Accordion>
+
+  <Accordion title="Credential rotation">
+    **When to rotate:**
+    - Every 90 days (recommended)
+    - If credentials may be compromised
+    - When team members leave
+    
+    **How to rotate:**
+    1. Contact ekaconnect@eka.care for new credentials
+    2. Update your `.env` file
+    3. Restart the MCP server
+    4. Update Claude Desktop config if needed
+  </Accordion>
+</AccordionGroup>
+
+---
+
+<Note>
+**Need Credentials?** Contact **ekaconnect@eka.care** with:
+- Your organization name
+- Integration type (OIDC or Client Credentials)
+- Use case description
+- Expected API usage volume
+</Note>
diff --git a/mcp/integrations/custom-client.mdx b/mcp/integrations/custom-client.mdx
new file mode 100644
index 00000000..ded20322
--- /dev/null
+++ b/mcp/integrations/custom-client.mdx
@@ -0,0 +1,245 @@
+---
+title: Custom MCP Client
+description: Integrate Eka.care MCP into your own application
+---
+
+## Overview
+
+Want to build your own AI-powered healthcare application? You can integrate Eka.care MCP into any application that supports the Model Context Protocol standard.
+
+<CardGroup cols={2}>
+  <Card title="📱 Build AI Health Apps" icon="mobile">
+    Create custom healthcare assistants
+  </Card>
+  <Card title="🤖 Automation Tools" icon="robot">
+    Automate clinic workflows
+  </Card>
+  <Card title="🔧 Internal Tools" icon="wrench">
+    Custom admin dashboards
+  </Card>
+  <Card title="🌐 Web Services" icon="globe">
+    API-powered AI services
+  </Card>
+</CardGroup>
+
+---
+
+## Quick Integration
+
+### Using the MCP SDK
+
+The easiest way is to use the official MCP SDK in your preferred language:
+
+<Tabs>
+  <Tab title="Python">
+    ```python
+    from mcp import ClientSession, StdioServerParameters
+    from mcp.client.stdio import stdio_client
+
+    # Create MCP client connection
+    server_params = StdioServerParameters(
+        command="/path/to/.venv/bin/python",
+        args=["-m", "eka_mcp_sdk.server"],
+        env={
+            "EKA_CLIENT_ID": "your_client_id",
+            "EKA_CLIENT_SECRET": "your_client_secret",
+            "EKA_API_KEY": "your_api_key"
+        }
+    )
+
+    async with stdio_client(server_params) as (read, write):
+        async with ClientSession(read, write) as session:
+            # Initialize connection
+            await session.initialize()
+            
+            # List available tools
+            tools = await session.list_tools()
+            print(f"Available tools: {[t.name for t in tools]}")
+            
+            # Call a tool
+            result = await session.call_tool(
+                "search_patients",
+                arguments={"prefix": "Kumar"}
+            )
+            print(result)
+    ```
+  </Tab>
+  
+  <Tab title="TypeScript">
+    ```typescript
+    import { Client } from "@modelcontextprotocol/sdk/client/index.js";
+    import { StdioClientTransport } from "@modelcontextprotocol/sdk/client/stdio.js";
+
+    const transport = new StdioClientTransport({
+      command: "/path/to/.venv/bin/python",
+      args: ["-m", "eka_mcp_sdk.server"],
+      env: {
+        EKA_CLIENT_ID: "your_client_id",
+        EKA_CLIENT_SECRET: "your_client_secret",
+        EKA_API_KEY: "your_api_key"
+      }
+    });
+
+    const client = new Client({
+      name: "my-healthcare-app",
+      version: "1.0.0"
+    }, {
+      capabilities: {}
+    });
+
+    await client.connect(transport);
+
+    // List available tools
+    const tools = await client.listTools();
+    console.log("Available tools:", tools.tools.map(t => t.name));
+
+    // Call a tool
+    const result = await client.callTool({
+      name: "search_patients",
+      arguments: { prefix: "Kumar" }
+    });
+    console.log(result);
+    ```
+  </Tab>
+  
+  <Tab title="Go">
+    ```go
+    package main
+
+    import (
+        "context"
+        "fmt"
+        "github.com/modelcontextprotocol/sdk-go/client"
+    )
+
+    func main() {
+        // Create MCP client
+        c := client.NewStdioClient(
+            "/path/to/.venv/bin/python",
+            []string{"-m", "eka_mcp_sdk.server"},
+            map[string]string{
+                "EKA_CLIENT_ID":     "your_client_id",
+                "EKA_CLIENT_SECRET": "your_client_secret",
+                "EKA_API_KEY":       "your_api_key",
+            },
+        )
+
+        // Connect
+        ctx := context.Background()
+        if err := c.Connect(ctx); err != nil {
+            panic(err)
+        }
+        defer c.Close()
+
+        // List tools
+        tools, err := c.ListTools(ctx)
+        if err != nil {
+            panic(err)
+        }
+        fmt.Printf("Available tools: %+v\n", tools)
+
+        // Call a tool
+        result, err := c.CallTool(ctx, "search_patients", map[string]interface{}{
+            "prefix": "Kumar",
+        })
+        if err != nil {
+            panic(err)
+        }
+        fmt.Printf("Result: %+v\n", result)
+    }
+    ```
+  </Tab>
+</Tabs>
+
+---
+
+## HTTP Integration
+
+Prefer REST APIs? Deploy the MCP server with HTTP transport:
+
+### Setup HTTP Server
+
+```python server.py
+from fastmcp import FastMCP
+from eka_mcp_sdk.tools.patient_tools import register_patient_tools
+from eka_mcp_sdk.tools.appointment_tools import register_appointment_tools
+
+# Create FastMCP instance
+mcp = FastMCP("Eka.care MCP")
+
+# Register tools
+register_patient_tools(mcp)
+register_appointment_tools(mcp)
+
+# Run with HTTP transport
+if __name__ == "__main__":
+    import uvicorn
+    uvicorn.run(mcp.get_asgi_app(), host="0.0.0.0", port=8000)
+```
+
+### Call via HTTP
+
+```bash
+# List available tools
+curl http://localhost:8000/tools
+
+# Call a tool
+curl -X POST http://localhost:8000/call_tool \
+  -H "Content-Type: application/json" \
+  -d '{
+    "name": "search_patients",
+    "arguments": {"prefix": "Kumar"}
+  }'
+```
+
+---
+
+## Docker Deployment
+
+Deploy as a containerized service:
+
+```dockerfile Dockerfile
+FROM python:3.11-slim
+
+WORKDIR /app
+
+# Install dependencies
+COPY requirements.txt .
+RUN pip install -r requirements.txt
+
+# Copy MCP server code
+COPY . .
+
+# Install package
+RUN pip install -e .
+
+# Expose port
+EXPOSE 8000
+
+# Run server
+CMD ["python", "-m", "eka_mcp_sdk.server"]
+```
+
+```yaml docker-compose.yml
+version: '3.8'
+
+services:
+  eka-mcp:
+    build: .
+    ports:
+      - "8000:8000"
+    environment:
+      - EKA_CLIENT_ID=${EKA_CLIENT_ID}
+      - EKA_CLIENT_SECRET=${EKA_CLIENT_SECRET}
+      - EKA_API_KEY=${EKA_API_KEY}
+      - EKA_API_BASE_URL=https://api.eka.care
+    restart: unless-stopped
+```
+
+---
+
+<Note>
+**Building Something Cool?** We'd love to hear about it!
+- Email us: ekaconnect@eka.care
+- Get featured in our showcase!
+</Note>
diff --git a/mcp/introduction.mdx b/mcp/introduction.mdx
new file mode 100644
index 00000000..20f853b4
--- /dev/null
+++ b/mcp/introduction.mdx
@@ -0,0 +1,382 @@
+---
+title: Eka MCP Server
+description: Connect your AI assistant to Eka.care's healthcare platform
+---
+
+<Frame>
+  <img src="/images/eka-remote-mcp.png" alt="MCP Overview" />
+  {/* Screenshot placeholder: Show diagram of AI Assistant <-> MCP <-> Eka.care APIs */}
+</Frame>
+
+**Model Context Protocol (MCP)** is an open standard that lets AI assistants like Claude connect directly to your applications and data securely. Think of it as a universal adapter that helps AI understand and work with your healthcare systems.
+
+Eka's MCP server follows the authenticated remote [MCP spec](https://modelcontextprotocol.io/specification/2025-03-26), so the server is centrally hosted and managed. Instead of copying and pasting patient data or manually creating appointments, your AI assistant can handle appointment booking, prescription creation, and patient lookups automatically with built in Authentication and HIPAA-compliant data handling.
+
+
+## Setup Instructions
+
+### General
+
+Eka's MCP server is currently supporting Streamable HTTP transport. It uses OAuth 2.0 with OpenID Connect (OIDC) flow for dynamic client registration for authentication at the following address:
+
+- HTTP : `https://mcp.eka.care/mcp`
+
+For setup instructions on specific clients, continue reading .. 
+
+
+<AccordionGroup>
+  <Accordion title="VS Code (macOS)" icon="apple">
+    
+**Requirements:** VS Code 1.95+ with GitHub Copilot
+
+1. Press `Cmd + Shift + P`
+2. Type and select **MCP: Add Server**
+3. Choose **HTTP** *(HTTP or Server-Sent Events)*
+4. Enter URL: `https://mcp.eka.care/mcp`
+5. Enter server name: `eka-care-mcp`
+6. Authenticate with your Eka.care email
+
+Done! Test by asking Copilot: *"Search for patient Raj Kumar"*
+
+  </Accordion>
+
+  <Accordion title="VS Code (Windows)" icon="windows">
+    
+**Requirements:** VS Code 1.95+ with GitHub Copilot
+
+1. Press `Ctrl + Shift + P`
+2. Type and select **MCP: Add Server**
+3. Choose **HTTP** *(HTTP or Server-Sent Events)*
+4. Enter URL: `https://mcp.eka.care/mcp`
+5. Enter server name: `eka-care-mcp`
+6. Authenticate with your Eka.care email
+
+Configuration saved to: `%APPDATA%\Code\User\globalStorage\github.copilot-chat\mcp.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Paid(macOS/Windows)" icon="crown">
+    
+**Requirements:** Claude Paid subscription
+
+1. Open Claude Desktop
+2. Click **Settings** → **Connectors** → **Add custom connector**
+3. Type the name as **Eka-Care-mcp**
+4. Type the URL as **https://mcp.eka.care/mcp**
+5. Tap **Add**
+6. Authenticate with Eka.care
+7. Save and restart
+
+Pro users get higher rate limits and priority access.
+
+Config(macOS): `~/Library/Application Support/Claude/claude_desktop_config.json`
+Config(Windows): `%APPDATA%\Claude\claude_desktop_config.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Free(macOS)" icon="message">
+    
+**Requirements:** Claude Desktop app (Free tier)
+
+1. Open Claude Desktop
+2. Click **Settings** (bottom-left gear icon)
+3. Navigate to **Developer** → **Edit Config**
+4. Add this configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "https://mcp.eka.care/mcp"]
+    }
+  }
+}
+```
+
+5. Save and restart Claude Desktop
+6. Authenticate when prompted
+
+Config location: `~/Library/Application Support/Claude/claude_desktop_config.json`
+
+  </Accordion>
+
+  <Accordion title="Claude Desktop Free(Windows)" icon="message">
+    
+**Requirements:** Claude Desktop app (Free tier)
+
+1. Open Claude Desktop
+2. Click **Settings** (gear icon)
+3. Go to **Developer** → **Edit Config**
+4. Add:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "command": "npx",
+      "args": ["-y", "mcp-remote", "https://mcp.eka.care/mcp"]
+    }
+  }
+}
+```
+
+5. Save and restart Claude
+6. Authenticate when prompted
+
+Config location: `%APPDATA%\Claude\claude_desktop_config.json`
+
+  </Accordion>
+  <Accordion title="ChatGPT (Go/Paid)" icon="code">
+    
+**Requirements:** Free chatgpt does not provide the remote mcp connectors currently, You should have >Go model.
+
+1. Open https://chatgpt.com/
+2. Go to profile (Left bottom)
+3. Click **Settings**
+4. Navigate to **Apps and Connectors** 
+5. Scroll down and inside the Developer mode, switch it on
+6. Inside Apps and Connectors, tap **Create app**
+7. Enter the name **eka-care-mcp**
+8. Enter the URL **https://mcp.eka.care/mcp** and tap **Create**
+9. Authenticate when prompted
+
+  </Accordion>
+  <Accordion title="Cursor (macOS)" icon="code">
+    
+**Requirements:** Cursor IDE
+
+1. Open Cursor
+2. Press `Cmd + Shift + P`
+3. Type **Cursor settings**
+4. Select **Tools & MCP**
+5. Tap on **New MCP Server** 
+6. Add server configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+7. Tap on Connect to Authenticate with Eka.care 
+8. Restart Cursor
+
+Config location: `~/Library/Application Support/Cursor/User/globalStorage/mcp.json`
+
+  </Accordion>
+
+  <Accordion title="Cursor (Windows)" icon="code">
+    
+**Requirements:** Cursor IDE
+
+1. Open Cursor
+2. Press `Ctrl + Shift + P`
+3. Type **Cursor settings**
+4. Select **Tools & MCP**
+5. Tap on **New MCP Server** 
+6. Add server configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+7. Restart Cursor
+8. Complete authentication
+
+Config: `%APPDATA%\Cursor\User\globalStorage\mcp.json`
+
+
+  </Accordion>
+
+  <Accordion title="Zed (macOS)" icon="z">
+    
+**Requirements:** Zed Editor with AI features enabled
+
+1. Open Zed
+2. Go to **Zed** → **Settings** → **Language Models**
+3. Scroll to **MCP Servers**
+4. Click **Add Server**
+5. Enter:
+   - Name: `eka-care`
+   - URL: `https://mcp.eka.care/mcp`
+   - Transport: `HTTP`
+
+6. Save and restart Zed
+7. Authenticate when prompted
+
+Config location: `~/.config/zed/settings.json`
+
+  </Accordion>
+
+  <Accordion title="Zed (Windows)" icon="z">
+    
+**Requirements:** Zed Editor with AI features
+
+1. Open Zed
+2. Settings → Language Models
+3. MCP Servers → Add Server
+4. Configure:
+   - Name: `eka-care`
+   - URL: `https://mcp.eka.care/mcp`
+   - Transport: `HTTP`
+
+5. Save and restart
+6. Complete authentication
+
+Config: `%APPDATA%\Zed\settings.json`
+
+<Frame>
+  <img src="/images/mcp-zed-windows.png" alt="Zed Windows Setup" />
+</Frame>
+
+  </Accordion>
+
+  <Accordion title="Windsurf (macOS)" icon="wind">
+    
+**Requirements:** Windsurf IDE
+
+1. Open Windsurf
+2. Press `Cmd + ,` for Settings
+3. Navigate to **Extensions** → **MCP**
+4. Add server:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+5. Restart Windsurf
+6. Authenticate with Eka.care
+
+<Frame>
+  <img src="/images/mcp-windsurf-mac.png" alt="Windsurf macOS Setup" />
+</Frame>
+
+  </Accordion>
+
+  <Accordion title="Windsurf (Windows)" icon="wind">
+    
+**Requirements:** Windsurf IDE
+
+1. Open Windsurf
+2. Press `Ctrl + ,` for Settings
+3. Extensions → MCP
+4. Add configuration:
+
+```json
+{
+  "mcpServers": {
+    "eka-care": {
+      "url": "https://mcp.eka.care/mcp",
+      "transport": {
+        "type": "http"
+      }
+    }
+  }
+}
+```
+
+5. Restart Windsurf
+6. Complete authentication
+
+<Frame>
+  <img src="/images/mcp-windsurf-windows.png" alt="Windsurf Windows Setup" />
+</Frame>
+
+  </Accordion>
+
+</AccordionGroup>
+
+You simply tell your AI assistant:
+
+<CodeGroup>
+```text Natural Language
+"Book an appointment for patient Raj Kumar with Dr. Singh tomorrow at 10 AM, 
+and create a prescription for Amoxicillin 500mg, 3 times daily for 7 days"
+```
+</CodeGroup>
+
+And it's done! ✨
+
+<Frame>
+  <img src="/images/claude-prompt.png" alt="Example Conversation" />
+  {/* Screenshot placeholder: Show actual Claude Desktop conversation doing this task */}
+</Frame>
+
+## Who Should Use This?
+
+<CardGroup cols={2}>
+  <Card title="Healthcare Providers" icon="user-doctor">
+    Doctors, clinics, and hospitals using Eka.care for patient management
+  </Card>
+  <Card title="Health Tech Companies" icon="hospital">
+    Platforms building healthcare workflows and automation
+  </Card>
+  <Card title="Medical Administrators" icon="clipboard-user">
+    Staff managing appointments, records, and prescriptions
+  </Card>
+  <Card title="Developers" icon="code">
+    Engineers building AI-powered healthcare applications
+  </Card>
+</CardGroup>
+
+## What Can You Do?
+
+<AccordionGroup>
+  <Accordion title="👥 Patient Management">
+    - Search and retrieve patient records
+    - Add new patients
+    - Update patient information
+    - View complete medical history
+  </Accordion>
+
+  <Accordion title="📅 Appointment Management">
+    - Check available slots
+    - Book appointments
+    - Reschedule or cancel
+    - View appointment history
+  </Accordion>
+
+  <Accordion title="💊 Prescriptions">
+    - Generate digital prescriptions
+    - View prescription history
+    - Access medication details
+  </Accordion>
+
+  <Accordion title="🏥 Doctor & Clinic Operations">
+    - Retrieve doctor profiles
+    - Access clinic information
+    - View available services
+  </Accordion>
+</AccordionGroup>
+
+For more details on supported tools visit - https://developer.eka.care/mcp/supported-tools
+
+<Note>
+**Need Help?** Email us at ekaconnect@eka.care
+</Note>
diff --git a/mcp/supported-tools.mdx b/mcp/supported-tools.mdx
new file mode 100644
index 00000000..43aa637b
--- /dev/null
+++ b/mcp/supported-tools.mdx
@@ -0,0 +1,127 @@
+---
+title: Supported Tools
+description: Complete list of available MCP tools and their capabilities
+---
+
+# Supported Tools
+
+Eka MCP provides 20+ tools across patient management, appointments, prescriptions, and clinic operations. All tools support natural language queries through your AI assistant.
+
+## Patient Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `search_patients` | Search for patients by name, mobile, email, or patient ID | `query` (string), `limit` (optional) | List of matching patients with IDs, contact info, and basic details |
+| `get_patient_details` | Retrieve complete patient information | `patient_id` (string) | Full patient profile including medical history, demographics, and appointments |
+| `add_patient` | Register a new patient | `name`, `mobile`, `email` (optional), `dob` (optional), `gender` (optional) | New patient ID and confirmation |
+| `update_patient` | Modify existing patient information | `patient_id`, fields to update | Updated patient details |
+
+## Appointment Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `get_available_slots` | Check doctor's availability | `doctor_id`, `date`, `clinic_id` (optional) | List of available time slots |
+| `book_appointment` | Schedule a new appointment | `patient_id`, `doctor_id`, `slot_time`, `clinic_id` | Appointment ID and confirmation |
+| `get_appointments` | List appointments by various filters | `patient_id` OR `doctor_id` OR `date`, `status` (optional) | List of appointments with details |
+| `reschedule_appointment` | Change appointment timing | `appointment_id`, `new_slot_time` | Updated appointment details |
+| `cancel_appointment` | Cancel scheduled appointment | `appointment_id`, `reason` (optional) | Cancellation confirmation |
+| `get_appointment_details` | Retrieve specific appointment info | `appointment_id` | Complete appointment information |
+
+## Prescription Management
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `create_prescription` | Generate digital prescription | `patient_id`, `medications` (array), `doctor_id`, `advice` (optional) | Prescription ID and details |
+| `get_prescriptions` | View prescription history | `patient_id`, `from_date` (optional), `to_date` (optional) | List of prescriptions |
+| `get_prescription_details` | Retrieve specific prescription | `prescription_id` | Complete prescription with medications and advice |
+| `update_prescription` | Modify existing prescription | `prescription_id`, fields to update | Updated prescription |
+
+## Doctor & Clinic Operations
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `get_doctor_profile` | Access doctor information | `doctor_id` | Doctor details, qualifications, specializations |
+| `search_doctors` | Find doctors by name or specialization | `query`, `specialization` (optional) | List of matching doctors |
+| `get_clinic_details` | Retrieve clinic information | `clinic_id` | Clinic address, services, contact info |
+| `get_doctor_clinics` | List clinics associated with doctor | `doctor_id` | Array of clinic details |
+| `get_clinic_services` | View services offered by clinic | `clinic_id` | List of available services |
+
+## Medication Database
+
+| Tool Name | Description | Input Parameters | Returns |
+|-----------|-------------|------------------|---------|
+| `search_medications` | Look up medicine information | `query` (drug name) | Medicine details, dosage forms, manufacturers |
+| `get_medication_details` | Get complete drug information | `medication_id` | Full drug profile with interactions and contraindications |
+
+## Tool Parameters
+
+
+## Usage Examples
+
+### Simple Queries
+```text
+"Search for patient Raj Kumar"
+→ Uses: search_patients
+
+"Show Dr. Singh's available slots tomorrow"
+→ Uses: get_available_slots
+
+"Get prescription history for patient 12345"
+→ Uses: get_prescriptions
+```
+
+### Complex Workflows
+```text
+"Book appointment for Raj Kumar with Dr. Singh tomorrow at 10 AM 
+and create prescription for Amoxicillin"
+→ Uses: search_patients → book_appointment → create_prescription
+```
+
+## Rate Limits
+
+| Plan | Requests/Minute | Requests/Day |
+|------|-----------------|--------------|
+| Free | 10 | 1,000 |
+| Pro | 60 | 10,000 |
+| Enterprise | Unlimited | Unlimited |
+
+## Error Handling
+
+All tools return standardized error responses:
+
+```json
+{
+  "error": true,
+  "message": "Patient not found",
+  "code": "PATIENT_NOT_FOUND"
+}
+```
+
+### Common Error Codes
+
+- `PATIENT_NOT_FOUND` - Patient ID doesn't exist
+- `SLOT_UNAVAILABLE` - Appointment slot already booked
+- `INVALID_PARAMETERS` - Missing or incorrect parameters
+- `UNAUTHORIZED` - Authentication required
+- `RATE_LIMIT_EXCEEDED` - Too many requests
+
+## Need More Details?
+
+<CardGroup cols={2}>
+  <Card title="Quick Start" icon="rocket" href="/mcp/quickstart">
+    Get started in 5 minutes
+  </Card>
+  <Card title="Examples" icon="lightbulb" href="/mcp/advanced/examples">
+    See real-world workflows
+  </Card>
+  <Card title="API Reference" icon="book" href="/api-reference/introduction">
+    Complete API documentation
+  </Card>
+  <Card title="Troubleshooting" icon="wrench" href="/mcp/advanced/troubleshooting">
+    Common issues and fixes
+  </Card>
+</CardGroup>
+
+---
+
+**Questions?** Email ekaconnect@eka.care
\ No newline at end of file
diff --git a/mint_old_deprecated.json b/mint_old_deprecated.json
index a58cb527..da8d1818 100644
--- a/mint_old_deprecated.json
+++ b/mint_old_deprecated.json
@@ -79,7 +79,7 @@
     {
       "group": "Android",
       "pages": [
-        "SDKs/android/voice-to-rx",
+        "SDKs/android/ekascribe",
         "SDKs/android/medical-records"
       ]
     },
@@ -331,6 +331,19 @@
             "api-reference/doc-tool/doctor-and-clinic-api/get-doc-service"
           ]
         },
+        {
+          "group": "Config management APIs",
+          "icon": "user-cog",
+          "pages": [
+            {
+              "group": "User APIs",
+              "pages": [
+                "api-reference/doc-tool/user-apis/get-all-users",
+                "api-reference/doc-tool/user-apis/get-user-by-id"
+              ]
+            }
+          ]
+        },
         {
           "group": "Appointment API",
           "icon": "calendar-check",
@@ -343,7 +356,8 @@
             "api-reference/doc-tool/appointment-api/update-appointment-v2",
             "api-reference/doc-tool/appointment-api/parked-appointment",
             "api-reference/doc-tool/appointment-api/complete-appointment",
-            "api-reference/doc-tool/appointment-api/cancel-appointment"
+            "api-reference/doc-tool/appointment-api/cancel-appointment",
+            "api-reference/doc-tool/appointment-api/change-status"
           ]
         },
         {
diff --git a/snippets/snippet-intro.mdx b/snippets/snippet-intro.mdx
deleted file mode 100644
index c57e7c75..00000000
--- a/snippets/snippet-intro.mdx
+++ /dev/null
@@ -1,4 +0,0 @@
-One of the core principles of software development is DRY (Don't Repeat
-Yourself). This is a principle that apply to documentation as
-well. If you find yourself repeating the same content in multiple places, you
-should consider creating a custom snippet to keep your content in sync.
diff --git a/styles.css b/styles.css
new file mode 100644
index 00000000..15db4ada
--- /dev/null
+++ b/styles.css
@@ -0,0 +1,19 @@
+.eka-card-wrapper {
+  border-radius: 14px;
+  transition: transform 0.15s ease;
+}
+
+.eka-card-wrapper:hover {
+  transform: translateY(-3px);
+}
+
+.eka-card-wrapper:hover > * {
+  box-shadow: 0 12px 28px rgba(80, 66, 189, 0.22);
+  border-color: #5042BD;
+}
+
+.eka-divider {
+  border: none;
+  border-top: 1px solid rgba(80, 66, 189, 0.25);
+  margin: 48px 0;
+}
\ No newline at end of file
diff --git a/user-guides/eka-products.mdx b/user-guides/eka-products.mdx
new file mode 100644
index 00000000..5d05bfba
--- /dev/null
+++ b/user-guides/eka-products.mdx
@@ -0,0 +1,158 @@
+---
+title: Eka Products
+description: <font size="2"> Explore all Eka platform products across Core EMR, Health AI, Interoperability, and MCP. </font>
+---
+
+import { Columns, Card } from '@mintlify/components'
+
+<hr
+  style={{
+    border: 'none',
+    borderTop: '1px solid rgba(211, 8, 8, 1)',
+    margin: '48px 0'
+  }}
+/>
+
+
+<h2 style={{ color: '#5042BD' }}>Health AI</h2>
+
+<Columns cols={3}>
+  <div className="eka-card-wrapper">
+    <Card title="Assessments"  href="/integrations/health-ai/assessments">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        AI-powered clinical and health risk assessments.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="EkaScribe"  href="/integrations/health-ai/ekascribe">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Ambient clinical documentation using voice.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="MedAssist"  href="/integrations/health-ai/medassist">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        AI assistance for clinical decision support.
+      </p>
+    </Card>
+  </div>
+</Columns>
+
+---
+
+<h2 style={{ color: '#5042BD' }}>MCP</h2>
+
+<Columns cols={2}>
+  <div className="eka-card-wrapper">
+    <Card title="MCP for Indian treatment protocol search" href="/integrations/mcp/MCP-for-Indian-treatment-protocol-search">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Infrastructure for Indian treatment protocol search workflows and agents.
+      </p>
+    </Card>
+  </div>
+  <div className="eka-card-wrapper">
+    <Card title="Model Context Protocol (MCP)" href="/integrations/mcp/mcp-for-emr">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Infrastructure for AI-native healthcare workflows and agents.
+      </p>
+    </Card> 
+  </div>
+</Columns>
+
+---
+
+<h2 style={{ color: '#5042BD' }}>General Tools</h2>
+
+<Columns cols={2}>
+  <div className="eka-card-wrapper">
+    <Card title="Medical DB"  href="/integrations/general-tools/medical-db">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Standardized medical knowledge base.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Medical Document Parsing"  href="/integrations/general-tools/medical-document-parsing">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Extract structured data from clinical documents.
+      </p>
+    </Card>
+  </div>
+</Columns>
+
+---
+
+<h2 style={{ color: '#5042BD' }}>Interoperability</h2>
+
+<Columns cols={2}>
+  <div className="eka-card-wrapper">
+    <Card title="ABDM"  href="/integrations/interoperability/abdm">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        India’s ABDM integrations for consent-based health data exchange.
+      </p>
+    </Card>
+  </div>
+</Columns>
+
+--- 
+
+<h2 style={{ color: '#5042BD' }}>Core EMR</h2>
+
+<Columns cols={4}>
+  <div className="eka-card-wrapper">
+    <Card title="Patient"  href="/integrations/core-emr/patients">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Patient profiles, demographics, medical history, and longitudinal records.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Doctor"  href="/integrations/core-emr/doctor">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Clinical workflows, charting tools, and physician productivity features.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Appointments"  href="/integrations/core-emr/appointments">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Scheduling and appointment lifecycle management.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Clinic"  href="/integrations/core-emr/clinic">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Clinic setup, configuration, staff, and operations.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Payments"  href="/integrations/core-emr/payments">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Billing, invoices, and payment tracking.
+      </p>
+    </Card>
+  </div>
+
+  <div className="eka-card-wrapper">
+    <Card title="Prescriptions"  href="/integrations/core-emr/prescription">
+      <p style={{ fontSize: '12px', color: '#475569', lineHeight: '1.45' }}>
+        Medication orders and prescription workflows.
+      </p>
+    </Card>
+  </div>
+
+  
+</Columns>
+
+---
diff --git a/user-guides/get-started.mdx b/user-guides/get-started.mdx
new file mode 100644
index 00000000..b3e72a99
--- /dev/null
+++ b/user-guides/get-started.mdx
@@ -0,0 +1,101 @@
+---
+title: Get Started
+description: <font color='blue' size="3"><b>SIGN UP. BUILD. DEPLOY. 🚀 </b> </font>
+---
+
+import { Columns, Card } from '@mintlify/components'
+
+<hr
+  style={{
+    border: 'none',
+    borderTop: '1px solid rgba(211, 8, 8, 1)',
+    margin: '48px 0'
+  }}
+/>
+
+---
+<h2 style={{ color: '#5042BD' }}>Eka Connect</h2>
+
+<Steps>
+    <Step title="ONBOARDING">
+         **STEP 1: Sign Up for an API Key**
+        
+         To get started, you need to sign up for an API key. This key will authenticate your requests and give you access to our API. Ping us and we will provide you with the required API Keys.
+     
+            **Pre-requisites**
+                <Columns cols={2}>
+                    <div className="eka-card-wrapper">
+                        <Card title="Client ID" href="/api-reference/authorization/client-login">
+                        <p style={{ fontSize: '13px', color: '#475569', lineHeight: '1.45' }}>
+                            A unique identifier assigned to a third-party application interacting with Eka's API.
+                        </p>
+                        </Card>
+                    </div>
+
+                    <div className="eka-card-wrapper">
+                        <Card title="Client Secret" href="/api-reference/authorization/client-login">
+                        <p style={{ fontSize: '13px', color: '#475569', lineHeight: '1.45' }}>
+                            It is a confidential key, similar to a password used alongside the Client ID.
+                        </p>
+                        </Card>
+                    </div>
+                </Columns>
+
+             **Obtain the Client ID and Client Secret**
+
+             - Login to your Eka Care Control Panel at [Console](https://console.eka.care) and create client_id and client_secret
+             - If you’re building an app for doctors or patients, you can either integrate Eka Accounts using end-to-end OIDC or request an API key from your healthcare provider’s workspace for access. [Hub](https://hub.eka.care/account/account/apitoken/)
+             - For support or more details, contact us at ekaconnect@eka.care
+
+        **STEP 2: Set Up Your Environment**
+
+            Before making API calls, ensure your environment is properly set up. We recommend using the following tools and libraries:
+            - <b>HTTP Client</b>: Use tools like Postman, cURL, or any HTTP client library in your preferred programming language.
+            - <b>Base URL</b>: All API requests should be directed to https://api.eka.care
+    </Step>
+    <Step title="AUTHENTICATION">
+        Eka Connect’s API authentication securely verifies users and applications, ensuring only authorized access to sensitive healthcare data.
+       
+        **How to Authenticate with EKA’s API**
+
+        1. Short Lived Token 
+        
+        <Columns cols={3}>
+                <div className="eka-card-wrapper">
+                    <Card title="1. Get Access Token" href="/api-reference/authorization/client-login">
+                    <p style={{ fontSize: '13px', color: '#475569', lineHeight: '1.45' }}>
+                        Authenticate your app using the login API with your Client ID and Client Secret to receive the required access tokens.
+                    </p>
+                    </Card>
+                </div>
+                
+                <div className="eka-card-wrapper">
+                    <Card title="2. Use Access Token" href="/api-reference/authorization/refresh-token-v2">
+                    <p style={{ fontSize: '13px', color: '#475569', lineHeight: '1.45' }}>
+                        Pass the access token in the Authorization header with each API request to confirm your app’s access to Eka services.
+                    </p>
+                    </Card>
+                </div>
+
+                <div className="eka-card-wrapper">
+                    <Card title="3. Handle Token Expiration" href="/api-reference/authorization/refresh-token-v2">
+                    <p style={{ fontSize: '13px', color: '#475569', lineHeight: '1.45' }}>
+                        Access tokens expire for security reasons and return a <b>401 Unauthorized error</b>, use the Refresh Token API to generate a new access token.
+                    </p>
+                    </Card>
+                </div>
+            </Columns>
+       
+        - **Access Token**: A short-lived token (usually <b>30 minutes</b>) sent with each API request to authorize your app, refreshed using the Refresh Token API.([Access Token API](https://developer.eka.care/api-reference/authorization/client-login))
+        - **Refresh Token**: A longer-lived token that helps you get a new Access Token when the old one expires, without having to log in again. ([Refresh Token API](/api-reference/authorization/refresh-token-v2))
+        
+        2. Long Lived Token  : ([Long Lived Token](https://developer.eka.care/api-reference/authorization/getting-started)) section. 
+    
+    </Step>
+    <Step title="INTEGRATION">
+        We recommend reviewing our products before starting integration and selecting the one that best fits your use case.
+        
+        See you in the ([Eka Products](/user-guides/eka-products)) section. 
+    </Step>
+</Steps>
+