Introduction
AIMCare ("we", "our", "us") is a Hospital Management Information System developed and operated by AIMDek Technologies. The platform holds patient health records, clinical documentation, operational information and financial data on behalf of the healthcare facilities that subscribe to it.
This document sets out the security controls built into AIMCare, how data is stored and governed, how responsibility is divided between AIMDek and the subscribing healthcare facility, and the regulatory work currently underway. It should be read alongside the AIMCare Privacy Policy, which governs how information is collected, used and shared.
AIMCare does not hold independent security or healthcare compliance certifications at this time. Where regulatory alignment work is underway it is described in Section 6 as in progress, and is not represented as complete. No software platform delivers compliance on its own; what a platform can do is provide the controls a healthcare organisation relies on to meet its own obligations.
1 Scope and roles
1.1 · Who this document applies to
This document applies to the AIMCare platform — the web application, mobile applications and associated services available at aim-care.health — and to the healthcare facilities, healthcare professionals and patients whose information is processed through it.
1.2 · Controller and processor roles
AIMCare acts as a data processor for patient health information. The subscribing healthcare facility is the data controller and remains responsible for obtaining appropriate patient consent, for determining what information is recorded, and for its own regulatory obligations.
This distinction matters throughout this document. AIMDek is responsible for the security of the platform and the controls it makes available. The healthcare facility is responsible for how those controls are configured and used. Section 7 sets out the division in full.
2 Platform security controls
The following technical controls are implemented across the AIMCare platform.
| Control | Implementation |
|---|---|
| Encryption at rest | AES-256. All stored data, including backups, is encrypted. |
| Encryption in transit | TLS 1.3 between browser and server. |
| Access control | Role-based. Data access is limited by role and department. |
| Authentication | Multi-factor authentication is available for every account. |
| Audit trail | Tamper-proof. Every action within the platform is logged. |
| Backups | Automated daily backups, stored offsite. |
| Monitoring | 24×7 monitoring with live intrusion detection. |
2.1 · Role-based access control
Healthcare teams need very different views of the same patient. A front-desk user, a consulting physician, a pharmacist and a billing executive do not require identical access to clinical and financial information.
AIMCare enforces role-based access control so that patient health information is accessible only to authorised staff of the subscribing healthcare facility, based on their assigned role and department. Access is limited to what is necessary for each role.
Permissions are configurable, so access rules can be adapted to how each organisation is structured, including differences between departments, specialties and operational units. For multi-location organisations, access can be granted according to role, location and responsibility across the wider group.
2.2 · Authentication and account management
Login credentials are stored with the password encrypted. Multi-factor authentication is available for every account.
Authorised administrators at the healthcare facility can create, change and remove user access as staff join the organisation, change role or leave it. Removing access promptly when a staff member leaves is the facility's responsibility, and is one of the most common sources of avoidable exposure in healthcare environments.
2.3 · Audit trails
Access control determines what a user can reach. Auditability records what they actually did.
AIMCare maintains a tamper-proof audit trail of activity within the platform, including actions performed by each user, login timestamps and session duration. Audit trail logs are retained for seven years, supporting the record-keeping expectations placed on healthcare organisations by NABH, NABL and applicable healthcare regulations, and the documentation required in medico-legal cases.
Audit information is available to authorised users according to role, rather than being open to every account with access to the underlying record.
2.4 · Encryption
All data stored by AIMCare is encrypted at rest using AES-256, including database contents and backups. All traffic between the user's browser and AIMCare servers is encrypted in transit using TLS 1.3.
2.5 · Separation between healthcare organisations
Each subscribing healthcare facility's information is logically separated within the platform. A user authenticated against one facility cannot reach another facility's records, and access controls are enforced at the application layer on every request rather than only at the point of login.
3 Infrastructure and operations
3.1 · Data location
All data collected and processed through AIMCare is stored on servers located in India, in compliance with applicable data localisation requirements and the National Health Authority's data governance framework.
Healthcare organisations that require confirmation of data residency for their own regulatory or procurement purposes can request it during evaluation.
3.2 · Backups and recovery
Backups run automatically on a daily cycle and are stored offsite. Backup data is encrypted to the same standard as production data.
3.3 · Monitoring
The platform is monitored 24×7, with intrusion detection running against live traffic. Monitoring covers unauthorised access attempts, suspicious activity, system errors and performance degradation.
3.4 · Infrastructure providers
AIMCare runs on cloud infrastructure operated by third-party providers. All such providers are bound by data processing agreements requiring them to maintain confidentiality, use data only for the specified purpose, and comply with applicable data protection laws. Section 4.4 lists the categories of provider involved in delivering the service.
4 Data governance
4.1 · Retention
Healthcare records cannot simply be deleted when they are no longer operationally useful; retention is set by clinical, legal and tax obligations. AIMCare applies the following retention periods.
| Data type | Retention period |
|---|---|
| Patient health records | Minimum 7 years from last encounter, per Medical Council guidelines |
| Medico-legal case records | Indefinitely — cannot be deleted |
| Billing and financial records | 8 years, per GST and Income Tax requirements |
| Audit trail logs | 7 years |
| User account data | Duration of subscription + 1 year |
| System and access logs | 1 year |
4.2 · Deletion and handover
On termination of a healthcare facility's subscription, data is retained for 90 days to allow for export and handover. After that period it is securely deleted, unless a longer retention period is required by law — most commonly for medico-legal records, which cannot be deleted.
4.3 · Data export
Healthcare facilities can obtain their information in a standard readable format, so that leaving the platform does not mean losing access to their own records. Patients exercise the equivalent right to portability through the facility that holds their records, as set out in the Privacy Policy.
4.4 · Sub-processors
AIMCare works with selected third-party service providers to deliver the platform. Each is bound by a data processing agreement.
| Category | Purpose |
|---|---|
| Cloud infrastructure | Hosting and storage of platform data |
| SMS and WhatsApp gateways | Appointment reminders, result alerts and patient notifications |
| Email service providers | System and transactional email |
| Payment processing partners | Subscription billing for healthcare facilities |
A current list of named providers is available to healthcare organisations on request during evaluation or at any point during the subscription.
4.5 · Limits on how data is used
We do not sell, rent or trade any personal or health information to third parties. We do not use patient health information for advertising, marketing or commercial profiling purposes.
Aggregated, de-identified usage data is analysed to improve platform features and clinical workflows. This analysis does not identify individual patients.
5 Artificial intelligence and patient data
AIMCare applies AI assistance inside clinical, operational and financial workflows. Because that intelligence works with patient information, it is governed by the same controls as the rest of the platform.
5.1 · Human oversight
AI provides suggestions, summaries or risk signals. Authorised users remain responsible for reviewing and acting on the output, and can accept, edit or reject it. AI does not complete a clinical or financial action on its own.
5.2 · AI activity is logged
AI-assisted actions are recorded in the same audit trail as any other activity, so a healthcare organisation can establish where AI contributed to a workflow. AI does not create an unlogged path through the platform.
5.3 · Fallback
Where AI assistance is unavailable, the underlying workflow continues to operate without it. No clinical or operational process depends on AI being available.
5.4 · Model training
Patient health information is not used to train or fine-tune artificial intelligence models. This is consistent with the commitment in our Privacy Policy that patient health information is not used for commercial purposes beyond delivering the platform.
Where AI capabilities involve a third-party model provider, that provider is treated as a sub-processor, is bound by a data processing agreement, and is disclosed on request under Section 4.4.
6 Regulatory position
6.1 · Certifications
AIMCare does not currently hold independent security or healthcare compliance certifications. We state this plainly rather than describing the platform as "compliant" with frameworks that do not certify software, because a healthcare organisation evaluating AIMCare needs an accurate picture of what it is buying.
The controls described in this document are implemented and can be demonstrated during evaluation. What is not yet in place is independent third-party attestation of them.
6.2 · Regulatory work underway
AIMCare's regulatory programme is sequenced around the markets it serves, with India first. The table below reflects current status. No item is represented as complete until it is.
| Framework | Status | Scope of work |
|---|---|---|
| India DPDP Act | In progress | Consent capture and management, purpose limitation, retention and deletion, access and correction requests, breach notification support, and the records required for assessments and audits |
| ABDM / ABHA | In progress | ABHA-linked identity and interoperability workflows, and the consent and data-exchange requirements that participation in ABDM carries |
| NABH | Planned | Documentation, record-keeping and traceability support aligned to hospital accreditation expectations |
| HITECH / HITRUST | Planned | Readiness work for healthcare organisations operating in or alongside the United States market. Not started. |
India's Digital Personal Data Protection Act is the primary focus. Its rules are being implemented on a phased basis, and healthcare organisations — particularly larger hospital groups, which may be classified as Significant Data Fiduciaries — will need to evidence consent handling, retention practice and data-subject request processes. AIMCare's DPDP work is directed at the platform capabilities those organisations will rely on.
6.3 · The healthcare organisation's own obligations
Applicable obligations depend on the organisation, jurisdiction, deployment, configuration, contractual responsibilities and how the platform is used. Depending on where they operate, healthcare organisations may need to address requirements beyond those listed above.
AIMCare provides security, privacy, access and governance capabilities designed to help healthcare organisations address applicable requirements as part of their wider compliance programmes. It is a vendor to that programme, not a substitute for it.
8 Incident response and continuity
8.1 · Detection
Unauthorised access attempts and suspicious activity are monitored continuously, with intrusion detection running against live traffic. Security incidents are investigated on identification.
8.2 · Notification
In the event of a personal data breach likely to result in a risk to the rights and freedoms of individuals, AIMDek will:
- Notify the affected healthcare facility without undue delay and within 72 hours of becoming aware of the breach.
- Provide details of the nature of the breach, the data affected, the likely consequences, and the measures taken or proposed.
- Assist the facility in notifying affected patients where required by applicable law.
- Cooperate with relevant regulatory authorities as required.
The healthcare facility, as data controller, carries its own statutory notification obligations. The 72-hour commitment is set to leave the facility time to meet them.
8.3 · Business continuity
Daily offsite backups support restoration of service in the event of an extended outage or data loss. Affected healthcare facilities are kept informed during any significant service disruption.
8.4 · Reporting a security issue
Security researchers, customers and members of the public can report a suspected vulnerability or security concern to dev-operations@aim-care.health. Reports are acknowledged and investigated. We ask that suspected vulnerabilities are reported to us before being disclosed publicly, so that affected healthcare organisations are not exposed while a fix is prepared.
9 Support during security evaluation
Security review is part of buying healthcare software, and AIMCare supports that process rather than treating it as an obstacle at the end of the sales cycle. The following are available to healthcare organisations during evaluation:
- Responses to your security questionnaire, in your own format
- A platform security overview covering access, audit, hosting and data protection
- An architecture and data-flow overview for your deployment
- The current named list of sub-processors
- Confirmation of data residency arrangements
- Contractual data protection terms appropriate to your jurisdiction
Requests can be made through your AIMCare contact or to dev-operations@aim-care.health.
10 Changes to this document
We may update this document to reflect changes in our practices, platform capabilities, regulatory position or applicable law. When we make material changes, we will:
- Update the "Last updated" date at the top of this page
- Notify subscribing healthcare facilities by email at least 30 days before the changes take effect
- Display a prominent notice on the AIMCare platform
Where a regulatory item in Section 6 moves from "In progress" to complete, this document will be updated at that point and not before.
Contact
Questions about AIMCare security, this document, or your organisation's security review:
This document should be read alongside the AIMCare Privacy Policy and Terms of Service.