Neptune HMIS

Legal & Compliance

Legal & Compliance Documents

Document set: 14 policy, contract and operational templates, prepared for Neptune Technolab Pvt. Ltd.

Important: This is a drafting pack for business and legal review, not a legal opinion or proof of compliance. It intentionally distinguishes the hospital’s role in deciding patient-care purposes from Neptune’s role as the software provider / processor. Do not publish or sign until all operational facts, vendor lists, technical controls, retention periods, contract terms and statutory obligations have been verified.

Document 1 of 14

1. Privacy Policy – Website, platform and patient-data role allocation

1.This notice explains how Neptune Technolab Pvt. Ltd. handles information in connection with the Neptune HMIS website and the Neptune HMIS software service. It must be read together with the hospital’s own patient privacy notice and the signed customer agreement.

1. Who is responsible for what

2.Neptune Technolab Pvt. Ltd. ("Neptune", "we", "us") operates the Neptune HMIS website and supplies the HMIS software. For information submitted through the public website enquiry forms, Neptune determines the purposes and means of processing. For patient and hospital operational information entered into a hospital’s HMIS tenant, the hospital / healthcare facility generally determines the purposes of processing and is responsible for its patient notices, lawful basis, consent, clinical records and access decisions. Neptune processes such information on the hospital’s documented instructions as a service provider / processor, subject to the signed agreement and applicable law.

2. Information we may process

  • 3.Website enquiries: name, mobile number, email, hospital / organisation, city, hospital type, bed count, modules of interest, preferred demo date, message and campaign parameters submitted through forms.
  • 4.Customer account and service information: authorised user names, work contact details, role, login and security events, subscription, configuration, support tickets, billing and service communications.
  • 5.Hospital / patient information, where enabled by the customer: patient identifiers and demographics, ABHA-related identifiers or addresses, appointments, OPD/IPD encounters, vitals, diagnoses, prescriptions, lab orders and reports, discharge summaries, billing, insurance / TPA, nursing and OT records, documents and audit events.
  • 6.Integration data: information exchanged with ABDM services, payment providers, SMS / WhatsApp / email providers, laboratory devices, insurance / TPA systems or other integrations configured by the hospital.
  • 7.Technical data: device, browser, access, security and diagnostic logs needed to operate, protect and troubleshoot the service. Exact fields and retention must be confirmed against production configuration.

3. Purposes and instructions

8.We use website enquiry information to respond to demo, sales, partnership and support requests. We use customer account and technical information to provision, secure, maintain, support, bill for and improve the service. Patient information is processed to provide the contracted HMIS functions, support authorised hospital workflows, maintain security and auditability, and perform integrations instructed by the hospital. Neptune does not independently use identifiable patient records for advertising, sale, unrelated profiling or model training.

4. ABDM and consent-based exchange

9.Where a hospital enables ABDM-connected workflows, health information exchange must follow the applicable ABDM ecosystem requirements, patient consent artefacts, purpose limitations and technical specifications. Neptune HMIS facilitates workflows; the hospital remains responsible for ensuring that the correct patient, purpose, data set, recipient and consent / authorisation are selected. Do not treat a general HMIS login or general privacy notice as a substitute for a specific ABDM consent request.

5. Sharing and recipients

  • 10.Authorised hospital personnel and configured users, according to customer-managed roles and permissions.
  • 11.Neptune personnel who require access for authorised support, security, maintenance or incident response, subject to access controls and confidentiality obligations.
  • 12.Hosting, infrastructure, backup, messaging, payment, analytics, support and integration providers actually engaged for the service, as listed in the current subprocessor register.
  • 13.ABDM / National Health Authority ecosystem endpoints and other healthcare entities only through configured, authorised and consent-based workflows where applicable.
  • 14.Government, regulators, courts or law enforcement where disclosure is legally required or necessary to protect rights and safety.

6. Security and breach handling

15.Neptune applies security controls appropriate to the service and documented customer commitments. Controls may include role-based access, authentication, audit trails, encryption in transit, backup, monitoring and secure document storage, but each control must be verified against the production environment before this policy is published. We will notify affected hospital customers of a confirmed personal-data breach in accordance with the DPA, applicable law and agreed timelines, and cooperate with the hospital’s response.

7. Retention, rights and contact

16.Patient-record retention is primarily determined by the hospital’s legal and clinical obligations and its instructions, subject to applicable law, backup cycles, security-log requirements and legal holds. Website enquiry data is retained only as long as reasonably needed for the enquiry, relationship, legal and recordkeeping purposes; set a definite schedule before publication. Individuals should ordinarily direct patient-record access, correction, consent withdrawal or deletion requests to the hospital that provided care. For questions about Neptune’s own processing, contact info@neptunetechnolab.com or write to East - 207, Siddharaj Z Square, Kudasan, Gandhinagar, Gujarat 382421, India.

8. Children and representatives

17.Hospitals must configure and follow lawful guardian / representative workflows for children and persons unable to provide consent. Neptune’s software does not itself determine legal guardianship or clinical capacity. The hospital must verify the authority of the person acting on the patient’s behalf.

9. Legal framework and changes

18.This notice is intended to support compliance with applicable Indian privacy, information technology, healthcare and ABDM requirements, including the DPDP Act, 2023 and DPDP Rules, 2025 as and when relevant provisions commence. We may update this notice when processing, integrations or legal requirements change. Material changes affecting hospital processing should be communicated to customers and handled through the DPA / contract change process.

Document 2 of 14

2. SaaS Subscription & Hospital Customer Agreement

19.Template agreement between Neptune and a hospital, clinic, nursing home, diagnostic centre or other healthcare customer. Complete the commercial schedule and attach the DPA, SLA, data-retention schedule and implementation scope before signature.

1. Parties and order form

20.This Agreement is between Neptune Technolab Pvt. Ltd., having its registered / principal office at East - 207, Siddharaj Z Square, Kudasan, Gandhinagar, Gujarat 382421, India ("Provider"), and the healthcare facility identified in the Order Form ("Customer"). Effective date: [DATE]. Customer legal name, facility names, GSTIN, billing address, authorised signatory and contact details must be completed in the Order Form.

2. Service scope

21.Provider grants Customer a limited, non-exclusive, non-transferable right during the subscription term to access Neptune HMIS for its internal healthcare and administrative operations, according to the subscribed plan, configured modules, user limits, facilities, integrations and implementation scope. Modules may include registration, OPD, IPD, EMR, appointments, billing, pharmacy, laboratory / LIMS, nursing, OT, inventory, TPA / insurance, patient portal, MIS and ABDM-related workflows. Only modules listed in the Order Form are included.

3. Customer responsibilities

  • 22.Customer remains responsible for patient care, diagnosis, treatment, prescriptions, clinical decisions, medical-record accuracy, statutory registers, record retention and disclosures.
  • 23.Customer must provide patient notices, determine lawful purposes and legal bases, obtain and record required consents / authorisations, including specific ABDM consent where applicable.
  • 24.Customer must appoint authorised administrators, maintain user access, promptly remove leavers, protect credentials and configure least-privilege roles.
  • 25.Customer must validate migrated data, master data, templates, tax settings, pharmacy / lab configurations, reports and integrations before production use.
  • 26.Customer must maintain appropriate connectivity, endpoint security, power and local processes, and must not use HMIS as the sole emergency-care or life-critical mechanism.

4. Provider responsibilities

27.Provider will make the subscribed service available with reasonable skill and care, provide support as agreed, maintain reasonable technical and organisational safeguards, process customer data only for authorised service purposes, maintain agreed backups and cooperate with customer incident response, subject to the DPA and SLA.

5. Fees, taxes and payment

28.Fees, subscription period, onboarding, migration, customisation, training, additional facilities, integrations, support and renewal charges are set out in the Order Form. Fees are exclusive of applicable taxes unless expressly stated. Invoices are payable within [15] days. Late payment may attract [1.5% per month] or the maximum lawful rate, whichever is lower, after written notice. Disputed amounts must be raised within [15] days, with undisputed amounts paid on time.

6. Implementation and acceptance

29.The parties will agree a project plan, data templates, responsibilities, milestones, training and go-live checklist. Customer must review and sign off migrated data and configured workflows. Delays caused by incomplete customer data, third-party dependencies, delayed decisions or unavailable personnel extend the schedule reasonably. Custom development is governed by a separate statement of work.

7. Confidentiality and data processing

30.Each party will protect the other party’s confidential information. The DPA attached as Schedule A governs personal data processing and prevails over inconsistent general terms on that subject. Customer owns its patient and hospital data. Provider receives only the limited rights needed to host, process, secure, back up and support the service.

8. ABDM / external integrations

31.ABDM and third-party integrations depend on external systems, credentials, sandbox / production approvals, network availability, policies and interface changes. Provider does not control external uptime or decisions. Customer must ensure eligibility, registration, authorised access, correct patient matching and valid consent. No statement in this Agreement guarantees a government approval, certification or regulatory outcome unless expressly documented in a valid certificate or written commitment.

9. Intellectual property

32.Provider retains all rights in the software, source code, platform, documentation, generic improvements and pre-existing materials. Customer retains its data and its own materials. Customer may use outputs and reports generated for its internal operations, subject to third-party rights and the Order Form. No source-code transfer is included unless separately agreed.

10. Warranties and exclusions

33.Provider warrants that it will provide the service materially in accordance with the applicable documentation and SLA. Except as expressly stated and to the extent permitted by law, the service is provided without implied warranties of uninterrupted availability, error-free operation or fitness for a particular clinical purpose. Provider is not a medical practitioner and does not replace clinical judgement, professional standards or hospital governance.

11. Liability

34.Subject to applicable law, neither party is liable for indirect, incidental, special or consequential loss, loss of profit or loss of goodwill. Provider’s aggregate liability arising from this Agreement will not exceed fees paid or payable for the preceding [12] months. This cap does not apply to liabilities that cannot lawfully be limited and may be subject to negotiated carve-outs for confidentiality, data protection, IP infringement, fraud, wilful misconduct and payment obligations. The parties must obtain legal advice before finalising this clause.

12. Term, suspension and termination

35.Initial term: [12 months]. Renewal: [automatic / written renewal] for successive [12-month] periods unless notice is given at least [30/60] days before expiry. Either party may terminate for material breach not cured within 30 days after written notice, insolvency or unlawful performance. Provider may suspend access for serious security risk, unlawful use or overdue undisputed fees after reasonable notice, except where immediate action is necessary to protect systems or data.

13. Exit and governing law

36.On termination, Provider will make customer data export available in the agreed standard format for [30/60] days, subject to fees for bespoke extraction. After the export window and applicable retention period, Provider will delete or anonymise data under the DPA, subject to backups, legal holds and mandatory logs. Governing law: India. Courts at [Gandhinagar / Ahmedabad, Gujarat] shall have exclusive jurisdiction, subject to legal review and applicable law.

14. Schedules

  • 37.Schedule A – Data Processing Agreement.
  • 38.Schedule B – Service Level Agreement and support matrix.
  • 39.Schedule C – Order Form, fees, modules, facilities, users and subscription dates.
  • 40.Schedule D – Implementation, migration, training and acceptance criteria.
  • 41.Schedule E – Retention, export, backup and deletion schedule.
  • 42.Schedule F – Current subprocessor and integration register.

Document 3 of 14

3. Terms & Conditions – Neptune HMIS Application

43.These terms govern access to and use of the Neptune HMIS application by Customer and its authorised users. They should be incorporated by reference into the signed subscription agreement and displayed in the application.

1. Acceptance and authority

44.By signing the subscription agreement, accepting an Order Form or using an authorised account, Customer agrees to these terms. The person accepting on behalf of a hospital confirms that they have authority to bind that organisation. Individual users must comply with their employer’s policies and these terms.

2. Account security

45.Accounts are assigned to named users. Users must keep credentials confidential, use approved authentication methods, promptly report suspected compromise and must not share accounts. Customer administrators are responsible for assigning and reviewing permissions.

3. Permitted use

46.Customer may use the service only for its lawful healthcare, administrative and business operations, within its subscribed modules and facilities. Customer must comply with medical, pharmacy, laboratory, insurance, tax, privacy, cybersecurity, recordkeeping and ABDM requirements applicable to its activities.

4. Prohibited conduct

47.Users must not access another facility’s data without authority, bypass permissions, reverse engineer or copy the software, introduce malware, interfere with service availability, scrape or bulk extract data except through authorised export functions, use the service for unlawful surveillance or marketing, or submit false, misleading or unauthorised patient information.

5. Clinical and operational responsibility

48.Neptune HMIS is an administrative and record-management tool. It does not independently diagnose, prescribe, triage, recommend treatment or replace a qualified healthcare professional. The hospital and its professionals must independently verify patient identity, allergies, medication, test results, clinical notes, prescriptions, discharge records and other care decisions. Emergency care must not be delayed because of service unavailability.

6. Patient records and data ownership

49.Customer retains control of its patient and hospital data. Customer must ensure that it has authority to enter, process, disclose and share the data. Provider processes the data under the DPA and subscription agreement. Provider will not sell patient records or use identifiable patient data for unrelated advertising.

7. ABDM and consent workflows

50.ABHA creation, verification, linking and health-information exchange must follow applicable ABDM specifications and consent requirements. Users must not access, request, share or retrieve records without valid authorisation. A user must verify that the intended patient and recipient are correct before initiating a transaction.

8. Availability and changes

51.Availability commitments are set out in the SLA. Provider may perform maintenance, updates and security changes. Provider may change or discontinue a feature where necessary for security, legal compliance or technical reasons, and will give reasonable notice for material adverse changes where practicable.

9. Third-party services

52.The service may connect with ABDM, hosting, messaging, payment, laboratory, insurance and other third-party systems. Such services are governed by their own terms and may be unavailable or changed independently. Provider is not responsible for external systems beyond its reasonable control.

10. Suspension and termination

53.Access may be suspended for security incidents, unlawful activity, breach, non-payment or a material risk to other customers or systems. Provider will restore access when the cause is resolved. Termination, data export and deletion are governed by the subscription agreement and DPA.

11. Disclaimers, liability and disputes

54.The application does not guarantee clinical outcomes, reimbursement, claim approval, statutory compliance or uninterrupted connectivity. Liability limitations and dispute resolution are governed by the signed subscription agreement. Indian law applies; jurisdiction is [Gandhinagar / Ahmedabad, Gujarat], subject to contract and legal review.

12. Support and contact

55.For application support, use the support channel stated in your Order Form. For legal or privacy questions, contact info@neptunetechnolab.com.

Document 4 of 14

4. Data Processing Agreement (DPA)

56.This DPA applies when Neptune processes personal data on behalf of a hospital customer through Neptune HMIS. It must be signed or incorporated into the subscription agreement and completed with a data-flow and subprocessor schedule.

1. Roles and scope

57.Customer is ordinarily the Data Fiduciary / controller for patient and hospital operational data because it determines the care, administrative and legal purposes. Neptune acts as Data Processor / service provider to the extent it processes such data on Customer’s documented instructions. For website enquiries, Neptune acts independently as the entity determining the purpose. Actual roles must be assessed for each processing activity.

2. Subject matter, duration and purpose

58.Processing relates to provision, hosting, maintenance, support, security, backup, migration and integration of the HMIS service during the subscription and permitted post-termination period. Processing ends when data is returned or deleted, subject to mandatory retention, backup expiry and legal holds.

3. Data subjects and categories

59.Data subjects may include patients, guardians, doctors, nurses, pharmacists, laboratory staff, employees, vendors, visitors and customer users. Data may include identity and contact details, demographic data, health and clinical information, ABHA identifiers, appointment and admission details, prescriptions, diagnostic results, billing and insurance data, user credentials, audit logs and support communications. Customer must document any additional sensitive or special-category data.

4. Customer instructions and legal basis

60.Customer will ensure lawful collection, notices, consent or other lawful basis, purpose limitation, data minimisation, accuracy, retention and data-subject request handling. Neptune will process data only on documented instructions, including the subscription agreement, configuration, support requests and this DPA. If an instruction appears unlawful, Neptune will notify Customer unless prohibited by law.

5. Confidentiality and personnel

61.Neptune will ensure that personnel authorised to process customer data are bound by confidentiality obligations and receive role-appropriate privacy and security training. Access must be limited to personnel with a legitimate service need.

6. Security measures

62.Neptune will maintain appropriate technical and organisational measures, which may include access controls, least privilege, authentication, encryption in transit, vulnerability management, secure development, audit logging, backup, monitoring, incident response and staff confidentiality. The parties must attach a verified Security Measures Annex listing actual controls, encryption standards, backup frequency, hosting locations, recovery objectives and audit evidence. No control should be represented as implemented until verified.

7. Subprocessors

63.Customer authorises the subprocessors listed in the current register for the specified functions. Neptune will impose written data-protection obligations on subprocessors and remains responsible for its contractual obligations regarding their processing. Neptune will provide advance notice of material subprocessor changes and a reasonable objection process, as detailed in the subscription agreement.

8. Cross-border processing

64.Neptune will disclose hosting and support locations and will not transfer customer personal data outside India except as authorised by Customer and permitted under applicable Indian law, government restrictions, contract and any sectoral / ABDM requirements. Customer must approve the countries, data types and providers in the transfer schedule.

9. Data-subject requests

65.Customer is responsible for responding to patient and other data-subject requests. Neptune will provide reasonable technical assistance to locate, export, correct, restrict or delete data where the functionality and law permit. Neptune will not respond directly to a patient request unless instructed or legally required.

10. Personal-data breach

66.Neptune will notify Customer without undue delay after becoming aware of a personal-data breach affecting Customer data, with available details of nature, affected systems / categories, likely consequences, containment and remediation. The parties will cooperate on investigation, evidence preservation, legally required notices and communications. Customer remains responsible for notices to patients / regulators where law assigns that duty; Neptune will assist.

11. Audit and compliance information

67.On reasonable written request, Neptune will provide relevant information about its processing and security controls, subject to confidentiality, security and other customers’ rights. Any on-site audit must be planned, proportionate, limited to relevant systems and conducted under confidentiality and safety rules. Independent audit reports may be supplied where available.

12. Return and deletion

68.At termination, Neptune will make data available for export for the period in the subscription agreement. After that period, Neptune will delete or anonymise active copies in accordance with the retention schedule, subject to legal holds, immutable backups and mandatory logs. Backup copies will expire through the documented rotation cycle.

13. Assistance and precedence

69.Neptune will reasonably assist Customer with impact assessments, regulator queries and security incidents to the extent related to Neptune’s processing, at agreed rates for substantial additional work. This DPA prevails over inconsistent terms on personal-data processing. The DPA does not make Neptune responsible for Customer’s clinical or statutory duties.

Document 5 of 14

5. Data Retention & Secure Deletion Policy

70.This policy sets the framework for retention and secure deletion. It deliberately does not prescribe a single retention period for all medical records because the hospital’s clinical, statutory and state-specific obligations may differ.

1. Governing principles

71.Retain personal data only for as long as required for the documented purpose, applicable law, patient-care continuity, dispute resolution, audit, security and contractual obligations. The hospital customer must define record-specific retention schedules and remain responsible for the legal retention of patient records.

2. Responsibility split

72.Customer determines retention periods for patient medical records, prescriptions, lab reports, discharge summaries, billing, insurance claims, consent records and statutory registers. Neptune maintains platform data according to customer instructions and the agreed schedule, while retaining limited service, security and billing records as legally required.

3. Record categories

  • 73.Patient clinical records: hospital-defined schedule based on applicable central and state law, professional rules, accreditation requirements and litigation holds.
  • 74.ABDM consent and transaction artefacts: retain as required by applicable ABDM specifications, consent records and customer instructions.
  • 75.Billing, invoices and tax records: retain for applicable accounting and tax periods.
  • 76.User accounts and access logs: retain for security, audit and applicable legal requirements.
  • 77.Support tickets and communications: retain for the agreed support and dispute period.
  • 78.Backups: rotate and expire under the documented backup cycle; do not treat backup copies as a substitute for an accessible medical-record archive.

4. CERT-In logging

79.The CERT-In Directions of 28 April 2022 require covered entities to maintain ICT system logs securely for a rolling period of 180 days within Indian jurisdiction and report specified cyber incidents within six hours of noticing them. Neptune and Customer must each assess and meet obligations applicable to their own systems and roles. This statutory security-log requirement does not mean all patient medical records should be retained for only 180 days.

5. Deletion and anonymisation

80.Upon a valid customer instruction or expiry of the applicable retention period, Neptune will delete or irreversibly anonymise data from active systems within [30/60] days, subject to the agreed export window, legal holds, incident investigation, mandatory records and technical constraints. Backups will be deleted through the documented rotation schedule, proposed at [90] days after active deletion, only if verified in production.

6. Customer export and exit

81.Before termination, Customer should export patient records and related documents in supported formats and verify readability, completeness and integrity. Bespoke extraction, transformation or migration may be chargeable. Customer must securely store exported data and ensure continuity of patient care.

7. Holds and exceptions

82.Deletion may be paused where data is required by court order, regulator, law enforcement, legal hold, audit, security investigation or mandatory retention. Access to retained data must remain restricted and the reason documented.

8. Schedule to complete

  • 83.Define retention period by record category and applicable state / central rule.
  • 84.Confirm active database deletion SLA and backup expiry period.
  • 85.Confirm log types, location and 180-day retention coverage.
  • 86.Define customer export formats, fees and delivery timelines.
  • 87.Document legal-hold approval, authorisation and release process.

Document 6 of 14

6. Information Security Policy

88.Internal policy template for the people and systems that build, host, operate and support Neptune HMIS. Publish externally only as a high-level security overview after verifying actual controls.

1. Governance

89.Management will assign accountable owners for information security, privacy, infrastructure, application development, incident response and vendor management. A current asset inventory, risk register, system diagram and data-flow register must be maintained.

2. Access management

90.Use named accounts, least privilege, role-based access, strong authentication, prompt joiner/mover/leaver processes, periodic access reviews and emergency access controls. Production access must be approved, logged, time-bound where practicable and reviewed.

3. Data protection

91.Classify patient health information and identifiers as highly sensitive operational data. Use encryption in transit and appropriate encryption at rest, secure key management, masking in non-production, restricted exports and approved secure transfer channels. Confirm the actual algorithms and key lifecycle before making public claims.

4. Application security

92.Follow secure coding practices, peer review, dependency scanning, secrets management, environment separation, change approval, vulnerability remediation and controlled deployment. Do not use live patient data in development or testing unless specifically authorised and protected.

5. Infrastructure and network

93.Maintain hardened cloud resources, network segmentation, firewall rules, administrative access restrictions, patching, endpoint protection, monitoring and secure configuration. Record hosting region, backup region and any cross-border access.

6. Backup and recovery

94.Define backup frequency, encryption, restoration tests, recovery time objective (RTO) and recovery point objective (RPO). Test restoration periodically and retain evidence. The proposed SLA values must not be published until the infrastructure team confirms them.

7. Logging and monitoring

95.Log authentication, privileged actions, access to patient records, exports, configuration changes and security events where technically feasible. Protect logs against tampering and restrict access. Meet applicable CERT-In requirements, including 180-day rolling log retention in India where applicable.

8. Incident response

96.Maintain a 24x7 escalation path appropriate to the service, incident severity matrix, evidence-preservation procedure, customer communication template and regulatory reporting checklist. Specified cyber incidents may require CERT-In reporting within six hours. Do not wait for a full forensic report before making a legally required initial report.

9. Personnel and physical security

97.Use confidentiality agreements, onboarding/offboarding controls, security awareness training, clean desk practices, secure devices, visitor controls and secure disposal of media.

10. Business continuity and vendor oversight

98.Maintain continuity plans for cloud outages, network disruption, ransomware, key-person unavailability and critical third-party failure. Assess vendors before onboarding and periodically thereafter; review access, certifications, breach terms, data locations and exit capability.

11. Audit and review

99.Review this policy at least annually and after major incidents, material architecture changes or legal updates. Record exceptions, approvals, remediation owners and due dates. Never claim ISO 27001, SOC 2, HIPAA or other certification unless a current certificate / report exists and its scope covers the relevant service.

Document 7 of 14

7. Subprocessors & Third-Party Services

100.Maintain this register as a live attachment to the DPA and make it available to hospital customers. The website identifies integration categories, but it does not publicly confirm every vendor name or the production data flow.

1. Register fields

  • 101.Provider legal name and product / service.
  • 102.Purpose: cloud hosting, database, backup, email, SMS, WhatsApp, payment, analytics, support, monitoring, laboratory device, insurance / TPA or ABDM integration.
  • 103.Data categories disclosed and whether patient health information is involved.
  • 104.Processing / storage country and support access locations.
  • 105.Security and privacy terms, breach notification commitment and deletion / exit process.
  • 106.Subprocessor appointment date, review date and status: active / pilot / planned / retired.

2. Current public integration categories

107.Neptune HMIS website lists payment gateways, SMS, WhatsApp, email, laboratory-device integrations, accounting software, insurance / TPA and ABDM / healthcare APIs. These are categories, not confirmation of a specific vendor or that every integration is enabled for every customer. Only list providers actually used in production.

3. ABDM ecosystem

108.Identify the relevant ABDM gateway / ecosystem endpoints and data exchanges in the technical architecture. Document the facility’s HIP / HIU configuration, credentials, consent artefacts, transaction logs, patient matching and data-sharing flows. Do not list ABDM as a commercial subprocessor without first confirming the correct legal and technical role.

4. Change management

109.Give customers advance notice of material new subprocessors where required by contract. Provide a reasonable objection route and explain the impact if an objection cannot be resolved. Update the register before the new provider receives customer data.

5. Initial register – completion required

  • 110.Cloud / hosting provider: [LEGAL NAME, REGION, SERVICE, DATA TYPES].
  • 111.Database / object storage / backup: [PROVIDER, REGION, DATA TYPES].
  • 112.Email / SMS / WhatsApp provider: [PROVIDER, MESSAGE TYPES, DATA TYPES].
  • 113.Payment gateway: [PROVIDER, PAYMENT DATA / TOKEN FLOW].
  • 114.Monitoring / error tracking / support: [PROVIDER, LOG DATA, ACCESS COUNTRY].
  • 115.ABDM and other health integrations: [ENDPOINT / ECOSYSTEM, PURPOSE, DATA FLOW].
  • 116.Other vendors: [LIST].

Document 8 of 14

8. Service Level Agreement (SLA)

117.The following is a proposed service-level framework, not a statement of current measured uptime. Confirm infrastructure capacity, support staffing, escalation arrangements and maintenance practice before adopting these values.

1. Availability target

118.Proposed monthly availability target: 99.5%, excluding scheduled maintenance, emergency security maintenance, customer-side connectivity or devices, force majeure, third-party / government systems, customer misconfiguration and events outside Provider’s reasonable control. Calculate availability at the application service boundary and define measurement method before signing.

2. Severity levels

  • 119.P1 – Critical: HMIS unavailable to all users at a facility, major security incident or critical workflow outage with no reasonable workaround. Acknowledge within 1 business hour; target workaround / restoration updates every 2 hours.
  • 120.P2 – High: major module unavailable or severe degradation affecting multiple users, with limited workaround. Acknowledge within 4 business hours; updates at reasonable intervals.
  • 121.P3 – Medium: non-critical feature issue affecting a limited set of users, with workaround available. Acknowledge within 1 business day.
  • 122.P4 – Low / request: how-to, configuration, enhancement or general query. Acknowledge within 2 business days.

3. Support hours and channels

123.Proposed standard support: Monday to Saturday, [9:00 AM–6:00 PM IST], excluding public holidays. P1 escalation: [24x7 phone / email / ticket channel – confirm before promising]. Contact details and escalation ladder must be included in each Order Form.

4. Maintenance

124.Provider may perform planned maintenance with at least [48] hours’ notice where practicable. Emergency maintenance may occur without advance notice where required to protect data or service integrity. Maintenance windows and exclusions must be clearly communicated.

5. Backups and recovery

125.Proposed targets for technical validation: database backup every [24 hours], RPO [24 hours], RTO [8 business hours]. These are not guarantees until confirmed by operations, tested and accepted in the Order Form. Define separate targets for documents, attachments and integrations.

6. Service credits

126.Optional proposed credit: 5% of monthly recurring subscription fee if availability falls below 99.5% but is at least 99.0%; 10% if below 99.0%. Cap at 10% of the affected monthly recurring fee. Claims must be submitted within 15 days after month end. Credits are the agreed remedy for availability shortfall, except where law requires otherwise. Do not use credits if the commercial model does not support them.

7. Customer duties and exclusions

127.Customer must provide timely logs, screenshots, affected user details, connectivity checks and authorised access. Service levels do not cover issues caused by customer devices, local networks, third-party systems, ABDM gateway, telecom providers, power failure, customer changes, unsupported configurations or force majeure.

8. Clinical continuity

128.Hospitals must maintain downtime procedures for registration, prescriptions, medication administration, lab orders, critical results, emergency care and discharge. The SLA is not a substitute for hospital business-continuity and patient-safety procedures.

Document 9 of 14

9. Refund, Suspension & Cancellation Policy

129.This policy should be attached to the Order Form and aligned with the subscription term, payment schedule, onboarding costs, custom development and applicable consumer / contract law.

1. Subscription cancellation

130.Customer may request non-renewal by giving [30/60] days’ written notice before the end of the then-current subscription term. Unless the Order Form states otherwise, subscription fees are billed in advance and are non-refundable after the service period begins, except where required by law or expressly agreed.

2. Refund eligibility

131.A refund may be considered where Provider fails to deliver a material contracted service and does not cure the failure within the agreed cure period, where duplicate payment is received, or where a refund is required by applicable law. Approved refunds will be processed to the original payment method within [15] business days, subject to payment-provider timelines.

3. Non-refundable work

132.Completed onboarding, data migration, training, customisation, third-party charges, travel, hardware, taxes and professional services are non-refundable to the extent lawfully permitted and disclosed in the Order Form. Work not yet performed may be refunded or credited as agreed.

4. Suspension for non-payment

133.Provider may suspend access for overdue undisputed invoices after written notice and a reasonable cure period of [15] days. Before suspension, the parties should agree an urgent patient-care continuity and data-export plan. Provider will not intentionally withhold patient records where prohibited by law.

5. Termination for cause

134.Either party may terminate for material breach not cured within 30 days after notice, insolvency or unlawful performance. Provider may terminate immediately where continued access creates an imminent security or legal risk, subject to applicable law and reasonable mitigation.

6. Data export and deletion

135.Customer may export its data during the subscription and for [30/60] days after termination, subject to agreed formats and charges for bespoke work. After the export period, Provider will delete or anonymise data according to the DPA and retention policy, subject to legal holds, mandatory logs and backup expiry.

7. How to request

136.Send a cancellation or refund request from an authorised customer contact to info@neptunetechnolab.com, including hospital name, Order Form / invoice number, reason, requested effective date and bank / payment details if required. Never send patient records or unnecessary health information in a refund request.

Document 10 of 14

10. Acceptable Use Policy

137.This policy applies to all hospital customers, administrators, clinicians, employees, contractors and other authorised users of Neptune HMIS.

1. Permitted use

138.Use HMIS only for authorised healthcare, facility administration, billing, records, diagnostics, pharmacy, insurance, reporting and other contracted purposes. Access only the patients, facilities and modules necessary for your role.

2. Patient privacy and confidentiality

139.Access patient information only where you have a legitimate care or administrative need and authority. Do not browse records out of curiosity, disclose records to unauthorised persons, use patient contact details for personal marketing or export bulk records without approval.

3. Consent and ABDM

140.Do not create, link, retrieve or share ABHA-linked records or health information without following the required patient identification, consent and authorisation process. Confirm the intended patient and recipient before each share or retrieval.

4. Clinical accuracy and safety

141.Enter accurate information, verify patient identity and review critical information before acting. Do not rely on auto-populated data without verification. Do not use HMIS as a substitute for professional judgement, emergency protocols or statutory clinical documentation.

5. Prohibited activity

  • 142.Credential sharing, impersonation or unauthorised privilege escalation.
  • 143.Malware, phishing, penetration testing or vulnerability scanning without written authorisation.
  • 144.Unauthorised extraction, copying, sale or disclosure of patient data.
  • 145.Altering audit logs, falsifying clinical entries or concealing a record change.
  • 146.Using the platform to discriminate, harass, stalk or unlawfully profile patients.
  • 147.Attempting to disrupt service or access another customer’s tenant.

6. Incident reporting

148.Immediately report suspected unauthorised access, lost devices, misdirected reports, ransomware, suspicious exports, compromised credentials or incorrect patient sharing to the hospital administrator and the designated Neptune support / security contact. Preserve evidence and do not delete logs.

7. Enforcement

149.Customer administrators may disable accounts or investigate misuse. Provider may suspend access to protect patients, data or service integrity. Serious violations may result in termination and referral to appropriate authorities.

Document 11 of 14

11. Cookie Policy

150.This policy covers the public neptunehmis.com website and, once verified, the authenticated HMIS application, patient portal and related subdomains. The live website currently states that the marketing website sets no cookies or browser storage and uses Google Fonts; re-check this before publication.

1. Public website

151.The current public website notice states that the marketing website does not set cookies, local storage, session storage, analytics or advertising trackers. It also states that Google Fonts are loaded from Google domains, which may disclose request metadata such as IP address to Google. This description must be re-tested after website updates.

2. Application and patient portal

152.The application may require strictly necessary session, authentication, security, load-balancing or preference technologies. List each cookie / storage key, provider, purpose, duration, first- or third-party status and whether it is essential. Do not assume the website’s no-cookie statement applies to app.neptunehmis.com or patient-facing apps.

3. Analytics and optional technologies

153.If analytics, chat, advertising, session replay, CAPTCHA or marketing tools are introduced, identify the provider, data collected, purpose, retention and consent / opt-out mechanism where required. Avoid session replay or analytics capture of patient clinical screens and form fields.

4. Third-party links

154.WhatsApp, Google Maps, payment gateways, ABDM and other external services apply their own privacy and cookie policies when a user follows or activates those services. Explain any embedded content separately.

5. User controls

155.Where non-essential cookies or similar technologies are used, provide a clear preference mechanism and honour choices. Strictly necessary security and authentication storage may be required for the service. Browser controls may also be used to block or delete cookies.

6. Updates and contact

156.Update this policy before enabling a new tracker or non-essential technology. Questions can be sent to info@neptunetechnolab.com.

Document 12 of 14

12. Grievance Redressal & Privacy Contact

157.This document establishes a single channel for privacy, security and service grievances. Assign a named grievance officer before publication; do not leave placeholders on the live site.

1. Grievance contact

158.Organisation: Neptune Technolab Pvt. Ltd.. Address: East - 207, Siddharaj Z Square, Kudasan, Gandhinagar, Gujarat 382421, India. Email: info@neptunetechnolab.com. Telephone: +91 95373 15640. Grievance Officer: [FULL NAME / DESIGNATION]. Dedicated grievance email: [privacy@ / grievance@ – create and test before publication].

2. Scope

159.This channel accepts complaints about Neptune’s website enquiry processing, HMIS service administration, suspected unauthorised access by Neptune personnel, privacy notices, security communications, data export / deletion assistance and other issues within Neptune’s control. Patient-care complaints, medical-record corrections and clinical disputes should first be directed to the hospital / healthcare facility.

3. Information to provide

160.Provide your name, preferred contact method, hospital / facility (if relevant), a concise description, approximate date, relevant ticket / account reference and the action requested. Do not email full medical records, Aadhaar numbers, passwords or unnecessary sensitive information.

4. Acknowledgement and response

161.Proposed internal target: acknowledge within 2 business days and provide a substantive response within 30 days, or explain the reason for delay and expected response date. Confirm whether any shorter statutory timeline applies to the specific complaint and comply with it.

5. Escalation

162.If unresolved, escalate to [Managing Director / designated senior officer] at [EMAIL]. For matters involving a hospital’s decisions as Data Fiduciary, Neptune will refer the individual to the hospital’s designated privacy / grievance contact, while cooperating with the hospital as required.

6. Security incidents

163.Urgent security incidents should be reported through [24x7 incident contact / phone]. The grievance mailbox is not an emergency response channel. Internal teams must preserve evidence and assess statutory reporting obligations, including CERT-In timelines where applicable.

Document 13 of 14

13. Privacy Rights / Patient Data Request Procedure

164.This procedure explains how a patient, guardian, customer user or other individual may request access, correction, erasure or other action relating to personal data. The correct recipient depends on who determines the purpose of processing.

1. Where to send a request

165.For patient records, clinical notes, prescriptions, lab results, discharge summaries, billing and ABDM-linked health information, contact the hospital / facility that provided care. The hospital is ordinarily the entity deciding the purpose and must verify identity and authority. For information submitted directly to Neptune’s public website, contact Neptune at the details below.

2. Requests Neptune can assist with

166.Where Neptune hosts or processes data on the hospital’s behalf, it can assist the hospital with locating records, producing exports, correcting data on authorised instruction, applying access restrictions, recording consent withdrawal instructions and deleting data where permitted. Neptune will not independently change clinical records or override a hospital’s lawful retention obligation.

3. Identity and authority verification

167.The hospital or Neptune may request proportionate information to verify the requester and, where relevant, guardian, nominee or authorised representative status. Do not send Aadhaar copies or full medical records unless specifically necessary and securely requested. Use the hospital’s approved identity verification channel.

4. Request details

  • 168.Full name and safe contact details.
  • 169.Hospital / facility and approximate date of visit or account reference.
  • 170.Type of request: access / copy, correction, erasure, consent withdrawal, restriction, grievance or other.
  • 171.Specific record or processing activity concerned and preferred response method.
  • 172.Proof of authority if acting for a child or another person, submitted through a secure channel.

5. Handling and timelines

173.The hospital must assess the request under applicable law, clinical-record rules, ABDM requirements and its privacy notice. Neptune will respond to a valid customer instruction within the DPA timeframe. Any refusal or limitation should explain the legal or operational reason and available escalation route, without disclosing another person’s information.

6. Consent withdrawal and ABDM

174.A patient may withdraw or modify consent through the applicable ABDM / consent workflow where available. Withdrawal does not automatically erase records already lawfully created or remove a hospital’s independent statutory retention duties. The hospital must explain the effect and stop future sharing where required.

7. Contact

175.Neptune privacy contact: info@neptunetechnolab.com. Postal address: East - 207, Siddharaj Z Square, Kudasan, Gandhinagar, Gujarat 382421, India. For a patient record request, contact the relevant hospital first.

Document 14 of 14

14. Cookie Preference Notice / Preference Mechanism

176.A preference notice is useful only if the website or application actually uses optional cookies or similar technologies. The current public website states that it sets none; therefore do not display a misleading consent banner unless the technical behaviour changes.

1. Current public website position

177.Based on the live Cookie Policy, the public marketing website currently states that it sets no cookies, local storage, session storage, analytics or advertising trackers. If this remains technically accurate, a non-essential cookie preference banner is not required for that website and the notice should simply explain the position.

2. Application preference controls

178.If the HMIS application or patient portal uses optional analytics, embedded media, chat or other non-essential technologies, provide controls to accept all, reject all and customise by category. Do not bundle optional technologies with essential authentication or security storage.

3. Suggested categories

  • 179.Strictly necessary: authentication, security, load balancing and core session continuity; always enabled where essential.
  • 180.Preferences: remember user-selected language, display or layout settings.
  • 181.Analytics: measure service performance only if enabled and approved.
  • 182.Marketing: advertising or campaign measurement only if introduced and legally permitted.

4. Preference record

183.If preferences are collected, record the choice, timestamp, notice version and relevant consent evidence without collecting unnecessary patient data. Provide a persistent link to change or withdraw preferences. Re-prompt only when purposes or technologies materially change or after a reasonable period.

5. Suggested banner wording

184.“We use essential technologies to keep Neptune HMIS secure and working. Optional technologies, if enabled, help us understand usage or remember preferences. You can accept all, reject optional technologies or manage your choices. See our Cookie Policy for details.” Use this wording only when optional technologies are actually deployed.

6. Implementation checklist

  • 185.Scan website, app and patient portal separately for cookies, local/session storage, SDKs, pixels and third-party requests.
  • 186.Maintain a cookie / storage inventory with owner, purpose, duration and provider.
  • 187.Verify consent state is respected before optional tags fire.
  • 188.Test reject, accept, withdraw and preference persistence.
  • 189.Update the public Cookie Policy and this notice before deploying new trackers.

Made in India

Proudly Made in India

Designed, developed & supported in India. Built for Indian hospitals of every size.

  • Designed

    in India, around how Indian hospitals work

  • Developed

    by Neptune Technolab Pvt. Ltd., Gandhinagar

  • Supported

    by our own team, here in India

  • Built for India

    ABDM, TPA & government schemes and UPI payments, built in

Book Demo