Security, HIPAA Compliance & Patient Confidentiality
Security governance policies, field-level encryption, role-based access control, and confidentiality rules protecting patient medical records.
1. Overview & Business Value#
This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for Security, HIPAA Compliance & Patient Confidentiality within SmartERP.

Security governance policies, field-level encryption, role-based access control, and confidentiality rules protecting patient medical records.
2. Prerequisites & Security Access Groups#
- Required Modules:
smarterp_healthcare, smarterp_clinical_core, smarterp_pharmacy - Security Groups:
Healthcare Receptionist(Technical ID:smarterp_healthcare.group_medical_receptionist)Physician / Attending Doctor(Technical ID:smarterp_healthcare.group_medical_doctor)Pharmacy Dispenser(Technical ID:smarterp_healthcare.group_medical_pharmacist)
- Master Data Dependencies: Patient master registry (Medical Record Number - MRN), EFDA drug formulary, Ethiopian Ministry of Health (MoH) HMIS disease codes, and EHIS insurance tariffs.
3. Step-by-Step Configuration & Execution#
Step 1: Navigating to the Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher (grid icon in the top-left corner).
- Navigate to Hospital → Patient Management → OPD / IPD.
Step 2: Operational Data Parameters & Controls#
Ensure all mandatory parameters comply with enterprise operational standards:
- Authorized Operator: Action executed under assigned RBAC permissions (Chief Medical Officer, Clinical Nurse, Receptionist, Pharmacist).
- Relational Integrity: Linked to upstream master records, approval requests, or transactional ledgers.
- Statutory & Quality Controls: Verified against Ethiopian statutory regulations and corporate governance standards.
Step 3: Operational Execution & State Progression#
- State Progression Gate: Advance record from Draft through Audited to Confirmed / Certified.
- Integrated System Impact: Automatically updates real-time operational states and posts financial/inventory journal moves.
- Audit Verification: System registers tamper-evident audit records logging user ID, timestamp, and cryptographic transaction digests.
Medical Record Privacy Principles#
SmartERP Healthcare adheres to the patient privacy protections established by the Ethiopian Criminal Code, MoH Healthcare Worker Ethical Guidelines, and international standards (HIPAA and ISO 27799 for health informatics security).
Medical data confidentiality is governed by four core pillars:
- Need-to-Know Access: Clinical staff access only the records of patients actively under their care.
- Segregation of Duties: Financial cashiers see billable diagnostic item codes but cannot view physician SOAP notes, psychiatric histories, or diagnostic findings.
- Immutable Audit Trails: Every read, edit, print, or export action on a patient file is permanently recorded.
- Data at Rest & in Transit Encryption: Database columns storing sensitive clinical notes use AES-256 field-level encryption; all network transit mandates TLS 1.3.
Access Control Matrix#
| Role | Demographics | Clinical Notes | Lab Results | Pharmacy Rx | Billing Folio | Audit Logs |
|---|---|---|---|---|---|---|
| Receptionist | Read/Write | None | None | None | Read | None |
| Triage Nurse | Read | Vitals Only | None | None | None | None |
| Physician | Read | Read/Write | Read | Read/Write | Read | None |
| Lab Tech | Read | None | Read/Write | None | None | None |
| Pharmacist | Read | None | None | Read/Write | None | None |
| Cashier | Read | None | None | None | Read/Write | None |
| Director / DPO | Read | Read | Read | Read | Read | Full Audit |
Break-the-Glass Emergency Protocol#
In acute emergency resuscitation when an unassigned physician must immediately access an unconscious patient's history:
- The clinician clicks Break-the-Glass Emergency Access.
- The user enters a mandatory clinical justification (e.g., "Unconscious trauma victim requiring immediate surgical history").
- Full medical record access unlocks immediately.
- An automated security event flags the Hospital Security Officer and Medical Director for next-day audit review.
4. Advanced Configuration Points#
- Automated Actions & Scheduled Tasks (Crons):
Healthcare: Generate daily MoH HMIS aggregate tally(smarterp_healthcare.ir_cron_hmis_sync): Runs daily at 23:00 to prepare DHIS2 health data summariesPharmacy: Flag expiring EFDA medicine batches(smarterp_healthcare.ir_cron_fefo_expiry): Runs daily at 06:00 to alert dispensers of lots expiring within 60 days
- Custom Print Templates & Reports:
- Official Patient Encounter Summary & Medical Certificate
- Electronic Prescription Order Form (Model 19 Compliant)
- Ethiopian Health Insurance Service (EHIS) Claim Dossier
- Daily MoH Outpatient / Inpatient Morbidity Tally Sheet
- Multi-Company Rules: Record-level security isolation under Company 1 (
Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.
5. Comprehensive Troubleshooting Matrix#
| Error Symptom / Exception | Probable Root Cause | Corrective Action / Resolution |
|---|---|---|
Access Block: Confidential clinical diagnosis restricted | User is not listed as the patient's attending physician or authorized consultant. | Request explicit clinical consultation delegation from the department head. |
Credit Ceiling Block: Corporate insurance expired | Patient corporate insurance policy limit exceeded or expired. | Switch billing mode to private cash settlement or upload pre-authorization approval from the insurer. |
FEFO Allocation Error: Expired medicine batch blocked | Dispenser selected medicine lot past statutory EFDA expiry date. | Isolate expired lot to quarantine storage and dispense compliant active lot. |