Your practice instance
Configured for one licensed organization, its brand, its selected plan, and its credentialed staff.
SECURITY + PROVISIONING
Control starts with a separate practice environment.
IPMS combines technical controls, accountable access, operational records, and careful contracting. It does not reduce security to a badge or unsupported promise.
2FA for the team
Every credentialed non-demo user enrolls an authenticator app before receiving a session. A password alone does not open the workspace.
Automatic logoff
Sessions end after 15 minutes of inactivity and hit a 12-hour hard limit even during continuous use.
Accountable access
Role-based permissions, password controls, lockout protection, and audit records support responsible workforce access.
Encryption + continuity
Configured production deployments use encrypted transport, encrypted storage, and encrypted off-site backup workflows.
Mandatory authenticator 2FA
Enrollment is required at first sign-in for credentialed staff, except the sample-data-only shared demo account.
15-minute idle protection
Active sessions renew safely; idle workstations automatically log off, and no session remains active beyond the absolute limit.
Encryption in transit and at rest
TLS protects network traffic. HIPAA-enabled production storage and backup services are configured for encryption at rest.
BAA-backed HIPAA deployment
Available when the customer agreement, infrastructure BAA, approved subprocessors, and HIPAA-enabled production workspace are executed and enabled.
Optional training workspace
HIPAA and compliance onboarding can be provisioned to organize assignments, acknowledgements, and completion follow-up.
Audit and backup workflows
Operational changes are recorded, while backup controls support recovery and continuity for configured environments.
HIPAA IS A SHARED RESPONSIBILITY
Controls, contracts, configuration, and daily practice all matter.
A BAA-supported deployment is not a blanket certification. HIPAA readiness depends on an executed BAA, enabled infrastructure, approved integrations, least-necessary access, workforce training, customer policies, and lawful use.
The practice remains responsible for workforce access, professional credentials, clinical protocols, consent language, communications, retention, and breach-response duties. IPMS configures the platform controls and contracted services identified in the order.
IPMS supports practice operations and documentation. It is not an emergency system and does not replace professional judgment or independent verification.
PROVISIONING PATH
From selected plan to private workspace.
- 1Choose the operating tier
Select Aegis, Athena, or Olympus based on staff count and workflow depth.
- 2Confirm the practice
Provide authorized business and contact details and accept the platform terms.
- 3Provision the environment
IPMS reserves implementation capacity and configures the practice instance.
- 4Set accountable access
Administrators receive sign-in details and establish staff roles and credentials.
A BETTER OPERATING DAY
Give your practice one place to move work forward.
Choose a plan, tell us about your team, and begin provisioning your private IPMS environment.