User:Shawndouglas/sandbox/sublevel3

Computers in the laboratory are not a recent phenomena. The mid-1960s saw clinical laboratory computerization become increasingly popular, though that enthusiasm was often based on the potential of the computers rather than their actual capabilities. Researchers imagined potentials such as automatic specimen label generation, daily log and report management, instrument interfacing and data processing, results comparisons, and time management tools. It would take some time for some of those potentials to be realized.

In 1970, Temple University Medical School's Marion Ball, M.A., an assistant professor in the Department of Medical Physics, conducted a survey of pathology directors in clinical laboratories that use computers. Asking their opinions about the advantages and disadvantages of computerized systems in the lab, she received responses from directors in 15 U.S. states, as well as from three other countries. Responses included:

The ability to rapidly prepare cumulative records and then to inspect them for possible errors through analysis trends has been proven to be of tremendous advantage in a number of laboratories. We can prevent errors in our analytical systems, but we are not prepared to prevent errors in the collecting of the sample, the mislabeling of the sample, or the accidental use of an incorrect sample. Thus, the ability to inspect data trends presents the only real tool that we currently have to pick out these kinds of errors. - Max E. Chilcote, Ph.D, Meyer Memorial Hospital Division

There is little argument about whether an operating computer system can be an advantage in a laboratory, but the most critical time is the installation and transition from a "manual" to a "computer" oriented laboratory. - Robert L. Habig, Duke University Medical Center

The most pressing future need for computerization of the laboratory lies in the area of medical diagnosis and guidance of the therapeutic management. This is where the physician's role for the future in the laboratory lies ... We will be gathering vast amounts of information on the health status of many individuals. We can then take advantage of large data processing computers to analyze this information and come up with patterns of disease states. - Leonard Jarett, M.D., Barnes Hospital

Reading about these potentials and opinions today, some 50 years later, we see both clear similarities and definite advances. For example, Habig's statement about transitioning from manual to more automated processes still rings true today: it can be nerve wracking and critical to get the transition right. Conversely, while the systems of decades past weren't able to "prevent errors in the collecting of the sample, the mislabeling of the sample, or the accidental use of an incorrect sample," modern laboratory informatics systems provide more assurances to sample management in the lab. In many cases, activities such as label generation, reporting, results analysis, workflow control, test ordering, and broad interoperability are commonplace in modern systems. And those systems continue to advance, with machine learning now becoming a part of laboratory data management and analysis.

We've come a long way since the 1960s, to a point where the question is no longer "can a computerized system help my lab?" but rather "how do I choose and implement an informatics system to help my lab?" What follows is information to help you with that question, while considering the technology, features, security, cost, implementation, and vendor guarantees that come with such a system.

2.1 Evaluation and selection

2.1.1 Technology considerations

Your laboratory's workflow, instruments, data management requirements, budget, technological expertise, business goals, and risk tolerances will all play a role in deciding what technology to invest in.

2.1.2 Features and functions

Base features

• synoptic reporting:
• barcode and RFID support:
• instrument and system/database interfacing for transferring test orders and data
• duplicate test checks

Specialty-specific functionality

Anatomical and clinical pathology lab:

https://www.labware.com/en/p/Industries/Healthcare/Hospitals-and-Reference-Labs/Anatomic-Pathology

https://www.sunquestinfo.com/software-and-services/copathplus/

https://www.novopath.com/

https://www.technidata-web.com/en-gb/solutions/disciplines/histopathology

• monitor disease populations through tracking of abnormal results and trending reports
• configure the system using templates for histology and cytology case types
• add, view, and link pre-generated organ maps and other diagrams
• add, view, and link custom annotated pathology imaging
• support blocks and slides as specimens, with predefined descriptions
• document grossing examinations
• print slides and cassettes
• provide case management, reporting, and test requisition
• provide specialty workflow for autopsy
• provide specialty workflow for gynecological cytology, including HPV + Pap co-testing for cervical cancer
• provide stain panels and histology worksheets
• support shared management of tissue samples among departments
• support EHR integration
• support PCR workflow and reporting
• support for pathology-specific reflex testing
• provide option to combine same-day anatomical and clinical pathology results and reporting
• flag unusual cases for conference or committee reporting

Forensic pathology lab:

https://www.informatics.abbott/us/en/industries/forensics

https://www.lablynx.com/forensics/

https://www.thermofisher.com/order/catalog/product/INF-12000-FORENSIC#/INF-12000-FORENSIC

http://www.porterlee.com/lims.html

• support pre-logging of evidence
• document a crime scene
• track storage, movement, and disposal of evidence and property using an ASTM-compliant log
• manage chain-of-custody transfers
• provide quarantine protocol for samples and evidence
• provide forensic case management, including case status and court testimony
• manage agency interactions and information
• add, view, and link forensic imaging into case files
• manage field scheduling for fingerprinting, homicide casing, and lab work
• provide custom reporting for toxicology and controlled substance analyses
• provide support for DNA profile management
• provide support for convicted offender and other database integration
• support the use of personal identity verification and other forms of hardware-based (i.e., public key infrastructure or PKI) token authentication

Physician office lab:

Integrative medicine lab:

Public health lab:

https://www.labware.com/en/p/Industries/Healthcare/Public-Health

https://www.orchardsoft.com/public-health-labs.html

https://www.apollolims.com/lab-expertise/public-health/

• provide specialty workflow for newborn screening
• provide surge capacity for high-priority analyses
• provide workflow and tools for managing microorganisms and toxins of elevated risk
• support most test protocols and sample types
• support ELISA, DNA extraction, sequencing, and other molecular workflows
• support for a robust set of decision support rules for reflex testing
• support the Center for Disease Control and Prevention's PHIN Messaging System
• support other electronic data exchange standards for critical community partners

Toxicology lab:

https://easytoxicology.com/features/

http://www.duii.com/products/starfruit-toxicology/

https://lablynx.com/toxicology/

https://www.dtpm.com/online-data-management/

https://www.orchardsoft.com/pain-management-toxicology-support.html

• support customizable drug panels and tests
• support for reference labs
• track prescribed medicines and associated history
• provide management for compounds and compound grouping
• provide medication-based compliance monitoring and interpretive reporting on it
• provide decision-support rules for pain management and toxicology
• provide toxicology-specific reporting formats
• manage drug court cases associated with testing

Blood bank and transfusion lab:

https://www.sunquestinfo.com/software-and-services/blood-bank-management/

https://www.softcomputer.com/products-services/blood-services/

http://www.hemasoft.com/

https://www.technidata-web.com/en-gb/solutions/disciplines/blood-banking

• manage inventory across multiple facilities
• support for donor and harvested tissues
• support positive patient identification (PPID)
• support the ISBT 128 standard for medical products of human origin
• support for both autologous and directed medical product management
• allow for emergency release of inventory
• allow for electronic crossmatch of a human-based medical products
• manage medical product recall and documentation
• manage donor demographics, notification, scheduling, and history
• manage donation drives and other campaigns
• track bag and supply lot numbers
• track quality control testing
• monitor access to and environmental conditions of supply fridges
• provide workflow management for non-standard patients
• support for antibody screening

Central and contract research lab:

https://www.eurofins.com/biopharma-services/central-lab/support-services/data-management/

https://www.informatics.abbott/us/en/industries/clinical-research

https://www.labware.com/en/p/Industries/Biobanking-and-Clinical-Research/Clinical-Research

https://www.medpace.com/capabilities/technology/laboratory-information-management/

• production and tracking management of clinical trial kits
• manage multi-site logistics of specimens
• provide a reservation function for specimens
• manage clinical trials and their various functions, including recruitment, study protocols, treatment groups, metadata, multi-site master scheduling, consent checks, and other required reporting
• provide special access privileges to sponsors, monitors, and investigators
• support a wide variety of data transfer formats, including CDISC, ASCII, SAS, and XML
• provide patient management, including demographics, consent forms, clinical notation, and test results
• provide highly configurable "blinding" features for reports and the user interface
• track contracts, budgets, and other financials
• develop exclusion rules and monitor exclusions
• support testing for a wide variety of disciplines
• provide study-specific monitoring and alerts
• provide granular cumulative reporting
• provide study-specific project portals that allow review of documents, data visualizations, training material, and other study information

Genetic diagnostics lab:

https://www.sunquestinfo.com/software-and-services/lims/

https://www.xifin.com/industry-solutions/laboratory/molecular-diagnostics

https://jmd.amjpathol.org/article/S1525-1578(17)30583-4/fulltext

https://psychesystems.com/enterprise-laboratory-information-software/nucleolis-molecular-lab-testing-software/

• management of sample collection kits
• management of informed consent documentation
• provide customized workflows for molecular and NGS testing,
• track specimen and aliquot lineage for cell lines, tissues, slides, etc.
• track nucleic acid quantity and quality of specimens
• support a wide array of molecular testing and associated data fields, including biochemical and molecular genetics, carrier screening, immunology, molecular profiling, prenatal and newborn testing, and pharmacogenetics
• provide custom workflows for FISH, PCR, gel eletrophoresis, cytogenetics, DNA sequencing, and more
• support specialty testing reimbursement and other revenue management unique to this lab
• support single sign-on with imaging platforms
• provide color coding for turn-around time and other testing statuses
• provide cleanly formatted rich-text reports customized for molecular diagnostics

Cytogenetics lab:

Medical cannabis testing lab:

2.1.3 Cybersecurity considerations

From law firms to automotive manufacturers, the need to address cybersecurity is increasingly apparent. In 2018, the Center for Strategic & International Studies estimated that cybercrime causes close to $600 billion in damages to the global economy every year, though due to underreporting of crimes, that number may be much higher. That number also likely doesn't take into account lost business, fines, litigation, and intangible losses In the end, businesses of all sizes average about $200,000 in losses due to a cybersecurity incident, and nearly 60 percent of small and midsize businesses go bankrupt within six months because of it.

Medical diagnostic and research laboratories are no exception, regardless of business size. Even tiny labs whose primary digital footprint is a WordPress website advertising their lab are at risk, as hackers could still spread malware, steal user data, add the website to a bot network, hack the site for the learning experience, or even hack it just for fun. Even more importantly are those labs performing digital data management tasks that handle sensitive patient and proprietary data, requiring additional cybersecurity considerations.

A laboratory can integrate cybersecurity thinking into its laboratory informatics product selection in several ways. First, the lab should have a cybersecurity plan in place, or if not, it should be on the radar. This is a good resource to tap into in regards to deciding what cybersecurity considerations should be made for the software. Can the software help your lab meet your cybersecurity goals? What regulatory requirements for your lab are or are not covered by the software? Another tool to consider—which may have been used in any prior cybersecurity planning efforts—is a cybersecurity framework. Many, but not all, cybersecurity frameworks include a catalog of security controls. Each control is "a safeguard or countermeasure prescribed for an information system or an organization designed to protect the confidentiality, integrity, and availability of its information and to meet a set of defined security requirements." These controls give the implementing organization a concrete set of configurable goals to apply to their overall cybersecurity strategy. Other frameworks may be less oriented to security controls and more program-based or risk-based. Choosing the best frameworks will likely depend on multiple factors, including the organization's industry type, the amount of technical expertise within the organization, the budget, the organizational goals, the amount of buy-in from key organizational stakeholders, and those stakeholders' preferred approach.

Finally, having a cybersecurity plan that incorporates one or more cybersecurity frameworks gives the laboratory ample opportunity to apply stated goals and chosen security controls to the evaluation and selection process. In particular, a user requirements specification (URS) that incorporates cybersecurity considerations will certainly help a laboratory with meeting regulatory requirements while also protecting its data systems. A USR that is pre-built with cybersecurity controls in mind—such as LIMSpec, discussed later—makes the evaluation process even easier.

2.1.4 Regulatory compliance considerations

Without a doubt, it's vital that medical diagnostic and research laboratories operate within the bounds of a regulatory atmosphere, not only to better ensure the best patient outcomes but also to ensure the quality of test results, the privacy of patient information, and the safety of personnel. Maintaining regulatory compliance requires deliberate approaches to developing and enforcing processes and procedures, quality training, consistent communication, and knowledgeable personnel. It also requires a top-down appreciation and commitment to a culture of quality. From the Clinical Laboratory Improvement Amendments (CLIA) and Health Insurance Portability and Accountability Act (HIPAA) to 21 CFR Part 11 and the General Data Protection Regulation, laboratories have much to consider in regards to what regulations impact them.

That said, consider approaching the question of regulatory compliance from the standpoint of adopting standards. Consider first that the risks and consequences of performing a task poorly drives regulation and, more preferably, standardization, which in turn moves the "goalposts" of quality and security among organizations. In the case of regulations, those organization that get caught not conforming to the necessary regulations tend to suffer negative consequences, providing some incentive for them to improve organizational processes and procedures.

One of the downsides of regulations is that they can at times be "imprecise" or "disconnected" from what actually occurs within the organization and its information systems. Rather than focusing heavily to regulatory conformance, well-designed standards may, when adopted, provide a clearer path of opportunity for organizations to improve their operational culture and outcomes, particularly since standards are usually developed with a broader consensus of interested individuals with expertise in a given field. In turn, the organizations that adopt well-designed standards likely have a better chance of conforming to the regulations they must, and they'll likely have more interest in maintaining and improving the goalposts of quality and security in the lab.

Additionally, reputable software developers of laboratory informatics software will not only adopt their own industry standards for software development but also understand the standards and regulations that affect laboratories and research centers. In turn, the developed software should meet regulations and standards, help the laboratory comply with its regulations and standards, and be of reliably good quality.

If you're a potential buyer of a laboratory informatics solution, it may be that you know a bit about your laboratory's workflow and a few of the regulations and standards that influence how that workflow is conducted, but you're not entirely informed about all the regulations and standards that affect your lab. Turning to a URS such as LIMSpec—which was developed around laboratory regulations and standards—and reviewing the various statements contained within may be necessary to help further inform you. Additionally, as you investigate various informatics options, you can then use the requirements in the URS as a base for your laboratory's own requirements list. Using the categories and their subdivisions, you can then add those requirements that are unique to your laboratory and industry that are not sufficiently covered by the base URS. As you review the various options available to you and narrow down your search, your own list of requirements can be used as both as a personal checklist and as a requirements list you hand over to the vendor you query. And since your URS is based off the standards and regulations affecting your lab, you can feel more confident in your acquisition and its integration into your laboratory workflow.

2.1.5 Cost considerations

First, you'll want to be clear on what will be included in the sales agreement. Whether through an estimate or statement of work (SOW), it is important it includes exactly what is expected, being as specific as possible, since this will be the entire contractual obligation for both you the buyer and them the vendor. Note that line items may differ slightly from system to system, according to what features and functions are included by default with each vendor's LIMS and which, if any, are additional. Also keep in mind that any hourly amount in the the estimate or SOW is usually a best estimate; however, if sufficient attention to detailed requirements has been given, then it should be quite accurate, and in fact the final cost may even be below the quoted cost if you prioritize your own obligations so that the vendor's hours are used sparingly and efficiently.

The estimate or SOW should optimally include:

• licensing or subscription rates;
• required core items to meet federal, state, and local regulations;
• additional optional items and totals; and
• required services (implementation, maintenance and support, optional add-ons).

There are two primary ways to price a laboratory informatics solution: a one-time license fee or a subscription rate (cloud-hosted software as a service [SaaS]). If you have your own dedicated IT department and staff, you may prefer the former (although many system administrators are just as happy to let it be hosted elsewhere rather than add to their workload). Otherwise, SaaS subscription may well be the better and more cost-effective way to go (since the primary IT cost is simply internet access). This item will be part of your up-front cost and, in the case of subscription, it will also figure into your first year and ongoing costs; otherwise only associated maintenance, support, and warranty (MSW) will figure in. Typically, your first year's subscription costs will be due at signing. More often, the vendor may require three months or even the first year up front, so be prepared to factor that into up-front costs. However, it still is almost always less expensive at the outset (and over time, if you factor in IT costs and annual MSW) than paying for a license fee.

In addition to the two types of software pricing, there are also sub-types. Generally these are based on the number of users (or, in some cases, "nodes," which are simply any entities that access the informatics system, including other systems, instruments, etc.). How these are counted can vary.

• Named users: This method bases pricing on the actual individual users of the system, even if they only log in sporadically. Users may not use each other's logins (this is a no-no regardless of pricing structure, for good laboratory practice and other regulatory reasons).
• Concurrent users: This bases pricing on the maximum number of users who will be logged in at any given time. You can define an unlimited number of named users in the system, each with their own login credentials. However, only the number of concurrent users specified in the license or subscription may be logged in at any one time. For example, you may have 10 staff, but due to work processes, shifts, etc., only up to six might ever be logged in simultaneously. Whereas this would require a named user license for 10, it would only require a concurrent user license for six.
• Unlimited users: In the case of very large labs (typically 30 to 50 and up), the license or subscription may simply be a flat fee that allows any number of users.

The line items in the estimate or SOW should reflect these nuances, as well as whether the listed costs are monthly or annual (for subscription services), hourly (typically for support and training), or a fixed one-time cost. Additionally, be cautious with fixed costs, as they typically represent one of two possible scenarios:

1. Final fixed cost: In this case, the cost has been figured by the vendor so as to cover their worst-case hourly labor total. If a line item (e.g., an interface) is not "worst case," then you are overpaying.
2. "Expandable" fixed cost: This is as bad as final fixed cost, and maybe even worse because it's almost a case of "bait-and-switch," popping up as a surprise. The initial "fixed cost" number is low, and additional hourly services are needed to actually deliver the item. This will have been provided for somewhere in the small print.

The bottom line is that everything in a laboratory informatics solution is really either licensing or hourly services. Just be careful if they are portrayed as anything else.

It is important to be clear which category each line item falls under when figuring costs: up-front (due upon signing), annual, or ongoing (e.g., SaaS subscription). It is useful to clearly lay out each and compute initial costs, as well as first-year and subsequent years' costings. For example, your initial obligation may be as little as your first year's subscription plus the first 40 hours of services. Different vendors have different policies, however, and you may be required to pay for your first full year's subscription and all services, or some other combination. Normally, though, any instrument interface or other service charges aren't due until the they are implemented, which may be a few weeks or even a month down the road. This may depend on your budget, complexity of the SOW, and urgency. Your first year's expenses will include everything, including initial license fees; all setup and training; any interfaces and additional configurations or customization; and first annual MSW. (If this isn't included in the SaaS subscription, then it usually commences on full system delivery). Afterwards, your subscription and MSW will be the only ongoing expenses (included as one in this example), unless you choose to have additional interfaces or other services performed at any time.

2.2 Implementation

If you've ever worked through a system implementation process with a vendor, it was hopefully a smooth process. However, there are plenty of horror stories out there, highlighting the need of the laboratory to discuss in detail how a potential vendor will handle installation, validation, and training for the informatics solution. Does the vendor truly understand the industry and your needs? Does the vendor assign a project manager who will work with you from planning to go-live and beyond? Can they offer you references of other labs who have gone through implementation so you can compare notes with the those labs? How much attention does the potential vendor give to related issues such as data integrity of migrated data? Do they have the means to properly handle your legacy data? And are they able to work with your schedule, even if it means implementing software at off-peak work hourse?

As you finally get down to the ultimate decision on which vendor to work with, you may wish to start setting up an implementation checklist as part of your early project planning. Do you receive a help desk account as part of the implementation process, and if so, what information is included? If not, you'll need to keep track of specific details such as business associate agreement (BAA), sales agreement, scope documents, welcome letters, documentation, and approved staff who can utilize the vendor's support. You'll likely need to pass on other configuration details to the vendor, including timezone requirements, DNS and URL requirements, uptime monitors, and administrative account requirements. Finally, you'll want to ensure you and the vendor are on the same page concerning any additional customization, integration, and system validation requirements, ensuring the roll-out period is pain-free and efficient.

2.2.1 Internal and external integrations

Laboratories acquire data management software for many reasons, including improving accuracy, saving time, increasing productivity, and adding capabilities. One way of doing all of those activities is to integrate or interface your systems, databases, and instruments so that human error is greatly reduced or eliminated, workflows are automated and sped up, and each component's capabilities are brought into play in the most efficient and effective ways possible. As such, you'll want to inquire with the vendor about its solution's hardware and software integration capabilities. Is it designed to interface with every laboratory instrument or software that can output any readable electronic file? Or are integrations limited to certain instruments and systems? How does it connect, i.e., what protocols does the software depend on to connect with other systems? Does the system allow a user to map their own file imports and exports? Can system processes be set to detect new instances of file outputs at regular intervals? Ask these and other questions to make sure the vendor clearly describes what internal and external integrations are supported with their application.

In many cases, a vendor's solution will have integration capability built into the software, but occasionally such interfaces are separate from the main software. Today's interfaces are generally built on standardized communication tools, including messaging formats like Health Level 7 (HL7). The HL7 messaging standards are particularly important to laboratory data management because they define how information is packaged and communicated from one party to another. Such standards set the language, structure, and data types required for seamless integration of various systems and instruments. Health Level 7 describes the types of information communicated between such systems in the clinical environment as including "process control and status information for each device or analyzer, [as well as] each specimen, specimen container, and container carrier; information and detailed data related to patients, orders, and results; and information related to specimen flow algorithms and automated decision making."

You may also want your laboratory informatics solution to be able to communicate with other software and databases. This is often done using application programming interfaces (APIs) using web services implementation protocols such as REST and SOAP. These messaging protocols actually allow for the creation of an API that receives communication requests and sends responses between two software systems. A more practical example is wanting your laboratory informatics solution to communicate with an enterprise resource planning (ERP) application. Perhaps the ERP system needs to create sample batches within the informatics solution, and when testing is done, have the results returned to the ERP. APIs and communication protocols make this happen.

2.3 MSW, updates, and other contracted services

The maintenance, support, and warranty (MSW) offered with the vendor's solution is almost as important as the solution itself. The laboratory informatics solution you acquire is more than than the software you operate: it's mission-critical and deserves having a reliable and responsive team with the necessary resources to ensure it remains operational. Downtime can negatively affect both immediate customer satisfaction and your reputation. As such, it's imperative you ask the vendor about the details of its MSW, making sure you understand what is and isn't covered, as well as how much it will cost. Cost-wise, industry norms are anywhere from 15% to 25% of either the license fee or total contract, levied annually to provide this coverage. Alternatively, it may simply be included with your subscription. The MSW will include a specified number of support and maintenance hours or guarantees. The actual warranty should be unlimited for as long as the MSW or subscription is kept current.

Maintenance includes any and all work necessary to keep your system working as designed. It should include updates, patches, or fixes, and most if not all upgrades. (Note, however, a major upgrade to a totally new edition may not be covered, but it may come at a negotiable, significantly lower cost.) The support aspect of MSW generally consists of a specified number of hours dedicated more to helping you with the operation of the system rather than "fixing" anything. Support includes guidance on training, password or login support, and more. Finally, with any professional application you also expect to have a warranty. The warranty should cover anything that doesn't work that otherwise should for the designated period of time. That includes any standard features and functions, as well as any additional ones that were delivered and signed off on, and any other work performed by the vendor or its representatives. However, a typical warranty does not cover anything that was working fine, but upon being manipulated in a way beyond normal operation the functionality ceased. In these cases, you'll probably have to pay to get it fixed.

Beyond the MSW, additional updates and services related to the system may also be required. No matter how well it is pre-configured, any professional laboratory informatics solution will require some amount of standard setup to reflect your particular lab. This includes adding lab branding and demographics for reports and certificates; entering users, their roles, and access permissions; adding and/or modifying tests and workflows; renaming fields; adding or hiding fields; setting up a web portal; and implementing interfaces. Equally indispensable is proper training for both users and administrators. And of course you may later find that you would like additional features or functions. These and other services may prove particularly useful to the laboratory with little in the way of IT and systems expertise. As such, the vendor may provide one or more of the following as a billable service for the laboratory:

• initial implementation meeting (e.g., initial planning, identify delta, set schedule)
• project management
• requirements gathering and documentation
• initial setup
• user and administrator training
• configuration and customization
• interface development and implementation
• custom screen and field development
• custom functionality development
• custom reports and labels
• custom triggers and alerts
• validation or acceptance testing (to a third-party standard or certification, or to agreed manufacturer specs)

2.4 How a user requirements specification fits into the entire process

Merriam-Webster defines a "specification" as "a detailed precise presentation of something or of a plan or proposal for something." In other words, an existing or theoretical product, concept, or idea is presented in detail for a particular audience. In a broad sense, detailing the specifics about a project, concept, or idea to others is just common sense. This applies just as well to the world of software development, where a software requirements specification is essential for preventing the second most commonly cited reason for project failure: poor requirements management.

In fact, the ISO/IEC/IEEE 29148:2018 standard (a conglomeration of what was formerly IEEE 830 and other standards) is in place to help specify "the required processes implemented in the engineering activities that result in requirements for systems and software products" and provide guidelines for how to apply those requirements. The standard describes the characteristics that make up quality software requirement development, including aspects such as:

• correctly describing system behavior;
• effectively removing ambiguity from the language used;
• completely covering the system behavior and features;
• accurately prioritizing and ranking the requirements; and
• unequivocally ensuring the requirements are testable, modifiable, and traceable.

A requirement typically comes in the form of a statement that begins with "the system/user/vendor shall/should ..." and focuses on a provided service, reaction to input, or expected behavior in a given situation. The statement may be abstract (high-level) or specific and detailed to a precise function. The statement may also be of a functional nature, describing functionality or services in detail, or of a non-functional nature, describing the constraints of a given functionality or service and how it's rendered. An example of a functional software requirement could be "the user shall be able to query either all of the initial set of databases or select a subset from it." This statement describes specific functionality the system should have. On the other hand, a non-functional requirement, for example, may state "the system's query tool shall conform to the ABC 123-2014 standard." The statement describes a constraint placed upon the system's query functionality.

This is where a requirements specification shines, not only for the software developer but also for those acquiring the software. A set of development requirements, compiled in the form of a software requirements specification, can serve to strengthen the software development process. For those acquiring the software, a set of user requirements, compiled in the form of a user requirements specification (URS), can be used for the selection and acquisition of software or a service. In the case of the URS, the acquiring business can approach this several ways. The simple way would be to essentially take the vendor at the word in regards to what they say their system can and can't do, agreeing formally to their description and taking responsibility that it will cover all the applicable regulations required by your business. However, this method isn't comprehensive and leaves the business open to not being able to fully meet its goals.

The other method has the URS be specific to your business' needs. The process is more work but leaves less to chance. Developing your own URS isn't always straightforward. Often times, the developed document turns into a mix of "wishlist" requirements from potential and active clients, as well as regulation-mandated requirements. The wishlist items aren't necessarily ignored by developers, but the URS should in fact clearly prioritize requirements as "nice to have" or "essential to system operation," or something in between. Whatever the URS looks like in the end, it's ultimately up to the vendor to be able to demonstrate how the software does and does not meet its requirements.

In the latter half of this guide, you'll be given an opportunity to see an example of a URS for the medical diagnostic and research industries in the form of LIMSpec, an evolving set of software requirements specifications for laboratory informatics systems. Built from requirements found in ASTM E1578-18 Standard Guide for Laboratory Informatics, as well as dozens of other standards and regulations, the LIMSpec examples we provide will demonstrate how a URS is put to use, while also showing you how an informatics system can help you laboratory better meet regulatory requirements.