User:Shawndouglas/sandbox/sublevel19 - Revision history

Shawndouglas: Replaced content with "
TOC
{{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

2023-08-16T20:12:49Z

Replaced content with "<div class="nonumtoc">__TOC__</div> {{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

Show changes

Shawndouglas at 19:07, 15 August 2023

2023-08-15T19:07:59Z

← Older revision		Revision as of 19:07, 15 August 2023
Line 12:		Line 12:
	An integrated risk management approach will naturally extend to an organization’s information technology and how it's used. From sticky-noted passwords on monitors to unauthorized USB hard drives, local IT systems and their data can be put at risk. Now imagine extending that risk to public cloud services. Remember, with added complexity comes added risk, and cloud computing is no exception. This requires a concerted effort from all levels of the organization (again, see Figure 4) to address the risks of doing business in the cloud. This effort can be expedited through the use of risk management and cybersecurity frameworks that guide the organization towards better security and data integrity.		An integrated risk management approach will naturally extend to an organization’s information technology and how it's used. From sticky-noted passwords on monitors to unauthorized USB hard drives, local IT systems and their data can be put at risk. Now imagine extending that risk to public cloud services. Remember, with added complexity comes added risk, and cloud computing is no exception. This requires a concerted effort from all levels of the organization (again, see Figure 4) to address the risks of doing business in the cloud. This effort can be expedited through the use of risk management and cybersecurity frameworks that guide the organization towards better security and data integrity.

	Cloud computing has existed for over a decade now, and many experts have arisen from the rapidly changing field. Some of those experts have contributed their experience and knowledge to the development of risk management and cybersecurity frameworks over the years. The most successful have been widely disseminated (though several may not be free), meaning you don't have to reinvent the wheel when it comes to assessing and managing risk in your existing and upcoming IT systems. Table 8 shows some popular examples of risk management and cybersecurity frameworks that can be applied to provider and customer cloud security efforts.		Cloud computing has existed for well over a decade now, and many experts have arisen from the rapidly changing field. Some of those experts have contributed their experience and knowledge to the development of risk management and cybersecurity frameworks over the years. The most successful have been widely disseminated (though several may not be free), meaning you don't have to reinvent the wheel when it comes to assessing and managing risk in your existing and upcoming IT systems. Table 8 shows some popular examples of risk management and cybersecurity frameworks that can be applied to provider and customer cloud security efforts.

	{\| class="wikitable" border="1" cellpadding="5" cellspacing="0" width="70%"		{\| class="wikitable" border="1" cellpadding="5" cellspacing="0" width="70%"

Shawndouglas at 18:51, 15 August 2023

2023-08-15T18:51:33Z

← Older revision		Revision as of 18:51, 15 August 2023
Line 12:		Line 12:
	An integrated risk management approach will naturally extend to an organization’s information technology and how it's used. From sticky-noted passwords on monitors to unauthorized USB hard drives, local IT systems and their data can be put at risk. Now imagine extending that risk to public cloud services. Remember, with added complexity comes added risk, and cloud computing is no exception. This requires a concerted effort from all levels of the organization (again, see Figure 4) to address the risks of doing business in the cloud. This effort can be expedited through the use of risk management and cybersecurity frameworks that guide the organization towards better security and data integrity.		An integrated risk management approach will naturally extend to an organization’s information technology and how it's used. From sticky-noted passwords on monitors to unauthorized USB hard drives, local IT systems and their data can be put at risk. Now imagine extending that risk to public cloud services. Remember, with added complexity comes added risk, and cloud computing is no exception. This requires a concerted effort from all levels of the organization (again, see Figure 4) to address the risks of doing business in the cloud. This effort can be expedited through the use of risk management and cybersecurity frameworks that guide the organization towards better security and data integrity.

	Cloud computing has existed for over a decade now, and many experts have arisen from the rapidly changing field. Some of those experts have contributed their experience and knowledge to the development of risk management and cybersecurity frameworks over the years. The most successful have been widely disseminated (though several may not be free), meaning you don't have to reinvent the wheel when it comes to assessing and managing risk in your existing and upcoming IT systems. Table 7 shows some popular examples of risk management and cybersecurity frameworks that can be applied to provider and customer cloud security efforts.		Cloud computing has existed for over a decade now, and many experts have arisen from the rapidly changing field. Some of those experts have contributed their experience and knowledge to the development of risk management and cybersecurity frameworks over the years. The most successful have been widely disseminated (though several may not be free), meaning you don't have to reinvent the wheel when it comes to assessing and managing risk in your existing and upcoming IT systems. Table 8 shows some popular examples of risk management and cybersecurity frameworks that can be applied to provider and customer cloud security efforts.

	{\| class="wikitable" border="1" cellpadding="5" cellspacing="0" width="70%"		{\| class="wikitable" border="1" cellpadding="5" cellspacing="0" width="70%"
	\|-		\|-
	\| style="background-color:white; padding-left:10px; padding-right:10px;" colspan="4"\|'''Table 7.''' Examples of some common risk management and cybersecurity frameworks for cloud security.		\| style="background-color:white; padding-left:10px; padding-right:10px;" colspan="4"\|'''Table 8.''' Examples of some common risk management and cybersecurity frameworks for cloud security.
	\|-		\|-
	! style="background-color:#e2e2e2; padding-left:10px; padding-right:10px;"\|Framework		! style="background-color:#e2e2e2; padding-left:10px; padding-right:10px;"\|Framework

Shawndouglas at 17:45, 26 July 2023

2023-07-26T17:45:09Z

Show changes

Shawndouglas: Replaced content with "
TOC
{{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

2021-09-06T13:08:12Z

Replaced content with "<div class="nonumtoc">__TOC__</div> {{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

Show changes

Shawndouglas at 18:13, 19 September 2019

2019-09-19T18:13:20Z

Show changes

Shawndouglas at 19:35, 17 September 2019

2019-09-17T19:35:00Z

← Older revision		Revision as of 19:35, 17 September 2019
Line 107:		Line 107:
	\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-18]		\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-18]
	\| style="background-color:white;" \|'''26.18''' The system should be capable of interfacing with enterprise middleware.		\| style="background-color:white;" \|'''26.18''' The system should be capable of interfacing with enterprise middleware.
			\|-
			\|}
			\|}

			==27. Laboratory Scheduling and Capacity Planning==
			{\|
			\| STYLE="vertical-align:top;"\|
			{\| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
			\|-
			! colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"\|
			\|-
			! style="color:brown; background-color:#ffffee; width:500px;"\| Regulation, Specification, or Guidance
			! style="color:brown; background-color:#ffffee; width:700px;"\| Requirement
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.law.cornell.edu/cfr/text/21/211.25 21 CFR Part 211.25 (c)]<br />[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-14-1]
			\| style="background-color:white;" \|'''27.1''' The system should be able to accurately gauge and report test-based work capacity or throughput.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-14-2]
			\| style="background-color:white;" \|'''27.2''' The system should provide scheduling tools for allocating personnel and instruments to laboratory tasks.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-14-3]
			\| style="background-color:white;" \|'''27.3''' The system should provide a means for tasks to be scheduled and allocated against available resources.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.law.cornell.edu/cfr/text/42/493.1274 42 CFR Part 493.1274 (d)]
			\| style="background-color:white;" \|'''27.4''' The system should be able to track and limit the quantity of samples or hours worked on a type of sample by personnel, e.g., number of cytology slides or hours worked on them.
			\|-
			\|}
			\|}

			==28. Lean Laboratory and Continuous Improvement==
			{\|
			\| STYLE="vertical-align:top;"\|
			{\| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
			\|-
			! colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"\|
			\|-
			! style="color:brown; background-color:#ffffee; width:500px;"\| Regulation, Specification, or Guidance
			! style="color:brown; background-color:#ffffee; width:700px;"\| Requirement
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-15-1]
			\| style="background-color:white;" \|'''28.1''' The system should support a workload leveling strategy that automatically releases laboratory tasks to personnel.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-15-2]<br />[https://www.fda.gov/food/hazard-analysis-critical-control-point-haccp/haccp-principles-application-guidelines FDA Hazard Analysis Critical Control Point Principle 1]
			\| style="background-color:white;" \|'''28.2''' The system should provide a means to quickly visualize and assess workflow processes at strategic points.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.law.cornell.edu/cfr/text/21/211.42 21 CFR Part 211.42 (b)]<br />[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-15-3]<br />[https://www.fda.gov/food/hazard-analysis-critical-control-point-haccp/haccp-principles-application-guidelines FDA Hazard Analysis Critical Control Point Principle 1]
			\| style="background-color:white;" \|'''28.3''' The system should provide a means for mapping everyday workflow while identifying potential failure points.
	\|-		\|-
	\|}		\|}
	\|}		\|}

Shawndouglas at 19:25, 17 September 2019

2019-09-17T19:25:39Z

← Older revision		Revision as of 19:25, 17 September 2019
Line 35:		Line 35:
	[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the PDP 5.5]		[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the PDP 5.5]
	\| style="background-color:white;" \|'''26.3''' The system shall provide a means to choose—based on date and type of data—electronic data and metadata to archive.		\| style="background-color:white;" \|'''26.3''' The system shall provide a means to choose—based on date and type of data—electronic data and metadata to archive.
			\|-
			\| style="padding:5px; width:500px;" \|
			[https://www.law.cornell.edu/cfr/text/21/11.10 21 CFR Part 11.10 (c)]<br />
			[https://www.law.cornell.edu/cfr/text/21/58.51 21 CFR Part 58.51]<br />
			[https://www.law.cornell.edu/cfr/text/21/58.190 21 CFR Part 58.190]<br />
			[http://www.abft.org/files/ABFT_LAP_Standards_May_31_2013.pdf ABFT Accreditation Manual C-15]<br />
			[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-4]<br />
			[https://www.epa.gov/sites/production/files/documents/erln_lab_requirements.pdf EPA ERLN Laboratory Requirements 4.9.5]<br />
			[https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-4/annex11_01-2011_en.pdf E.U. Annex 11-17]<br />
			[https://www.iso.org/standard/66912.html ISO/IEC 17025:2017 8.4.2]<br />
			[http://www.oecd.org/chemicalsafety/testing/oecdseriesonprinciplesofgoodlaboratorypracticeglpandcompliancemonitoring.htm OECD GLP Principles 3.4]<br />
			[http://www.oecd.org/chemicalsafety/testing/oecdseriesonprinciplesofgoodlaboratorypracticeglpandcompliancemonitoring.htm OECD GLP Principles 10]<br />
			[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the PDP 5.2.1]<br />
			[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the PDP 5.5]
			\| style="background-color:white;" \|'''26.4''' The system shall provide a guaranteed means to retrieve and restore archived data and metadata that is readable and accurate.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-5]
			\| style="background-color:white;" \|'''26.5''' The system should feature a reliable, effective, and supported data storage system.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 C-6-6]<br />[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-6]
			\| style="background-color:white;" \|'''26.6''' The system should be able to interface directly with a third-party reporting tool.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-7]
			\| style="background-color:white;" \|'''26.7''' The system should be capable of being configured to and conform to the laboratory's existing data storage platforms and standards.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-8]
			\| style="background-color:white;" \|'''26.8''' The system should provide the ability to modify the data structures of the data storage mechanism as needed.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-9]
			\| style="background-color:white;" \|'''26.9''' The system should allow for both development and production environments for its data storage tools and allow the movement of records from one environment to another.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-10]
			\| style="background-color:white;" \|'''26.10''' The system shall provide data storage tools capable of fine-tuning the performance and security of data.
			\|-
			\| style="padding:5px; width:500px;" \|
			[https://www.law.cornell.edu/cfr/text/21/11.10 21 CFR Part 11.10 (c)]<br />
			[https://www.law.cornell.edu/cfr/text/21/211.68 21 CFR Part 211.68 (b)]<br />
			[https://www.law.cornell.edu/cfr/text/21/820.180 21 CFR Part 820.180]<br />
			[https://www.law.cornell.edu/cfr/text/45/164.308 45 CFR Part 164.308]<br />
			[https://www.aavld.org/accreditation-requirements-page AAVLD Requirements for an AVMDL Sec. 4.10.1.4]<br />
			[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-11]<br />
			[https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-4/annex11_01-2011_en.pdf E.U. Annex 11-7.2]<br />
			[https://nepis.epa.gov/Exe/ZyPDF.cgi?Dockey=30006MXP.PDF EPA 815-R-05-004 Chap. IV, Sec. 8]<br />
			[https://nepis.epa.gov/Exe/ZyPDF.cgi?Dockey=30006MXP.PDF EPA 815-R-05-004 Chap. VI, Sec. 7.6]<br />
			[https://www.epa.gov/sites/production/files/documents/erln_lab_requirements.pdf EPA ERLN Laboratory Requirements 4.9.5 and 4.9.14]<br />
			[https://www.epa.gov/quality/guidance-quality-assurance-project-plans-epa-qag-5 EPA QA/G-5 2.1.9]<br />
			[https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-1/dir_2003_94/dir_2003_94_en.pdf E.U. Commission Directive 2003/94/EC Article 9.2]<br />
			[https://www.iso.org/standard/56115.html ISO 15189:2012 5.10.3]<br />
			[https://www.iso.org/standard/66912.html ISO/IEC 17025:2017 8.4.2]<br />
			[https://extranet.who.int/prequal/content/who-technical-report-series WHO Technical Report Series, #986, Annex 2, 15.9]
			\| style="background-color:white;" \|'''26.11''' The system’s data storage tools shall provide data backup and retrieval functions that meet or exceed industry best practices, including producing exact and complete backups that are secure from manipulation and loss.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-12]
			\| style="background-color:white;" \|'''26.12''' The architecture of the system should be organized such that modules are clearly and logically separated, with standard interfaces provided between the modules.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-13]
			\| style="background-color:white;" \|'''26.13''' The system should be able to optimally use system and hardware resources to allow for concurrent usage and high-peak usage.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-14]
			\| style="background-color:white;" \|'''26.14''' The system should come with a well-documented application programming interface in order to facilitate granular interfaces with the system's underlying modular functionality.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-15]<br />[https://ec.europa.eu/health/sites/health/files/files/eudralex/vol-4/annex11_01-2011_en.pdf E.U. Annex 11-5]<br />[https://www.iso.org/standard/56115.html ISO 15189:2012 5.10.3]
			\| style="background-color:white;" \|'''26.15''' The system shall provide a means to integrate and exchange data electronically based on relevant methods, and in such a way so as to ensure accurate and secure data transfer and processing.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-16]
			\| style="background-color:white;" \|'''26.16''' The system shall be able to accurately replicate its data storage tools to ensure a recoverable system in the event of hardware failure.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-17]
			\| style="background-color:white;" \|'''26.17''' The system should be able to interface with an external enterprise resource planning system.
			\|-
			\| style="padding:5px; width:500px;" \|[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-18]
			\| style="background-color:white;" \|'''26.18''' The system should be capable of interfacing with enterprise middleware.
	\|-		\|-
	\|}		\|}
	\|}		\|}

Shawndouglas: Saving and adding more.

2019-09-17T18:15:12Z

Saving and adding more.

New page

<div class="nonumtoc">__TOC__</div>
{{ombox
| type = notice
| style = width: 960px;
| text = This is sublevel19 of my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see [[User_talk:Shawndouglas|my discussion page]] instead.<p></p>
}}

==Sandbox begins below==

==26. Systems Integration==
{|
| STYLE="vertical-align:top;"|
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
|-
! colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"|
|-
! style="color:brown; background-color:#ffffee; width:500px;"| Regulation, Specification, or Guidance
! style="color:brown; background-color:#ffffee; width:700px;"| Requirement
|-
| style="padding:5px; width:500px;" |[https://www.law.cornell.edu/cfr/text/21/211.105 21 CFR Part 211.105 (a)]<br />[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-1]
| style="background-color:white;" |'''26.1''' The system should be capable of communicating any status changes for samples, lots, instruments, and other dynamic entities to and from external systems.
|-
| style="padding:5px; width:500px;" |[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-2]
| style="background-color:white;" |'''26.2''' The system should accurately communicate status changes to external systems.
|-
| style="padding:5px; width:500px;" |
[https://www.law.cornell.edu/cfr/text/21/11.10 21 CFR Part 11.10 (c)]<br />
[https://www.law.cornell.edu/cfr/text/21/58.190 21 CFR Part 58.190]<br />
[http://www.abft.org/files/ABFT_LAP_Standards_May_31_2013.pdf ABFT Accreditation Manual C-15]<br />
[https://www.astm.org/Standards/E1578.htm ASTM E1578-18 E-13-3]<br />
[https://www.epa.gov/sites/production/files/documents/erln_lab_requirements.pdf EPA ERLN Laboratory Requirements 4.9.5 and 4.9.14]<br />
[https://www.iso.org/standard/66912.html ISO/IEC 17025:2017 8.4.2]<br />
[http://www.oecd.org/chemicalsafety/testing/oecdseriesonprinciplesofgoodlaboratorypracticeglpandcompliancemonitoring.htm OECD GLP Principles 3.4]<br />
[http://www.oecd.org/chemicalsafety/testing/oecdseriesonprinciplesofgoodlaboratorypracticeglpandcompliancemonitoring.htm OECD GLP Principles 10]<br />
[https://www.ams.usda.gov/datasets/pdp/pdp-standard-operating-procedures USDA Administrative Procedures for the PDP 5.5]
| style="background-color:white;" |'''26.3''' The system shall provide a means to choose—based on date and type of data—electronic data and metadata to archive.
|-
|}
|}

User:Shawndouglas/sandbox/sublevel19 - Revision history

Shawndouglas: Replaced content with "__TOC__ {{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

Shawndouglas at 19:07, 15 August 2023

Shawndouglas at 18:51, 15 August 2023

Shawndouglas at 17:45, 26 July 2023

Shawndouglas: Replaced content with "__TOC__ {{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

Shawndouglas at 18:13, 19 September 2019

Shawndouglas at 19:35, 17 September 2019

Shawndouglas at 19:25, 17 September 2019

Shawndouglas: Saving and adding more.

Shawndouglas: Replaced content with "
TOC
{{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."

Shawndouglas: Replaced content with "
TOC
{{ombox | type = notice | style = width: 960px; | text = This is sublevel19 of my sandbox, where I play with features and..."