Difference between revisions of "User:Shawndouglas/sandbox"
Shawndouglas (talk | contribs) (→1.2 Information technology: Added item.) |
Shawndouglas (talk | contribs) (→1.4 General system functions: Updated items.) |
||
Line 467: | Line 467: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''p.''' Does your system provide data archival and retention functionality? | | style="padding:5px; width:500px;" |'''p.''' Does your system provide data archival and retention functionality? If so, what is your system strategy for maintaining the archives as technology changes? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 1,061: | Line 1,061: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''o.''' | | style="padding:5px; width:500px;" |'''o.''' Does your system support both structured and synoptic reporting? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''p.''' Can your system generate | | style="padding:5px; width:500px;" |'''p.''' Can your system generate management and turn-around time reports and graphs? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''q.''' Can your system | | style="padding:5px; width:500px;" |'''q.''' Can your system generate customized final reports? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''r.''' Can your system automatically generate | | style="padding:5px; width:500px;" |'''r.''' Can your system automatically generate laboratory reports of findings and other written documents? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''s.''' Can your system automatically generate and | | style="padding:5px; width:500px;" |'''s.''' Can your system automatically generate individual and aggregate workload and productivity reports on all operational and administrative activities? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''t.''' Can your system generate | | style="padding:5px; width:500px;" |'''t.''' Can your system automatically generate and transmit exception trails and exception reports for all entered and/or stored out-of-specification data? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''u.''' | | style="padding:5px; width:500px;" |'''u.''' Can your system generate a read-only progress report that allows for printed reports of sample status and data collected to date? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''v.''' | | style="padding:5px; width:500px;" |'''v.''' Does your system provide an ad-hoc web reporting interface to report on user-selected criteria? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''w.''' Can your system generate | | style="padding:5px; width:500px;" |'''w.''' Can your system automatically generate and update control charts? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''x.''' | | style="padding:5px; width:500px;" |'''x.''' Can your system generate QA/QC charts for all recovery, precision, and lab control samples via a full statistics package, including Levy-Jennings plots? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''y.''' | | style="padding:5px; width:500px;" |'''y.''' Does your system display history of previous results for an analyte's sample point in a tabular report, graphic trend chart, and statistical summary? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''z.''' | | style="padding:5px; width:500px;" |'''z.''' Can your system automatically generate and post periodic static summary reports on an internal web server? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''aa.''' Does your system | | style="padding:5px; width:500px;" |'''aa.''' Does your system transmit results in a variety of ways including fax, e-mail, print, and website in formats like RTF, PDF, HTML, XML, DOC, XLS, and TXT? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ab.''' Does your system | | style="padding:5px; width:500px;" |'''ab.''' Does your system prohibit issuing reports outside of qualified areas? If so, how? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ac.''' Does your system | | style="padding:5px; width:500px;" |'''ac.''' Does your system electronically transmit results via final report only when all case reviews have been completed by the case coordinator? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ad.''' | | style="padding:5px; width:500px;" |'''ad.''' Does your system include a rules engine to determine the recipients of reports and other documents based on definable parameters? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''ae.''' Does your system allow database access using user-friendly report writing and inquiry tools? | | style="padding:5px; width:500px;" |'''ae.''' Can your system send on-screen output to a printer or file? If so, does it contradict view-only statuses? | ||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''af.''' Does your system allow database access using user-friendly report writing and inquiry tools? | |||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | |
Revision as of 02:07, 26 September 2013
This is my sandbox, where I play with features and test MediaWiki code. If you wish to leave a comment for me, please see my discussion page instead. |
Sandbox begins below
System questionnaire
This questionnaire lists the extensive requirements of a laboratory informatics system, primarily of a LIMS, though these requirements could easily apply to other informatics systems. The intention of this document is 1. to assist labs with identifying their system needs and 2. to help labs better determine if a specific vendor/product meets their requirements in the form of a request for information (RFI).
This questionnaire is comprehensive and includes many items that do not apply to every lab. Additionally, some laboratories' requirements include a functionality item not common to other labs. Section 1.5 "Industry-specific" contains a selection of those industry-specific requirements and will continue to be amended over time. The last section, 1.6 "Custom functions," is designed for the vendor to insert any additional functionality that doesn't fall under the categories provided.
When referencing a particular item for someone else, use the section number followed by the requirement letter, e.g. 1.4.2.f for "Does your system allow the administrator to create custom screens, applications, and reports? Please give details."
Requirement code and notes
In responding to each requirement, the vendor must select a requirement code from the following:
- Y: Meets requirement in commercial off-the-shelf solution as delivered/configured (or vendor provides service)
- YC: Meets requirement only with customization (additional code, using a third-party application, etc.)
- N: Does not meet requirement
- I: Informational response only, N/A
The vendor should ideally enter a requirement code and a response for each functionality question.
To add the requirement code and vendor notes to a functionality item, look for this kind of code in the appropriate section: | style="padding:5px; width:500px;" |'''a.''' Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor
|
1.0 Vendor information
|
1.1 Vendor services
|
1.2 Information technology
|
1.3 Regulatory compliance and security
|
1.4 General system functions
|
1.5 Industry-specific
|
1.6 Custom functions
|