User:Shawndouglas/sandbox/sublevel31 - Revision history

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

2023-08-16T20:36:08Z

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

← Older revision		Revision as of 20:36, 16 August 2023
Line 1:		Line 1:
	==~~7. Final thoughts and additional resources~~==		<div class="nonumtoc">__TOC__</div>
			{{ombox
			\| type = notice
			\| style = width: 960px;
			\| text = This is sublevel31 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>
			}}

	===~~7.1 Final thoughts~~===		==Sandbox begins below==
	~~<blockquote>The cloud is about how you do computing, not where you do computing.<br /> <br />- Paul Maritz, former CEO of VMware</blockquote>~~

	This quote from Paul Maritz has been floating around for some time, but how relevant is it today? The first chapter of this guide examined what [[cloud computing]] actually is and how it has changed since the mid-2000s. We've gone from talking about how to implement web services at the turn of the century to advanced cloud services that are going "hybrid" or "serverless." Despite the massive shift in thinking, however, one aspect has always remained the same: you have to have internet access to use services provided on the web. In that sense, the "where" of the performed computing is important. In another sense, "where" matters, as we discovered in the second chapter on cloud standards, regulations, and security. Where the data is created and where it resides are important considerations for regulatory purposes, as are the methods used to secure the cloud, and who holds responsibility for them. "Where" is also a consideration when asking about your data in the cloud. Its location is relevant to not only risk assessments and [[risk management]] practices—as described in the third chapter—but also to where you do your work: the laboratory. In the fourth chapter we discussed how a laboratory and its unique [[workflow]]s, industries services, and affecting regulations shape decisions on cloud projects, while also addressing the benefits and drawbacks. In the fifth, we explained the concept of managed security services, which further abstracted the “how” and “where” of computing via the third party, who manages the security of your cloud and on-premises solutions remotely! And in the sixth chapter, we distilled much of the previous chapters down into how a [[laboratory]] chooses and implements one or more cloud solutions. Even there, "where" comes into play, as you ask the cloud service provider where their servers are located and where your data will be stored, while you ask yourself "where" you envision your lab with cloud computing solutions in the future.

	When considering all this, however, Maritz was only partially off. There are many "wheres" to choosing and implementing a cloud-based service for your laboratory, including where you do your computing from, and even where your security is managed from. But cloud computing is certainly more about “how” you do computing in your laboratory. Cloud computing has proven to be at least a partially disruptive force over the years, changing organizations' IT departments, security planning, budgeting, and many other aspects, often for the better, though with its own complications. Laboratories can now host [[laboratory information management system]]s (LIMS) and [[electronic laboratory notebook]]s (ELNs) in the cloud and use [[infrastructure as a service]] (IaaS) to host serverless code that triggers when a cloud-connected instrument takes a reading and uploads the data. Laboratory users can now pull up information about not only automated lab procedures but also the security status of the equipment managing those procedures using a tablet while parked in the grocery store parking lot. Environmental sensors in Alaska can send data to a [[software as a service]] (SaaS) application hosted in Europe for processing, and then be accessed by an authorized user in Australia. Yes, the where of it all is related, but ultimately how the laboratory computes has now been changed with cloud computing.

	That doesn't mean there are fewer considerations and complications with a shift to the cloud. The laboratory should approach any migration to or addition of cloud services with assertive yet balanced project planning that takes into account organizational goals, management buy-in, necessary stakeholders, scope and responsibility, existing IT and data structures, risk management and regulatory considerations, budgeting and IT requirements, provider vetting, training, maintenance, and security monitoring. Vetting providers and their services can be particularly time-consuming, but it remains a critical component of any cloud-based move in your lab. Given all these complications, laboratories shouldn't be afraid to seek additional help from knowledgeable consultants and managed security service providers with experience implementing and securing cloud services in laboratories, particularly when in-house expertise is lacking.

	Hopefully this guide has been a boon to understanding cloud computing and all the considerations that come with it. Laboratories have much to consider when moving to or adding to their position in the cloud. The fact that you've made it through this document is a strong testament to your desire to ensure the success of a cloud project for your lab going forward. Good fortunes to you and your organization going forward.

Shawndouglas at 14:52, 16 August 2023

2023-08-16T14:52:04Z

← Older revision		Revision as of 14:52, 16 August 2023
Line 8:		Line 8:
	When considering all this, however, Maritz was only partially off. There are many "wheres" to choosing and implementing a cloud-based service for your laboratory, including where you do your computing from, and even where your security is managed from. But cloud computing is certainly more about “how” you do computing in your laboratory. Cloud computing has proven to be at least a partially disruptive force over the years, changing organizations' IT departments, security planning, budgeting, and many other aspects, often for the better, though with its own complications. Laboratories can now host [[laboratory information management system]]s (LIMS) and [[electronic laboratory notebook]]s (ELNs) in the cloud and use [[infrastructure as a service]] (IaaS) to host serverless code that triggers when a cloud-connected instrument takes a reading and uploads the data. Laboratory users can now pull up information about not only automated lab procedures but also the security status of the equipment managing those procedures using a tablet while parked in the grocery store parking lot. Environmental sensors in Alaska can send data to a [[software as a service]] (SaaS) application hosted in Europe for processing, and then be accessed by an authorized user in Australia. Yes, the where of it all is related, but ultimately how the laboratory computes has now been changed with cloud computing.		When considering all this, however, Maritz was only partially off. There are many "wheres" to choosing and implementing a cloud-based service for your laboratory, including where you do your computing from, and even where your security is managed from. But cloud computing is certainly more about “how” you do computing in your laboratory. Cloud computing has proven to be at least a partially disruptive force over the years, changing organizations' IT departments, security planning, budgeting, and many other aspects, often for the better, though with its own complications. Laboratories can now host [[laboratory information management system]]s (LIMS) and [[electronic laboratory notebook]]s (ELNs) in the cloud and use [[infrastructure as a service]] (IaaS) to host serverless code that triggers when a cloud-connected instrument takes a reading and uploads the data. Laboratory users can now pull up information about not only automated lab procedures but also the security status of the equipment managing those procedures using a tablet while parked in the grocery store parking lot. Environmental sensors in Alaska can send data to a [[software as a service]] (SaaS) application hosted in Europe for processing, and then be accessed by an authorized user in Australia. Yes, the where of it all is related, but ultimately how the laboratory computes has now been changed with cloud computing.

	That doesn't mean there are fewer considerations and complications with a shift to the cloud. The laboratory should approach any migration to or addition of cloud services with assertive yet balanced project planning that takes into account organizational goals, management buy-in, necessary stakeholders, scope and responsibility, existing IT and data structures, risk management and regulatory considerations, budgeting and IT requirements, provider vetting, training, maintenance, and security monitoring. Vetting providers and their services can be particularly time-consuming, but it remains a critical component of any cloud-based move in your lab. Given all these complications, laboratories shouldn't be afraid to seek additional help from knowledgeable consultants and managed security service providers with experience implementing and securing cloud in laboratories, particularly when in-house expertise is lacking.		That doesn't mean there are fewer considerations and complications with a shift to the cloud. The laboratory should approach any migration to or addition of cloud services with assertive yet balanced project planning that takes into account organizational goals, management buy-in, necessary stakeholders, scope and responsibility, existing IT and data structures, risk management and regulatory considerations, budgeting and IT requirements, provider vetting, training, maintenance, and security monitoring. Vetting providers and their services can be particularly time-consuming, but it remains a critical component of any cloud-based move in your lab. Given all these complications, laboratories shouldn't be afraid to seek additional help from knowledgeable consultants and managed security service providers with experience implementing and securing cloud services in laboratories, particularly when in-house expertise is lacking.

	Hopefully this guide has been a boon to understanding cloud computing and all the considerations that come with it. Laboratories have much to consider when moving to or adding to their position in the cloud. The fact that you've made it through this document is a strong testament to your desire to ensure the success of a cloud project for your lab going forward. Good fortunes to you and your organization going forward.		Hopefully this guide has been a boon to understanding cloud computing and all the considerations that come with it. Laboratories have much to consider when moving to or adding to their position in the cloud. The fact that you've made it through this document is a strong testament to your desire to ensure the success of a cloud project for your lab going forward. Good fortunes to you and your organization going forward.

Shawndouglas at 22:57, 27 July 2023

2023-07-27T22:57:58Z

← Older revision	Revision as of 22:57, 27 July 2023
Line 1:	Line 1:
		==7. Final thoughts and additional resources==

		===7.1 Final thoughts===
		<blockquote>The cloud is about how you do computing, not where you do computing.<br /> <br />- Paul Maritz, former CEO of VMware</blockquote>

		This quote from Paul Maritz has been floating around for some time, but how relevant is it today? The first chapter of this guide examined what [[cloud computing]] actually is and how it has changed since the mid-2000s. We've gone from talking about how to implement web services at the turn of the century to advanced cloud services that are going "hybrid" or "serverless." Despite the massive shift in thinking, however, one aspect has always remained the same: you have to have internet access to use services provided on the web. In that sense, the "where" of the performed computing is important. In another sense, "where" matters, as we discovered in the second chapter on cloud standards, regulations, and security. Where the data is created and where it resides are important considerations for regulatory purposes, as are the methods used to secure the cloud, and who holds responsibility for them. "Where" is also a consideration when asking about your data in the cloud. Its location is relevant to not only risk assessments and [[risk management]] practices—as described in the third chapter—but also to where you do your work: the laboratory. In the fourth chapter we discussed how a laboratory and its unique [[workflow]]s, industries services, and affecting regulations shape decisions on cloud projects, while also addressing the benefits and drawbacks. In the fifth, we explained the concept of managed security services, which further abstracted the “how” and “where” of computing via the third party, who manages the security of your cloud and on-premises solutions remotely! And in the sixth chapter, we distilled much of the previous chapters down into how a [[laboratory]] chooses and implements one or more cloud solutions. Even there, "where" comes into play, as you ask the cloud service provider where their servers are located and where your data will be stored, while you ask yourself "where" you envision your lab with cloud computing solutions in the future.

		When considering all this, however, Maritz was only partially off. There are many "wheres" to choosing and implementing a cloud-based service for your laboratory, including where you do your computing from, and even where your security is managed from. But cloud computing is certainly more about “how” you do computing in your laboratory. Cloud computing has proven to be at least a partially disruptive force over the years, changing organizations' IT departments, security planning, budgeting, and many other aspects, often for the better, though with its own complications. Laboratories can now host [[laboratory information management system]]s (LIMS) and [[electronic laboratory notebook]]s (ELNs) in the cloud and use [[infrastructure as a service]] (IaaS) to host serverless code that triggers when a cloud-connected instrument takes a reading and uploads the data. Laboratory users can now pull up information about not only automated lab procedures but also the security status of the equipment managing those procedures using a tablet while parked in the grocery store parking lot. Environmental sensors in Alaska can send data to a [[software as a service]] (SaaS) application hosted in Europe for processing, and then be accessed by an authorized user in Australia. Yes, the where of it all is related, but ultimately how the laboratory computes has now been changed with cloud computing.

		That doesn't mean there are fewer considerations and complications with a shift to the cloud. The laboratory should approach any migration to or addition of cloud services with assertive yet balanced project planning that takes into account organizational goals, management buy-in, necessary stakeholders, scope and responsibility, existing IT and data structures, risk management and regulatory considerations, budgeting and IT requirements, provider vetting, training, maintenance, and security monitoring. Vetting providers and their services can be particularly time-consuming, but it remains a critical component of any cloud-based move in your lab. Given all these complications, laboratories shouldn't be afraid to seek additional help from knowledgeable consultants and managed security service providers with experience implementing and securing cloud in laboratories, particularly when in-house expertise is lacking.

		Hopefully this guide has been a boon to understanding cloud computing and all the considerations that come with it. Laboratories have much to consider when moving to or adding to their position in the cloud. The fact that you've made it through this document is a strong testament to your desire to ensure the success of a cloud project for your lab going forward. Good fortunes to you and your organization going forward.

Shawndouglas: Blanked the page

2021-09-06T13:12:59Z

Blanked the page

← Older revision		Revision as of 13:12, 6 September 2021
Line 1:		Line 1:
	~~[[File:SARS-CoV-2 without background.png\|right\|300px]]~~
	~~'''Title''': ''COVID-19 Testing, Reporting, and Information Management in the Laboratory''~~

	~~'''Edition''': First edition~~

	~~'''Author for citation''': Shawn E. Douglas~~

	~~'''License for content''': [https://creativecommons.org/licenses/by-sa/4.0/ Creative Commons Attribution-ShareAlike 4.0 International]~~

	~~'''Publication date''': TBD~~


	This guide discusses the evolving status of [[laboratory]] testing, reporting, and [[information management]] for the [[COVID-19]] disease in the United States (and other parts of the world). It also addresses the disease's history, what makes it difficult to combat, and what diagnostic testing methods are currently available. Additionally, the guide examines that testing [[workflow]], along with the equipment, software, and reporting required by testing labs. It closes with a listing of associated resources, including guidance documents, web portals, and key reading.

	~~The table of contents for ''COVID-19 Testing, Reporting, and Information Management in the Laboratory'' is as follows:~~


	1. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Overview of COVID-19 and its challenges\|Overview of COVID-19 and its challenges]]//-->[[User:Shawndouglas/sandbox/sublevel32\|Overview of COVID-19 and its challenges]]

	~~:1.1 COVID-19: The terminology~~
	~~:1.2 COVID-19: History and impact (so far)~~
	~~:1.3 Challenges of managing the disease in the human population~~

	2. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Diagnostic testing of COVID-19 and other coronaviruses\|Diagnostic testing of COVID-19 and other coronaviruses]]//-->[[User:Shawndouglas/sandbox/sublevel33\|Diagnostic testing of COVID-19 and other coronaviruses]]
	~~:2.1 Testing terminology~~
	~~::2.1.1 Introduction~~
	~~::2.1.2 Polymerase chain reaction (PCR)~~
	~~::2.1.3 Lateral flow assay (LFA)~~
	~~:2.2 Testing conducted on previous coronaviruses~~
	~~::2.2.1 Severe acute respiratory syndrome (SARS)~~
	~~::2.2.2 Middle East respiratory syndrome (MERS)~~
	~~::2.2.3 The common cold~~
	~~:2.3 Organizational and agency guidance on COVID-19 testing~~
	~~:2.4 Current test methods and their differences~~
	~~::2.4.1 Background on the laboratory testing environment~~
	~~::2.4.2 PCR-based~~
	~~::2.4.3 LFA- and LAMP-based~~
	~~::2.4.4 Blood serum~~
	~~::2.4.5 Testing alternatives and challenges~~

	3. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Workflow and information management for COVID-19 (and other respiratory diseases)\|Workflow and information management for COVID-19 (and other respiratory diseases)]]//-->[[User:Shawndouglas/sandbox/sublevel34\|Workflow and information management for COVID-19 (and other respiratory diseases)]]

	~~:3.1 Laboratory informatics and workflow management~~
	~~::3.1.1 Does the system provide a flexible provider portal?~~
	~~::3.1.2 Does the system allow for the flexible addition of users, providers, and patients?~~
	~~::3.1.3 Does the system allow for laboratory workflows sympathetic to COVID-19 and other types of respiratory illness testing?~~
	~~::3.1.4 Does the system allow for interfacing with most instruments currently used for testing for COVID-19?~~
	~~::3.1.5 Does the system allow for versatile viewing and reporting of COVID-19 results?~~
	~~:3.2 Laboratory informatics and reporting requirements~~
	~~::3.2.1 ICD and CPT coding~~
	~~::3.2.2 Reporting to local and regional health departments~~
	~~:3.3 Additional benefits and challenges of laboratory informatics in disease testing and public health~~
	~~::3.3.1 System interoperability~~

	4. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Final thoughts and additional resources\|Final thoughts and additional resources]]//-->[[User:Shawndouglas/sandbox/sublevel35\|Final thoughts and additional resources]]

	~~:4.1 Final thoughts~~
	~~:4.2 Key guidance documents~~
	~~:4.3 Web portals~~
	~~:4.4 Key journal articles~~
	~~:4.5 Public health lab directory~~
	~~:4.6 Test kit and other resources~~
	~~:4.7 Public health laboratory informatics vendors~~


	~~<!---Place all category tags here-->~~

Shawndouglas at 19:06, 3 May 2020

2020-05-03T19:06:37Z

← Older revision		Revision as of 19:06, 3 May 2020
Line 11:		Line 11:


	This guide discusses the evolving status of laboratory testing, reporting, and information management for the [[COVID-19]] disease in the United States (and other parts of the world). It also addresses the disease's history, what makes it difficult to combat, and what diagnostic testing methods are currently available. Additionally, the guide examines that testing workflow, along with the equipment, software, and reporting required by testing labs. It closes with a listing of associated resources, including guidance documents, web portals, and key reading.		This guide discusses the evolving status of [[laboratory]] testing, reporting, and [[information management]] for the [[COVID-19]] disease in the United States (and other parts of the world). It also addresses the disease's history, what makes it difficult to combat, and what diagnostic testing methods are currently available. Additionally, the guide examines that testing [[workflow]], along with the equipment, software, and reporting required by testing labs. It closes with a listing of associated resources, including guidance documents, web portals, and key reading.

	The table of contents for ''COVID-19 Testing, Reporting, and Information Management in the Laboratory'' is as follows:		The table of contents for ''COVID-19 Testing, Reporting, and Information Management in the Laboratory'' is as follows:
Line 22:		Line 22:
	:1.3 Challenges of managing the disease in the human population		:1.3 Challenges of managing the disease in the human population

	2. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Diagnostic testing of COVID-19\|Diagnostic testing of COVID-19]]//-->[[User:Shawndouglas/sandbox/sublevel33\|Diagnostic testing of COVID-19 and other coronaviruses]]		2. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Diagnostic testing of COVID-19 and other coronaviruses\|Diagnostic testing of COVID-19 and other coronaviruses]]//-->[[User:Shawndouglas/sandbox/sublevel33\|Diagnostic testing of COVID-19 and other coronaviruses]]
	:2.1 Testing terminology		:2.1 Testing terminology
	::2.1.1 Introduction		::2.1.1 Introduction

Shawndouglas at 18:19, 3 May 2020

2020-05-03T18:19:03Z

← Older revision		Revision as of 18:19, 3 May 2020
Line 11:		Line 11:


	This guide discusses the evolving status of ~~the~~ laboratory testing, reporting, and information management for the [[COVID-19]] disease in the United States (and other parts of the world). It also addresses the disease's history, what makes it difficult to combat, and what diagnostic testing methods are currently available. Additionally, the guide examines that testing workflow, along with the equipment, software, and reporting required by testing labs. It closes with a listing of associated resources, including guidance documents, web portals, and key reading.		This guide discusses the evolving status of laboratory testing, reporting, and information management for the [[COVID-19]] disease in the United States (and other parts of the world). It also addresses the disease's history, what makes it difficult to combat, and what diagnostic testing methods are currently available. Additionally, the guide examines that testing workflow, along with the equipment, software, and reporting required by testing labs. It closes with a listing of associated resources, including guidance documents, web portals, and key reading.

	The table of contents for ''COVID-19 Testing, Reporting, and Information Management in the Laboratory'' is as follows:		The table of contents for ''COVID-19 Testing, Reporting, and Information Management in the Laboratory'' is as follows:

Shawndouglas at 18:05, 3 May 2020

2020-05-03T18:05:14Z

← Older revision		Revision as of 18:05, 3 May 2020
Line 39:		Line 39:
	::2.4.5 Testing alternatives and challenges		::2.4.5 Testing alternatives and challenges

	3. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Workflow and information management for COVID-19 (and other ~~pandemics~~)\|Workflow and information management for COVID-19 (and other ~~pandemics~~)]]//-->[[User:Shawndouglas/sandbox/sublevel34\|Workflow and information management for COVID-19 (and other ~~pandemics~~)]]		3. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Workflow and information management for COVID-19 (and other respiratory diseases)\|Workflow and information management for COVID-19 (and other respiratory diseases)]]//-->[[User:Shawndouglas/sandbox/sublevel34\|Workflow and information management for COVID-19 (and other respiratory diseases)]]

	:3.1 Laboratory informatics and workflow management		:3.1 Laboratory informatics and workflow management
			::3.1.1 Does the system provide a flexible provider portal?
			::3.1.2 Does the system allow for the flexible addition of users, providers, and patients?
			::3.1.3 Does the system allow for laboratory workflows sympathetic to COVID-19 and other types of respiratory illness testing?
			::3.1.4 Does the system allow for interfacing with most instruments currently used for testing for COVID-19?
			::3.1.5 Does the system allow for versatile viewing and reporting of COVID-19 results?
	:3.2 Laboratory informatics and reporting requirements		:3.2 Laboratory informatics and reporting requirements
	::3.2.1 ICD and CPT coding		::3.2.1 ICD and CPT coding
Line 55:		Line 60:
	:4.4 Key journal articles		:4.4 Key journal articles
	:4.5 Public health lab directory		:4.5 Public health lab directory
	:4.6 ~~National~~ and ~~global~~ resources		:4.6 Test kit and other resources
	:4.7 Public health laboratory informatics ~~solutions~~		:4.7 Public health laboratory informatics vendors


	<!---Place all category tags here-->		<!---Place all category tags here-->

Shawndouglas at 19:58, 25 April 2020

2020-04-25T19:58:21Z

← Older revision		Revision as of 19:58, 25 April 2020
Line 46:		Line 46:
	::3.2.2 Reporting to local and regional health departments		::3.2.2 Reporting to local and regional health departments
	:3.3 Additional benefits and challenges of laboratory informatics in disease testing and public health		:3.3 Additional benefits and challenges of laboratory informatics in disease testing and public health
			::3.3.1 System interoperability

	4. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Final thoughts and additional resources\|Final thoughts and additional resources]]//-->[[User:Shawndouglas/sandbox/sublevel35\|Final thoughts and additional resources]]		4. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Final thoughts and additional resources\|Final thoughts and additional resources]]//-->[[User:Shawndouglas/sandbox/sublevel35\|Final thoughts and additional resources]]

Shawndouglas at 19:56, 25 April 2020

2020-04-25T19:56:10Z

← Older revision		Revision as of 19:56, 25 April 2020
Line 45:		Line 45:
	::3.2.1 ICD and CPT coding		::3.2.1 ICD and CPT coding
	::3.2.2 Reporting to local and regional health departments		::3.2.2 Reporting to local and regional health departments
	:3.3 Additional benefits and ~~considerations~~ of laboratory informatics in disease testing and public health		:3.3 Additional benefits and challenges of laboratory informatics in disease testing and public health
	~~:: 3.3.1 Bioinformatics~~

	4. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Final thoughts and additional resources\|Final thoughts and additional resources]]//-->[[User:Shawndouglas/sandbox/sublevel35\|Final thoughts and additional resources]]		4. <!--[[LII:COVID-19 Testing, Reporting, and Information Management in the Laboratory/Final thoughts and additional resources\|Final thoughts and additional resources]]//-->[[User:Shawndouglas/sandbox/sublevel35\|Final thoughts and additional resources]]

Shawndouglas at 17:23, 25 April 2020

2020-04-25T17:23:06Z

← Older revision		Revision as of 17:23, 25 April 2020
Line 45:		Line 45:
	::3.2.1 ICD and CPT coding		::3.2.1 ICD and CPT coding
	::3.2.2 Reporting to local and regional health departments		::3.2.2 Reporting to local and regional health departments
	:3.3 ~~AAdditional~~ benefits and considerations of laboratory informatics in disease testing and public health		:3.3 Additional benefits and considerations of laboratory informatics in disease testing and public health
	:: 3.3.1 Bioinformatics		:: 3.3.1 Bioinformatics