Privacy and security safeguards should be added only after a digital healthcare platform has been deployed.

### Why this is right The statement is false because the material recommends integrating privacy and security requirements into the design and operation of digital health systems. Waiting until after deployment can leave important protections out of the system's basic processes. ### The concept Design-time planning can shape what information a system collects, who can access it, and how it is stored and used. Operational safeguards then maintain protection as the platform runs. The two stages work together; privacy is not a final patch that can substitute for careful system design. ### Terms - **Privacy by design**: Building privacy requirements into a system's design rather than treating them as an afterthought. - **Deployment**: Making a system available for actual use. ### Remember Plan privacy and security before launch, then maintain them during operation.