Difference between revisions of "User:Shawndouglas/sandbox"

From LIMSWiki
Jump to navigationJump to search
(→‎Citation: Added content.)
(Saving content. Adding more.)
Line 8: Line 8:
==Sandbox begins below==
==Sandbox begins below==


You'll notice a box with text and a big blue "i" in it above. We'll get to that in a second. But first let's talk about the...
:1.1 '''Evaluation demonstration requirements'''
::a. The solution must be available for full demonstration (preferably online), and the provider must be able to conduct an on-site demonstration. Explain your ability to meet these conditions.
:1.2 '''IT requirements'''
::1.2.1 IT General
:::a. Single database that supports multiple laboratory sites and laboratory departments


===Links===


This is me making an internal link to the template "ombox," which is used on this page: [[Template:Ombox]]
{|
 
| STYLE="vertical-align:top;"|
This is me making an internal link to the template "ombox," but this time making different text appear for the link: [[Template:Ombox|I'm such a rebel]]
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
 
|-
This is me making an external link to the same template located on Wikipedia: [http://en.wikipedia.org/wiki/Template:Ombox]
  ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.1 '''Evaluation demonstration requirements'''
 
|-
This is me making an external link to the same template located on Wikipedia, using different link text: [http://en.wikipedia.org/wiki/Template:Ombox Why is there no pipe in this type of link?]
  ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
 
  ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
<pre>
  ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
You should notice the difference between these two types of links and how to format them.
|-
 
  | style="padding:5px; width:500px;" |'''a.''' Available for full demonstration (preferably online) and provider able to conduct an on-site demonstration
You can make an internal link by using a set of double square brackets. The title can be left as the default:
  | style="background-color:white; padding:5px;" |
[[Laboratory informatics]] yields...
  | style="background-color:white;" |
</pre>
|-
[[Laboratory informatics]]
|}
<pre>
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
Or you can give it a new title by adding a pipe (|) and then typing the text you want to appear in place of the original:
|-
[[Laboratory informatics|cool laboratory stuff]] yields...
  ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.2 '''IT requirements'''
</pre>
|-
[[Laboratory informatics|cool laboratory stuff]]
  ! colspan="3" style="color:DarkSlateGray; text-align:left; padding-left:40px;"| 1.2.1 '''IT general'''
<pre>
|-
You can make an external link by using a set of single square brackets. The title can be left blank:
  ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
[http://www.nupedia.com] yields...
  ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
</pre>
  ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
[http://www.nupedia.com]
|-
<pre>
  | style="padding:5px; width:500px;" |'''a.''' Single database that supports multiple laboratory sites and laboratory departments
However, it's better you give it a title by adding one space and typing the text you want to appear in place of the URL:
  | style="background-color:white; padding:5px;" |
[http://www.nupedia.com Nupedia] yields...
  | style="background-color:white;" |
</pre>
|-
[http://www.nupedia.com Nupedia]
  | style="padding:5px; width:500px;" |'''b.''' Client passwords encrypted in database with support for multi-case and special characters
 
  | style="background-color:white; padding:5px;" |
Consult the relevant [[Help:Contents#Links|Help:Contents]] section for more information.
  | style="background-color:white;" |
 
|-
===Templates===
  | style="padding:5px; width:500px;" |'''c.''' Secured Socket Layer (SSL) encryption on web client interface
 
  | style="background-color:white; padding:5px;" |
Let's get back to that box with text and a big blue "i" at the top. We call that an "infobox." That's created using the template "ombox," referenced above in the first set of example links. Open one of those links in a new tab or window to learn more about this template.
  | style="background-color:white;" |
 
|-
Templates are distinct because they contain two braces in front (like this: <nowiki>{{</nowiki> ) and two in the back (like this: <nowiki>}}</nowiki> ).
  | style="padding:5px; width:500px;" |'''d.''' System designed so upgrades to back-end database do not require extensive reconfiguration or effectively cripple the system
 
  | style="background-color:white; padding:5px;" |
Here are some internal links to pages on this wiki that utilize a variety of different templates. Let's look at each page (open in a new tab or window) and choose the "edit" option to see the code:
  | style="background-color:white;" |
 
|-
* [[LIMS vendor]]
  | style="padding:5px; width:500px;" |'''e.''' System provides all secured users access to its data via the Internet, LAN, or direct modem connection
* [[LIMSWiki:Vendor page]]
  | style="background-color:white; padding:5px;" |
* [[2nd Sight Solutions]]
  | style="background-color:white;" |
* [[National Cancer Institute]]
|-
* [[LIMSWiki:Product page]]
  | style="padding:5px; width:500px;" |'''f.''' LIMS database conforms to [[ODBC|Open Database Connectivity Standard]] (ODBC)
 
  | style="background-color:white; padding:5px;" |
Consult the relevant [[Help:Contents#Templates|Help:Contents]] section for more information.
  | style="background-color:white;" |
 
|-
===Formatting text===
  | style="padding:5px; width:500px;" |'''g.''' All LIMS system files capable of having security applied to them
 
  | style="background-color:white; padding:5px;" |
====Bold text====
  | style="background-color:white;" |
 
|-
'''Here I bold this text for effect''': Do you think it looks ok?
  | style="padding:5px; width:500px;" |'''h.''' All servers and workstations accessing LIMS system have login security
 
  | style="background-color:white; padding:5px;" |
I can even make a link appear in bold like this: '''[[LIMS vendor]]'''
  | style="background-color:white;" |
<pre>
|-
How did I do that? I simply added three apostrophes to each side like so:
  | style="padding:5px; width:500px;" |'''i.''' LIMS able to use TCP/IP as its network transport
 
  | style="background-color:white; padding:5px;" |
'''Here I bold this text for effect'''
  | style="background-color:white;" |
 
|-
'''[[LIMS vendor]]'''
  | style="padding:5px; width:500px;" |'''j.''' Sized to not be impacted by multiple users or failover processes
</pre>
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
====Italic text====
|-
 
  | style="padding:5px; width:500px;" |'''k.''' Archive utility without off-line
''Here's italic text for you'': What do you think?
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
Like bold text, I can italicize a link like this: ''[[LIMS vendor]]''
|-
 
  | style="padding:5px; width:500px;" |'''l.''' System provides a workstation and server authentication mechanism
<pre>
  | style="background-color:white; padding:5px;" |
How did I do that? I simply added two apostrophes to each side like so:
  | style="background-color:white;" |
 
|-
''Here's italic text for you''
  | style="padding:5px; width:500px;" |'''m.''' System provides local restore capability without support intervention
 
  | style="background-color:white; padding:5px;" |
''[[LIMS vendor]]''
  | style="background-color:white;" |
</pre>
|-
 
  | style="padding:5px; width:500px;" |'''n.''' System Interfaces with database using ASP/ASP.net
====Preformatted text====
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
You'll notice so far I've used several instances of gray boxes with wiki code in them on this page. How do you display that wiki code like that without the browser running it? You do it by using the preformatted text tag:
|-
 
  | style="padding:5px; width:500px;" |'''o.''' System able to maintain transactional history
<pre>&lt;pre&gt;This is preformatted text. Here is the ombox code used on this page:
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
{{ombox
|-
| type      = notice
  ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.2 '''Hardware environment'''
| 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>
  ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
}}
  ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
&lt;/pre&gt;</pre>
  ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
 
|-
So you essentially use the <nowiki><pre></nowiki> tag to display the code without rendering it.
  | style="padding:5px; width:500px;" |'''a.''' System compatible with the hardware environment
 
  | style="background-color:white; padding:5px;" |
But wait a minute. How did I just get the <nowiki><pre></nowiki> tag to show on the page without the browser running it? In this sentence and the one previous to this, I used a different technique to display the tag:
  | style="background-color:white;" |
 
|-
<pre>
  ! colspan="3" style="color:DarkSlateGray;text-align:left; padding-left:40px;"| 1.2.3 '''Software environment'''
&lt;nowiki&gt;&lt;pre&gt;&lt;/nowiki&gt;
|-
</pre>
  ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
 
  ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
I used the <nowiki><nowiki></nowiki> tag to display what would otherwise be rendered as code. Note that with both tags, I had to "close" their use with a corresponding duplicate but with the "/" character in front of the word.
  ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
 
|-
This may seem a bit confusing at first, but don't worry. You'll get the hang of this type of formatting. I wanted to introduce it for the next topic: spacing.
  | style="padding:5px; width:500px;" |'''a.''' System utilizes a non-proprietary database such as Oracle or Microsoft SQL Server
 
  | style="background-color:white; padding:5px;" |
====Spacing====
  | style="background-color:white;" |
 
|-
This is my first line of text.
  | style="padding:5px; width:500px;" |'''b.''' System compatible with the software environment
This is my second line of text.
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
Here's what I entered into the edit box to get the above to appear:
|-
<pre>
|}
This is my first line of text.
{| class="wikitable collapsible" border="1" cellpadding="10" cellspacing="0"
This is my second line of text.
|-
</pre>
  ! colspan="3" style="text-align:left; padding-left:20px; padding-top:10px; padding-bottom:10px;"| 1.3 '''Regulatory compliance requirements'''
 
|-
Notice what happens if I don't put a space between the lines of text in the edit screen? The lines run together. You'd think putting a line under another with a hard return would be enough, but it's not. You must add an additional hard return, creating a space between the lines in the edit box.
  ! style="color:brown; background-color:#ffffee; width:500px;"| Functional requirement
 
  ! style="color:brown; background-color:#ffffee; width:100px;"| Requirement code
I actually want it to look like this:
  ! style="color:brown; background-color:#ffffee; width:700px;"| Notes
 
|-
This is my first line of text.
  | style="padding:5px; width:500px;" |'''a.''' LIMS has security consistent with [[21 CFR Part 11]] and [[40 CFR Part 3]]; system has security to enter the system, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature; provides a single point of access for all programs associated with the system for ease of administration and use
 
  | style="background-color:white; padding:5px;" |
This is my second line of text.
  | style="background-color:white;" |
 
|-
So I have to edit it like this in the code:
  | style="padding:5px; width:500px;" |'''b.''' [[Audit trail]] and specifications violation trails maintained; audit trail includes result changes, header information changes, as well as the user, date/time, and a required reason for the changes as a standard part of the application
 
  | style="background-color:white; padding:5px;" |
<pre>
  | style="background-color:white;" |
This is my first line of text.
|-
 
  | style="padding:5px; width:500px;" |'''c.''' System maintains an audit trail of all data manipulation, consistent with all applicable regulations and standards
This is my second line of text.
  | style="background-color:white; padding:5px;" |
</pre>
  | style="background-color:white;" |
 
|-
There are several relevant [[Help:Contents]] sections with more information about text formatting.
  | style="padding:5px; width:500px;" |'''d.''' System provides user selectable [[The NELAC Institute|NELAP]]-compliant internal [[chain of custody]] that tracks all samples and associated containers from the time they are collected until disposed of
 
  | style="background-color:white; padding:5px;" |
===Organizing text===
  | style="background-color:white;" |
 
|-
If you are viewing the code to this page, you'll notice there are several bits of code with numerous "=" signs. These are responsible for creating headings and subheadings.
  | style="padding:5px; width:500px;" |'''e.''' System meets all standards of [[The NELAC Institute]]
 
  | style="background-color:white; padding:5px;" |
<pre>
  | style="background-color:white;" |
You'll notice the first example:
|-
 
  | style="padding:5px; width:500px;" |'''f.''' System provides persistent auditing capabilities
==Sandbox begins below==
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
This is the first level of headings, the section heading. You do this by placing two "=" in front and behind some text.
|-
</pre>
  | style="padding:5px; width:500px;" |'''g.''' System meets government requirements for handling classified information and documents
 
  | style="background-color:white; padding:5px;" |
'''NOTE''': ''Know we have a rule here, just as in Wikipedia; with the exception of proper nouns, only the first word of the heading or subheading is capitalized! In this case, it's "Organizing text," not "Organizing Text."''
  | style="background-color:white;" |
 
|-
<pre>
  | style="padding:5px; width:500px;" |'''h.''' System includes automatic date and time stamping
If you look under the heading "Sandbox begins below," you'll notice numerous subheadings. And in the subsection "Formatting text" there is yet another subheading below that:
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
===Formatting text===
|-
 
  | style="padding:5px; width:500px;" |'''i.''' System provides the ability to insert/manage secure electronic and/or digital signatures
====Bold text====
  | style="background-color:white; padding:5px;" |
 
  | style="background-color:white;" |
Simply add another "=" to the front and back to create an additional subheading.
|-
</pre>
  | style="padding:5px; width:500px;" |'''j.''' System supports [[ISO/IEC 17025]]
 
  | style="background-color:white; padding:5px;" |
You can also create ordered and unordered lists, add definition lists, add extra spacing in the front of text (useful for commenting on talk pages), and how to sign your comments (also very important). Learn about these items and more in the relevant [[Help:Contents#Organizing_your_writing|Help:Contents]] section.
  | style="background-color:white;" |
 
|-
===Citation===
  | style="padding:5px; width:500px;" |'''k.''' System supports [[21 CFR Part 11]]
 
  | style="background-color:white; padding:5px;" |
To begin using citations, it's easy to start with a copy/paste of existing citation code. Inline citations are added directly after a piece of information or quote in a body of wiki text.
  | style="background-color:white;" |
 
|-
You'll want to use this page as your initial guide: [[LIMSWiki:Citation guidelines]]
  | style="padding:5px; width:500px;" |'''l.''' System supports [[40 CFR Part 3]]
 
  | style="background-color:white; padding:5px;" |
It details the citation code you'll use on probably 95 percent of the references you make: Cite web, Cite book, and Cite journal
  | style="background-color:white;" |
 
|-
You can copy code from there, paste it into your edit, and then edit the values of the fields. That page also has links to the original templates in case you need additional attributes not listed in the examples.
  | style="padding:5px; width:500px;" |'''m.''' System supports [[HIPAA]] requirements
 
  | style="background-color:white; padding:5px;" |
Also, it's imperative to include a references section on any page that includes inline citations. Otherwise, pages won't show up properly. You do that by placing the following code:
  | style="background-color:white;" |
 
|-
<pre>
  | style="padding:5px; width:500px;" |'''n.''' System supports [[GALP]] and/or [[GAMP]] standards
==References==
  | style="background-color:white; padding:5px;" |
<references />
  | style="background-color:white;" |
</pre>
|-
 
|}
===Images===
|}
 
[[File:Wiki puzzle.svg|Wiki puzzle]]This is me playing with linking to images on Wikimedia Commons. We'll get into image uploading and linking a little later.

Revision as of 17:05, 14 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

1.1 Evaluation demonstration requirements
a. The solution must be available for full demonstration (preferably online), and the provider must be able to conduct an on-site demonstration. Explain your ability to meet these conditions.
1.2 IT requirements
1.2.1 IT General
a. Single database that supports multiple laboratory sites and laboratory departments


1.1 Evaluation demonstration requirements
Functional requirement Requirement code Notes
a. Available for full demonstration (preferably online) and provider able to conduct an on-site demonstration
1.2 IT requirements
1.2.1 IT general
Functional requirement Requirement code Notes
a. Single database that supports multiple laboratory sites and laboratory departments
b. Client passwords encrypted in database with support for multi-case and special characters
c. Secured Socket Layer (SSL) encryption on web client interface
d. System designed so upgrades to back-end database do not require extensive reconfiguration or effectively cripple the system
e. System provides all secured users access to its data via the Internet, LAN, or direct modem connection
f. LIMS database conforms to Open Database Connectivity Standard (ODBC)
g. All LIMS system files capable of having security applied to them
h. All servers and workstations accessing LIMS system have login security
i. LIMS able to use TCP/IP as its network transport
j. Sized to not be impacted by multiple users or failover processes
k. Archive utility without off-line
l. System provides a workstation and server authentication mechanism
m. System provides local restore capability without support intervention
n. System Interfaces with database using ASP/ASP.net
o. System able to maintain transactional history
1.2.2 Hardware environment
Functional requirement Requirement code Notes
a. System compatible with the hardware environment
1.2.3 Software environment
Functional requirement Requirement code Notes
a. System utilizes a non-proprietary database such as Oracle or Microsoft SQL Server
b. System compatible with the software environment
1.3 Regulatory compliance requirements
Functional requirement Requirement code Notes
a. LIMS has security consistent with 21 CFR Part 11 and 40 CFR Part 3; system has security to enter the system, settable automatic logouts, periodic requirements for mandatory password changes, limits on reusability of passwords, and full electronic signature; provides a single point of access for all programs associated with the system for ease of administration and use
b. Audit trail and specifications violation trails maintained; audit trail includes result changes, header information changes, as well as the user, date/time, and a required reason for the changes as a standard part of the application
c. System maintains an audit trail of all data manipulation, consistent with all applicable regulations and standards
d. System provides user selectable NELAP-compliant internal chain of custody that tracks all samples and associated containers from the time they are collected until disposed of
e. System meets all standards of The NELAC Institute
f. System provides persistent auditing capabilities
g. System meets government requirements for handling classified information and documents
h. System includes automatic date and time stamping
i. System provides the ability to insert/manage secure electronic and/or digital signatures
j. System supports ISO/IEC 17025
k. System supports 21 CFR Part 11
l. System supports 40 CFR Part 3
m. System supports HIPAA requirements
n. System supports GALP and/or GAMP standards
Retrieved from "https://www.limswiki.org/index.php?title=User:Shawndouglas/sandbox&oldid=12198"