Security & Compliance
Lynx Compliance - Guides for HIPAA
Maps the compliance implementation guides onto HIPAA controls, so a control assessment for that framework links straight to the runbook that implements it.
lynx_compliance_guides_hipaa
· v19.0.1.0.0
· Standard
What this solves
Lynx Compliance - Guides for HIPAA
The implementation guides are framework-agnostic runbooks: how to offboard a user, how to run an access review, how to handle a vendor. What differs per framework is which controls each runbook satisfies.
This bridge carries the HIPAA half of that mapping. It exists so lynx_compliance_guides can depend on nothing but lynx_compliance and therefore reach every tenant, instead of requiring five framework modules a customer may never have bought.
It carries no licence feature of its own, deliberately. Odoo applies auto_install with a direct SQL update that never runs the licence gate, so an auto-installing module must be one that cannot grant anything the customer has not already paid for. This bridge qualifies: it appears only when both the guides and HIPAA are already installed, and installing HIPAA required its own licence.
Auto-Installation
Installs itself as soon as both lynx_compliance_guides and lynx_compliance_hipaa are present, and does nothing otherwise. It has no licence feature of its own because Odoo applies auto_install with a direct SQL update that bypasses the licence gate entirely - so anything auto-installing must be incapable of granting unpaid-for value. A mapping between two modules the customer already has qualifies.
Key Features
13 guide-to-control mappings for HIPAA, appended rather than replaced so admin edits survive an upgrade.
Auto-installs the moment both the guides module and HIPAA are present, with no menu, model or setting of its own.
Licence-safe by construction - it unlocks nothing that was not already unlocked by the framework module it bridges.
Depends on
Try Lynx Compliance - Guides for HIPAA on your team.
Free trial, no credit card. Talk to sales when you're ready.