Difference between revisions of "User:Shawndouglas/sandbox"
Shawndouglas (talk | contribs) (→1.3 Regulatory compliance and security: Updated via Jeff's feedback.) |
Shawndouglas (talk | contribs) (→1.4 General system functions: Made recommended changes from Jeff.) |
||
Line 543: | Line 543: | ||
! style="color:brown; background-color:#ffffee; width:700px;"| Vendor response | ! 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 characteristics of a laboratory? Please explain how. | | style="padding:5px; width:500px;" |'''a.''' Can your system can be configured to meet the characteristics of a laboratory without additional programming? Please explain how. | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 551: | Line 551: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''c.''' | | 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''d.''' Can your system | | 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''e.''' | | style="padding:5px; width:500px;" |'''e.''' Can your system support customized screens with user-definable information specific to a customer, department, analysis, etc.? | ||
| 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;" |'''f.''' Does | | 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''g.''' Does | | style="padding:5px; width:500px;" |'''g.''' Does the system allow a user to 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''h.''' Does your system | | style="padding:5px; width:500px;" |'''h.''' Does your system allow a user to independently add universal fields on all samples 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''i.''' Does your system | | style="padding:5px; width:500px;" |'''i.''' Does your system dynamically change captions (labels) on system fields? | ||
| 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;" |'''j.''' Does your system allow for the integration of additional printers and scanners both locally and externally? | | style="padding:5px; width:500px;" |'''j.''' 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;" |'''k.''' 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 709: | Line 713: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''i.''' Does your system permit user-generated and modifiable | | 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
Line 903: | Line 907: | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |'''f.''' Can your system interface with contract laboratories to electronically retrieve datasheets, sample analysis, and other related information? | | 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 contract laboratories to electronically retrieve datasheets, sample analysis, and other related information? | |||
| style="background-color:white; padding:5px;" | | |||
| style="background-color:white;" | | |||
|- | |||
| style="padding:5px; width:500px;" |'''h.''' 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;" |'''i.''' 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |''' | | style="padding:5px; width:500px;" |'''j.''' 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |''' | | style="padding:5px; width:500px;" |'''k.''' 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; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | | ||
|- | |- | ||
| style="padding:5px; width:500px;" |''' | | style="padding:5px; width:500px;" |'''l.''' Does your system support dockable mobile devices and handle information exchange between them and the system? | ||
| style="background-color:white; padding:5px;" | | | style="background-color:white; padding:5px;" | | ||
| style="background-color:white;" | | | style="background-color:white;" | |
Revision as of 17:22, 19 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 questionnaire" contains a selection of those industry-specific requirements and will continue to be amended over time. The last section, 1.6 "Custom system functions questionnaire," 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 the system allow the system admin to create custom screens, apps, and reports?"
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
|