How healthcare legal teams use Justis AI
Hospital legal work is a reading problem. A negligence notice arrives and the answer is in a case sheet of three hundred handwritten pages. An inspection is due and the licences for six units sit in six folders with six renewal dates. A trial site agreement, a consultant's contract and a device supply agreement all wait on the same two people, and each one answers to a different regulator.
Justis reads the record with you. Upload the file to a project and it reads every page, handwritten notes and scans included, sets the facts against the rule that applies, and drafts the reply or the redline. Every conclusion carries the document and page it came from, and where an entry is illegible or a point of law is unsettled, it says so rather than filling the gap.
01
A negligence notice, read against the case sheet
The problem
A legal notice or a consumer complaint alleges a sequence: delayed diagnosis, no consent, a missed referral, a discharge too early. The answer is in the case sheet, the nursing notes, the anaesthesia record and the discharge summary, much of it handwritten, and the treating team remembers it differently from how it was written.
Under the Consumer Protection Act 2019 the written version is due within thirty days of service, extendable by no more than fifteen, so there is little time to read the record twice.
How Justis handles it
Upload the complaint and the medical record. Justis reads both, runs OCR on the handwritten pages and tells you when it is doing so, then sets each allegation against what the record shows, with the page on each side.
It marks entries that are undated, overwritten or missing, which matter as much as what the record says, checks the forum's pecuniary jurisdiction and the limitation period, and drafts the written version in your format.
| What comes back | Example |
|---|---|
| Record read | Case sheet of 286 pages, 212 handwritten, read by OCR |
| Allegation holds | No fresh consent for the second procedure on 06.02.2026; only the first consent is on file (p. 41) |
| Allegation fails | Referral to cardiology within 36 hours, recorded in the nursing notes at p. 118 |
| Record risk | Two progress notes undated and one overwritten, pp. 131 and 134 |
| Forum and time | Served 02.09.2026: written version due 02.10.2026, outer limit 17.10.2026 |
| Deliverable | Draft written version in Word with a list of dates |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Read the complaint and the full medical record in this project. For each allegation, say whether the record supports it, with the page on each side, list any undated, overwritten or missing entries, and compute the deadline for the written version from service on 2 September 2026.
02
Auditing consent forms across departments
The problem
Each department has its own consent forms, some printed years ago, some translated by whoever was available. Consent is specific to the procedure consented to, and a form that says 'any further procedure the doctor considers necessary' does not protect the hospital when the further procedure is the one in dispute.
Nobody has read all of them side by side, and a gap is usually found by the claimant's lawyer first.
How Justis handles it
Tabular review reads every consent form in one pass and asks the same questions of each: the procedure named, risks and alternatives set out, language versions, the witness line, and blanket clauses. Each cell cites the page.
Justis then drafts a revised template for each department, in English and Hindi where you need both, and a short note for the clinical teams on what changed and why.
| What comes back | Example |
|---|---|
| Forms read | 38 consent forms across 11 departments, 14 scanned |
| Blanket clause | 17 forms authorise 'any further procedure', flagged for procedure-specific wording |
| Risks and alternatives | 9 forms list neither |
| Language | Hindi version of the anaesthesia form omits two risks listed in English |
| Deliverables | Grid in Excel with a cited cell for each answer, and revised templates in Word |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Run a tabular review of every consent form in this project. For each, extract the procedure named, the risks and alternatives disclosed, the language versions and any blanket authorisation, compare the Hindi and English versions, and flag every form that would not support procedure-specific consent.
03
The licence register for every unit
The problem
A hospital runs on registrations and clearances: the clinical establishment registration under the state Act, biomedical waste authorisation, the fire NOC, AERB licences for imaging, PC-PNDT registration, drug licences for the pharmacy and the blood centre licence. Each has its own renewal date and its own conditions.
They are scanned into different folders by different units, and the register that tracks them is a spreadsheet last updated before the new wing opened.
How Justis handles it
Upload the licences and tabular review returns a register: the licence, the unit, the authority, the expiry date and the conditions attached, with the document and page behind each row.
Justis flags what has lapsed or will lapse within the window you choose, lists the conditions a unit may not be meeting, and drafts the renewal cover letters for your team to file.
| What comes back | Example |
|---|---|
| Documents read | 54 licences and clearances across 4 units |
| Lapsed | Fire NOC for the main block, expired 12.02.2026 |
| Due within 90 days | AERB licence for the CT unit and the biomedical waste authorisation |
| Condition at risk | PC-PNDT registration lists two machines; the imaging inventory shows three |
| Deliverables | Licence register in Excel and renewal cover letters in Word |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Read every licence and registration in this project and build a register by unit: licence, issuing authority, expiry date and attached conditions, with the page for each. Flag anything lapsed or expiring in the next 90 days and any condition the unit may not be meeting.
04
Consultant and doctor engagement agreements
The problem
Visiting consultants are engaged on dozens of agreements: fixed retainers, fee-for-service, revenue shares. A share tied to referred diagnostics looks like a commission for referrals, which the professional conduct regulations for doctors prohibit, and an uncapped indemnity for clinical acts puts the hospital's balance sheet behind a doctor it does not employ.
The agreements were negotiated one at a time, and nobody knows how many carry which terms.
How Justis handles it
Your positions go into a playbook once: how compensation may be structured, who indemnifies whom and up to what cap, what insurance the doctor carries, and how patient data may be used. Every agreement is read against it, the offending clause is quoted back, and your position is already drafted.
Across the whole set, tabular review shows which agreements carry which terms, and the redlines arrive as tracked changes in Word.
| What comes back | Example |
|---|---|
| Agreements read | 126 consultant agreements on 5 templates |
| Referral-linked pay | 8 agreements pay a share of revenue from referred imaging, flagged under the professional conduct regulations |
| Indemnity | 31 agreements have the hospital indemnifying clinical acts without a cap |
| Insurance | 19 agreements silent on professional indemnity cover |
| Deliverables | Grid in Excel, and tracked-change redlines in Word against your playbook |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Review every consultant agreement in this project against our playbook. Flag compensation linked to referrals, one-sided or uncapped indemnities, missing professional indemnity cover and patient data terms, quote each clause with its page, and redline to our positions as tracked changes.
05
Clinical trial agreements at the site
The problem
A sponsor sends a clinical trial agreement drafted for another jurisdiction. The New Drugs and Clinical Trials Rules 2019 require free medical management for trial-related injury and compensation for injury or death as the Central Licensing Authority determines, and the draft caps the sponsor's liability, routes compensation through the site's insurance and says nothing about the ethics committee's registration.
The site signs as a party, and its liability for a sponsor's obligations is the question the legal team is asked to answer by Friday.
How Justis handles it
Justis reads the agreement, the protocol synopsis, the insurance certificate and the ethics committee approval together, and checks each obligation against the Rules: who pays for medical management and compensation, the ethics committee's registration, trial registration before enrolment, and the site's record retention duties.
It marks the clauses that shift a sponsor obligation to the site, drafts the redline and a short note for the investigator on what the site is agreeing to.
| What comes back | Example |
|---|---|
| Documents read | Agreement of 48 pages, protocol synopsis, insurance certificate, EC approval |
| Compensation | Clause 11 caps sponsor liability at the budget; the Rules leave the amount to the licensing authority |
| Medical management | Clause 11.3 routes costs through the site's insurance; flagged as a sponsor obligation |
| Ethics committee | Registration number not in the approval letter; asked for before signing |
| Deliverables | Redline in Word and a one-page note for the principal investigator |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Read the clinical trial agreement, the protocol synopsis, the insurance certificate and the ethics committee approval. Check each obligation against the New Drugs and Clinical Trials Rules 2019, mark every clause that shifts a sponsor obligation to the site, and redline it.
06
Supply agreements for drugs and devices
The problem
Procurement signs supply agreements for implants, consumables and equipment on the vendor's paper. Under the Medical Devices Rules 2017 every class of device now needs a licence to import or manufacture, and drugs move only through licensed wholesalers under the Drugs and Cosmetics Act. A vendor without the right licence leaves the hospital holding stock it should not have bought.
The agreements also rarely say who manages a recall, who bears the cost, or what happens to traceability records for implants.
How Justis handles it
Justis reads the agreement with the vendor's licences and checks that the licence covers the product, its class and the premises, and is current. It tests the agreement against your procurement playbook on recall, warranty, traceability, indemnity and liability caps.
It lists what to ask the vendor for before signing and drafts the redline in Word.
| What comes back | Example |
|---|---|
| Product | Orthopaedic implants, Class C devices, imported |
| Licence | Vendor's import licence covers the knee system but not the new hip range listed in Schedule 2 |
| Recall | Agreement silent on recall cost and notification |
| Traceability | No obligation to supply lot and serial numbers for each implant |
| Deliverables | List of documents to request from the vendor, and a redline in Word |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Read this supply agreement and the vendor's licences. Check that each product listed is covered by a current licence under the Medical Devices Rules 2017 or the Drugs and Cosmetics Act for its class, test the agreement against our playbook on recall, traceability and indemnity, and redline it.
07
A patient data breach
The problem
The IT team reports unauthorised access to the lab system. CERT-In's 2022 directions require the incident to be reported within six hours of noticing it, and the Digital Personal Data Protection Act 2023 and the Rules 2025 add intimation to the Data Protection Board and to each affected patient as their obligations come into force.
The facts arrive in pieces: a log export, a vendor's email, a count of records that changes every hour. Someone has to keep the timeline straight while it is still moving.
How Justis handles it
Justis builds the incident timeline from the documents as they land, marks the rule each step answers to and the time it was due, and says which obligations apply today and which apply once the DPDP Rules take effect.
It reads the vendor contract for notification and indemnity terms, drafts the reports and the patient notice for your team to review and send, and keeps the record of what was known when.
| Step | Example |
|---|---|
| Detected | Unauthorised access noticed 12.01.2026 at 09:40, from the SOC ticket |
| CERT-In | Report due within six hours; draft ready, facts still unconfirmed marked |
| Scope | 2,140 patient records, including lab results, from the log export |
| Vendor | Lab software contract: vendor must notify within 24 hours; notified on day 3, clause 9.2 |
| Deliverables | Incident timeline, draft CERT-In report, draft patient notice, note on DPDP duties |
Illustrative example. Names, figures and dates are invented; the provisions are real.
Build the incident timeline from the documents in this project, with the rule each step answers to and when it was due. Say which reporting obligations apply now under CERT-In's directions and the DPDP Act, read the vendor contract for notification terms, and draft the reports for our review.
Make it repeatable
A claim, a unit or a contract set stays in its own project. Every document you add is read as it lands, so the question asked when the matter reaches the State Commission is answered across the whole record, not the part someone attached.
When the same work comes back, save it once. A playbook carries your positions on consultant pay, indemnities and patient data; a workflow carries the steps from notice to written version; a skill carries a method, such as the way you check a consent form, and you can attach it to any message.
- An allegation-by-allegation check for every negligence notice
- A licence register refreshed every quarter, by unit
- A consultant agreement playbook applied to every renewal
- A trial agreement checklist run before the site signs
- Committee meetings and hearings, in English or Hindi, transcribed into the file
