<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/in/rss-styles.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hospital AI Lab</title><description>Columns on the regulation of medical AI in India: CDSCO’s device software guidance, the DPDP Act and ICMR’s AI guidelines.</description><link>https://hospital-ai-lab.com/in/</link><language>en</language><atom:link href="https://hospital-ai-lab.com/in/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Mon, 16 Nov 2026 00:00:00 GMT</lastBuildDate><item><title>DPDP Act: what a hospital owes patients after a data breach</title><link>https://hospital-ai-lab.com/in/blog/2026-11-16-dpdp-act-data-breach-security-safeguards-hospital/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-16-dpdp-act-data-breach-security-safeguards-hospital/</guid><description>If an AI vendor&apos;s system leaks patient data, who must be told? A plain reading of DPDP Act sections 8(4) to 8(6) and the Schedule penalties.</description><pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Picture the call: an AI vendor tells the hospital that a test server holding patient records was open to the internet over the weekend. The first questions are practical. What counts as a “breach”? Who must be told, and by when? India’s Digital Personal Data Protection Act, 2023 answers some of this and leaves the rest to rules. This post reads only the Act itself, as published in the Gazette of India, and says plainly what it does not settle.&lt;/p&gt;
&lt;h2 id=&quot;what-counts-as-a-breach&quot;&gt;What counts as a breach&lt;/h2&gt;
&lt;p&gt;Section 2(u) defines a “personal data breach” as any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to it, that compromises its confidentiality, integrity or availability. Notice that it covers more than theft. Records that become unavailable, or that are changed without authority, are also within the definition.&lt;/p&gt;
&lt;h2 id=&quot;the-duty-to-keep-data-safe&quot;&gt;The duty to keep data safe&lt;/h2&gt;
&lt;p&gt;Section 8(5) says a data fiduciary (the body that decides why and how personal data is processed, which includes a hospital) must protect personal data in its possession or under its control by taking reasonable security safeguards to prevent a personal data breach. The same sentence covers processing done on its behalf by a data processor. In plain terms, using a vendor does not move the responsibility away from the hospital.&lt;/p&gt;
&lt;p&gt;Section 8(4) adds that the fiduciary must put in place appropriate technical and organisational measures so that the Act and its rules are actually followed.&lt;/p&gt;
&lt;h2 id=&quot;the-duty-to-tell&quot;&gt;The duty to tell&lt;/h2&gt;
&lt;p&gt;Section 8(6) says that if a breach happens, the data fiduciary must give the Data Protection Board and each affected data principal (the patient) an intimation of the breach, in the form and manner prescribed. The Act itself does not give a deadline or a format. Those are left to rules that this site has not read, so we cannot say how many hours or days apply. Do not copy a number from another country’s law, because it may not match.&lt;/p&gt;
&lt;h2 id=&quot;what-the-schedule-says-about-penalties&quot;&gt;What the Schedule says about penalties&lt;/h2&gt;
&lt;p&gt;The Schedule lists a penalty that may extend to two hundred and fifty crore rupees for breaching the obligation to take reasonable security safeguards (section 8(5)). It lists a penalty that may extend to two hundred crore rupees for failing to give the Board or affected patients notice of a breach (section 8(6)). The Schedule words both as amounts that “may extend” to those figures, so they are upper limits, not fixed amounts. Nothing here predicts what a hospital would face.&lt;/p&gt;
&lt;h2 id=&quot;what-a-hospital-can-prepare&quot;&gt;What a hospital can prepare&lt;/h2&gt;
&lt;p&gt;The points below are practical suggestions, not legal advice.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Put breach alerts in the vendor contract.&lt;/strong&gt; Ask for a written duty to tell the hospital quickly and to share what happened, since the hospital must inform the Board and patients.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Name one person who decides.&lt;/strong&gt; Decide in advance who confirms that an event is a breach under the definition and who prepares the intimation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Keep a log.&lt;/strong&gt; Note when the hospital learned of the event, what data was involved and what was done, so the hospital can explain its steps later.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Watch for the rules.&lt;/strong&gt; The form, manner and timing of the intimation come from rules, so check the current rules with your legal adviser before finalising any procedure.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The Act defines a personal data breach widely (section 2(u)) and makes the hospital responsible for safeguards even when a processor handles the data (section 8(5)).&lt;/li&gt;
&lt;li&gt;After a breach, the hospital must give the Data Protection Board and each affected patient an intimation in the prescribed form and manner (section 8(6)); the Act itself sets no deadline.&lt;/li&gt;
&lt;li&gt;The Schedule sets maximum penalties of two hundred and fifty crore rupees for safeguards and two hundred crore rupees for notice failures. This is general information, not legal advice.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://prsindia.org/files/bills_acts/bills_parliament/2023/Digital_Personal_Data_Protection_Act,_2023.pdf&quot;&gt;The Digital Personal Data Protection Act, 2023 (Gazette of India copy, hosted by PRS Legislative Research)&lt;/a&gt;, sections 2(u), 8(4)-(6) and the Schedule. Read on 16 November 2026.&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;&lt;em&gt;This site’s content is for general information, research, and education. It does not replace medical diagnosis or advice for any specific patient, and it is not legal advice.&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Column</category></item><item><title>When the AI model changes: what to ask the vendor (CDSCO)</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-ai-model-updates-algorithm-change-protocol-cdsco/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-ai-model-updates-algorithm-change-protocol-cdsco/</guid><description>CDSCO’s guidance describes an Algorithm Change Protocol for software that changes. A checklist of what it can contain, for a hospital reading a proposal.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;An AI model that works well in a pilot may not be the same model a year later. Vendors retrain, update and replace. CDSCO’s Guidance Document on Medical Device Software addresses this with an Algorithm Change Protocol, which it says “may be devised, wherever applicable”.&lt;/p&gt;
&lt;h2 id=&quot;what-the-protocol-is&quot;&gt;What the protocol is&lt;/h2&gt;
&lt;p&gt;The guidance says the protocol shall include an overview of all the procedures to be followed so that changes to the software do not compromise its safety and its intended use. It may be submitted as part of the risk management file. Because it uses the word “may”, a vendor can lawfully have none; the guidance does not make it universal.&lt;/p&gt;
&lt;h2 id=&quot;what-it-may-contain&quot;&gt;What it may contain&lt;/h2&gt;
&lt;p&gt;According to the guidance, the protocol may contain:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a data management plan, covering data management, risk assessment, new data collection and quality assurance;&lt;/li&gt;
&lt;li&gt;a performance evaluation and monitoring plan, with metrics, a statistical analysis plan, how often performance is assessed, performance targets and a post-market monitoring overview;&lt;/li&gt;
&lt;li&gt;an algorithm retraining plan, where applicable;&lt;/li&gt;
&lt;li&gt;a software update plan, with version tracking, verification and validation, update triggers, update procedures and ways to communicate updates transparently to end users; and&lt;/li&gt;
&lt;li&gt;a rollback plan, with triggers, backup and recovery procedures and communication to users.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The guidance also asks applicants to document risks including cybersecurity and AI bias, and treats unintended bias in clinical decision-making caused by a software output as a possible indirect harm.&lt;/p&gt;
&lt;h2 id=&quot;questions-for-a-vendor&quot;&gt;Questions for a vendor&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Do you have an algorithm change protocol for this product, and which changes does it cover?&lt;/li&gt;
&lt;li&gt;How will we be told before a change reaches our wards, and can we delay it?&lt;/li&gt;
&lt;li&gt;What performance figures do you monitor after go-live, and will you share them?&lt;/li&gt;
&lt;li&gt;If an update causes a problem, how is it rolled back and who tells our staff?&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;CDSCO describes an Algorithm Change Protocol as something that “may be devised, wherever applicable”; it is not stated as mandatory for every product.&lt;/li&gt;
&lt;li&gt;It can include data, performance monitoring, retraining, update and rollback plans.&lt;/li&gt;
&lt;li&gt;Ask how updates are communicated and rolled back before the contract is signed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://cdsco.gov.in/opencms/export/sites/CDSCO_WEB/Pdf-documents/Guidance-document-on-Medical-Device-Software-under-MDR-2017.pdf&quot;&gt;CDSCO, Guidance Document on Medical Device Software, Algorithm Change Protocol&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>AI Tools</category></item><item><title>AI vendor, patient data: the hospital stays responsible</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-dpdp-act-ai-vendor-processes-patient-data/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-dpdp-act-ai-vendor-processes-patient-data/</guid><description>Under the DPDP Act the hospital remains answerable for data a vendor processes for it. Contract, security safeguards and breach intimation, in plain words.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Sending patient records to an AI vendor feels like handing a task to someone else. The Digital Personal Data Protection Act, 2023 treats it differently: the hospital that decides why and how the data is processed stays responsible.&lt;/p&gt;
&lt;h2 id=&quot;who-is-who&quot;&gt;Who is who&lt;/h2&gt;
&lt;p&gt;The Act calls the hospital a data fiduciary: a person who alone or with others decides the purpose and means of processing. A vendor that processes personal data on the hospital’s behalf is a data processor.&lt;/p&gt;
&lt;h2 id=&quot;responsibility-does-not-move&quot;&gt;Responsibility does not move&lt;/h2&gt;
&lt;p&gt;Section 8(1) says the data fiduciary is responsible for complying with the Act for any processing it undertakes, or that a data processor undertakes on its behalf, irrespective of any agreement to the contrary. A processor may be engaged to offer goods or services only under a valid contract (section 8(2)). A clause in the vendor’s standard terms that puts all risk on the hospital does not change the Act’s allocation.&lt;/p&gt;
&lt;h2 id=&quot;security-safeguards-and-breaches&quot;&gt;Security safeguards and breaches&lt;/h2&gt;
&lt;p&gt;Section 8(5) requires reasonable security safeguards to prevent a personal data breach, including in processing by a data processor. In the Schedule, a breach of this obligation carries a penalty that may extend to two hundred and fifty crore rupees. If a breach occurs, section 8(6) requires the data fiduciary to give the Data Protection Board and each affected person an intimation in the form and manner prescribed. Failing to give it carries a penalty that may extend to two hundred crore rupees. The deadline and form sit in the Rules, which this site could not open, so it states no deadline.&lt;/p&gt;
&lt;h2 id=&quot;data-used-to-make-decisions&quot;&gt;Data used to make decisions&lt;/h2&gt;
&lt;p&gt;Where personal data is likely to be used to make a decision that affects a person, or disclosed to another data fiduciary, section 8(3) asks the data fiduciary to ensure its completeness, accuracy and consistency. A tool that scores or ranks patients on the basis of records is the obvious place to ask who is responsible for this.&lt;/p&gt;
&lt;h2 id=&quot;what-to-put-in-the-vendor-contract&quot;&gt;What to put in the vendor contract&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;The purposes for which the vendor may process the data, and nothing else, including whether it may use it to improve its own product.&lt;/li&gt;
&lt;li&gt;Its security safeguards, described so that you can compare them with section 8(5).&lt;/li&gt;
&lt;li&gt;How and how fast it tells you of a breach, and who answers at night.&lt;/li&gt;
&lt;li&gt;Erasure when consent is withdrawn or the purpose ends, including by its sub-processors (section 8(7)).&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The hospital is the data fiduciary and stays responsible for what its processor does (section 8(1)).&lt;/li&gt;
&lt;li&gt;A processor may be engaged only under a valid contract (section 8(2)).&lt;/li&gt;
&lt;li&gt;Reasonable security safeguards are required, and the Schedule sets penalties up to ₹250 crore for that failure.&lt;/li&gt;
&lt;li&gt;A breach must be intimated to the Board and each affected person; check the Rules for the form and time.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://prsindia.org/files/bills_acts/bills_parliament/2023/Digital_Personal_Data_Protection_Act,_2023.pdf&quot;&gt;The Digital Personal Data Protection Act, 2023 (Gazette of India copy, hosted by PRS)&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Column</category></item><item><title>DPDP Act: what a patient must be told before they consent</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-dpdp-act-consent-notice-hospital/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-dpdp-act-consent-notice-hospital/</guid><description>The Act asks for a notice before every consent request and sets what valid consent looks like. A plain reading of sections 5 and 6 for hospitals.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Many hospital forms already ask a patient to “consent” to the use of their data. The Digital Personal Data Protection Act, 2023 sets out in detail what has to come before that consent and what makes it valid. This note reads sections 5 and 6 for people who run a hospital. When each provision starts to apply depends on government notification, which this note comes back to at the end.&lt;/p&gt;
&lt;h2 id=&quot;the-notice-comes-first&quot;&gt;The notice comes first&lt;/h2&gt;
&lt;p&gt;Under section 5(1), every request for consent must be accompanied or preceded by a notice. The notice must tell the person the personal data and the purpose for which it is to be processed, how they can exercise their rights, and how they can make a complaint to the Data Protection Board. Section 5(3) gives the person the option to read the notice in English or any language in the Eighth Schedule to the Constitution.&lt;/p&gt;
&lt;h2 id=&quot;what-valid-consent-looks-like&quot;&gt;What valid consent looks like&lt;/h2&gt;
&lt;p&gt;Section 6(1) says consent must be free, specific, informed, unconditional and unambiguous, with a clear affirmative action. It must signify agreement to processing for the specified purpose and be limited to the personal data necessary for that purpose. The Act gives an example from health: a telemedicine app that asks for consent to process data for telemedicine and also to access the phone’s contact list. The contact list is not necessary for telemedicine, so the consent is limited to what telemedicine needs.&lt;/p&gt;
&lt;p&gt;Requests must be in clear and plain language, in English or an Eighth Schedule language, with the contact details of a Data Protection Officer where applicable or of another authorised person (section 6(3)).&lt;/p&gt;
&lt;h2 id=&quot;withdrawal-and-proof&quot;&gt;Withdrawal and proof&lt;/h2&gt;
&lt;p&gt;The person can withdraw consent at any time, and withdrawing must be as easy as giving it (section 6(4)). The hospital must then stop processing, and have its processors stop, within a reasonable time unless processing is required or authorised by law (section 6(6)). If a question arises, the data fiduciary has to prove that notice was given and consent obtained in line with the Act (section 6(10)).&lt;/p&gt;
&lt;h2 id=&quot;when-consent-is-not-the-basis&quot;&gt;When consent is not the basis&lt;/h2&gt;
&lt;p&gt;Section 7 lists legitimate uses that do not depend on consent. They include responding to a medical emergency involving a threat to life or an immediate threat to health, and providing treatment or health services during an epidemic or outbreak. A routine form is not an emergency.&lt;/p&gt;
&lt;h2 id=&quot;check-the-dates&quot;&gt;Check the dates&lt;/h2&gt;
&lt;p&gt;Section 1(2) says the Act comes into force on a date the Central Government appoints by notification, and different dates may be appointed for different provisions. This site could not open the Ministry’s notifications and rules, so it does not state any date. Check the current notifications before you plan around one.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A notice must come with or before each consent request (section 5), in English or an Eighth Schedule language.&lt;/li&gt;
&lt;li&gt;Consent must be free, specific, informed, unconditional and unambiguous, and limited to what the purpose needs (section 6).&lt;/li&gt;
&lt;li&gt;Withdrawal must be as easy as giving consent, and the hospital must be able to prove notice and consent.&lt;/li&gt;
&lt;li&gt;Medical emergencies and similar cases are legitimate uses without consent (section 7).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://prsindia.org/files/bills_acts/bills_parliament/2023/Digital_Personal_Data_Protection_Act,_2023.pdf&quot;&gt;The Digital Personal Data Protection Act, 2023 (Gazette of India copy, hosted by PRS)&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Column</category></item><item><title>Which hospital software CDSCO says is not a medical device</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-hospital-information-systems-not-medical-devices-cdsco/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-hospital-information-systems-not-medical-devices-cdsco/</guid><description>Admission, scheduling and billing systems are on CDSCO’s list of software that is not a medical device. What that means for an AI add-on.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A hospital information system and an AI tool that sits on top of it are often bought together. Under India’s medical device rules they do not always stand in the same place. CDSCO’s Guidance Document on Medical Device Software gives practical examples of software that is not a medical device.&lt;/p&gt;
&lt;h2 id=&quot;the-examples-cdsco-gives&quot;&gt;The examples CDSCO gives&lt;/h2&gt;
&lt;p&gt;In section 5.2, the guidance lists illustrations of software that is not Medical Device Software. They include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;hospital or clinical information systems that support patient data management and are intended only for patient admission, scheduling appointments or visits, insurance and billing, clinical communication such as voice or video calling, and storing and transferring patient information;&lt;/li&gt;
&lt;li&gt;general communication systems that carry both medical and non-medical information, such as email;&lt;/li&gt;
&lt;li&gt;laboratory information systems whose main intended use is managing and validating information coming from analysers; and&lt;/li&gt;
&lt;li&gt;software that only transfers, stores, archives, converts, formats or performs simple searches.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The guidance says the examples are illustrations.&lt;/p&gt;
&lt;h2 id=&quot;why-the-intended-use-is-the-test&quot;&gt;Why the intended use is the test&lt;/h2&gt;
&lt;p&gt;What makes software a medical device is its intended use as the manufacturer states it, not the label “HIS” or “AI”. A scheduling system that only schedules is on the list. If the same product adds a function that analyses patient data to support a diagnosis or a treatment decision, the question changes. This is why the guidance says the class rests on intended use.&lt;/p&gt;
&lt;h2 id=&quot;what-to-do-with-this&quot;&gt;What to do with this&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Write down, for each system in your hospital, what the vendor states it is intended for.&lt;/li&gt;
&lt;li&gt;For an AI add-on to a system on the “not a medical device” list, ask whether the add-on has its own intended use statement and licence.&lt;/li&gt;
&lt;li&gt;Keep the vendor’s answer with the contract.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;CDSCO lists admission, scheduling, billing and similar hospital information systems as examples of software that is not a medical device.&lt;/li&gt;
&lt;li&gt;The test is the manufacturer’s stated intended use, so a new analytic function can change the answer.&lt;/li&gt;
&lt;li&gt;Ask about each AI add-on separately from the system it plugs into.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://cdsco.gov.in/opencms/export/sites/CDSCO_WEB/Pdf-documents/Guidance-document-on-Medical-Device-Software-under-MDR-2017.pdf&quot;&gt;CDSCO, Guidance Document on Medical Device Software, section 5.2&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Column</category></item><item><title>ICMR’s ten AI principles, read by a hospital administrator</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-icmr-ai-guidelines-ten-principles-for-administrators/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-icmr-ai-guidelines-ten-principles-for-administrators/</guid><description>ICMR’s 2023 guidelines list ten ethical principles for AI in healthcare. What each one means when you are reading a vendor proposal.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;ICMR’s Ethical Guidelines for Application of Artificial Intelligence in Biomedical Research and Healthcare (2023) were prepared by the DHR-ICMR Artificial Intelligence Cell. They are ethical guidelines for research and healthcare, and this note treats them as guidance, not as a statute. They are worth an administrator’s time because their principles map onto questions you already ask a vendor.&lt;/p&gt;
&lt;h2 id=&quot;the-ten-principles&quot;&gt;The ten principles&lt;/h2&gt;
&lt;p&gt;Section 1 lists: autonomy; safety and risk minimization; trustworthiness; data privacy; accountability and liability; optimization of data quality; accessibility, equity and inclusiveness; collaboration; non-discrimination and fairness; and validity.&lt;/p&gt;
&lt;h2 id=&quot;how-to-read-them-for-a-proposal&quot;&gt;How to read them for a proposal&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Autonomy.&lt;/strong&gt; Does the tool leave the patient and the clinician in charge, or does it act on its own?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safety and risk minimization.&lt;/strong&gt; What can go wrong, how would you notice, and who can switch it off?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Trustworthiness and validity.&lt;/strong&gt; Was it tested on patients like yours, and by whom?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Data privacy and data quality.&lt;/strong&gt; Where does the data go, and how is its quality kept up?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Accountability and liability.&lt;/strong&gt; Who is answerable when it errs: the vendor, the hospital, the clinician?&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Accessibility, equity, non-discrimination and fairness.&lt;/strong&gt; Does it work for your languages and regions, and for every patient group?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;beyond-the-principles&quot;&gt;Beyond the principles&lt;/h2&gt;
&lt;p&gt;Section 2 gives guiding principles for the development, validation and clinical deployment phases. Section 3 covers ethical review, Section 4 informed consent and Section 5 governance of AI use, and the document ends with an ethics checklist. The introduction also describes medical AI for hospital management systems, such as help with scheduling and with coordination between departments, and names ethical concerns including algorithmic transparency and explainability, clarity on liability, accountability and oversight, and bias and discrimination.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;ICMR’s 2023 guidelines list ten ethical principles for AI in biomedical research and healthcare.&lt;/li&gt;
&lt;li&gt;Each maps to an ordinary vendor question: who decides, what can go wrong, who is answerable, who is left out.&lt;/li&gt;
&lt;li&gt;They are guidance for ethics review and governance, and end with an ethics checklist you can borrow from.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://www.icmr.gov.in/icmrobject/uploads/Guidelines/1724842648_ethical_guidelines_application_artificial_intelligence_biomed_rsrch_2023.pdf&quot;&gt;ICMR, Ethical Guidelines for Application of Artificial Intelligence in Biomedical Research and Healthcare (2023)&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>Research Review</category></item><item><title>Is your hospital AI a medical device in India? CDSCO says</title><link>https://hospital-ai-lab.com/in/blog/2026-11-07-is-your-hospital-ai-a-medical-device-cdsco/</link><guid isPermaLink="true">https://hospital-ai-lab.com/in/blog/2026-11-07-is-your-hospital-ai-a-medical-device-cdsco/</guid><description>CDSCO’s 2026 guidance on medical device software says what counts. A plain reading for administrators and nurse leaders before they sign a proposal.</description><pubDate>Sat, 07 Nov 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;When a vendor says its AI tool is “CDSCO approved”, or says it needs no approval at all, an administrator has no easy way to judge. CDSCO’s Guidance Document on Medical Device Software (Doc No. CDSCO/MD/GD/MDSW/01/2026) is the first place to look. CDSCO’s public-notices page lists it with a release date of 21 July 2026.&lt;/p&gt;
&lt;h2 id=&quot;what-the-guidance-covers&quot;&gt;What the guidance covers&lt;/h2&gt;
&lt;p&gt;The document applies to software that meets the definition of a “medical device” in the Medical Devices Rules, 2017. It calls this Medical Device Software, and says mobile apps, AI/ML-based software and cloud or network-based software that meet the definition are considered Medical Device Software. Software that controls or adjusts a medical device is considered a medical device, and standalone software intended for a medical purpose is covered too. Software merely intended for general wellness or fitness tracking, with no medical purpose, is outside the document.&lt;/p&gt;
&lt;p&gt;The guidance says it reflects current practice under the Rules and should not be misconstrued as a new regulatory control.&lt;/p&gt;
&lt;p&gt;The guidance also carries a notice. It is meant to create public awareness and is not meant for legal or professional use. The legal texts are the Drugs and Cosmetics Act, 1940 and the Medical Devices Rules, 2017.&lt;/p&gt;
&lt;h2 id=&quot;what-decides-the-class&quot;&gt;What decides the class&lt;/h2&gt;
&lt;p&gt;Rule 4 of the Rules sets four risk classes: A (low risk), B (low moderate), C (moderate high) and D (high risk). The guidance says the class of this kind of software is fundamentally based on its intended use and the applicable rules in the First Schedule. In the Schedule, software that drives a device or influences its use automatically falls in the same class as that device.&lt;/p&gt;
&lt;p&gt;For a hospital, the practical point is the intended use statement. The same model can sit in different places depending on whether the manufacturer says it informs, supports or makes a clinical decision.&lt;/p&gt;
&lt;h2 id=&quot;three-questions-to-put-to-the-vendor&quot;&gt;Three questions to put to the vendor&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Does the vendor treat this product as a medical device under the Rules, and in which class?&lt;/li&gt;
&lt;li&gt;What licence or permission does it hold for this software and this intended use?&lt;/li&gt;
&lt;li&gt;Does your planned use match the intended use on that permission?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Ask for the answers in writing and attach them to the contract.&lt;/p&gt;
&lt;h2 id=&quot;key-takeaways&quot;&gt;Key takeaways&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Software that meets the medical device definition is regulated under the Medical Devices Rules, 2017, and CDSCO’s guidance considers AI/ML-based software that meets it to be Medical Device Software.&lt;/li&gt;
&lt;li&gt;Class A to D depends on the intended use the manufacturer states.&lt;/li&gt;
&lt;li&gt;The guidance is for public awareness, not legal use; read the Rules for a real decision.&lt;/li&gt;
&lt;li&gt;Ask the vendor for class, licence and intended use in writing.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Sources: &lt;a href=&quot;https://cdsco.gov.in/opencms/export/sites/CDSCO_WEB/Pdf-documents/Guidance-document-on-Medical-Device-Software-under-MDR-2017.pdf&quot;&gt;CDSCO, Guidance Document on Medical Device Software&lt;/a&gt;, &lt;a href=&quot;https://cdsco.gov.in/opencms/resources/UploadCDSCOWeb/2022/m_device/Medical%20Devices%20Rules,%202017.pdf&quot;&gt;Medical Devices Rules, 2017&lt;/a&gt;, &lt;a href=&quot;https://cdsco.gov.in/opencms/opencms/en/Notifications/Public-Notices/&quot;&gt;CDSCO public notices&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</content:encoded><category>News</category></item></channel></rss>