Healthcare Data Shield
Healthcare · MediCare Plus

Healthcare Data Shield

Security hardening of a healthcare Odoo platform holding patient and supply data: field-level encryption, granular access control, immutable audit logging, penetration testing and HIPAA-aligned policies.

Client
MediCare Plus
Category
Healthcare
Platform
Odoo 17 + security hardening
Duration
10 weeks
Team
4 specialists

0%

critical findings remediated

0%

fewer users with sensitive access

0%

sensitive record access logged

The system

Field-level access per role, encryption at rest and an audit trail of every sensitive read.

Field-level access matrix

Encrypted fields: 46
NamePhoneDiagnosisPrescriptionInsuranceBilling
DoctorFullFullFullFullReadRead
NurseFullReadReadReadNoneNone
PharmacistReadNoneNoneFullNoneNone
BillingReadMaskedNoneNoneFullFull
Front deskFullFullNoneNoneReadNone
IT adminMaskedMaskedNoneNoneNoneNone

Audit stream

live
  • Bulk export attempt by staff.20414:12
  • Prescription viewed by dr.saleh13:58
  • Access denied: billing → diagnosis13:41
  • Patient record updated by nurse.3113:20

Illustrative view with representative data.

The challenge

MediCare Plus stored patient contact details, prescriptions and supply records in Odoo. As the business grew, too many staff had broad access, there was no record of who viewed sensitive data, and an upcoming partner audit required proof of strong controls.

They needed to lock down sensitive data without slowing clinicians and staff down.

Problems & solutions

Problem 1

Sensitive data visible to everyone

Default access groups gave many users read access to patient details they didn't need.

How we fixed it

We redesigned access around least privilege, with role-based groups, record rules by clinic and field-level restrictions on sensitive fields.

Problem 2

Data at rest unprotected

Database backups and dumps contained readable patient information.

How we fixed it

Sensitive fields are encrypted at the application layer with managed keys, backups are encrypted and test databases are automatically anonymised.

Problem 3

No audit trail

The client couldn't show who had viewed or changed a patient record.

How we fixed it

An immutable audit log records reads, writes and exports of sensitive records, with alerts for unusual access patterns such as bulk exports.

What we delivered

  • Least-privilege access model and field-level security
  • Application-layer encryption of sensitive fields
  • Immutable audit logging with anomaly alerts
  • MFA, SSO and session hardening
  • Penetration test and remediation of all critical findings
  • HIPAA-aligned policies and anonymised test data

How the system flows

  1. 1Data classified
  2. 2Access redesigned
  3. 3Fields encrypted
  4. 4Activity logged
  5. 5Pentest & fix
  6. 6Audit passed
Impact

Key operating metrics before the project and after go-live.

Users with patient-data access

-83%
Before140
After24

Critical / high vulnerabilities

-100%
Before11
After0

Time to answer audit evidence requests

-90%
Before10 days
After1 days

Tell us about your challenge. A solutions architect will reply within one business day with ideas, not a sales pitch.