Privacy Policy

1. User Data Collection

Resident Companion is built on the principles of privacy-by-design and data minimization. We only collect and handle data that is strictly necessary for its clinical productivity and documentation assistance features:

• Patient Identification & Encounter Metadata: When active on an authorized hospital Electronic Medical Record (EMR) or Clinical Hospital Information page, the extension inspects DOM elements to read basic patient metadata (e.g., Patient Name, Medical Record Number / No. RM, room/ward, gender, and attending physician / DPJP). This information is displayed in the side panel solely for patient safety cross-checking to prevent documentation on the wrong patient record.
• Clinical Documentation & Notes (SOAP / CPPT): Clinical progress notes (Subjective, Objective, Assessment, Plan, and Instructions / SOAPI), procedure records, ICD-10 and ICD-9 codes, prescription orders, and medication instructions drafted, reviewed, or submitted by the clinician.
• Diagnostic & Laboratory Data:Laboratory values, imaging results, or pathology reports parsed from the active EMR view at the user's explicit request to compile structured clinical summaries.
• Authentication Information:An optional user-provided integration API token used solely to authenticate with the user's personal dashboard account to synchronize departmental clinical note templates and resident procedure checklists.
• User Preferences & Clinical Presets: Custom medication dosages, favorite note templates, local hospital profile selections, and interface preferences.
• Technical Metadata: Active browser tab URL and ID, used solely to confirm whether the user is viewing a supported hospital portal before enabling clinical autofill functionality.

2. User Data Handling and Use

All data accessed or collected by Resident Companion is processed solely to deliver the single-purpose clinical documentation functionality requested by the clinician:

• Clinical Documentation Assistance: Formatting and populating standardized progress notes (SOAP/CPPT) and electronic prescriptions into the hospital EMR upon explicit user confirmation.
• Patient Safety Cross-Verification: Cross-checking that the active patient open in the EMR matches the record currently being drafted to prevent accidental patient misattribution.
• Local Pediatric & Medical Dosage Calculations: Calculating recommended medication dosages and intravenous fluid drop rates directly in-browser using formulas based on user-entered patient weight.
• Template & Checklist Synchronization: Querying the authorized backend server (https://omfsunhas.site) to fetch department-standard clinical note templates and synchronize the user's personal procedure completion checklist.
• Limited Use Policy: We do NOT use user data for any secondary purposes, advertising, consumer profiling, machine learning model training without explicit consent, or commercial resale.

3. User Data Storage and Retention

• Local On-Device Storage: All drafted notes, customized presets, active patient cache, and preferences are stored exclusively on the user's local device using the Chrome Extension Local Storage API (chrome.storage.local).
• Zero Remote Patient Storage: Identifiable patient medical record drafts and clinical notes are NEVER uploaded to or stored on external cloud databases, third-party servers, or remote analytics storage.
• Retention Period: Data remains in local storage only for the duration of the active clinical session or until cleared by the user. When the clinician uninstalls the extension or clears data, all local records are permanently wiped.

4. User Data Sharing and Disclosure

• No Sale of Data: We do NOT sell, rent, lease, or monetize user data or patient health information under any circumstances.
• No Third-Party Transfers: We do NOT transfer or share personal or sensitive user data with third-party data brokers, advertising networks, marketing firms, or analytics providers.
• No External AI / LLM Processing: Patient data and clinical notes are never transmitted to third-party commercial large language models (LLMs) or external AI API services.
• Authorized Backend Only: Network communication occurs exclusively with the user's authorized application backend (https://omfsunhas.site) over secure, encrypted HTTPS/TLS connections, strictly for template and checklist synchronization upon user request.
• Chrome Web Store Compliance: Our use and transfer of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

5. Data Deletion and User Control

Users have complete autonomy over their stored data at all times:

• In-Panel Clear / Reset:Clinicians can immediately purge current patient drafts, SOAP fields, and prescription entries by clicking the "Reset" / "Kosongkan" buttons in the extension panel.
• Disconnect Token: Users can revoke and delete their integration token at any time in the settings tab, severing all communication with the dashboard server.
• Complete Uninstallation:Uninstalling the extension (right-click the Resident Companion extension icon in Chrome and select "Remove from Chrome") permanently deletes all locally stored extension data and configurations from the browser.

6. Security Safeguards

We implement robust technical safeguards to protect data integrity:

• Strict HTTPS/TLS encryption for all network communication with the backend.
• Isolated extension sandboxes preventing cross-context script contamination.
• Strict least-privilege permission scoping in the extension manifest.

7. Developer & Contact Information

For questions, feedback, or inquiries regarding this Privacy Policy and our user data practices, please contact:

• Application: Resident Companion
• Developer: alfanmaulanae-oms
• Contact Email: alfanmaulanae@gmail.com
• Official Portal: https://omfsunhas.site
• Policy URL: https://omfsunhas.site/privacy