Difference between revisions of "User:Shawndouglas/sandbox/sublevel6"

From LIMSWiki
Jump to navigationJump to search
m (Testing)
(Saving and adding more.)
Line 1: Line 1:
==Overview==
==A framework for the laboratories in our lives==
{{lablynxwiki::Overview - HCP URS|Overview}}
Below is a diagrammatic expression of one method of organizing laboratories of the world. The idea behind the framework is that you could name a specific laboratory and be able to put it somewhere within the framework. For example:
==System==
{{lablynxwiki::LIMSpec for the Physician Office Laboratory - System|System}}
==Architecture and technology==
Any software application is product of the technology used and its design/architecture. This is the core that determines its functionality, reliability, integration capabilities, scalability, ease of use and ultimately its usefulness. Additionally, it is important if you ever want to make code-level changes. A poor design and/or a little-used or inadequate coding language make changes difficult and expensive.<ref name=Architecture>{{cite web|url=https://en.wikipedia.org/wiki/Software_architecture|title=Software architecture  |work=Wikipedia: Software architecture |publisher=Wikipedia |accessdate=29 July 2015}}</ref>


===Design considerations (from Wikipedia)===
* The U.S. Federal Bureau of Investigation's mobile forensics laboratory<ref name="StephensInside15">{{cite web |url=http://www.kctv5.com/story/28266161/inside-look-at-fbis-new-mobile-forensics-lab |title=Inside look at FBI's new mobile forensics lab |author=Stephens, B. |work=KCTV5 News |publisher=Gannaway Web Holdings, LLC |date=04 March 2015 |accessdate=29 March 2017}}</ref> would fall under Government > Public > Compliance and Legal > Wet (or Dry) > Mobile.  
There are many aspects to consider in the design of a piece of software. The importance of each should reflect the goals the software is trying to achieve.  Some of these aspects are:


* '''Compatibility''' - The software is able to operate with other products that are designed for interoperability with another product.  For example, a piece of software may be backward-compatible with an older version of itself.
* An engineering design laboratory based within a for-profit car manufacturing company would fall under Private > Internal Customer > Research / Design > Dry > Fixed.  
* '''Extensibility''' - New capabilities can be added to the software without major changes to the underlying architecture.
* '''Fault-tolerance''' - The software is resistant to and able to recover from component failure.
* '''Maintainability''' - A measure of how easily bug fixes or functional modifications can be accomplished. High maintainability can be the product of modularity and extensibility.
* '''Modularity''' - the resulting software comprises well defined, independent components which leads to better maintainability. The components could be then implemented and tested in isolation before being integrated to form a desired software system. This allows division of work in a software development project.
* '''Reliability''' - The software is able to perform a required function under stated conditions for a specified period of time.
* '''Reusability''' - the software is able to add further features and modification with slight or no modification.
* '''Robustness''' - The software is able to operate under stress or tolerate unpredictable or invalid input.  For example, it can be designed with a resilience to low memory conditions.
* '''Security''' - The software is able to withstand hostile acts and influences.
* '''Usability''' - The software user interface must be usable for its target user/audience. Default values for the parameters must be chosen so that they are a good choice for the majority of the users.<ref>{{cite book|last=Carroll, ed.|first=John|title=Scenario-Based Design: Envisioning Work and Technology in System Development|year=1995|publisher=John Wiley & Sons|location=New York|isbn=0471076597}}</ref>
* '''Performance''' - The software performs its tasks within a user-acceptable time. The software does not consume too much memory.
* '''Portability''' - The usability of the same software in different environments.
* '''Scalability''' - The software adapts well to increasing data or number of users.<ref name=DesignConsiderations>{{cite web|url=https://en.wikipedia.org/wiki/Software_design#Design_considerations|title=Software Design Considerations  |work=Wikipedia: Software design |publisher=Wikipedia |accessdate=29 July 2015}}</ref>


For the Physician Office Lab, the characteristics listed above may be less or more important than for other businesses. For instance, Portability is probably not a main concern, since its use is most likely confined to the lab. The other characteristics are factors to be considered by the user/purchaser when assessing an LIS, based on their own unique situation and priorities.
* A chemistry laboratory housed in a secondary school in Germany would fall under Academic > Teaching > Secondary > Wet > Fixed.


The User Requirement Specifications here address the Physician Office Laboratory Information System's system architecture and technology characteristics with these considerations in mind, with reference to any applicable clinical or lab compliance standards. The '''Application Functional Descriptions''' describe how '''HealthCloudPOL''' meets these specifications.
The original inspiration for this chart came from Jain and Rao's attempt to diagram Indian diagnostic laboratories in 2015.<ref name="JainMedical15">{{cite journal |title=Medical diagnostic laboratories provisioning of services in India |journal=CHRISMED Journal of Health and Research |author=Jain, R.; Rao, B. |volume=2 |issue=1 |pages=19–31 |year=2015 |doi=10.4103/2348-3334.149340}}</ref> While their diagram focused entirely on the clinical sphere of laboratories, it was easy to envision expanding upon their work to express laboratories of all types. Additional inspiration came from KlingStubbins architecture textbook ''Sustainable Design of Research Laboratories: Planning, Design, and Operation''<ref name="KlingstubbinsSustainable10">{{cite book |title=Sustainable Design of Research Laboratories: Planning, Design, and Operation |author=KlingStubbins |publisher=John Wiley & Sons |year=2010 |pages=17–18 |isbn=9780470915967}}</ref>, which lists several methods for organizing types of laboratories, and Daniel D. Watch's ''Building Type Basics for Research Laboratories''.<ref name="WatchBuilding01">{{cite book |chapter=Chapter 2: Laboratory Types |title=Building Type Basics for Research Laboratories |author=Watch, D.D. |publisher=John Wiley & Sons |year=2001 |pages=37–99 |isbn=9780471217572}}</ref>


{{limspecwiki:Specification POL S0010 System Design/Architecture Description and Documentation}}{{lablynxwiki::HealthCloudPOL}}{{lablynxwiki::Optional Plugins - HCP}}
The benefit of this diagrammatic approach — with client type at its base — becomes more apparent when we start considering the other methods we could use to categorize laboratories, as described by KlingStubbins: by building type (architecturally), by function, and by science.


===In Short===
[[File:Laboratory types diagram v2.0.png|1400px]]
The [[LabLynx, Inc.]] [[Glossary#HealthCloudPOL|HealthCloudPOL]] is an unprecedented ''free'' LIS built with the very best technologies, meeting the [[#Design considerations (from Wikipedia)|LIS Design Considerations]], architectural, technical specifications and industry standards referenced in '''Specification POL S0010 System Design/Architecture Description and Documentation'''.


__________________________________________________________________________________________
==References==
 
{{Reflist|colwidth=30em}}
 
{{limspecwiki:Specification SLS0216 Hardware and infrastructure requirements}}{{lablynxwiki::SLS0216}}
 
==SaaS and Cloud Hosting==
More and more, the need for labs to have their own application servers is being replaced by the advent of [[Glossary#LabLynx Cloud Infrastructure|Cloud-hosted]] solutions.<ref name=Cloud>{{cite web|url=https://en.wikipedia.org/wiki/Cloud_computing#The_New_Millenium:_2000s  |title=Cloud computing, The New Millennium |work=Wikipedia: Cloud computing |publisher=Wikipedia |accessdate=29 July 2015}}</ref> This is especially true in the [[Glossary#POL|POL]] market, with budgets aimed at maximizing core services rather than extensive IT infrastructure.<ref name=ASTM>{{cite web|url=http://www.astm.org/Standards/E1578.htm  |title=Standard Guide for Laboratory Informatics |work=International Standard |publisher=ASTM International |accessdate=4 Aug 2015}}</ref> If the [[Glossary#LIS|LIS]] is offered as a hosted [[Glossary#SaaS|Software as a Service (SaaS)]] or [[Glossary#LabLynx Cloud Infrastructure|Cloud-hosted]] product, then it, its hosting infrastructure and associated services need to meet certain standards and requirements.
 
{{limspecwiki:Specification POL0006 Cloud hosting standards}}{{lablynxwiki::POL0006}}
 
__________


 
<!--Place all category tags here-->
{{limspecwiki:Specification POL0010 Uptime guarantee}}{{lablynxwiki::POL0010}}
 
 
==References==
<references />

Revision as of 17:37, 29 March 2017

A framework for the laboratories in our lives

Below is a diagrammatic expression of one method of organizing laboratories of the world. The idea behind the framework is that you could name a specific laboratory and be able to put it somewhere within the framework. For example:

  • The U.S. Federal Bureau of Investigation's mobile forensics laboratory[1] would fall under Government > Public > Compliance and Legal > Wet (or Dry) > Mobile.
  • An engineering design laboratory based within a for-profit car manufacturing company would fall under Private > Internal Customer > Research / Design > Dry > Fixed.
  • A chemistry laboratory housed in a secondary school in Germany would fall under Academic > Teaching > Secondary > Wet > Fixed.

The original inspiration for this chart came from Jain and Rao's attempt to diagram Indian diagnostic laboratories in 2015.[2] While their diagram focused entirely on the clinical sphere of laboratories, it was easy to envision expanding upon their work to express laboratories of all types. Additional inspiration came from KlingStubbins architecture textbook Sustainable Design of Research Laboratories: Planning, Design, and Operation[3], which lists several methods for organizing types of laboratories, and Daniel D. Watch's Building Type Basics for Research Laboratories.[4]

The benefit of this diagrammatic approach — with client type at its base — becomes more apparent when we start considering the other methods we could use to categorize laboratories, as described by KlingStubbins: by building type (architecturally), by function, and by science.

1400px

References

  1. ↑ Stephens, B. (4 March 2015). "Inside look at FBI's new mobile forensics lab". KCTV5 News. Gannaway Web Holdings, LLC. http://www.kctv5.com/story/28266161/inside-look-at-fbis-new-mobile-forensics-lab. Retrieved 29 March 2017. 
  2. ↑ Jain, R.; Rao, B. (2015). "Medical diagnostic laboratories provisioning of services in India". CHRISMED Journal of Health and Research 2 (1): 19–31. doi:10.4103/2348-3334.149340. 
  3. ↑ KlingStubbins (2010). Sustainable Design of Research Laboratories: Planning, Design, and Operation. John Wiley & Sons. pp. 17–18. ISBN 9780470915967. 
  4. ↑ Watch, D.D. (2001). "Chapter 2: Laboratory Types". Building Type Basics for Research Laboratories. John Wiley & Sons. pp. 37–99. ISBN 9780471217572. 


Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox/sublevel6&oldid=29635"