Separation at the data layer
HarpethIQ uses an Azure SQL database for each tenant. The application resolves the organization’s database from the authenticated member session. Tenant isolation is enforced centrally in the data-access layer.
Security & architecture
A foundation your
IT team can examine.
Healthcare maintenance records need clear boundaries and accountable access. Here’s how those principles shape HarpethIQ.
Data isolation
Your organization
has its own database.
Service-line scope
Within an organization, service-line and location controls limit which records a member can access.
Access & accountability
A record of
who changed what.
Access controls
Authorization governs access to product features and records. Tenant member access is separate from the platform’s administrative identity plane.
Audit history
Changes pass through a centralized audit path. Audit events are append-only records that retain attribution and timestamps.
Controlled changes
Controlled equipment revisions support review and electronic signatures, including separation between the person requesting a change and the person approving it.
Your review
Bring your
requirements.
Hosting and operations
HarpethIQ runs on Microsoft Azure. We can discuss hosting, identity, network controls, and deployment practices as part of your technical evaluation.
Compliance is a conversation
Product controls support your review; they are not a claim of certification or a guarantee that a deployment meets your obligations. Discuss intended use, contractual requirements, and any BAA requirements with us before sharing protected information.
Start with the right people
Include your IT or security team in the demo request and tell us which topics you want to cover. Please do not put sensitive records into the request form.