|
Tags: Manual revert Replaced |
| (152 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
| | type = notice | | | type = notice |
| | style = width: 960px; | | | style = width: 960px; |
| | text = This is 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> | | | text = This is my primary sandbox page, 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> |
| }} | | }} |
|
| |
|
| ==Sandbox begins below== | | ==Sandbox begins below== |
|
| |
|
| |
| ==1.0 Vendor information==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="2" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px; width:800px;"| 1.0 '''Vendor information'''
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Company name'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Physical address'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Website'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''LIMSwiki web page'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Contact name and title'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Contact e-mail'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Contact phone and fax'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| | style="padding:5px; width:200px;" |'''Years in business'''
| |
| | style="background-color:white; padding:5px; width:600px;" |
| |
| |-
| |
| |}
| |
| |}
| |
| ==1.1 Vendor services==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.1 '''Vendor services'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does the vendor offer an online demonstration and/or an on-site demonstration?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does the vendor provide a detailed project approach and plan that includes the project team, timeline, deliverables, and risk and issue management procedures?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does the vendor explain their overall project approach, acknowledgement of the deliverables, time/schedule constraints, and any other criteria for the project?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does the vendor provide reliable cost estimates and pricing schedules, including all products and services in the scope of work?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Can the vendor detail the amount of time and staff that purchaser will have to provide for the implementation process?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Can the vendor explain the maintenance and support offered during and after implementation, including times and methods of availability, issue escalation and management, etc.? Give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does the vendor provide a support schedule for the implementation process, including optional support levels and their function and availability? Give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does the vendor provide support during the "go-live" period between system validation/operational deployment and final acceptance/beginning of maintenance and support agreements?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does the vendor provide a gap analysis after initial system installation, identifying the deliverables or tasks remaining?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does the vendor provide a table linking each deliverable to the corresponding user requirement specification it fulfills?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does the vendor use a consistent training methodology for training new users? Give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does the vendor supply [[Laboratory information system|LIS]]-specific training program curricula?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does the vendor provide user, administrator, developer, installation, and reference manuals? Give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does the vendor provide design qualification documentation?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does the vendor provide installation qualification documentation?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does the vendor provide operation qualification documentation?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does the vendor provide performance qualification documentation during implementation?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does the vendor provide well-documented system upgrades that authorized users can independently install?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Does the vendor provide source code for the system?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does the vendor provide an optional comprehensive set of test codes suitable for use by the purchasing facility?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
|
| |
| ==1.2 Information technology==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| ===1.2.1 General IT===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.2.1 '''General IT'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system operate with a web-based interface (hosted on a server and accessed via a web browser) or on a more traditional client-server architecture? If web-based, what technology does it support?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system contain a single database that supports multiple laboratory sites and departments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system's database conform to the [[ODBC|Open Database Connectivity Standard]] (ODBC)?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Did you design your system so upgrades to the back-end database do not require extensive reconfiguration or effectively cripple the system? Please describe.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Did you design your system to not be impacted by multiple users or failover processes? Please describe.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system apply security features to all system files?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system apply login security to all servers and workstations accessing it?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system provide a workstation and server authentication mechanism?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system apply Secured Socket Layer (SSL) encryption on the web client interface?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system encrypt client passwords in a database with support for multi-case and special characters?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system provide all secured users access to its data via the Internet, LAN, or direct modem connection?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system use TCP/IP as its network transport?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system contain an archive utility that doesn't require off-line mode?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system provide local backup and restore capability without support intervention?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system maintain the transactional history of system administrators?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system maintain an analyst communication log, accessible by the administrator?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system architecture facilitate the incorporation of new technology and interfaces?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| ===1.2.2 Hardware environment===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.2 '''Hardware environment'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system prove compatible with a variety of hardware environments? Please describe how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Can your system be utilized with a touch-screen?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| ===1.2.3 Software environment===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.3 '''Software environment'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system utilize a non-proprietary database such as Oracle or Microsoft SQL Server? Please explain.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system prove compatible with a variety of software environments? Please describe how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
|
| |
| ==1.3 Regulatory compliance and security==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| ===1.3.1 Regulatory compliance===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.3.1 '''Regulatory compliance'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system support [[21 CFR Part 11]] and [[40 CFR Part 3]] requirements, including login security, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature? Please explain in detail.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system support [[ISO/IEC 17025]] requirements? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system support [[HIPAA]] requirements? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system support [[GALP]] and/or [[GAMP]] standards? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system support the standards of [[The NELAC Institute]]? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system meet government requirements for handling classified information and documents?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system maintain [[audit trail|audit]] and specification violation trails of all data manipulation — such as result and header information changes — as consistent with all applicable regulations and standards? Provide details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system's audit log retain all data, prohibit any deletions, allows user comments, and allow reporting of contained information?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system provide additional persistent auditing capabilities, such as the audit of cancelled tests and scheduled system functions? If so, what?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system provide user-selectable [[The NELAC Institute|NELAP]]-compliant internal [[chain of custody]] that tracks all specimens and associated containers from the time they are collected until disposed of? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system provide the ability to insert/manage secure [[ELN feature#Electronic signatures|electronic]] and/or digital signatures?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system incorporate automatic date and time stamping of additions, changes, etc.?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| ===1.3.2 Security===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.3.2 '''Security'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system allow system administrators and managers to configure multiple levels of user rights and security by site location, department, [[LIMS feature#Configurable roles and security|role]], and/or specific function? Please explain the depth of this security.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system allow administrators to reset user passwords?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system enforce rules concerning password complexity, reuse, and expiration? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system provide automatic logout based on keyboard or mouse inactivity?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system prompt users for a reason for database record changes?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system allow administrators to modify records, while also maintaining an audit trail of such actions?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system allow authorized personnel to review audit logs at will?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system allow authorized users to query and print chain of custody for items, cases, projects, and batches?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system allow supervisors to override chain of custody?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system automatically track when supervisors review critical result values?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system provide email notification of lockout, security access, and improper workstation access?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system allow multiple users to connect simultaneously to a contract lab?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system provide read-only access to contract laboratory results?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system prohibit issuing reports outside of qualified areas while also allowing reports to be viewed locally or remotely based on security application limits and/or specimen ownership? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
|
| |
| ==1.4 General system functions==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| ===1.4.1 General functions===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.4.1 '''General functions'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system offer non-LIS trained personnel the ability to easily access system data via an intuitive, user-friendly Windows-type graphical user interface (GUI) which permits the display of data from specimen points, projects, and user-defined queries, and can be configured to language, character set, and time zone needs?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system permit remote access for users, system admins, and support agents?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system allow for the use of navigation keys to freely move from field to field?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system allow data tables to be sorted?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' 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;" |'''f.''' Does your system provide single data entry, automatically populate other data fields, and remember pertinent and relevant data so it doesn't need to be re-entered, selected, or searched for?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system support multiple users entering data simultaneously?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system eliminate (or significantly reduce) redundant data entry and paper trails? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system contain one or more spell-check dictionaries that allow authorized users to add, edit, or remove entries?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system provide full database keyword and field [[LIS feature#Query capability|search capability]], including the use of multiple search criteria?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system include the ability to search multiple databases, including those containing legacy data?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system interface with or [[LIS feature#Import data|import existing data]] from other systems and/or databases?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does you system cleanly convert migrated data to allow for reporting of historical specimen collections? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system provide data archival and retention functionality for both paper-based and electronic laboratory records? If so, what is your system strategy for maintaining the archives as technology changes?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system allow users to associate and store both specimen- and non-specimen-related objects such as pictures from microscopes, GCMS scans of peaks, PDF files, spreadsheets, or even raw data files from instrument runs for later processing?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system store more non-traditional information and objects like project- or specimen-specific special information fields, user-defined fields, scanned chain of custodies and digital photos of such items as specimen events, bitmaps, movies, and .wav audio files?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system issue sequential numbers for chain of custody?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does your system's numbering scheme allow for sub-numbering while maintaining parent-child relationships?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Does your system efficiently utilize standardized data input points and enhanced individual workload tracking?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does your system capture data from all laboratory processes, ensuring uniformity of statistical reporting and other electronic data shared with designated users of the data?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' Does your system link or embed standard operation procedures (SOPs) to/in other objects like analysis requests and test results?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''v.''' Does your system [[LIS feature#Alarms and/or alerts|notify users]] of events like the scheduling, receipt, and completion of tasks?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''w.''' Does your system include the ability to set up alerts via email?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''x.''' Does your system have real-time messaging capabilities, including instant messaging to one or more users?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''y.''' Does your system support the use of a voice recognition system (for navigation or transcription) or have that functionality?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''z.''' Does your system offer integrated or online user help screens?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.2 Configuration and customization===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.2 '''Configuration and customization'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Can your system can be configured to meet the workflow of a laboratory without additional programming? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Can your system easily and efficiently be modified to meet lab growth and changing business needs? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system include an application programming interface (API)? If so, what kind? If web, does it use Simple Object Access Protocol (SOAP) or representational state transfer (REST)?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Can your system expand to accommodate a new discipline? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Can your system support [[LIS feature#Customizable fields and/or interface|customized screens]] with user-definable information specific to a customer, department, analysis, etc.?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system allow the administrator to create custom screens, applications, and reports? Please give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does the system allow a user to [[LIS feature#Customizable fields and/or interface|independently add fields]] without requiring reconfiguration of the system, even after routine upgrades and maintenance?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system allow a user to independently add universal fields on all specimens logged into the system at any time during or after implementation, while neither voiding the warranty nor requiring vendor review at a later date?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system support the definition and maintenance of edit tables and lists?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system dynamically change captions (labels) on system fields?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system have dynamically configurable limit periods and notification hierarchy?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system allow for the integration of additional printers and scanners both locally and externally?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| ===1.4.3 Receiving and scheduling===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.3 '''Receiving and scheduling'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system track status and [[workflow]] of the [[Accessioning (medical)|accession]] throughout the laboratory lifecycle, from submission to final analysis, including receiving, diagnostic testing, diagnostic test result reporting, and billing?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system support [[LIS feature#Barcode support|barcoded specimen]] labeling and tracking?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system create and maintain a unique electronic accession record for each accession received?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system support standard-format digital picture and document upload and attachment to electronic accession records?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system support a user-configurable, spreadsheet-style, templated ''multi-specimen'' ([[LIS feature#Sample and result batching|batch]]) login without requiring additional programming?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system support the modification of specimen or specimen batch information prior to actual ''multi-specimen'' (batch) login?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system support ad-hoc specimens not predefined in the specimen point list during ''multi-specimen'' (batch) login?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system create, save, and recall pre-login groups for routine specimens to simplify recurring logins?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system streamline the [[LIS feature#Sample login and management|login]] of recurring specimen projects?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system automatically [[LIS feature#Label support|generate labels]] for recurring specimens and specimen groups?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system allow authorized users to generate user-definable or rules-based chain of custodies, worksheets, routing sheets, and custom labels upon specimen login?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system provide a comprehensive view of all specimens and projects in the system using a color-coded status view of the current and scheduled specimens via user-configurable templates, all without requiring additional programming?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system include [[LIS feature#Environmental monitoring|environmental monitoring]] (EM) functionality or integrate with an external EM product?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system prevent a specimen from being placed in a report queue until approved?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system include comprehensive [[LIS feature#Task and event scheduling|scheduling]], [[LIS feature#Sample tracking|tracking]], and [[LIS feature#Workflow management|flow management]] of specimens?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system allow authorized users to accept, cancel, re-run, and override attributes of one or multiple tests for a given patient?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system allow authorized users to review the available test types in the system, including their reference range and units of measure?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does your system have a "miscellaneous" test code to allow a test undefined in the system to be ordered and billed?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Can your system automatically run medical necessity checks (based on diagnosis codes) on a requested test?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does your system allow authorized users to schedule routine specimens on an hourly, daily, weekly, or monthly basis, allowing them to be enabled and disabled as a group?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' Does your system generate an hourly, daily, weekly, or monthly specimen collection schedule from a scheduling database?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''v.''' Does your system schedule and [[LIS feature#Project and/or task management|assign tasks]] based on available inventory and personnel?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''w.''' Does your system support automatic assignment and scheduling of [[LIS feature#Data and trend analysis|analysis requests]]?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''x.''' Can your system receive accession/analysis request information from web-enabled forms?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''y.''' Can your system electronically receive and process collection and analysis request information and schedules from third parties?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''z.''' Does your system have an inter-lab transfer function?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aa.''' Can your system process automated uploading of field-derived specimen collection data?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ab.''' Does your system allows users to handle billable and non-billable tests on the same accession?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ac.''' Does your system support tracking of shipping and receiving?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.4 Analysis and data entry===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.4 '''Analysis and data entry'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system support a variety of test protocols, each capable of storing test comments, test required, and special information like GCMS conditions or special objects associated with the test? Please give details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system provide normal data range values for diagnostic tests?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system includes default input values for diagnostic tests?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system provide for a single test code requiring multiple analytes as targets?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system limit test code authorization to only qualified personnel and maintain their certification(s) to run assigned tests?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system support and qualify text-based tests?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system support single-component tests such as pH, BOD, CD, etc.?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system allow users to specify a single-component, multi-component, or narrative text test or group of tests, which represent all tests required?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system permit user-generated and modifiable calculations (based on a formulaic language) to be applied to all tests?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system distinguish between routine and duplicate analysis?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system provide an overview of all outstanding tests/analyses for better coordination of work schedules?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system notify analysts of applicable safety hazards associated with a specimen, reagent, or test before testing begins?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system electronically transfer an item during testing from one functional area to another?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system's user interface display visual indicators such as status icons to indicate a specimen's status in the workflow?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system allow file transfer of data from instruments via intelligent interfaces or multi-specimen/multi-test ASCII files, with full on-screen review prior to database commitment?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system permit [[LIS feature#Option for manual result entry|manual data entry]] into an electronic worksheet of test measurements and results?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system allow incorrectly inputted data to be manually corrected?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does your system provide colored visual indication of previously entered data as well as new data associated with a single specimen when a result is entered, with the indicator changing color if the value is out of specification?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Does your system allow automated or semi-automated data insertion?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does your system store non-narrative textual results in searchable fields?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| ===1.4.5 Post-analysis and validation===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.5 '''Post-analysis and validation'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system update specimen/item status when tests are completed?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Can your system automatically reorder a test or order additional tests if results don't meet lab-defined criteria?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system read results from previously entered tests to calculate a final result and immediately display the calculated result?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system allow authorized users to review all analytical results, including pricing, spec violations, history or trend analysis by analyte, and comments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Can your system graphically display the results of one or more tests in a graph (normalized or otherwise) for the purpose of visualizing data or searching for possible trends?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system allow on-screen review of the stored test result, diluted result with corrected method detection limits (MDLs), and qualifiers after running samples for multiple dilutions as in [[gas chromatography–mass spectrometry]] (GC-MS)?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system display the standard operating procedure (SOP) associated with each test result to ensure proper techniques were used?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system store test-related analysis comments with the test?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system provide auto-commenting for common laboratory result comments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system provide for high-volume multi-component transfers of test results, with the ability to automatically match samples to data files in either a backlog mode or a designated file mode, to parse the data, and to review and commit the sample data?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system's results [[LIMS feature#Data validation|validation process]] access all information about a sample or group of samples, including comments or special information about the sample?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system's results validation process check each result against its individual sample location specifications (both warning and specification limits)?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system support validation at the analysis and sample level, while also prohibiting sample validation when analysis validation is incomplete?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system use a menu-driven process for results validation?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system provide secure electronic peer review of results?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Can your system clearly differentiate released preliminary data from fully validated results?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system validate/approve data prior to being moved to the main database?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does your system fully manage all aspects of laboratory [[LIMS feature#QA/QC functions|quality control]], including the reporting and charting of all quality control data captured in the lab? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Does your system provide a base for a quality assurance program, including proficiency testing, scheduled maintenance of equipment, etc.? Please explain how.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does your system distinguish QA/QC duplicates from normal samples?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' Does your system allow QA/QC tests to be easily created and associated with the primary analytical test?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''v.''' Does your system allow manual entry of QA and QC data not captured as part of the system's regular processes?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''w.''' Does your system calculate monthly QA/QC percentages for testing?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''x.''' Does your system automatically flag out-of-range quality control limits?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''y.''' Does your system check data files for specification and corrects them for specific reporting and analyte limits and qualifiers like dilution factor, automatically assigning qualifiers based on project analyte limiting?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.6 Instruments===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.6 '''Instruments'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system bilaterally [[LIS feature#Instrument interfacing and management|interface with instruments]] and related software? If so, please provide details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Can your system download data directly from laboratory instruments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system permit the defining and exporting of sequences to instruments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system track and report on laboratory equipment usage?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system allow automatic or manual reservation/scheduling of laboratory instruments?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system automatically (or manually allow an authorized user to) remove an instrument from potential use when it falls out of tolerance limit or requires scheduled calibration?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system provide a database of preventative maintenance, calibration, and repair records for laboratory equipment, preferably supported by standardized reporting?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Can your system schedule calibration, verification, and maintenance tasks in the worksheets or work flow process and make that schedule available for viewing?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system allow users to create and edit instrument maintenance profiles?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.7 External system interfaces===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.7 '''External system interfaces'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system support a library of common and/or basic electronic data deliverable (EDD) formats? If so, which?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Can your system transfer data to and from another record management system? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system [[LIS feature#Third-party software integration|integrate]] with Microsoft Exchange services?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Can your system [[LIS feature#Import data|import data]] from and export data to Microsoft Word, Excel, and/or Access?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Can your system interface with non-Microsoft programs? If so, which?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Can your system interface with external billing systems? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Can your system interface with enterprise resource planning (ERP) systems? If so, how?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Can your system interface with external contract or reference laboratories to electronically send or retrieve datasheets, analysis reports, and other related information?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Can your system exchange data with National Identification System (NAIS) tracking systems?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Can your system generate and exchange data with other systems using [[Health Level 7]] (HL7) standards?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Can your system leverage the application programming interface (API) of other systems to establish integration between systems?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system provide a real-time interface for viewing live and stored data transactions and errors generated by interfaced instruments and systems?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Can your system transmit status changes of specimens, inventory, equipment, etc. to an external system?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Can your system direct output from ad-hoc queries to a computer file for subsequent analysis by other software?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Does your system support the manual retransmission of data to interfaced systems?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system support [[LIS feature#Mobile device integration|dockable mobile devices]] and handle information exchange between them and the system?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system support the use of optical character recognition (OCR) software?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.8 Reporting===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.8 '''Reporting'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system include a versatile report writer and forms generator that can generate reports from any data in tables? If so, please provide details.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system include a custom graphic generator for forms?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system interface with a third-party reporting application?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system allow the development of [[LIS feature#Configurable templates and forms|custom templates]] for different types of reports?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system maintain template versions and renditions, allowing management and tracking of the template over time?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Can your system generate template letters for semi-annual reports?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system support report queries by fields/keys, status, completion, or other variables?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system use Microsoft Office tools for formatting reports?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system support multiple web browsers for viewing online reports? If so, list which ones.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Can your system generate, store, reproduce, and display laboratory, statistical, and inventory reports on demand, including narrative?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system include several standard reports and query routines to access all specimens with the pending status through a backlog report that includes the following criteria: all laboratory, department, analysis, submission date, collection date, prep test complete, location, project, specimen delivery group, and other user-selectable options?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Can your system indicate whether a report is preliminary, amended, corrected, or final while retaining revision history?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system support both structured and [[LIS feature#Synoptic reporting|synoptic reporting]]?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Can your system generate management and turn-around time reports and graphs?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Can your system generate customized final reports?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Can your system automatically generate laboratory reports of findings and other written documents?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Can your system generate a read-only progress report that allows for printed reports of specimen status and data collected to date?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' Can your system automatically generate and update control charts?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''v.''' Can your system generate QA/QC charts for all recovery, precision, and lab control specimens via a full statistics package, including Levy-Jennings plots and Westgard multi-rule?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''w.''' Does your system display history of previous results for an analyte's specimen point in a tabular report, graphic trend chart, and statistical summary?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''x.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''y.''' 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? Please explain.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''z.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''aa.''' 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;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''ab.''' Does your system allow database access using user-friendly report writing and inquiry tools?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
|
| |
| ===1.4.9 Laboratory management===
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.4.9 '''Laboratory management'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:500px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''a.''' Does your system allow the creation, modification, and duplication of user profiles?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''b.''' Does your system allow entry, maintenance, and administration of [[LIS feature#Customer, supplier, and physician management|customers]], suppliers, and other outside entities?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''c.''' Does your system allow the creation, modification, and maintenance of user [[LIS feature#Performance evaluation|training records]] and associated training materials?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''d.''' Does your system allow the management of information workflow, including notifications for requests and exigencies?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''e.''' Does your system allow the [[LIS feature#Document creation and management|management of documents]] like SOPs, MSDS, etc. to better ensure they are current and traceable?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''f.''' Does your system allow the management and monitoring of resources by analyst, priority, analysis, and instrument?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''g.''' Does your system allow authorized persons to select and assign tasks by analysts, work group, instrument, test, specimen, and priority?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''h.''' Does your system allow authorized persons to review unassigned work by discipline and by lab?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''i.''' Does your system allow authorized persons to review pending work by analyst prior to assigning additional work?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''j.''' Does your system manage and report on reference specimens, reagents, and other inventory, including by department? If so, to what extent?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''k.''' Does your system automatically warn specified users when [[LIS feature#Inventory management|inventory counts]] reach a definable threshold and either prompt for or process a reorder?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''l.''' Does your system allow authorized users to monitor and report on reference and reagent creation, use, and expiration?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''m.''' Does your system allow authorized users to search [[LIS feature#Billing and revenue management|invoice information]] by invoice number, account number, accession, payment types, client, or requested diagnostic test(s)?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''n.''' Does your system include [[LIS feature#Performance evaluation|performance assessment]] tracking?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''o.''' Can your system receive, record, and maintain customer and employee feedback and apply tools to track the investigation, resolution, and success of any necessary corrective action?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''p.''' Does your system monitor proficiency test assignment, completion, and casework qualification for analytical staff?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''q.''' Does your system provide analysis tools to better support laboratory functions like resource planning, productivity projections, workload distribution, and work scheduling? Do those tools display information in a consolidated view, with the ability to drill down to more detailed data? Please explain.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''r.''' Does your system calculate administrative and lab costs?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''s.''' Does your system capture and maintain patient, submitter, supplier, and other client demographics and billing information for costing, invoicing, collecting, reporting, and other billing activities?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''t.''' Does your system support multiple customer [[LIS feature#Billing and revenue management|payment sources]] (e.g. grants}? Please explain the extent.
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:5px; width:500px;" |'''u.''' Does your system track number of visits per specific industry?
| |
| | style="background-color:white; padding:5px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
|
| |
| ==1.5 System-specific==
| |
|
| |
| The system-specific addendum [[LIMS and laboratory informatics questionnaire/1.5 System-specific|can be found here]].
| |
|
| |
| ==1.6 Industry-specific==
| |
|
| |
| The industry-specific addendum [[LIMS and laboratory informatics questionnaire/1.6 Industry-specific|can be found here]].
| |
|
| |
| ==1.7 Custom requirements==
| |
| {|
| |
| | STYLE="vertical-align:top;"|
| |
| {| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
| |
| |-
| |
| ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px; width:1300px;"| 1.7 '''Custom requirements'''
| |
| |-
| |
| ! style="color:brown; background-color:#ffffee; width:470px;"| Request for information
| |
| ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
| |
| ! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''a.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''b.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''c.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''d.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''e.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''f.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''g.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''h.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''i.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''h.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''i.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| | style="padding:15px; width:470px;" |'''j.'''
| |
| | style="background-color:white; padding:15px;" |
| |
| | style="background-color:white;" |
| |
| |-
| |
| |}
| |
| |}
| |
