|
|
| (286 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ==Overview== | | ==This is demo code demoing math== |
| {{lablynxwiki::Overview - HCP URS|Overview}}
| |
| ==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)===
| | As a typical example, from a [[calibration plot]] following a [[linear equation]] taken here as the simplest possible model: |
| 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.
| | : <math>f(x) = ax + b </math> |
| * '''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.
| | where, <math>f(x)</math> corresponds to the signal measured (e.g. voltage, luminescence, energy, etc.) |
| | |
| 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.
| |
| | |
| {{limspecwiki:Specification POL S0010 System Design/Architecture Description and Documentation}}{{lablynxwiki::HealthCloudPOL}}{{lablynxwiki::Optional Plugins - HCP}}
| |
| | |
| ===In Short===
| |
| 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'''.
| |
| | |
| __________________________________________________________________________________________
| |
| | |
| | |
| {{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}}
| |
| | |
| __________
| |
| | |
| | |
| {{limspecwiki:Specification POL0010 Uptime guarantee}}{{lablynxwiki::POL0010}}
| |
| | |
| | |
| ==References==
| |
| <references />
| |
