E-Atria HMS Open-Source Software Use Terms

01Plain-Language Summary

The E-Atria Hospital Management System is open-source software.

Anyone may download, install, use, study, modify, copy, redistribute, implement, maintain, and support the HMS, including for commercial purposes, provided the conditions in these terms and all applicable third-party licenses are followed.

Install and use

Hospitals, clinics, professionals, companies, NGOs, governments, and individuals may operate the HMS.

Modify and extend

Adapt workflows, add modules, integrate systems, and maintain your own version.

Copy and redistribute

Share original or modified copies while retaining the required notices and licenses.

Provide paid support

Any person or organization may charge for installation, customization, training, hosting, maintenance, or support.

Important distinction: Open-source HMS code does not make every connected service free. Hosting, infrastructure, implementation, support, E-Atria's hosted ABDM Bridge, AI tools, messaging, cloud services, and other external products may carry separate charges.

02Scope

These terms apply to the E-Atria HMS application code, custom HMS modules, interfaces, workflows, documentation, and business logic made available with this distribution, except where a file or component carries a different license.

Third-party frameworks, libraries, fonts, editors, icons, medical terminologies, standards, APIs, models, and services remain governed by their respective owners and licenses. These terms do not grant rights that E-Atria does not own or control.

Interpretation: When a specific file includes its own license or attribution notice, that specific notice controls for that file. An upstream component's license controls if it conflicts with these terms.

03Open-Source Rights

Subject to the conditions below, every recipient receives a worldwide, non-exclusive, royalty-free right to:

download, install, run, and use the HMS for any lawful purpose;
inspect, study, test, modify, translate, and create derivative works;
copy and redistribute the original HMS or a modified version;
deploy the HMS for one or multiple healthcare organizations;
offer free or paid implementation, customization, hosting, migration, training, maintenance, and support;
charge users for professional work, infrastructure, service levels, or other value-added services; and
use alternative service providers or self-hosted integrations where technically and legally available.

No royalty is owed to E-Atria merely for installing, using, modifying, redistributing, or supporting the open-source HMS code in accordance with these terms.

04Conditions You Must Fulfil

Preserve notices. Keep applicable copyright, attribution, license, and open-source notices with copies or substantial portions of the software.
Respect third-party licenses. Review and comply with the licenses of all bundled or separately installed dependencies, assets, standards, models, and integrations.
Describe material changes. Clearly identify modified distributions so users do not mistake them for an unchanged E-Atria release.
Do not misrepresent authorship or endorsement. You may state that your service uses or supports E-Atria HMS, but may not claim to be E-Atria or an authorized E-Atria partner without written authorization.
Use the software lawfully. Do not use it to violate healthcare, privacy, cybersecurity, intellectual-property, export, or other applicable laws.
Protect patient data. The deployer and operator must implement appropriate access controls, encryption, backups, audit review, retention, consent, and breach-response practices.
Do not imply warranties. If you redistribute or support the HMS, clearly identify the warranties and service commitments, if any, that you provide yourself.

Healthcare responsibility: The HMS assists clinical and administrative work but does not replace professional judgment. Each organization must validate its configuration, templates, calculations, clinical content, integrations, and operational procedures before production use.

05Commercial Support Is Allowed

Open source does not mean that professional work must be free. Any individual, developer, company, system integrator, or service provider may support HMS users and charge a service fee.

Permitted activity	Examples	Who may provide it
Installation and deployment	Server setup, domain, SSL, database, migration, upgrades	Any capable provider
Customization and integration	Reports, forms, modules, devices, APIs, accounting links	Any capable provider
Training and support	User training, help desk, on-site support, annual maintenance	Any capable provider
Hosting and operations	Cloud hosting, monitoring, backups, security, disaster recovery	Any capable provider
Data and migration services	Import, cleanup, mapping, validation, legacy-system migration	Any capable provider

Independent providers set their own prices and are responsible for their own contracts, service quality, taxes, warranties, security, and legal obligations. Their fees are not automatically E-Atria fees.

06Optional Paid E-Atria Services

The following may be offered by E-Atria under a separate subscription, usage plan, quotation, or service agreement. They are not included merely because the HMS source code is open source.

Hosted ABDM Bridge PAID

Managed connectivity through abdm-bridge.e-atria.in, including gateway operations, credentials, monitoring, updates, and supported ABDM transaction flows.

E-Atria AI Tools PAID

AI-assisted clinical drafting, extraction, analysis, imaging, automation, model/API usage, or other AI capabilities supplied or operated by E-Atria.

Managed Hosting OPTIONAL

Servers, storage, backup, monitoring, deployment, security maintenance, and availability commitments.

Professional Services OPTIONAL

Implementation, customization, migration, integration, training, priority support, and maintenance provided by E-Atria.

Price, scope, service level, usage limits, renewal, suspension, data handling, and support terms for paid services are governed by the applicable order, quotation, subscription, or separate agreement.

No forced purchase: The right to use the open-source HMS is not conditional on purchasing E-Atria support, hosted ABDM Bridge access, AI tools, or managed hosting.

07ABDM and AI Clarifications

ABDM

ABDM, ABHA, HFR, HPR, health-information exchange, consent, and related standards or services are governed by the applicable Government of India and ecosystem requirements.
The open-source HMS may contain ABDM integration code, screens, data structures, or connectors.
Use of E-Atria's hosted bridge at https://abdm-bridge.e-atria.in/ is a separate chargeable service unless E-Atria expressly provides a free plan in writing.
Organizations remain responsible for valid facility/professional registrations, credentials, consent, policies, certification, and lawful production use.

Artificial intelligence

AI features may require paid E-Atria services, third-party APIs, model licenses, compute, storage, or usage credits.
AI output is assistive and may be incomplete or incorrect. Qualified users must review it before clinical, financial, or operational use.
Organizations must decide whether patient or confidential data may be processed by an AI service and obtain all required notices, consent, contracts, and safeguards.

08Third-Party Software and Services

The HMS uses or may integrate with software and services supplied by others. Examples include CodeIgniter, Composer packages, JavaScript libraries, databases, web servers, fonts, editors, DICOM tools, terminology datasets, messaging providers, payment services, cloud platforms, and external APIs.

Each third-party component or service remains subject to its own license, terms, privacy policy, pricing, and availability.
You are responsible for obtaining any required license, subscription, API key, dataset permission, or infrastructure.
E-Atria cannot grant rights to third-party software, standards, content, or services beyond the rights granted by their owners.
Removal or replacement of one optional integration does not cancel the open-source rights granted for the HMS code itself.

09Data, Security, and Compliance

The organization deploying or operating the HMS is the controller or custodian of its patient, employee, billing, and operational data as determined by applicable law. It is responsible for:

lawful collection, use, disclosure, correction, retention, archival, and deletion of data;
role-based access, strong authentication, secure configuration, patching, encryption, logging, and incident response;
tested backups, restore procedures, business continuity, and disaster recovery;
clinical safety, financial controls, audit review, record retention, and statutory reporting;
contracts and safeguards for hosting, support, bridge, AI, messaging, and other processors; and
compliance with applicable healthcare, privacy, cybersecurity, tax, labor, and consumer laws.

Production deployment: Never expose a development configuration, default credential, debug output, unprotected backup, or patient data to the public internet.

10Names, Marks, and Attribution

The software-use rights do not transfer ownership of E-Atria names, logos, domains, service marks, or other brand assets.

You may truthfully state that a deployment is based on, derived from, compatible with, or supported for E-Atria HMS.
You may not imply that an independent product or service is operated, certified, endorsed, or warranted by E-Atria without written authorization.
Modified distributions should identify the modifier and material changes.
Required copyright, attribution, and license notices must remain available to recipients.

11Warranty Disclaimer and Liability

To the maximum extent permitted by applicable law, the open-source HMS is provided "as is" and "as available", without warranties of any kind, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, accuracy, security, availability, and non-infringement.

To the maximum extent permitted by law, contributors and rights holders are not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for loss of data, revenue, profit, goodwill, clinical opportunity, or business continuity arising from use or inability to use the software.

A separate paid service agreement may provide specific support commitments or service levels. Such commitments apply only to that agreement and do not change the general open-source software disclaimer.

12Compliance and Termination

Your rights under these terms continue while you comply with their conditions. Rights may terminate for a material breach that is not corrected after notice where correction is possible. Rights under third-party licenses remain governed by those licenses.

Termination of an E-Atria paid service, subscription, or support agreement does not by itself terminate your right to continue using the open-source HMS code, provided you continue to comply with these terms. After a paid service ends, related hosted APIs, credentials, models, infrastructure, support, or service data access may stop according to that service agreement.

13Questions and References

Review the notices supplied with your distribution before deployment or redistribution:

SOFTWARE_USE_LICENSE.md for repository terms;
OPEN_SOURCE_NOTICE.md for the open-source component notice;
LICENSE files included with specific framework or component code;
composer.json and composer.lock for PHP dependency records; and
license or notice files included with frontend assets and other dependencies.

For E-Atria hosted ABDM Bridge, AI, implementation, hosting, or support pricing, obtain a current written quotation or service agreement from E-Atria.

Questions about use: Keep a copy of the terms distributed with your software version. For material redistribution, healthcare deployment, or regulatory questions, obtain qualified legal and compliance advice for your jurisdiction.

Back to top