Legal & Commercial

Terms & Conditions

These Terms govern access to and use of MyHospital, owned and operated by AFCKS Technologies, together with any accepted quotation, agreement, implementation scope and hospital-specific commercial terms.

Last updated 2 September 2026 Core + Add-ons commercial model GST applicable as configured
Hospital-specific pricing, implementation scope, migration, training, user/device capacity and add-ons are governed by the accepted quotation/agreement where those documents provide more specific commercial terms.

1. Acceptance of Terms

By accessing or using MyHospital on behalf of a hospital or other organization, the customer confirms that the person acting for it is authorized to accept these Terms and the applicable quotation, agreement or order.

2. Platform Service

MyHospital is a configurable hospital information and operations platform. Available functions depend on the Core subscription, purchased add-ons, platform-level availability, hospital operational settings and authorized user permissions.

Features may include patient registration, appointments, consultations, billing, queue management, pharmacy, laboratory, radiology, IPD, emergency, procurement, biomedical, quality, HR, communications, analytics and other modules made available from time to time.

3. Subscription, Capacity & Add-ons

Production pricing is determined from the applicable commercial configuration and the accepted quotation. The recurring subscription may include a Core platform amount, agreed user capacity, display-device capacity and selected add-ons.

Add-ons may be priced using a percentage of the Basic/Core amount, a fixed fee, usage/capacity basis or a custom quoted amount. Platform-level availability is separate from commercial entitlement and from a hospital's operational module toggle.

Changes to users, display devices, modules, branches, integrations or other scope may require a revised quotation and recurring fee.

4. Setup, Data Migration, Training & Other Services

Implementation costs vary by hospital size, users, display devices, departments, selected add-ons, existing systems, data quality and required assistance. Mandatory setup and optional services are separately identified in the quotation.

Data migration, historical migration, data cleanup, mapping, integration work, additional training, on-site support, custom reports or custom workflow configuration are included only where expressly quoted.

Migration outcomes depend on the quality, format, completeness and accessibility of the source information supplied by the customer. The customer remains responsible for validating migrated information before Go-Live.

5. Payment, Taxes & GST

Fees, billing cycle, validity, payment terms and initial amounts are specified in the accepted quotation or agreement. GST and other applicable taxes are charged as configured and as required by applicable law.

Unless a payment gateway is expressly enabled in the future, payment confirmation is recorded manually by an authorized platform administrator after the relevant payment information has been verified.

6. Hospital Provisioning, Onboarding & Go-Live

Hospital provisioning may occur after required commercial acceptance and payment verification. Provisioning may create the hospital tenant, database configuration, initial Hospital Admin, commercial entitlements and onboarding records.

Provisioned status does not necessarily mean the hospital is ready for production. Configuration, data migration, training, validation, integrations and customer sign-off may still be required before Go-Live.

7. Accounts, Roles & Authorized Access

Customers are responsible for ensuring that user accounts are assigned only to authorized individuals and that roles and permissions reflect actual job responsibilities. Credentials must not be shared in a manner that defeats individual accountability.

Access may be restricted by tenant isolation, subscription entitlement, platform module status, hospital module settings, commercial capacity and role-based permissions.

8. Hospital Responsibilities

The customer is responsible for:

  • the accuracy and lawfulness of information entered into its hospital environment;
  • obtaining appropriate patient, employee and other permissions or consents;
  • maintaining authorized staff access and promptly removing unnecessary accounts;
  • validating configuration, migrated data and operational workflows before Go-Live;
  • maintaining any local policies, procedures and statutory records required for its operations;
  • using the service only for lawful hospital and healthcare operations.

9. Clinical and Professional Responsibility

The platform supports recordkeeping and operational workflows but does not replace the professional judgment, statutory responsibilities or clinical governance of licensed healthcare professionals and healthcare organizations.

Any AI, automation or workflow feature that is enabled remains subject to its configured safeguards, human review requirements and permitted operational scope. The customer must not treat software output as a substitute for professional clinical decision-making.

10. Availability, Maintenance & Platform Changes

Reasonable efforts are made to operate and maintain the service, but uninterrupted availability is not guaranteed. Maintenance, infrastructure incidents, telecommunications problems, third-party failures or security events may affect access.

Features may be enhanced, replaced, restricted or retired where needed for security, compliance, technical maintenance or product development. Material commercial changes will be handled through the applicable customer commercial process.

11. Data, Privacy, Backup & Security

Use of information is also governed by the Privacy Policy. Customers control the hospital records entered into their tenant environment and remain responsible for authorized use and retention requirements.

Operational backups and recovery procedures may be maintained according to platform configuration. A backup service does not replace any customer-specific statutory archiving requirement unless expressly agreed.

12. Demo and Learning Environment

The shared Demo Hospital is provided only for demonstration, training and product evaluation. It uses synthetic data, may be reset at any time and must not be used for real patient records, confidential production information or real financial transactions.

Role-play and Learning Center access does not create a production subscription entitlement or grant the user another real staff member's permissions.

13. Intellectual Property

The MyHospital software, interface, platform documentation, templates, brand assets and underlying platform technology remain the property of their respective owner/licensor. A subscription provides a limited right to use the service during the applicable subscription period; it does not transfer ownership of the platform source code or technology.

The customer retains its rights in hospital data that it lawfully provides to the service.

14. Suspension and Termination

Access may be suspended or restricted for material non-payment, security risk, unlawful use, misuse of the service, expiry/cancellation of the applicable subscription or other material contractual breach, subject to applicable commercial terms and law.

Data export, retention and deletion following termination should be handled according to the applicable agreement, customer instructions, technical capabilities and legal retention requirements.

15. Liability

To the extent permitted by applicable law, the platform is provided subject to the limitations, exclusions and commercial allocation of risk stated in the applicable agreement. Neither these Terms nor the software should be interpreted as guaranteeing a particular clinical, financial, regulatory or business outcome.

Nothing in these Terms is intended to exclude liability that cannot lawfully be excluded or limited.

16. Customer Responsibility for Misuse

The customer is responsible for losses, claims or issues arising from its unauthorized, unlawful or negligent use of the platform, including unauthorized accounts, unlawful data entry, misuse of patient information or configuration of third-party integrations contrary to applicable requirements, subject to the allocation of responsibility in the applicable agreement and law.

17. Governing Law & Jurisdiction

Unless the applicable signed agreement states otherwise, these Terms are governed by the laws of India. Subject to applicable law and any agreed dispute-resolution process, courts having jurisdiction in Pune, Maharashtra will have jurisdiction over disputes relating to these Terms.

18. Changes to These Terms

These Terms may be updated as the platform, commercial model, legal requirements or operating practices change. The current version will be published at this URL. An accepted customer quotation/agreement remains the applicable commercial snapshot for the scope it covers unless revised or replaced.

19. Contact

AFCKS Technologies
G-25, 2nd Floor, Shantikunj
Opposite GPO, Beside Nucleus Mall
Sadhu Vaswani Road, Camp
Pune - 411001

Support: mohammed.raza@afcks.com