# Publication And Compliance Checklist

This checklist reduces foreseeable licensing, privacy, and product-positioning
risks. It is not legal advice and does not replace review by a qualified
lawyer or medical-device regulatory professional.

## Required For Every Public Release

- Publish the complete application source, not only a minified or bundled copy.
- Include `LICENSE`, `NOTICE.md`, `THIRD_PARTY_NOTICES.md`, and `SOURCE.md`.
- Keep the SimTIVA and Terence Luk attribution and the modification notice.
- Keep the Chart.js MIT notice in `vendor/Chart.js-LICENSE.md`.
- Link the running application to `legal.html` and `source.html`.
- Regenerate `tci-simulator-source.zip` after every code change.
- Mark modified versions and their release date.
- Do not imply that SimTIVA, Terence Luk, Open TCI, STANPUMP, or the
  pharmacokinetic model authors endorse this application.

## Medical-Device Boundary

- Market and describe this release only as an unvalidated educational,
  research, and software-testing simulation.
- Do not claim that it recommends, verifies, or calculates a clinically
  appropriate dose for an individual patient.
- Do not connect it to, drive, or control an infusion pump.
- Do not use screenshots or promotional copy showing the output as a
  substitute for clinical judgment or an approved TCI system.
- Stop before clinical commercialization or deployment in patient care and
  obtain a formal medical-device qualification and classification assessment.

Software intended to provide information used for therapeutic decisions may
fall under medical-device software rules. A disclaimer alone does not override
the application's actual intended purpose, features, instructions, or
marketing claims.

## Privacy And Hosting

- Confirm that no analytics, advertising, form, or telemetry script has been
  added without updating `legal.html`.
- If feedback is later transmitted to a server, publish a controller identity,
  lawful basis, retention period, recipients, security details, and a contact
  channel before enabling transmission.
- Avoid collecting identifiable patient data.
- Document the hosting provider's access logs, retention, and applicable data
  processing terms.
- Add a cookie consent mechanism only if non-essential cookies or similar
  tracking technologies are introduced.

## Ownership And Branding

- Confirm that every contributor had the right to contribute their work.
- Check employment, university, or contractor agreements for competing
  ownership claims.
- Perform a trademark and domain-name clearance for the final product name.
- Keep records of source versions, release dates, tests, and third-party
  licenses.

## Commercial Use

GPL permits charging for copies, hosting, support, and related services. When
you distribute the software, recipients retain the GPL rights to access,
modify, and redistribute the corresponding source. Do not advertise the
distributed client code as proprietary or impose terms that contradict those
rights.