<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ich-Q9 on HJohansen.dk</title><link>https://hjohansen.dk/en/tags/ich-q9/</link><description>Recent content in Ich-Q9 on HJohansen.dk</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 24 May 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://hjohansen.dk/en/tags/ich-q9/index.xml" rel="self" type="application/rss+xml"/><item><title>Pharma Automation Documentation Framework</title><link>https://hjohansen.dk/en/knowledge/pharma/framework/</link><pubDate>Sun, 24 May 2026 10:00:00 +0200</pubDate><guid>https://hjohansen.dk/en/knowledge/pharma/framework/</guid><description>&lt;p&gt;In a pharma automation context, the clean mental chain is:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;business need → user requirements → functional requirements → design → risk-based validation evidence → continued verification.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;FDA describes process validation as a lifecycle (three stages, not a one-time event), and ICH Q9 says the level of effort, formality, and documentation should match the level of risk.&lt;/p&gt;
&lt;h2 id="the-document-split"&gt;The Document Split&lt;/h2&gt;
&lt;h3 id="1-user-requirements-specification-urs"&gt;1. User Requirements Specification (URS)&lt;/h3&gt;
&lt;p&gt;The &lt;em&gt;what&lt;/em&gt; and &lt;em&gt;why&lt;/em&gt; from the user/business side. Describes process intent, operator needs, data capture, compliance needs, quality outcomes. ISA-88 gives a shared batch-control language for structuring this.&lt;/p&gt;</description></item></channel></rss>