wikidoc - User contributions [en]

wikidoc:Log in

2010-07-13T11:43:13Z

Levacher: /* Logging In */ link to C Michael Gibson user page

==''' Logging In'''==
WikiDoc requires that you [[Wikidoc:log in|log in]] with your full name.
*Once you are logged in, please provide contact information. In the event that we have questions regarding the content posted, posting your biography would be optimal, however an email is sufficient (telephone or fax is optional)
:*This can be done by clicking on your name, and inserting the information appropriately
*Click on C Michael Gibson on the user page to see an example or click on this [[User:C Michael Gibson|link]]

== Why log in? ==

Logging in is required for these reasons:

* Other users will be able to recognise you by your username when you make changes to pages. As a "name" an IP address is somewhat clumsy. Also, if you use computers at different locations (home, office, internet cafe, etc.) you have a different IP-address in each case; even in the same location, depending on the Internet connection, the IP-address may be different each time. Therefore a username is better to maintain an identity.
*You will have your own user page where you can write a bit about yourself, and a user talk page which you can use to communicate with other users.
* You will be able to mark an edit as minor, which avoids inconvenience for other users.
* You will be able to keep track of changes to modules you are interested in using a watch list.
* If you choose to give an email address, other users will be able to contact you by email. This feature is anonymous - the user who emails you will not know your email address. You don't have to give your email address if you don't want to.
** Check the privacy policy of the individual site you're visiting.
* You will be able to rename pages.
* You will be able to set your own preferences, to change things such as:
** The number of pages displayed in [[Special:Recent changes|Recent changes]]
** The fonts, colours and layout of the site, by using different skins.

== How to log in ==

First, make sure that your browser accepts cookies. Some browsers can accept or reject cookies from individual sites; users of these should configure the browser to accept cookies from each wiki you plan to edit, such as www.clinicaltrialresults.org.

Click on the ''[[wikidoc:log in|Log in]]'' link at the top right of the page. You will then be prompted to enter your username and password. If you haven't logged in before, you will need to enter your password twice.

If you click the box ''Remember me'', you will not have to give your password again when you access MediaWiki wiki from the same computer. This feature will only work if your password was not generated by the Mediawiki software. So change your password please.

Logging in and setting preferences are done separately on each wiki. You may find like to maintain a cross-wiki identity by using the same username on each wiki that you use, if that name is still free.

=== Log in problems ===
If you appear to be able to log in, but as soon as you try to look at a page after the 'Log in successful' page you appear logged out again, it is very likely to be a cookie problem. If you are certain that cookies are enabled, make sure that you haven't inadvertently listed server on a list of sites to never allow cookies for (This feature is available in (at least) Mozilla Firebird (Firefox) 0.6 and above and Microsoft Internet Explorer version 6 and above). Also make sure your computer's date and time are set correctly; if they are not, cookies may expire before they are supposed to. Note that some firewall and ad-blocking software may interfere with the cookie that it uses to keep a person logged in.

In addition to these steps, check to make sure PHP's directory for storing session data is writable. This directory can be found in the php.ini file under the session.save_path setting. Errors in this php.ini setting can also cause other problems. Examples of these errors are referencing a non-existent directory or leaving out " marks around the directory name. Random Wiki pages or edit previews might appear blank in Internet Explorer, but not with other browsers. Also, the Save Page button might act as if one had pressed the Show Preview button when a user is logged in, but work correctly when one is not logged in.

A user may occasionally find him/herself "automatically " logged out in between beginning an edit and saving it, or when switching between multiple pages open in multiple windows. This can be a result of your browser's cookie, cache, or firewall settings, but due to the nature of the MediaWiki software, some user ID information is stored in the servers; sometimes, especially during heavy server load, the system can "glitch" and your ID information will be misplaced, resulting in a logout. Regardless of the reason for the logout, the simplest solution to the problem is to check the '''Remember me''' box. If you do this on a computer that can be accessed by more than one person (i.e. at the library, at work, at school), please find and erase your user ID cookies after your editing session.

If you log in and enabled the cookie feature, a subsequent log in as a different user without the cookie feature enabled will appear as logged out.

=== What if I forget the password? ===
If you enter an e-mail address when signing up for the account, or in your Preferences, you can request on the login screen for a temporary password to be sent to that address, which will allow you to retrieve your account. If you did not enter an e-mail address, or the address was out of date, but you are determined to regain access to the account, you ''might'' be able to persuade someone with direct access to the database that it is your account, and ask them to retrieve it for you.

=== Creating an account ===

To create an account, select [[Wikidoc:log in|Log in]] (top right of page) then [ create an account. You usually need only provide a username and password. Some wikis require a visual Users with text, speech, or legacy browsers will be unable to create an account if they can not view this image.
== How to set preferences ==

Click on the ''Preferences'' link at the top right of the page for various options, including:
* Changing your password.
* Changing the ''skin'', which changes the way that the web pages look.

== Your ''User page'' and ''User talk page'' ==

As a logged in user, you will be able to create your own ''user page'' and ''user talk page''. When you are logged in, you will see your username displayed at the top right of the page. Click on this to get to your user page, which you can edit in the same way as any MediaWiki wiki page.

Most users write a little bit about themselves and their interests on their user page.

You also have a ''User talk page''. You can access this by clicking on the ''Talk'' link next to your username at the top right of the page. Other people may write messages in your user talk page by editing it, and you can respond.
== How to log out ==

You can log out any time by clicking on the ''Log out'' link at the top right of the page.

All information on this page is attributed to Wikipedia and its contributors

wikidoc:Editing policy

2010-07-08T15:01:15Z

Levacher: /* On editing styles */ spelling Etiquette + link

==Perfection Not Required, or, The Joy of Editing==

It is wonderful when someone adds complete, detailed, medical information to Wikidoc. This should always be encouraged.

However, one of the great advantages of the Wiki system is that incomplete or
poorly written first drafts of articles can evolve into polished, presentable masterpieces through the process of collaborative editing. This gives our approach an advantage over other ways of producing similar end-products. Hence, the submission of rough drafts should also be encouraged as much as possible.

One person can start an article with, perhaps, an overview or a few random facts. Meanwhile,
another person can add an additional differential diagnosis or symptom. Someone else can round off the article with additional test. Yet another can play up an angle that has been neglected, or reword the earlier opinions to a more neutral point of view. Another person might have facts and figures or a graphic to include, and yet another might fix the spelling and grammatical errors that have crept in throughout these multiple edits.

As all this material is added, anyone may contribute and refactor to turn it into a more cohesive whole. Then, more text may be added; and it may also be rewritten... and so on.

During this process, the article might look like a first draft; or worse,
a random collection of notes and factoids. Rather than being horrified by this ugliness, we should rejoice in its potential, and have faith that the [[Help:Editing|editing process]] will turn it into essential medical information. Of course, we don't have to like it; we may occasionally criticize really substandard work, in addition to simply correcting it. It is most important that it is corrected, if it can be corrected. For text that is beyond hope we will remove the offending article to the corresponding talk page, or, in cases in which the article obviously has no redeeming merit whatsoever, delete it outright. The decision to take the latter action should not be made lightly, however.

==On editing styles==

Generally, different people here have different editing "styles".
Some people edit lightly and focus on contributing new content.
Others prefer to improve and greatly expand existing "stubs" and articles.
Some like to make relatively small copyediting (such as grammar, spelling, clarification, and syntax) changes, as well as adding new links and move pages (so as to rename them without losing history and talk).

There's room for all of this on Wikidoc.

There are also different editing styles in the sense of how bold people are willing to be:
*Generally, most of us think we should [[wikidoc:Be bold in updating pages|be bold in updating pages]].
*Virtually no one behaves as though previous authors need to be consulted before making changes; if we thought that, we'd make little progress.
*Quite the contrary: some Wikidocs think you should not beat around the bush at all; simply change a page immediately if you see a problem, rather than waiting to discuss changes that you believe need to be made. Discussion becomes the last resort.
*An intermediate viewpoint accords that dialogue should be respected, but at the same time a minor tweak should be accepted. In this view, to edit radically or not will often depend on the context—which seems reasonable enough.

There is a place for all of these attitudes on WikiDoc.

With large proposed deletions or replacements, it may be best to suggest changes in a discussion, lest the original author be discouraged from posting again.
One person's improvement is another's desecration, and nobody likes to see their work destroyed without warning.

So, whatever you do, try to preserve information. Reasons for removing bits of an article include:

* duplication
* irrelevancy
* patent nonsense
* copyright violations
* Inaccuracy, or where the accuracy of the information cannot be established

Alternatives include:

* rephrasing or providing an accurate précis while keeping the content
* moving text within an article or to another article (existing or new)
* adding more of what you think is important to make an article more balanced

If, in your considered judgment, a page simply needs to be rewritten or changed substantially, go ahead and do that. But preserve any old contents you think might have some discussion value on the talk page, along with a comment about ''why'' you made the change. Even if you delete something that's just plain false, odds are that it got there because someone believed it was true, so preserve a comment to inform later editors that it is in fact false.


In any event, whether you decide to edit very boldly or to make inquiries on the talk page first, please bear in mind that WikiDoc is not a discussion forum.
WikiDoc can be a very energetic place, and it's best for the project as a whole if we concentrate our energies on improving articles rather than defending our pet theories, ideologies, religions, etc.
Some consideration of [[Wikidoc:Etiquette|Etiquette]] wouldn't hurt. 

All information on this page is attributed to Wikipedia and its contributors

wikidoc:Avoiding common mistakes

2010-07-08T14:56:05Z

Levacher: link and spelling Etiquette

Newcomers to Wikidoc may find that it's easy to commit a ''[[Wikidoc:faux pas|faux pas]]''. That's OK; everybody does it! Here are a few common ones you might try to avoid:

===Helping in the wrong way===
* '''Making dictionary-type entries.''' We take the stance that ''Wikidoc is not an academic medical dictionary''. Each article should aim to cover its topic beyond a simple definition and teach something about greater context.
* '''Making redundant articles.''' Before creating a new article, run a search for the topic; you may find a related one that already exists. Consider adding to existing articles before creating an entirely new one. In searching keywords, remember that article titles are usually singular, e.g. "Tree", not "Trees".

===Deleting...===
* '''Deleting useful content.''' A piece of content may be written poorly, yet still have a purpose. Consider what a sentence or paragraph tries to say. Clarify it instead of throwing it away. If the material seems miscategorized or out of place, consider moving the wayward material to another page, or creating a new page for it. If all else fails, and you can't resist removing a good chunk of content, it's usually best to move it to the article's "Talk page", which can be accessed using the "discussion" button at the top of each page. The author of the text once thought it valuable, so it is polite to preserve it for later discussion.
* '''Deleting biased content.''' Biased content can be useful content (see above). Remove the bias and keep the content.
* '''Deleting without announcing that you're doing it.''' Remark on it in the [[edit summary]] box. Otherwise, other users who care about the article's development will be caught unaware, and may think you're being intentionally sneaky.
*'''Deleting without justifying.''' Deleting anything that isn't trivial requires some words of justification in the [[edit summary]] or on the talk page. If the justification is presented on the talk page, you can simply write "See talk:" in the edit summary box.
* '''Deleting or removing text from any Talk page without archiving it.''' Talk pages or any discussion pages are part of the historical record in Wiki. Every time the pages are cleaned up, don't forget to store the removed text in its corresponding archive.See [[Wikidoc:How to archive a talk page|How to archive a talk page]].
* '''Deleting your User Talk page or removing text from your User Talk page.''' Your User Talk page is the best way others have of communicating with you. It's OK to clean up or archive old content, but please be careful before removing content from your User Talk page; it may look as though you're trying to hide criticism.

===Over-doing it===
* '''Over-respecting "the author".'''
**''Critiquing instead of editing.'' Articles have no single author with one overarching plan. Offering a suggestion or critique on the Talk page can be helpful, but it is often faster to just give the article what you think it needs.
** ''Failing to [[Wikidoc:Be bold in updating pages|be bold in updating pages]].'' Yes, you might mess things up a little. But someone else will probably clean up after you. Really, go ahead and change it. We mean it.
* '''Over-capitalizing titles.''' For instance, the second word in "French grammar" is in lowercase.
* '''Over-Wikifying.''' Wikidoc thrives on internal links, but keep it within reason; see the style guideline, [[Manual of Style|manual of style]].
===Taking it too seriously===
* '''Arming for war.''' WikiDoc is a unique community of reasonable and consensus-oriented people. In other words, this isn't Usenet, and flaming is severely looked down upon. For more about Wikidoc manners, see [[Wikidoc:Etiquette|Etiquette]].
* '''Using WikiDoc pages as a chat room.'''
* '''Getting annoyed because you find some bad articles.''' WikiDoc is a work in progress; please tolerate our imperfection, and help us improve. There are a lot of smart people here, and everyone finds they have something to contribute.

All information on this page is attributed to Wikipedia and its contributors

wikidoc:Etiquette

2010-07-08T14:44:56Z

Levacher:

=='''Etiquette'''==
* Assume good faith. Wiki Doc has worked remarkably well so far based on a policy of nearly complete freedom to edit. People come here to collaborate and submit helpful medical information.
* Treat others as you would have them treat you.
* Be polite, please!
** Irony isn't always obvious - text comes without facial expressions, vocal inflection or body language. Be careful of the words you choose — what you intended might not be what others perceive, and what you read might not be what the author intended.
* Please register yourself and sign and date your posts to talk pages (not articles!), unless you have some excellent reasons not to do so.
* Work toward agreement.
* Argue facts, not personalities.
* Don't ignore questions.
** If another disagrees with your edit, provide good reasons why you think it's appropriate.
* Concede a point, when you have no response to it; or admit when you disagree based on intuition or taste.
* Be civil.
* Although it's understandably difficult in a heated argument, if the other party is not as civil as you'd like them to be, make sure to be '''more''' civil than him or her, not less.
** That way at least you're not spiralling down to open conflict and name-calling by your own accord, you're actively doing something about it: taking a hit and refraining from hitting back - everybody appreciates that (or at least they should).
** However, don't hesitate to let the other party know that you're not comfortable with their tone in a neutral way -- otherwise they might think you're too dense to understand their "subtlety", and you'll involuntarily encourage them (e.g. "I know you've been sarcastic above, but I don't think that's helping us resolve the issue. However, I don't think your argument stands because...").
* Be prepared to apologize.
**In animated discussions, we often say things we later wish we hadn't. Say so.
* Forgive and forget.
* Recognize your own biases and keep them in check.
* Give praise when due. Everybody likes to feel appreciated, especially in an environment that often requires compromise. Drop a friendly note on users' talk pages.
* Remove or summarize resolved disputes that you initiated.
* Help mediate disagreements between others.
* If you're arguing, take a break; if you're mediating, recommend a break.
**Take it slow. If you're angry, take time out instead of posting or editing. Come back in a day or a week. You might find that someone else has made the change or comment you wanted for you. If no one is mediating, and you think mediation is needed, enlist someone.
**Walk away or find another Wiki doc article to distract yourself there are a number of articles on Wikidoc!
* Remember the things that Wiki Doc is not.
* Review the list of [[Wikidoc:faux pas|faux pas]].
*Avoid reverts and deletions whenever possible, and stay within the three revert rule, except in cases of clear vandalism. Explain reversions in the edit summary box.
** Amend, edit, discuss.
* Remind yourself that these are ''people'' you're dealing with. They are individuals with feelings and probably have other people in the world who love them. Try to allow dignity to others.
All information on this page is attributed to Wikipedia and its contributors

wikidoc:Profanity

2010-07-08T14:41:36Z

Levacher: link

Words and images that would be considered offensive, profane, or obscene by typical WikiDoc readers should be used if and only if their omission would cause the article to be less informative, relevant, or accurate, and no equally suitable alternatives are available. Including information about offensive material is part of WikiDoc's encyclopedic mission; being offensive is not.

In original WikiDoc content, a profanity should either appear in its full form or not at all; obscene words should never be bowdlerized by replacing letters in the word with dashes, asterisks, or other symbols. However, when quoting relevant material from external sources, rendering a quote as it was originally spoken/written trumps our style guidelines. If necessary, you may indicate that the blanking was in the original quote by saying so in some way outside of the quote, for example by using "<nowiki>[</nowiki>[[sic]]<nowiki>]</nowiki>".

Discussions about whether to include an offensive image or profanity are often controversial. As in all discussions on WikiDoc, it is vital that all parties practice [[Wikidoc:Etiquette|etiquette]] and assume good faith. Words like "pornography" or "censorship" tend to inflame the discussion and should be avoided. Objective terminology is more helpful than subjective terminology. 

All information on this page is attributed to Wikipedia and its contributors

wikidoc:Etiquette

2010-07-08T14:34:21Z

Levacher: wikidoc:Etiquitte moved to wikidoc:Etiquette: spelling

=='''Etiquitte'''==
* Assume good faith. Wiki Doc has worked remarkably well so far based on a policy of nearly complete freedom to edit. People come here to collaborate and submit helpful medical information.
* Treat others as you would have them treat you.
* Be polite, please!
** Irony isn't always obvious - text comes without facial expressions, vocal inflection or body language. Be careful of the words you choose — what you intended might not be what others perceive, and what you read might not be what the author intended.
* Please register yourself and sign and date your posts to talk pages (not articles!), unless you have some excellent reasons not to do so.
* Work toward agreement.
* Argue facts, not personalities.
* Don't ignore questions.
** If another disagrees with your edit, provide good reasons why you think it's appropriate.
* Concede a point, when you have no response to it; or admit when you disagree based on intuition or taste.
* Be civil.
* Although it's understandably difficult in a heated argument, if the other party is not as civil as you'd like them to be, make sure to be '''more''' civil than him or her, not less.
** That way at least you're not spiralling down to open conflict and name-calling by your own accord, you're actively doing something about it: taking a hit and refraining from hitting back - everybody appreciates that (or at least they should).
** However, don't hesitate to let the other party know that you're not comfortable with their tone in a neutral way -- otherwise they might think you're too dense to understand their "subtlety", and you'll involuntarily encourage them (e.g. "I know you've been sarcastic above, but I don't think that's helping us resolve the issue. However, I don't think your argument stands because...").
* Be prepared to apologize.
**In animated discussions, we often say things we later wish we hadn't. Say so.
* Forgive and forget.
* Recognize your own biases and keep them in check.
* Give praise when due. Everybody likes to feel appreciated, especially in an environment that often requires compromise. Drop a friendly note on users' talk pages.
* Remove or summarize resolved disputes that you initiated.
* Help mediate disagreements between others.
* If you're arguing, take a break; if you're mediating, recommend a break.
**Take it slow. If you're angry, take time out instead of posting or editing. Come back in a day or a week. You might find that someone else has made the change or comment you wanted for you. If no one is mediating, and you think mediation is needed, enlist someone.
**Walk away or find another Wiki doc article to distract yourself there are a number of articles on Wikidoc!
* Remember the things that Wiki Doc is not.
* Review the list of [[Wikidoc:faux pas|faux pas]].
*Avoid reverts and deletions whenever possible, and stay within the three revert rule, except in cases of clear vandalism. Explain reversions in the edit summary box.
** Amend, edit, discuss.
* Remind yourself that these are ''people'' you're dealing with. They are individuals with feelings and probably have other people in the world who love them. Try to allow dignity to others.
All information on this page is attributed to Wikipedia and its contributors

How to avoid plagiarism

2010-03-24T14:10:46Z

Levacher: /* Where can I find copyleft material? */

'''''If you find a WikiDoc chapter which you believe contains plagiarized content, please contact the WikiDoc Plagiarism Hotline (617-632-7590) or email help@wikidoc.org. All concerns or comments can be given anonymously.

'''''
__NOTOC__
==What is Plagiarism?==
Plagiarism is using someone else's words or ideas without giving credit. If you only make small changes to the text, even if you cite your source, you may still be guilty of plagiarizing. Intentional or unintentional, plagiarism is a very serious issue with possible legal consequences.

==How can plagiarism be avoided?==
#'''''Always''''' cite your sources
#If a source is copyrighted, you must summarize content in your own words in addition to citing the source you used.
#For [[How to avoid plagiarism#What does copyleft mean?|copyleft]] sources, you may copy directly in addition to citing the source you used. However, please note that the person who posted the content originally to a copyleft source may have plagiarized another original source!
#Create content using original words and sentence structure. Simply changing a few words in a sentence may not be sufficient defense against a claim of plagiarism.
#Search engines are your friend. You can always search the internet to ascertain whether the material you have was taken directly from somewhere else.
#When in doubt, ask! Please contact us [mailto:mgibson@wikidoc.org] with any questions regarding plagiarism or the principles of copyleft and copyright. If you see any content in WikiDoc that you believe violates a copyright or constitutes an act of plagiarism, please let us know. Please also see WikiDoc's [[wikidoc:General disclaimer|disclaimers]].

==Guidelines for avoiding plagiarism==
The following guidelines are taken directly from "Avoiding plagiarism, self-plagiarism, and other questionable writing practices: A guide to ethical writing" by Miquel Roig <ref>Roig, M. Avoiding plagiarism, self-plagiarism, and other questionable writing practices: A guide to ethical writing. St Johns University. 03/12/2009. http://ori.hhs.gov/education/products/roig_st_johns/</ref>.

-----
'''Guideline 1: '''An ethical writer ALWAYS acknowledges the contributions of others and the source of his/her ideas.

'''Guideline 2: '''Any verbatim text taken from another author must be enclosed in quotation marks.

'''Guideline 3: '''We must always acknowledge every source that we use in our writing; whether we paraphrase it, summarize it, or enclose it quotations.

'''Guideline 4: '''When we summarize, we condense, in our own words, a substantial amount of material into a short paragraph or perhaps even into a sentence.

'''Guideline 5: '''Whether we are paraphrasing or summarizing we must always identify the source of your information.

'''Guideline 6: '''When paraphrasing and/or summarizing others’ work we must reproduce the exact meaning of the other author’s ideas or facts using our words and sentence structure.

'''Guideline 7: '''In order to make substantial modifications to the original text that result in a proper paraphrase, the author must have a thorough understanding of the ideas and terminology being used.

'''Guideline 8: '''A responsible writer has an ethical responsibility to readers, and to the author/s from whom s/he is borrowing, to respect others’ ideas and words, to credit those from whom we borrow, and whenever possible, to use one’s own words when paraphrasing.

'''Guideline 9: '''When in doubt as to whether a concept or fact is common knowledge, provide a citation.

'''Guideline 10: '''Authors who submit a manuscript for publication containing data, reviews, conclusions, etc. that have already been disseminated in some significant manner (e.g. published as an article in another journal, presented at a conference, posted on the internet) must clearly indicate to the editors and readers the nature of the previous dissemination.

'''Guideline 11: '''Authors of complex studies should heed the advice previously put forth by Angell & Relman (1989). If the results of a single complex study are best presented as a ‘cohesive’ single whole, they should not be partitioned into individual papers. Furthermore, if there is any doubt as to whether a paper submitted for publication represents fragmented data, authors should enclose other papers (published or unpublished) that might be part of the paper under consideration (Kassirer & Angell, 1995). Similarly, old data that have been merely augmented with additional data points and that are subsequently presented as a new study can be an equally serious ethical breach.

'''Guideline 12: '''Because some instances of plagiarism, self-plagiarism, and even some writing practices that might otherwise be acceptable (e.g., extensive paraphrasing or quoting of key elements of a book) can constitute copyright infringement, authors are strongly encouraged to become familiar with basic elements of copyright law.

'''Guideline 13: '''While there are some situations where text recycling is an acceptable practice, it may not be so in other situations. Authors are urged to adhere to the spirit of ethical writing and avoid reusing their own previously published text, unless it is done in a manner consistent with standard scholarly conventions (e.g., by using of quotations and proper paraphrasing).

'''Guideline 14: '''Authors are strongly urged to double-check their citations. Specifically, authors should always ensure that each reference notation appearing in the body of the manuscript corresponds to the correct citation listed in the reference section and vice versa and that each source listed in the reference section has been cited at some point in the manuscript. In addition, authors should also ensure that all elements of a citation (e.g., spelling of authors’ names, volume number of journal, pagination) are derived directly from the original paper, rather than from a citation that appears on a secondary source. Finally, authors should ensure that credit is given to those authors who first reported the phenomenon being studied.

'''Guideline 15: '''The references used in a paper should only be those that are directly related to its contents. The intentional inclusion of references of questionable relevance for purposes of manipulating a journal’s or a paper’s impact factor or a paper’s chances of acceptance is an unacceptable practice.

'''Guideline 16: '''Authors should follow a simple rule: Strive to obtain the actual published paper. When the published paper cannot be obtained, cite the specific version of the material being used, whether it is conference presentation, abstract, or an unpublished manuscript.

'''Guideline 17: '''Generally, when describing others’ work, do not rely on a secondary summary of that work. It is a deceptive practice, reflects poor scholarly standards, and can lead to a flawed description of the work described. Always consult the primary literature.

'''Guideline 18: '''If an author must rely on a secondary source (e.g., textbook) to describe the contents of a primary source (e.g., an empirical journal article), s/he should consult writing manuals used in her discipline to follow the proper convention to do so. Above all, always indicate the actual source of the information being reported.

'''Guideline 19: '''When borrowing heavily from a source, authors should always craft their writing in a way that makes clear to readers, which ideas are their own and which are derived from the source being consulted.

'''Guideline 20: '''When appropriate, authors have an ethical responsibility to report evidence that runs contrary to their point of view. In addition, evidence that we use in support of our position must be methodologically sound. When citing supporting studies that suffer from methodological, statistical, or other types of shortcomings, such flaws must be pointed out to the reader.

'''Guideline 21: '''Authors have an ethical obligation to report all aspects of the study that may impact the independent replicability of their research.

'''Guideline 22: '''Researchers have an ethical responsibility to report the results of their studies according to their a priori plans. Any post hoc manipulations that may alter the results initially obtained, such as the elimination of outliers or the use of alternative statistical techniques must be clearly described along with an acceptable rationale for using such techniques.

'''Guideline 23: '''Authorship determination should be discussed prior to commencing a research collaboration and should be based on established guidelines, such as those of the International Committee of Medical Journal Editors.

'''Guideline 24: '''Only those individuals who have made substantitve contributions to a project merit authorship in a paper.

'''Guideline 25: '''Faculty-student collaborations should follow the same criteria to establish authorship. Mentors must exercise great care to neither award authorship to students whose contributions do not merit it, nor to deny authorship and due credit to the work of students.

'''Guideline 26: '''Academic or professional ghost authorship in the sciences is ethically unacceptable.

==What does copyleft mean?==
Copyleft is a principle whereby information is available for anyone to copy, modify, or redistribute, as long as the new version
# Grants the same freedoms to others
# Acknowledges the original authors of the content
You can copy and paste directly from copyleft material as long as your work follows the two rules above.

==Where can I find copyleft material?==
#Wikis: All wikimedia projects (including [[Main_Page|WikiDoc]] and Wikipedia) that operate under the Creative Commons Attribution-ShareAlike (CC-BY-SA) 3.0 license are governed by this principle.
#Public domain information: All information on public domain website (.gov)
#One important exception is the National Guidelines Clearinghouse. Although the site states that the content is free for you to use and distribute, the copyright of the society or entity that originally created the guidelines must be respected. Therefore, large sections of background materials from guidelines content from these societies should not be distributed without their permission.

==What about other websites or journal articles that are copyrighted?==
If a source is copyrighted (whether a journal article or a popular medical site), you are '''LEGALLY PROHIBITED FROM COPYING IT WITHOUT PERMISSION!''' Simply changing or adding a few words does not absolve the fact that you are stealing someone else's words and ideas.

==Current work to remove plagiarized content==
WikiDoc users are now reviewing all cardiology chapters for plagiarized content. Sections of each page are copied into a search engine to look for potential copyrighted original sources. Once all cardiology chapters have been reviewed, users will continue with other topic areas.

==References==
{{reflist}}
{{WH}}
{{WS}}

How to avoid plagiarism

2010-03-24T14:08:22Z

Levacher: /* Where can I find copyleft material? */ Licence Creative Commons Attribution-ShareAlike (CC-BY-SA) 3.0

'''''If you find a WikiDoc chapter which you believe contains plagiarized content, please contact the WikiDoc Plagiarism Hotline (617-632-7590) or email help@wikidoc.org. All concerns or comments can be given anonymously.

'''''
__NOTOC__
==What is Plagiarism?==
Plagiarism is using someone else's words or ideas without giving credit. If you only make small changes to the text, even if you cite your source, you may still be guilty of plagiarizing. Intentional or unintentional, plagiarism is a very serious issue with possible legal consequences.

==How can plagiarism be avoided?==
#'''''Always''''' cite your sources
#If a source is copyrighted, you must summarize content in your own words in addition to citing the source you used.
#For [[How to avoid plagiarism#What does copyleft mean?|copyleft]] sources, you may copy directly in addition to citing the source you used. However, please note that the person who posted the content originally to a copyleft source may have plagiarized another original source!
#Create content using original words and sentence structure. Simply changing a few words in a sentence may not be sufficient defense against a claim of plagiarism.
#Search engines are your friend. You can always search the internet to ascertain whether the material you have was taken directly from somewhere else.
#When in doubt, ask! Please contact us [mailto:mgibson@wikidoc.org] with any questions regarding plagiarism or the principles of copyleft and copyright. If you see any content in WikiDoc that you believe violates a copyright or constitutes an act of plagiarism, please let us know. Please also see WikiDoc's [[wikidoc:General disclaimer|disclaimers]].

==Guidelines for avoiding plagiarism==
The following guidelines are taken directly from "Avoiding plagiarism, self-plagiarism, and other questionable writing practices: A guide to ethical writing" by Miquel Roig <ref>Roig, M. Avoiding plagiarism, self-plagiarism, and other questionable writing practices: A guide to ethical writing. St Johns University. 03/12/2009. http://ori.hhs.gov/education/products/roig_st_johns/</ref>.

-----
'''Guideline 1: '''An ethical writer ALWAYS acknowledges the contributions of others and the source of his/her ideas.

'''Guideline 2: '''Any verbatim text taken from another author must be enclosed in quotation marks.

'''Guideline 3: '''We must always acknowledge every source that we use in our writing; whether we paraphrase it, summarize it, or enclose it quotations.

'''Guideline 4: '''When we summarize, we condense, in our own words, a substantial amount of material into a short paragraph or perhaps even into a sentence.

'''Guideline 5: '''Whether we are paraphrasing or summarizing we must always identify the source of your information.

'''Guideline 6: '''When paraphrasing and/or summarizing others’ work we must reproduce the exact meaning of the other author’s ideas or facts using our words and sentence structure.

'''Guideline 7: '''In order to make substantial modifications to the original text that result in a proper paraphrase, the author must have a thorough understanding of the ideas and terminology being used.

'''Guideline 8: '''A responsible writer has an ethical responsibility to readers, and to the author/s from whom s/he is borrowing, to respect others’ ideas and words, to credit those from whom we borrow, and whenever possible, to use one’s own words when paraphrasing.

'''Guideline 9: '''When in doubt as to whether a concept or fact is common knowledge, provide a citation.

'''Guideline 10: '''Authors who submit a manuscript for publication containing data, reviews, conclusions, etc. that have already been disseminated in some significant manner (e.g. published as an article in another journal, presented at a conference, posted on the internet) must clearly indicate to the editors and readers the nature of the previous dissemination.

'''Guideline 11: '''Authors of complex studies should heed the advice previously put forth by Angell & Relman (1989). If the results of a single complex study are best presented as a ‘cohesive’ single whole, they should not be partitioned into individual papers. Furthermore, if there is any doubt as to whether a paper submitted for publication represents fragmented data, authors should enclose other papers (published or unpublished) that might be part of the paper under consideration (Kassirer & Angell, 1995). Similarly, old data that have been merely augmented with additional data points and that are subsequently presented as a new study can be an equally serious ethical breach.

'''Guideline 12: '''Because some instances of plagiarism, self-plagiarism, and even some writing practices that might otherwise be acceptable (e.g., extensive paraphrasing or quoting of key elements of a book) can constitute copyright infringement, authors are strongly encouraged to become familiar with basic elements of copyright law.

'''Guideline 13: '''While there are some situations where text recycling is an acceptable practice, it may not be so in other situations. Authors are urged to adhere to the spirit of ethical writing and avoid reusing their own previously published text, unless it is done in a manner consistent with standard scholarly conventions (e.g., by using of quotations and proper paraphrasing).

'''Guideline 14: '''Authors are strongly urged to double-check their citations. Specifically, authors should always ensure that each reference notation appearing in the body of the manuscript corresponds to the correct citation listed in the reference section and vice versa and that each source listed in the reference section has been cited at some point in the manuscript. In addition, authors should also ensure that all elements of a citation (e.g., spelling of authors’ names, volume number of journal, pagination) are derived directly from the original paper, rather than from a citation that appears on a secondary source. Finally, authors should ensure that credit is given to those authors who first reported the phenomenon being studied.

'''Guideline 15: '''The references used in a paper should only be those that are directly related to its contents. The intentional inclusion of references of questionable relevance for purposes of manipulating a journal’s or a paper’s impact factor or a paper’s chances of acceptance is an unacceptable practice.

'''Guideline 16: '''Authors should follow a simple rule: Strive to obtain the actual published paper. When the published paper cannot be obtained, cite the specific version of the material being used, whether it is conference presentation, abstract, or an unpublished manuscript.

'''Guideline 17: '''Generally, when describing others’ work, do not rely on a secondary summary of that work. It is a deceptive practice, reflects poor scholarly standards, and can lead to a flawed description of the work described. Always consult the primary literature.

'''Guideline 18: '''If an author must rely on a secondary source (e.g., textbook) to describe the contents of a primary source (e.g., an empirical journal article), s/he should consult writing manuals used in her discipline to follow the proper convention to do so. Above all, always indicate the actual source of the information being reported.

'''Guideline 19: '''When borrowing heavily from a source, authors should always craft their writing in a way that makes clear to readers, which ideas are their own and which are derived from the source being consulted.

'''Guideline 20: '''When appropriate, authors have an ethical responsibility to report evidence that runs contrary to their point of view. In addition, evidence that we use in support of our position must be methodologically sound. When citing supporting studies that suffer from methodological, statistical, or other types of shortcomings, such flaws must be pointed out to the reader.

'''Guideline 21: '''Authors have an ethical obligation to report all aspects of the study that may impact the independent replicability of their research.

'''Guideline 22: '''Researchers have an ethical responsibility to report the results of their studies according to their a priori plans. Any post hoc manipulations that may alter the results initially obtained, such as the elimination of outliers or the use of alternative statistical techniques must be clearly described along with an acceptable rationale for using such techniques.

'''Guideline 23: '''Authorship determination should be discussed prior to commencing a research collaboration and should be based on established guidelines, such as those of the International Committee of Medical Journal Editors.

'''Guideline 24: '''Only those individuals who have made substantitve contributions to a project merit authorship in a paper.

'''Guideline 25: '''Faculty-student collaborations should follow the same criteria to establish authorship. Mentors must exercise great care to neither award authorship to students whose contributions do not merit it, nor to deny authorship and due credit to the work of students.

'''Guideline 26: '''Academic or professional ghost authorship in the sciences is ethically unacceptable.

==What does copyleft mean?==
Copyleft is a principle whereby information is available for anyone to copy, modify, or redistribute, as long as the new version
# Grants the same freedoms to others
# Acknowledges the original authors of the content
You can copy and paste directly from copyleft material as long as your work follows the two rules above.

==Where can I find copyleft material?==
#Wikis: All wikimedia projects (including [[Main_Page|WikiDoc]] and Wikipedia) that operate under the Creative Commons Attribution-ShareAlike (CC-BY-SA) 3.0 licence are governed by this principle.
#Public domain information: All information on public domain website (.gov)
#One important exception is the National Guidelines Clearinghouse. Although the site states that the content is free for you to use and distribute, the copyright of the society or entity that originally created the guidelines must be respected. Therefore, large sections of background materials from guidelines content from these societies should not be distributed without their permission.

==What about other websites or journal articles that are copyrighted?==
If a source is copyrighted (whether a journal article or a popular medical site), you are '''LEGALLY PROHIBITED FROM COPYING IT WITHOUT PERMISSION!''' Simply changing or adding a few words does not absolve the fact that you are stealing someone else's words and ideas.

==Current work to remove plagiarized content==
WikiDoc users are now reviewing all cardiology chapters for plagiarized content. Sections of each page are copied into a search engine to look for potential copyrighted original sources. Once all cardiology chapters have been reviewed, users will continue with other topic areas.

==References==
{{reflist}}
{{WH}}
{{WS}}

User talk:Jef-Infojef

2009-10-19T16:37:10Z

Levacher: New page: == WikiDocteurs parlant français == Bonjour, il semble que vous êtes un contributeur vous exprimant en français. Ce serait aimable à vous de me contacter, car j'essaie de développer W...

== WikiDocteurs parlant français ==
Bonjour, il semble que vous êtes un contributeur vous exprimant en français. Ce serait aimable à vous de me contacter, car j'essaie de développer WikiDoc en Français. 
à bientôt j'espère! [[User:Levacher|Maryse LEVACHER]] 16:37, 19 October 2009 (UTC)

User talk:Alara

2009-10-18T12:28:23Z

Levacher: New page: == WikiDoc en Français == Bonjour, la version de WikiDoc en Français attend des contributeurs, si vous êtes interessé(e), contactez-moi! ~~~~

== WikiDoc en Français ==

Bonjour, la version de WikiDoc en Français attend des contributeurs, si vous êtes interessé(e), contactez-moi! 
[[User:Levacher|Maryse LEVACHER]] 12:27, 18 October 2009 (UTC)

Flu vaccine

2009-10-07T17:15:41Z

Levacher: /* See also */ spelling

{{Flu}}
[[Image:Influenza virus.jpg|frame|Model of Influenza Virus from [[NIH]]]]

The '''influenza vaccine''' or '''flu shot''' is a [[vaccine]] to protect against the highly variable [[influenza]] [[virus]].

The annual flu kills an estimated 36,000 people in the [[United States]]. The annually updated [[trivalent]] flu vaccine for the 2007–2008 season consists of [[hemagglutinin]] (HA) surface glycoprotein components from influenza [[H3N2]], [[H1N1]], and [[Influenzavirus B|B influenza]] viruses.<ref>[http://www.cdc.gov/flu/professionals/acip/composition0708.htm CDC Flu Vaccine Composition 07/08]</ref>

Each year the influenza virus changes and different strains become dominant. Due to the high [[mutability]] of the virus a particular [[vaccine]] formulation usually only works for about a year. The [[World Health Organization]] coordinates the contents of the vaccine each year to contain the most likely strains of the virus to attack the next year. The flu [[vaccine]] is usually recommended for anyone in a high-risk group who would be likely to suffer complications from [[influenza]].

==History of the flu vaccine==
{{seealso|Timeline of vaccines}}
Vaccines are used in both humans and nonhumans. Human vaccine is meant unless specifically identified as a veterinary or poultry or livestock vaccine.

===Influenza===
[[Influenza]], commonly known as the flu, is an [[infectious disease]] that infects [[bird]]s and [[mammal]]s (primarily of the upper airways and [[lungs]] in mammals) and is caused by an [[RNA virus]] of the [[Orthomyxoviridae]] family (the [[Orthomyxoviridae#Types of influenza virus|influenza viruses]]). The most common and characteristic symptoms of influenza in humans are [[fever]], [[pharyngitis]] (sore throat), [[myalgia]] (muscle pains), severe [[headache]], [[cough]]ing, and [[malaise]] (weakness and fatigue).<ref name=Merck>[http://www.merck.com/mmhe/sec17/ch198/ch198c.html? Influenza: Viral Infections: Merck Manual Home Edition]</ref> [[Hippocrates]] first described the symptoms of influenza in 412 B.C. Since then, the virus has undergone mutations and shifts and has caused numerous pandemics. The first influenza pandemic was recorded in 1580, since this time, various methods have been employed to eradicate its cause.<ref name=Webster1>

{{cite journal
| author=[[Robert Webster|Webster, R. G.]] and Walker, E. J. | title=The world is teetering on the edge of a pandemic that could kill a large fraction of the human population | journal=American Scientist | year=2003 | pages=122 | volume=91 | issue=2 |url=http://www.americanscientist.org/template/AssetDetail/assetid/17221?fulltext=true | id={{DOI|10.1511/2003.2.122}}

}} </ref> The etiological cause of influenza, the orthomyxoviridae was finally discovered by the [[Medical Research Council (UK)|Medical Research Council]] (MRC) of the [[United Kingdom]] in 1933.<ref name=Blakemore>

{{cite news
| author=Blakemore, C.
| url=http://www.timesonline.co.uk/article/0,,2087-2125521,00.html
| title=Battle of time, luck and science
| publisher=The Sunday Times - Britain
| date=[[200-04-09]]
| accessdate=2006-06-22
}}
</ref>

Known flu pandemics:<ref>[http://biomicro.sdstate.edu/WangX/Micr425/Pathogenesis/Influenza_A.pdf Influenza PDF]</ref>
* [[1889]]–[[1890|90]] - Asiatic (Russian) Flu, mortality rate said to be 0.75-1 death per 1000 possibly [[H2N2]]
* [[1900]] - possibly [[H3N8]]
* [[1918]]–[[1920|20]] – [[Spanish flu|Spanish Flu]], 500 million ill, at least 20-40 million died of [[H1N1]]
* [[1957]]–[[1958|58]] – [[Asian Flu]], 1 to 1.5 million died of [[H2N2]]
* [[1968]]–[[1969|69]] – [[Hong Kong Flu]], 3/4 to 1 million died of [[H3N2]]

===Flu vaccine origins===
In the world wide [[Spanish flu]] pandemic of 1918, "Physicians tried everything they knew, everything they had ever heard of, from the ancient art of bleeding patients, to administering oxygen, to developing new vaccines and sera (chiefly against what we now call ''Hemophilus influenzae''—a name derived from the fact that it was originally considered the etiological agent—and several types of pneumococci). Only one therapeutic measure, transfusing blood from recovered patients to new victims, showed any hint of success."<ref> [http://darwin.nap.edu/books/0309095042/html/62.html The Threat of Pandemic Influenza: Are We Ready? Workshop Summary (2005) (free online book)] page 62</ref>

"In 1931, viral growth in embryonated hens' eggs was discovered, and in the 1940s, the U.S. military developed the first approved inactivated vaccines for influenza, which were used in the Second World War".<ref name=Korsman/>

===Flu vaccine acceptance===
The current egg-based technology for producing influenza vaccine was created in the 1950s.<ref> [http://content.nejm.org/cgi/content/full/352/18/1839 NEJM Volume 352:1839-1842 May 5, 2005 Number 18] article ''Preparing for the Next Pandemic'' by Michael T. Osterholm</ref>

"The WHO [[National Influenza Centers|Global Influenza Surveillance Network]] was established in 1952. The network comprises 4 WHO Collaborating Centres (WHO CCs) and 112 institutions in 83 countries, which are recognized by WHO as WHO National Influenza Centres (NICs). These NICs collect specimens in their country, perform primary virus isolation and preliminary antigenic characterization. They ship newly isolated strains to WHO CCs for high level antigenic and genetic analysis, the result of which forms the basis for [[WHO]] recommendations on the composition of influenza vaccine for the Northern and Southern Hemisphere each year."<ref> [http://www.who.int/csr/disease/influenza/influenzanetwork/en/index.html WHO] article ''Global influenza surveillance''</ref>

In the U.S. [[swine flu]] scare of 1976 President [[Gerald Ford]] was confronted with a potential swine flu pandemic. The [[vaccination]] program was plagued by delays and public relations problems, but about 24% of the population was vaccinated by the time the program was canceled with much concern and doubt about flu vaccination.<ref name=analysis>[http://www.haverford.edu/biology/edwards/disease/viral_essays/warnervirus.htm The Sky is Falling: An Analysis of the Swine Flu Affair of 1976]</ref>

According to the CDC: "Influenza vaccination is the primary method for preventing influenza and its severe complications. [...] Vaccination is associated with reductions in influenza-related respiratory illness and physician visits among all age groups, hospitalization and death among persons at high risk, otitis media among children, and work absenteeism among adults. Although influenza vaccination levels increased substantially during the 1990s, further improvements in vaccine coverage levels are needed".<ref> [http://www.cdc.gov/mmwr/preview/mmwrhtml/rr5103a1.htm CDC] report ''Prevention and Control of Influenza'' published April 12, 2002</ref>

===Current status===
[[Flu research]] includes [[molecular virology]], [[molecular evolution]], [[pathogenesis]], host [[immune response]]s, [[genomics]], and [[epidemiology]]. These help in developing influenza countermeasures such as [[vaccine]]s, therapies and diagnostic tools. Improved influenza countermeasures require basic research on how viruses enter cells, replicate, mutate, evolve into new strains and induce an immune response. The [[Influenza Genome Sequencing Project]] is creating a library of influenza sequences that will help us understand what makes one strain more lethal than another, what genetic determinants most affect [[immunogenicity]], and how the virus evolves over time. Solutions to limitations in current vaccine methods are being researched.

"Today, we have the capability to produce 300 million doses of trivalent vaccine per year - enough for current epidemics in the Western world, but insufficient for coping with a pandemic."<ref name=Korsman/><ref>See [http://www.cidrap.umn.edu/ecolab/influenza/general/news/jan2606fluvax.html CIDRAP] article ''Record flu vaccine supply expected next season'' published January 26, 2006 for detailed current availabliity in the US.</ref>

==Clinical trials of vaccines==
A vaccine is assessed in terms of the reduction of the risk of disease produced by vaccination, its ''efficacy''. In contrast, in the field, the ''effectiveness'' of a vaccine is the practical reduction in risk for an individual when they are vaccinated under real-world conditions.<ref>{{cite journal | author = Fedson D | title = Measuring protection: efficacy versus effectiveness. | journal = Dev Biol Stand | volume = 95 | issue = | pages = 195-201 | year = | id = PMID 9855432}}</ref> Measuring efficacy of influenza vaccines is relatively simple, as the immune response produced by the vaccine can be assessed in animal models, or the amount of antibody produced in vaccinated people can be measured,<ref>{{cite journal | author = Stephenson I, Zambon M, Rudin A, Colegate A, Podda A, Bugarini R, Del Giudice G, Minutello A, Bonnington S, Holmgren J, Mills K, Nicholson K | title = Phase I evaluation of intranasal trivalent inactivated influenza vaccine with nontoxigenic Escherichia coli enterotoxin and novel biovector as mucosal adjuvants, using adult volunteers. | journal = J Virol | volume = 80 | issue = 10 | pages = 4962-70 | year = 2006 | id = PMID 16641287}}</ref> or most rigorously, by immunising adult volunteers and then challenging with virulent influenza virus.<ref name=Treanor>{{cite journal | author = Treanor J, Kotloff K, Betts R, Belshe R, Newman F, Iacuzio D, Wittes J, Bryant M | title = Evaluation of trivalent, live, cold-adapted (CAIV-T) and inactivated (TIV) influenza vaccines in prevention of virus infection and illness following challenge of adults with wild-type influenza A (H1N1), A (H3N2), and B viruses. | journal = Vaccine | volume = 18 | issue = 9-10 | pages = 899-906 | year = 1999 | id = PMID 10580204}}</ref> In studies such as these, influenza vaccines showed high efficacy and produced a protective immune response. For ethical reasons, such challenge studies cannot be performed in the population most at risk from influenza - the elderly and young children. However, studies on the effectiveness of flu vaccines in the real world are uniquely difficult. The vaccine may not be matched to the virus in circulation; virus prevalence varies widely between years, and influenza is often confused with other flu-like illnesses.<ref name=Jefferson1>{{cite journal | author = Jefferson T | title = Influenza vaccination: policy versus evidence. | journal = BMJ | volume = 333 | issue = 7574 | pages = 912-5 | year = 2006 | id = PMID 17068038}}</ref>

Nevertheless, multiple clinical trials of both live and inactivated influenza vaccines have been performed and their results pooled and analyzed in several recent meta-analyses. Studies on live vaccines have very limited data, but these preparations may be more effective than inactivated vaccines.<ref name=Treanor/> The meta-analyses examined the efficacy and effectiveness of inactivated vaccines in adults,<ref name=Demicheli>{{cite journal | author = Demicheli V, Rivetti D, Deeks J, Jefferson T | title = Vaccines for preventing influenza in healthy adults. | journal = Cochrane Database Syst Rev | volume = | issue = | pages = CD001269 | year = | id = PMID 15266445}}</ref> children,<ref name=Smith>{{cite journal | author = Smith S, Demicheli V, Di Pietrantonj C, Harnden A, Jefferson T, Matheson N, Rivetti A | title = Vaccines for preventing influenza in healthy children. | journal = Cochrane Database Syst Rev | volume = | issue = | pages = CD004879 | year = | id = PMID 16437500}}</ref> and the elderly.<ref name=Rivetti>{{cite journal | author = Rivetti D, Jefferson T, Thomas R, Rudin M, Rivetti A, Di Pietrantonj C, Demicheli V | title = Vaccines for preventing influenza in the elderly. | journal = Cochrane Database Syst Rev | volume = 3 | issue = | pages = CD004876 | year = | id = PMID 16856068}}</ref><ref name=Jefferson>{{cite journal | author = Jefferson T, Rivetti D, Rivetti A, Rudin M, Di Pietrantonj C, Demicheli V | title = Efficacy and effectiveness of influenza vaccines in elderly people: a systematic review. | journal = Lancet | volume = 366 | issue = 9492 | pages = 1165-74 | year = 2005 | id = PMID 16198765}}</ref> In adults, vaccines show high efficacy against the targeted strains, but low effectiveness overall, so the benefits of vaccination are small, with a one-quarter reduction in risk of contracting influenza but no effect on the rate of hospitalization.<ref name=Demicheli/> In children, vaccines again showed high efficacy, but low effectiveness in preventing "flu-like illness", in children under two the data are extremely limited, but vaccination appeared to confer no measurable benefit.<ref name=Smith/> In the elderly, vaccination does not reduce the frequency of influenza, but may reduce pneumonia, hospital admission and deaths from influenza or pneumonia.<ref name=Rivetti/><ref name=Jefferson/> The measured effectiveness of the vaccine in the elderly varies depending on whether the population studied is in residential care homes, or in the community, with the vaccine appearing more effective in an institutional environment. This apparent effect may be due to selection bias or differences in diagnosis and surveillance.

Overall, the benefit of influenza vaccination is clearest in the elderly, with vaccination in children of questionable benefit. Vaccination of adults is not predicted to produce significant improvements in public health. The apparent contradiction between vaccines with high efficacy, but low effectiveness, may reflect the difficulty in diagnosing influenza under clinical conditions and the large number of strains circulating in the population.<ref name=Jefferson1/>

==Who should get it==
[[Image:Vaccination US Navy.jpg|thumb|250px|right|[[United States Navy|U.S. Navy]] personnel receiving influenza vaccination]]
Yearly influenza vaccination should be routinely offered to patients at risk of complications of influenza:
*the elderly (UK recommendation is those aged 65 or above)
*patients with chronic lung diseases ([[asthma]], [[chronic obstructive airway disease|COPD]], etc.)
*patients with chronic heart diseases ([[congenital heart disease]], chronic [[heart failure]], [[ischaemic heart disease]])
*patients with chronic liver diseases (including [[liver cirrhosis]])
*patients who are immunosuppressed (those with [[HIV]] or who are receiving drugs to suppress the [[immune system]] such as chemotherapy and long-term [[steroids]]) and their household contacts
*all people who are institutionalized in an environment where influenza can spread rapidly, such as in prisons or nursing homes
*healthcare workers (both to prevent sickness and to prevent spread to patients)<ref name="Thomas2006">{{cite journal | author=Thomas RE, Jefferson TO, Demicheli V, Rivetti D | title=Influenza vaccination for health-care workers who work with elderly people in institutions: a systematic review | journal=Lancet Infect Dis | year=2006 | volume=6 | issue=5 | pages=273–279 | id=PMID 16631547}}</ref>

The only [[Wiktionary:contraindication|contraindication]] is known [[anaphylaxis]] to the vaccine or its component.

In the United States a person aged 50–64 is nearly ten times more likely to die an influenza-associated death than a younger person, and a person over age 65 is over ten times more likely to die an influenza-associated death than the 50–64 age group.<ref>{{cite journal | author=Thompson WW, Shay DK, Weintraub E, Brammer L, Cox N, Anderson LJ, Fukuda K | title=Mortality associated with influenza and respiratory syncytial virus in the United States | journal=THE JOURNAL OF THE AMERICAN MEDICAL ASSOCIATION | volume=289 | issue=2 | year=2003 | pages=179-186 | id=PMID 12517228 }}</ref> Vaccination of those over age 65 reduces influenza-associated death by about 50%.<ref>{{cite journal | author=Hak E, Buskens E, van Essen GA, de Bakker DH, Grobbee DE, Tacken MA, van Hout BA, Verheij TJ | title=Clinical effectiveness of influenza vaccination in persons younger than 65 years with high-risk medical conditions: the PRISMA study | journal=ARCHIVES OF INTERNAL MEDICINE | volume=165 | issue=3 | year=2005 | pages=274-280 | id=PMID 15710789 }}</ref><ref>{{cite journal | author=Nichol KL, Nordin J, Mullooly J, Lask R, Fillbrandt K, Iwane M | title=Influenza vaccination and reduction in hospitalizations for cardiac disease and stroke among the elderly | journal=THE NEW ENGLAND JOURNAL OF MEDICINE | volume=348 | issue=14 | year=2003 | pages=1322-1332 | id=PMID 12672859 }}</ref> However, it is unlikely that the vaccine completely explains the results since elderly people who get vaccinated are probably more healthy and health-conscious than those who do not.<ref>{{cite news | author=Woloshin S, Schwartz LM, Welch HG | title=A shot of fear | publisher = The Washington Post | date = [[2005-10-25]] | url =http://www.washingtonpost.com/wp-dyn/content/article/2005/10/22/AR2005102200042.html | accessdate = 2006-11-09 }}</ref>

As mortality is high among infants who contract influenza, the household contacts and caregivers of infants should be vaccinated to reduce the risk of passing an influenza infection to the infant.

Data from the years when Japan required annual flu vaccinations for school-aged children indicate that vaccinating children—the group most likely to catch and spread the disease—has a strikingly positive effect on reducing mortality among older people: one life saved for every 420 children who received the flu vaccine.<ref>http://content.nejm.org/cgi/content/abstract/344/12/889</ref> This may be due to [[herd immunity]] or to direct causes, such as individual older people not being exposed to influenza. For example, retired grandparents often risk infection by caring for their sick grandchildren in households where the parents can't take time off work or are sick themselves.

==Flu vaccine virus selection==
Selecting viruses for the vaccine manufacturing process is very difficult.

At the [[United States|U.S.]]'s [[Food and Drug Administration]]'s (FDA) [[Center for Biologics Evaluation and Research]]'s Vaccines and Related Biological Products Advisory Committee's 101st meeting of [[February 16]] [[2005]], an extensive discussion and vote was held concerning the following year's flu vaccine virus selection, but began with a summary of the previous year:

===Influenza B===
:"For [[Influenza B]], the question was asked: are there new strains present? And the answer was yes, and in 2004, the majority of the viruses were similar to a strain called B/Shanghai/361/2002, which is from the so-called B/Yamagata/1688 hemagglutinin lineage. That lineage was not the one that was being used in the vaccine that was current last year. In a minority of the strains that were found during the epidemiologic studies were similar to the strain that was in the vaccine for last year, which was B/Hong Kong/330/2001, which belongs to the HA lineage that we represent with the strain B/Victoria/287. In answer to the question were these new viruses spreading, the answer, of course, is definitely yes. The Fujian-like viruses had become widespread around the world and were predominant everywhere, and these B/Shanghai-like strains at the time we were holding this meeting in February were predominant not only in North America and the United States, but also in Asia and Europe."

===New viruses===
:"Were the new viruses that were identified and spreading, were those inhibited by the current vaccines? And this question, as it sometimes is, was not a very definite no or yes. It was a little bit difficult to interpret, but it seemed like many of the A/Fujian-like viruses were not well inhibited by the current vaccines, although some of them were. For the B/Shanghai-like strains, of course, we've known for a long time that these two divergent hemagglutinin lineages are not that well inhibited one by the other, and as time has gone on and antigenic drift has occurred in these strains, that has become truer. Generally we also know that for the B/Yamagata-like strains and the B/Victoria-like strains, that very young children and people who haven't been immunologically primed, exposure to one of these does not seem to immediately give antibodies that cross-react with the other HA lineage."

===Manufacturing issues===
:"So were there strains that were suitable for manufacturing? And the answer was yes. Of course, we all know that for inactivated vaccines and for live attenuated vaccines manufacturing depends on having egg adapted strains, either the wild-type or reassortant, and in the case of the live vaccine, of course, it has to be a reassortant for the attenuation phenotype. But there were A/Fujian-like strains that were available, and there was a high growth reassortant that was being used in manufacturing for the Southern Hemisphere already, the A/Wyoming/3/2003 X 147 reassortant. For the B strain, there were a number of wild-type isolates that seemed to be suitable for manufacturing, including B/Jilin/20/2003 and B/Jiangsu/10/2003, in addition to the B/Shanghai/361 strain itself."

===Strains selected===
:"So based on that, the strains that were selected for this year include A/New Caledonia/20/99-like strain, which in this case really is A/New Caledonia/20/99. For the B/Shanghai/361/2002-like recommendation that was made, there were all three of these strains, B/Shanghai, B/Jilin, and B/Jiangsu. And for the A/Fujian/411/2002-like recommendation that was made and the A/Wyoming/3/2003 strain was chosen or is the one that has become widely used for vaccine preparation. Now, the implications of the strain selection were that preparation of the vaccines was on schedule throughout the year. All of the strains seemed to be typical and easy to adapt for manufacturing purposes, and going into the summer, the supply of vaccine was expected to match the demand predicted by previous years' experiences."

===Unexpected difficulties===
:"But what happened was that we ended up with a vaccine shortage at the end of the summer, and just to try to put that into a little perspective, from January until August, manufacturing had been progressing on schedule even including these two new strains that were recommended for use in vaccines, and it was anticipated there were going to be about 100 million doses of vaccine from all of the manufacturers combined for this year. In August of 2004, Chiron notified regulatory authorities about a sterility issue and indicated that investigation to identify the cause and the implementation of corrections was underway, and at that time Chiron made a public announcement indicating that there would be a possible delay in distribution and possibly a reduction in the amount of vaccine that would be available. You also probably all know that in early October of 2004, the MHRA, the UK regulatory authority, announced that they were suspending Chiron's license to manufacture inactivated influenza vaccine for three months, and that was based on the issues that have previously been identified and were in investigation and correction by Chiron. Subsequently, over the next few weeks and certainly by November of 2004, it became clear after consultation between FDA and MHRA that the vaccine that Chiron had planned to make was not going to be available for us in the United States."

===Response to unexpected difficulties===
:"In response to that, there were a number of things that happened within the Public Health Service, and I'll just very briefly indicate some of those. At FDA there was a lot of work done to evaluate manufacturers who were not licensed in the United States to identify whether their vaccines could be used under IND. There was consultation with manufacturers to discuss regulatory mechanisms going forward from this time for getting approval of new products in the United States. That includes accelerated approval, fast track and priority reviews to facilitate those new licenses, and all of these things actually have been continuing."<ref>(transcript of U.S. FDA Center for Biologics Evaluation and Research Vaccines and Related Biological Products Advisory Committee's 101st meeting of February 16, 2005 is here: [http://origin.www.fda.gov/ohrms/dockets/ac/05/transcripts/2005-4087T1.DOC origin.www.fda.gov in .DOC format] [http://www.google.com/search?q=cache:8hPXwU4pfyAJ:origin.www.fda.gov/ohrms/dockets/ac/05/transcripts/2005-4087T1.DOC+CDC+H5N1+research+%22two+clades%22&hl=en&gl=us&ct=clnk&cd=18 in Google provided HTML format])</ref>

==Flu vaccine manufacturing==
Flu vaccines are available both as an [[Injection (medicine)|injection]] of killed virus and as [[nasal spray]] of live attenuated influenza virus (LAIV) (sold as [[FluMist]]). Clinical trials suggest that the live virus may be more effective at preventing infection. FluMist previously was not approved in the United States for use in children younger than 5<ref> [http://news.yahoo.com/s/ap/20060501/ap_on_he_me/flu_spray Yahoo News]</ref>. Starting in 2006 it is available to healthy children aged 2 and older.

Flu vaccine is usually grown in fertilized [[chicken]] eggs. Both types of flu vaccines are contraindicated for those with severe [[allergy|allergies]] to egg proteins and people with a history of [[Guillain-Barré syndrome]].<ref>[http://www.cdc.gov/flu/about/qa/flushot.htm CDC]</ref>

On [[October 5]] [[2004]], [[Chiron Corporation]], a corporation contracted to deliver half of the expected flu vaccine for the [[United States]] and a significant portion to the [[United Kingdom|UK]], issued a press release<ref>[http://www.chiron.com/investors/pressreleases/press_release100504.pdf Chiron]</ref> that stated it was unable to dispense its stock for the [[2004]]-[[2005]] season, due to suspension of the corporation's license to produce the vaccine by the [[Medicines and Healthcare Products Regulatory Agency]]. However, the [[Centers for Disease Control and Prevention]] took swift action to enlist the help of other companies such as [[MedImmune]] and [[Sanofi pasteur]] to supply [[vaccine]] in high-risk populations in the United States.

Most flu vaccines intended for adults in the United States still contain [[Thiomersal]], despite having been banned in many countries.

==H5N1==
{{H5N1}}
{{main|Flu research}}
There are several [[H5N1]] [[vaccine]]s for several of the avian H5N1 varieties, some for use in humans and some for use in poultry. H5N1 continually mutates, meaning vaccines based on current samples of avian H5N1 cannot be depended upon to work in the case of a future pandemic of H5N1. While there can be some cross-protection against related flu strains, the best protection would be from a vaccine specifically produced for any future pandemic flu virus strain. Dr. Daniel Lucey, co-director of the Biohazardous Threats and Emerging Diseases graduate program at Georgetown University has made this point, "There is no [[H5N1]] [[pandemic]] so there can be no pandemic [[vaccine]]." However, "pre-pandemic vaccines" have been created; are being refined and tested; and do have some promise both in furthering research and preparedness for the next pandemic. Vaccine manufacturing companies are being encouraged to increase capacity so that if a pandemic vaccine is needed, facilities will be available for rapid production of large amounts of a vaccine specific to a new pandemic strain.

Problems with [[H5N1]] vaccine production include:
*lack of overall production capacity
*lack of surge production capacity (it is impractical to develop a system that depends on hundreds of millions of 11-day old specialized eggs on a standby basis)
*the pandemic H5N1 might be lethal to chickens

[[Cell culture]] (cell-based) manufacturing technology can be applied to influenza vaccines as they are with most viral vaccines and thereby solve the problems associated with creating flu vaccines using chicken eggs as is currently done.<ref>According to the U.S. HHS ([[United States]] [[Department of Health & Human Services]]) Pandemic Influenza Plan Appendix F: Current HHS Activities last revised on November 8, 2005 at http://www.hhs.gov/pandemicflu/plan/appendixf.html :

:Currently, influenza vaccine for the annual, seasonal influenza program comes from four manufacturers. However, only a single manufacturer produces the annual [[vaccine]] entirely within the U.S. Thus, if a pandemic occurred and existing U.S.-based influenza vaccine manufacturing capacity was completely diverted to producing a pandemic vaccine, supply would be severely limited. Moreover, because the annual influenza manufacturing process takes place during most of the year, the time and capacity to produce vaccine against potential pandemic viruses for a stockpile, while continuing annual influenza vaccine production, is limited. Since supply will be limited, it is critical for HHS to be able to direct vaccine distribution in accordance with predefined groups (see [http://www.hhs.gov/pandemicflu/plan/appendixd.html Appendix D]); HHS will ensure the building of capacity and will engage states in a discussion about the purchase and distribution of pandemic influenza vaccine.

:Vaccine production capacity: The protective immune response generated by current influenza vaccines is largely based on viral [[hemagglutinin]] (HA) and [[neuraminidase]] (NA) [[antigen]]s in the vaccine. As a consequence, the basis of influenza vaccine manufacturing is growing massive quantities of virus in order to have sufficient amounts of these protein antigens to stimulate immune responses. Influenza vaccines used in the United States and around world are manufactured by growing virus in fertilized hens’ [[Egg (biology)|egg]]s, a commercial process that has been in place for decades. To achieve current vaccine production targets millions of 11-day old fertilized eggs must be available every day of production.

:In the near term, further expansion of these systems will provide additional capacity for the U.S.-based production of both seasonal and pandemic vaccines, however, the surge capacity that will be needed for a pandemic response cannot be met by egg-based vaccine production alone, as it is impractical to develop a system that depends on hundreds of millions of 11-day old specialized eggs on a standby basis. In addition, because a pandemic could result from an [[avian influenza]] strain that is lethal to [[chicken]]s, it is impossible to ensure that eggs will be available to produce vaccine when needed.

:In contrast, [[cell culture]] manufacturing [[technology]] can be applied to influenza vaccines as they are with most viral vaccines (e.g., [[polio]] vaccine, [[measles]]-[[mumps]]-[[rubella]] vaccine, [[chickenpox]] vaccine). In this system, viruses are grown in closed systems such as [[bioreactor]]s containing large numbers of cells in growth media rather than eggs. The surge capacity afforded by cell-based technology is insensitive to seasons and can be adjusted to vaccine demand, as capacity can be increased or decreased by the number of bioreactors or the volume used within a bioreactor. In addition to supporting basic research on cell-based influenza vaccine development, HHS is currently supporting a number of vaccine manufacturers in the advanced development of cell-based influenza vaccines with the goal of developing U.S.-licensed cell-based influenza vaccines produced in the United States.</ref><ref>{{cite journal | author = Bardiya N, Bae J | title = Influenza vaccines: recent advances in production technologies. | url=http://www.springerlink.com/content/jdt26gc39v4bwk9q/ | journal = Appl Microbiol Biotechnol | volume = 67 | issue = 3 | pages = 299-305 | year = 2005 | id = PMID 15660212}}</ref> The US government has purchased from [[Sanofi Pasteur]] and [[Chiron Corporation]] several million doses of [[vaccine]] meant to be used in case of an [[influenza pandemic]] of [[H5N1]] avian influenza and is conducting clinical trials with these vaccines.<ref> [http://www.nytimes.com/2006/03/30/health/30vaccine.html?_r=1&oref=slogin New York Times article ""Doubt Cast on Stockpile of a Vaccine for Bird Flu""] by Denise Grady. Published: March 30, 2006. Accessed 19 Oct 06</ref> Researchers at the University of Pittsburgh have had success with a genetically engineered vaccine that took only a month to make and completely protected chickens from the highly pathogenic [[H5N1]] virus.<ref>[http://wired.com/news/wireservice/0,70102-0.html?tw=wn_index_7 Wired News] [http://jvi.asm.org/cgi/content/abstract/80/4/1959 JVI]</ref>

According to the [[United States]] [[Department of Health & Human Services]]:
:In addition to supporting basic research on cell-based influenza vaccine development, HHS is currently supporting a number of [[vaccine]] manufacturers in the advanced development of cell-based influenza vaccines with the goal of developing U.S.-licensed cell-based influenza vaccines produced in the United States. Dose-sparing technologies. Current U.S.-licensed vaccines stimulate an immune response based on the quantity of HA ([[hemagglutinin]]) [[antigen]] included in the dose. Methods to stimulate a strong immune response using less HA antigen are being studied in [[H5N1]] and H9N2 vaccine trials. These include changing the mode of delivery from intramuscular to intradermal and the addition of immune-enhancing [[adjuvant]] to the vaccine formulation. Additionally, HHS is soliciting contract proposals from manufacturers of [[vaccine]]s, [[adjuvant]]s, and medical devices for the development and licensure of influenza vaccines that will provide dose-sparing alternative strategies.<ref>[http://www.hhs.gov/pandemicflu/plan/appendixf.html Department of Health & Human Services]</ref>

[[Chiron Corporation]] is now recertified and under contract with the [[National Institutes of Health]] to produce 8,000-10,000 investigational doses of [[H5N1|Avian Flu (H5N1) vaccine]]. [[MedImmune]] and [[Aventis Pasteur]] are under similar contracts.<ref> [http://www3.niaid.nih.gov/news/newsreleases/2004/flucontracts.htm NAID - 2004 News] [http://www3.niaid.nih.gov/news/newsreleases/2005/medimmune.htm NAID - 2005 News]</ref> The [[United States]] government hopes to obtain enough [[vaccine]] in [[2006]] to treat 4 million people. However, it is unclear whether this vaccine would be effective against a hypothetical mutated strain that would be easily transmitted through human populations, and the shelflife of stockpiled doses has yet to be determined.<ref>[http://www.npr.org/templates/story/story.php?storyId=5133306 NPR]</ref>

The ''[[New England Journal of Medicine]]'' reported on March 30, 2006 on one of dozens of vaccine studies currently being conducted. The Treanor et al. study was on vaccine produced from the human isolate (A/Vietnam/1203/2004 [[H5N1]]) of a virulent clade 1 influenza A (H5N1) virus with the use of a plasmid rescue system, with only the hemagglutinin and neuraminidase genes expressed and administered without adjuvant. "The rest of the genes were derived from an avirulent egg-adapted influenza A/PR/8/34 strain. The hemagglutinin gene was further modified to replace six basic amino acids associated with high pathogenicity in birds at the cleavage site between hemagglutinin 1 and hemagglutinin 2. Immunogenicity was assessed by microneutralization and hemagglutination-inhibition assays with the use of the vaccine virus, although a subgroup of samples were tested with the use of the wild-type influenza A/Vietnam/1203/2004 (H5N1) virus." The results of this study combined with others scheduled to be completed by Spring 2007 is hoped will provide a highly immunogenic vaccine that is cross-protective against heterologous influenza strains.<ref>[http://content.nejm.org/cgi/content/full/354/13/1411 New England Journal of Medicine]Volume 354:1411-1413 - March 30, 2006 - Number 13 - ''Vaccines against Avian Influenza — A Race against Time''</ref>

On August 18, 2006. the [[World Health Organization]] changed the [[H5N1]] strains recommended for candidate vaccines for the first time since 2004. "The WHO's new prototype strains, prepared by reverse genetics, include three new H5N1 subclades. The [[hemagglutinin]] sequences of most of the H5N1 avian influenza viruses circulating in the past few years fall into two genetic groups, or clades. Clade 1 includes human and bird isolates from [[Vietnam]], [[Thailand]], and [[Cambodia]] and bird isolates from [[Laos]] and [[Malaysia]]. Clade 2 viruses were first identified in bird isolates from [[China]], [[Indonesia]], [[Japan]], and [[South Korea]] before spreading westward to the [[Middle East]], [[Europe]], and [[Africa]]. The clade 2 viruses have been primarily responsible for human H5N1 infections that have occurred during late 2005 and 2006, according to WHO. Genetic analysis has identified six subclades of clade 2, three of which have a distinct geographic distribution and have been implicated in human infections:
* Subclade 1, Indonesia
* Subclade 2, Middle East, Europe, and Africa
* Subclade 3, China
On the basis of the three subclades, the WHO is offering companies and other groups that are interested in pandemic vaccine development these three new prototype strains:
* An A/Indonesia/2/2005-like virus
* An A/Bar headed goose/Quinghai/1A/2005-like virus
* An A/Anhui/1/2005-like virus
[...] Until now, researchers have been working on prepandemic vaccines for H5N1 viruses in clade 1. In March, the first clinical trial of a U.S. vaccine for H5N1 showed modest results. In May, French researchers showed somewhat better results in a clinical trial of an H5N1 vaccine that included an adjuvant. Vaccine experts aren't sure if a vaccine effective against known H5N1 viral strains would be effective against future strains. Although the new viruses will now be available for vaccine research, WHO said clinical trials using the clade 1 viruses should continue as an essential step in pandemic preparedness, because the trials yield useful information on priming, cross-reactivity, and cross-protection by vaccine viruses from different clades and subclades."<ref> [http://www.cidrap.umn.edu/cidrap/content/influenza/avianflu/news/aug1806vaccines.html CIDRAP News] article ''
WHO changes H5N1 strains for pandemic vaccines, raising concern over virus evolution'' published August 18, 2006</ref><ref> [http://www.who.int/csr/disease/avian_influenza/guidelines/recommendationvaccine.pdf WHO (PDF}] article ''Antigenic and genetic characteristics of H5N1 viruses and candidate H5N1 vaccine viruses developed for potential use as pre-pandemic vaccines'' published August 18, 2006</ref>

As of November 2006, the United States [[Department of Health and Human Services]] still had enough H5N1 pre-pandemic vaccine to treat about 3 million people (5.9 million full-potency doses) in spite of 0.2 million doses used for research and 1.4 million doses that have begun to lose potency (from the original 7.5 million full-potency doses purchased from [[Sanofi Pasteur]] and [[Chiron Corp.]]). The expected shelf life of [[seasonal flu]] vaccine is about a year so the fact that most of the H5N1 pre-pandemic stockpile is still good after about 2 years is considered encouraging.<ref> [http://www.cidrap.umn.edu/cidrap/content/influenza/panflu/news/nov1706stockpile.html CIDRAP] article ''HHS: Most H5N1 vaccine on hand is still potent'' published November 17, 2006</ref>

==Flu seasons==
===2003–2004 season (Northern Hemisphere)===
The production of flu [[vaccine]] requires a lead time of about six months before the season. It is possible that by flu season a strain becomes common for which the vaccine does not provide protection. In the [[2003]]–[[2004]] season the [[vaccine]] was produced to protect against A/Panama, A/New Caledonia, and B/Hong Kong. A new strain, A/Fujian, was discovered after production of the vaccine started and vaccination gave only partial protection against this strain.

Nature magazine reported that the [[Influenza Genome Sequencing Project]], using phylogenetic analysis of 156 [[H3N2]] genomes, "explains the appearance, during the 2003–2004 season, of the 'Fujian/411/2002'-like strain, for which the existing vaccine had limited effectiveness" as due to an epidemiologically significant [[reassortment]]. "Through a [[reassortment]] event, a minor clade provided the [[haemagglutinin]] gene that later became part of the dominant strain after the [[2002]]–[[2003]] season. Two of our samples, A/New York/269/2003 ([[H3N2]]) and A/New York/32/2003 ([[H3N2]]), show that this minor clade continued to circulate in the [[2003]]–[[2004]] season, when most other isolates were reassortants." <ref>[http://www.nature.com/nature/journal/v437/n7062/full/nature04239.html Nature]</ref>

According to the [[Centers for Disease Control and Prevention|CDC]]:
:During the 2003–2004 [[Flu season|influenza season]], [[Influenzavirus A|influenza A]] (H1), A ([[H3N2]]), and [[influenzavirus B|B]] viruses co-circulated worldwide, and influenza A (H3N2) [[virus]]es predominated. Several Asian countries reported widespread outbreaks of avian influenza A ([[H5N1]]) among poultry. In [[Vietnam]] and [[Thailand]], these outbreaks were associated with severe illnesses and deaths among humans. In the [[United States]], the 2003–2004 influenza season began earlier than most seasons, peaked in December, was moderately severe in terms of its impact on mortality, and was associated predominantly with influenza A (H3N2) viruses.<ref name= "CDC 2003 to 2005"> [http://www.cdc.gov/mmwr/preview/mmwrhtml/mm5325a1.htm CDC] article ''Update: Influenza Activity — United States and Worldwide, 2003–04 Season, and Composition of the 2004–05 Influenza Vaccine'' published July 2, 2004 </ref>

During September 28, 2003–May 22, 2004, [[WHO]] and NREVSS collaborating laboratories in the United States tested 130,577 respiratory specimens for influenza viruses; 24,649 (18.9%) were positive. Of these, 24,393 (99.0%) were influenza A viruses, and 249 (1.0%) were influenza B viruses. Among the influenza A viruses, 7,191 (29.5%) were subtyped; 7,189 (99.9%) were influenza A (H3N2) viruses, and two (0.1%) were influenza A (H1) viruses. The proportion of specimens testing positive for influenza first increased to >10% during the week ending October 25, 2003 (week 43), peaked at 35.2% during the week ending November 29 (week 48), and declined to <10% during the week ending January 17, 2004 (week 2). The peak percentage of specimens testing positive for influenza during the previous four seasons had ranged from 23% to 31% and peaked during late December to late February.<ref name= "CDC 2003 to 2005"/>

As of June 15, 2004, CDC had antigenically characterized 1,024 influenza viruses collected by U.S. laboratories since October 1, 2003: 949 influenza A ([[H3N2]]) viruses, three influenza A (H1) viruses, one influenza A ([[H7N2]]) virus, and 71 influenza B viruses. Of the 949 influenza A (H3N2) isolates characterized, 106 (11.2%) were similar antigenically to the vaccine strain A/Panama/2007/99 (H3N2), and 843 (88.8%) were similar to the drift variant, A/Fujian/411/2002 (H3N2). Of the three A (H1) isolates that were characterized, two were H1N1 viruses, and one was an [[H1N2]] virus. The hemagglutinin proteins of the influenza A (H1) viruses were similar antigenically to the hemagglutinin of the vaccine strain A/New Caledonia/20/99. Of the 71 influenza B isolates that were characterized, 66 (93%) belonged to the B/Yamagata/16/88 lineage and were similar antigenically to B/Sichuan/379/99, and five (7%) belonged to the B/Victoria/2/87 lineage and were similar antigenically to the corresponding vaccine strain B/Hong Kong/330/2001.<ref name= "CDC 2003 to 2005"/>

;H9N2
In December 2003, one confirmed case of avian influenza A ([[H9N2]]) virus infection was reported in a child aged 5 years in Hong Kong. The child had fever, cough, and nasal discharge in late November, was hospitalized for 2 days, and fully recovered. The source of this child's H9N2 infection is unknown.<ref name= "CDC 2003 to 2005"/>

;H5N1
During January–March 2004, a total of 34 confirmed human cases of avian influenza A ([[H5N1]]) virus infection were reported in Vietnam and Thailand. The cases were associated with severe respiratory illness requiring hospitalization and a case-fatality proportion of 68% (Vietnam: 22 cases, 15 deaths; Thailand: 12 cases, eight deaths). A substantial proportion of the cases were among children and young adults (i.e., persons aged 5–24 years). These cases were associated with widespread outbreaks of highly pathogenic H5N1 influenza among domestic poultry.<ref name= "CDC 2003 to 2005"/>

;H7N3
During March 2004, health authorities in Canada reported two confirmed cases of avian influenza A ([[H7N3]]) virus infection in poultry workers who were involved in culling of poultry during outbreaks of highly pathogenic H7N3 on farms in the Fraser River Valley, British Columbia. One patient had unilateral conjunctivitis and nasal discharge, and the other had unilateral conjunctivitis and headache. Both illnesses resolved without hospitalization.<ref name= "CDC 2003 to 2005"/>

;H7N2
During the 2003–2004 influenza season, a case of avian influenza A ([[H7N2]]) virus infection was detected in an adult male from New York, who was hospitalized for upper and lower respiratory tract illness in November 2003. Influenza A (H7N2) virus was isolated from a respiratory specimen from the patient, whose acute symptoms resolved. The source of this person's infection is unknown.<ref name= "CDC 2003 to 2005"/>

===2004 season (Southern Hemisphere)===
The composition of influenza virus vaccines for use in the 2004 Southern Hemisphere influenza season recommended by the World Health Organization was:
* an A/New Caledonia/20/99(H1N1)-like virus
* an A/Fujian/411/2002(H3N2)-like virus (A/Kumamoto/102/2002 and A/Wyoming/3/2003 were egg-grown A/Fujian/411/2002-like viruses)
* a B/Hong Kong/330/2001-like virus (B/Shandong/7/97, B/Hong Kong/330/2001 and B/Hong Kong/1434/2002 were among those used at the time. B/Brisbane/32/2002 was also available.)
<ref>[http://www.who.int/csr/disease/influenza/vaccinerecommendations1/en/index5.html WHO website recommendation for the 2004 season]</ref>
<ref>[http://www.who.int/csr/disease/influenza/recommendations2004/en/index.html WHO — Recommended composition of influenza virus vaccines for use in the 2004 influenza season]</ref>

===2004–2005 season (Northern Hemisphere)===
According to the [[Centers for Disease Control and Prevention|CDC]]:
:On the basis of antigenic analyses of recently isolated influenza viruses, epidemiologic data, and postvaccination serologic studies in humans, the Food and Drug Administration's Vaccines and Related Biological Products Advisory Committee (VRBPAC) recommended that the 2004–05 trivalent influenza vaccine for the United States contain A/New Caledonia/20/99-like (H1N1), [[Fujian flu|A/Fujian/411/2002-like (H3N2)]], and B/Shanghai/361/2002-like viruses. Because of the growth properties of the A/Wyoming/3/2003 and B/Jiangsu/10/2003 viruses, U.S. vaccine manufacturers are using these antigenically equivalent strains in the vaccine as the H3N2 and B components, respectively. The A/New Caledonia/20/99 virus will be retained as the H1N1 component of the vaccine.<ref name= "CDC 2003 to 2005"/>

===2005 season (Southern Hemisphere)===
The composition of influenza virus vaccines for use in the 2005 Southern Hemisphere influenza season recommended by the World Health Organization was:
* an A/New Caledonia/20/99(H1N1)-like virus;
* an A/Wellington/1/2004(H3N2)-like virus;
* a B/Shanghai/361/2002-like virus (B/Shanghai/361/2002, B/Jilin/20/2003 and B/Jiangsu/10/2003 were used at the time)
<ref>[http://www.who.int/csr/disease/influenza/vaccinerecommendations1/en/index3.html WHO website recommendation for the 2005 season]</ref>
<ref>[http://www.who.int/wer/2004/en/wer7941.pdf WHO — Weekly epidemiological record — 8 October 2004, No. 41, 2004, 79, 369–376] (PDF)</ref>

===2005–2006 season (Northern Hemisphere)===
The [[vaccine]]s produced for the [[2005]]–[[2006]] season use:
* an A/New Caledonia/20/[[1999]]-like([[H1N1]]);
* an A/California/7/[[2004]]-like([[H3N2]]) (or the antigenically equivalent strain A/New York/55/[[2004]]);
* a B/Jiangsu/10/[[2003]]-like viruses.

In people in the U.S., overall [[flu]] and [[pneumonia]] deaths were below those of a typical [[flu season]] with 84% [[Influenzavirus A]] and the rest [[Influenzavirus B]]. Of the patients who had Type A viruses, 80% had viruses identical or similar to the A bugs in the vaccine. 70% of the people testing positive for a B virus had Type B Victoria, a version not found in the vaccine.<ref> [http://news.yahoo.com/s/ap/20060428/ap_on_he_me/flu_season;_ylt=ArqgzESNaMQox6OHu5YxxlKs0NUE;_ylu=X3oDMTA3czJjNGZoBHNlYwM3NTE- Yahoo News] [[Associated Press]] article ''CDC: Milder Than Normal Flu Season Ending'' published April 27, 2006</ref>

"During the 2005–06 season, influenza A (H3N2) viruses predominated overall, but late in the season influenza B viruses were more frequently isolated than influenza A viruses. Influenza A (H1N1) viruses circulated at low levels throughout the season. Nationally, activity was low from October through early January, increased during February, and peaked in early March. Peak activity was less intense, but activity remained elevated for a longer period of time this season compared to the previous three seasons. The longer period of elevated activity may be due in part to regional differences in the timing of peak activity and intensity of influenza B activity later in the season."<ref> [http://www.cdc.gov/flu/weekly/weeklyarchives2005-2006/05-06summary.htm CDC - 2005-06 U.S. INFLUENZA SEASON SUMMARY]</ref>

===2006 season (Southern Hemisphere)===
The composition of influenza virus vaccines for use in the 2006 Southern Hemisphere influenza season recommended by the World Health Organization was:
* an A/New Caledonia/20/99(H1N1)-like virus;
* an A/California/7/2004(H3N2)-like virus (A/New York/55/2004 was used at the time);
* a B/Malaysia/2506/2004-like virus
<ref>[http://www.who.int/csr/disease/influenza/recommendations2006south/en/index.html WHO website recommendation for the 2006 season]</ref>
<ref>[http://www.who.int/wer/2005/wer8040.pdf WHO — Weekly epidemiological record — 7 October 2005, No. 40, 2005, 80, 341–352] (PDF)</ref>

===2006–2007 season (Northern Hemisphere)===
The 2006–2007 influenza vaccine composition recommended by the World Health Organization on February 15, 2006 and the U.S. FDA's Vaccines and Related Biological Products Advisory Committee (VRBPAC) on February 17, 2006 use:
* an A/New Caledonia/20/99 (H1N1)-like virus;
* an A/Wisconsin/67/2005 (H3N2)-like virus (A/Wisconsin/67/2005 and A/Hiroshima/52/2005 strains);
* a B/Malaysia/2506/2004-like virus from B/Malaysia/2506/2004 and B/Ohio/1/2005 strains which are of B/Victoria/2/87 lineage.
<ref>[http://www.cdc.gov/flu/professionals/vaccination/composition0607.htm CDC] [http://www.phac-aspc.gc.ca/fluwatch/05-06/w08_06/index.html fluwatch] B/Victoria/2/87 lineage</ref>

===2007 season (Southern Hemisphere)===
The composition of influenza virus vaccines for use in the 2006 Southern Hemisphere influenza season recommended by the World Health Organization on September 20, 2006 <ref>[http://www.who.int/csr/disease/influenza/vaccinessouth2007/en/index1.html 20 September 2006: WHO information meeting (Morning)]</ref> was:
* an A/New Caledonia/20/99(H1N1)-like virus,
* an A/Wisconsin/67/2005(H3N2)-like virus (A/Wisconsin/67/2005 and A/Hiroshima/52/2005 were used at the time),
* a B/Malaysia/2506/2004-like virus
<ref>[http://www.who.int/csr/disease/influenza/recommendations2007south/en/index.html WHO website recommendation for 2007 season]</ref>
<ref>[http://www.who.int/csr/disease/influenza/recommendationfinal22sept.pdf WHO — Recommended composition of influenza virus vaccines for use in the 2007 influenza season — September 2006] (PDF)</ref>

===2007-2008 season (Northern Hemisphere)===
The composition of influenza virus vaccines for use in the 2007–2008 Northern Hemisphere influenza season recommended by the World Health Organization on February 14, 2007 <ref>[http://www.who.int/csr/disease/influenza/vaccinesnorth2008/en/index1.html 14 February 2007: WHO information meeting (Morning)]</ref> was:
* an A/Solomon Islands/3/2006 (H1N1)-like virus;
* an A/Wisconsin/67/2005 (H3N2)-like virus (A/Wisconsin/67/2005 (H3N2) and A/Hiroshima/52/2005 were used at the time);
* a B/Malaysia/2506/2004-like virus
<ref>[http://www.who.int/csr/disease/influenza/recommendations2007north/en/index.html WHO website recommendation for 2007-2008 season]</ref>
<ref>[http://www.who.int/csr/disease/influenza/recommendationfinal22sept.pdf WHO — Recommended composition of influenza virus vaccines for use in the 2007-2008 influenza season] (PDF)</ref>

===2008 season (Southern Hemisphere)===
The composition of virus vaccines for use in the 2006 Southern Hemisphere influenza season recommended by the World Health Organization on September 17-19, 2007 was:
* an A/Solomon Islands/3/2006 (H1N1)-like virus;
* an A/Brisbane/10/2007 (H3N2)-like virus;
* a B/Florida/4/2006-like virus
<ref>[http://www.who.int/csr/disease/influenza/recommendations2008south/en/index.html WHO website recommendation for 2008 season]</ref><ref>[http://www.who.int/entity/csr/disease/influenza/recommendationlong2.pdf WHO — Recommended composition of influenza virus vaccines for use in the 2008 influenza season] (PDF)</ref>

==Flu vaccine for nonhumans==
"Vaccination in the veterinary world pursues four goals: (i) protection from clinical disease, (ii) protection from infection with virulent virus, (iii) protection from virus excretion, and (iv) serological differentiation of infected from vaccinated animals (so-called DIVA principle). In the field of influenza vaccination, neither commercially available nor experimentally tested vaccines have been shown so far to fulfil all of these requirements."<ref> [http://www.influenzareport.com/ir/ai.htm Influenza Report (online book)] chapter ''Avian Influenza'' by Timm C. Harder and Ortrud Werner</ref>

===Horses===
[[Horse]]s with [[horse flu]] can run a fever, have a dry hacking cough, have a runny nose, and become depressed and reluctant to eat or drink for several days but usually recover in 2 to 3 weeks. "Vaccination schedules generally require a primary course of 2 doses, 3–6 weeks apart, followed by boosters at 6–12 month intervals. It is generally recognised that in many cases such schedules may not maintain protective levels of antibody and more frequent administration is advised in high-risk situations."<ref>[http://195.224.162.216/equiflunet/equiflunet_vaccines.html equiflunet_vaccines]</ref>

===Poultry===
[[Poultry]] vaccines for [[bird flu]] are made on the cheap and are not filtered and purified like human vaccines to remove bits of bacteria or other viruses. They usually contain whole virus, not just [[hemagglutin]] as in most human flu vaccines. Purification to standards needed for humans is far more expensive than the original creation of the unpurified vaccine from eggs. There is no market for veterinary vaccines that are that expensive. Another difference between human and poultry vaccines is that poultry vaccines are [[adjuvated]] with mineral oil, which induces a strong immune reaction but can cause inflammation and abscesses. "Chicken vaccinators who have accidentally jabbed themselves have developed painful swollen fingers or even lost thumbs, doctors said. Effectiveness may also be limited. Chicken vaccines are often only vaguely similar to circulating flu strains — some contain an [[H5N2]] strain isolated in Mexico years ago. 'With a chicken, if you use a vaccine that's only 85 percent related, you'll get protection,' Dr. Cardona said. 'In humans, you can get a single point mutation, and a vaccine that's 99.99 percent related won't protect you.' And they are weaker [than human vaccines]. 'Chickens are smaller and you only need to protect them for six weeks, because that's how long they live till you eat them,' said Dr. John J. Treanor, a vaccine expert at the University of Rochester. Human seasonal flu vaccines contain about 45 micrograms of antigen, while an experimental A([[H5N1]]) vaccine contains 180. Chicken vaccines may contain less than 1 microgram. 'You have to be careful about extrapolating data from poultry to humans,' warned Dr. David E. Swayne, director of the agriculture department's Southeast Poultry Research Laboratory. 'Birds are more closely related to [[dinosaur]]s.'"<ref> [http://www.nytimes.com/2006/05/02/science/02chic.html New York Times] article ''Turning to Chickens in Fight With Bird Flu'' published May 2, 2006</ref>

Researchers, led by Nicholas Savill of the University of Edinburgh in Scotland, used mathematical models to simulate the spread of [[H5N1]] and concluded that "at least 95 per cent of birds need to be protected to prevent the virus spreading silently. In practice, it is difficult to protect more than 90 per cent of a flock; protection levels achieved by a vaccine are usually much lower than this."<ref> [http://www.scidev.net/gateways/index.cfm?fuseaction=readitem&rgwid=4&item=News&itemid=3051&language=1 SciDev.Net] article ''Bird flu warning over partial protection of flocks'' published August 16,2006</ref>

===Pigs===
[[Swine influenza]] virus (SIV) vaccines are extensively used in the [[swine]] industry in Europe and North America. Most swine flu vaccine manufacturers include an [[H1N1]] and an [[H3N2]] SIV strains.

Swine influenza has become a greater problem in recent decades. [[Evolution]] of the virus has resulted in inconsistent responses to traditional vaccines. Standard commercial swine flu vaccines are effective in controlling the problem when the virus strains match enough to have significant cross-protection and custom (autogenous) vaccines made from the specific viruses isolated are created and used in the more difficult cases.<ref> [http://nationalhogfarmer.com/mag/swine_flu_virus_endemic/ National Hog Farmer] article ''Swine Flu Virus Turns Endemic'' published September 15, 2007 </ref> SIV vaccine manufacture Novartis paints this picture: "A strain of swine influenza virus (SIV) called H3N2, first identified in the US in 1998, has brought exasperating production losses to swine producers. Abortion storms are a common sign. Sows go off feed for two or three days and run a fever up to 106° F. Mortality in a naïve herd can run as high as 15%."<ref> [http://www.livestock.novartis.com/cv_swine.html livestock.novartis.com] Custom Vaccines: Swine</ref>

==See also==
*[[Vaccine]] for information valid about all vaccines, not just flu vaccines.
*[[Vaccine controversy]] for the pros and cons of being vaccinated.
*[[Thiomersal]] is a controversial mercury-containing organic compound used as an antiseptic and antifungal agent in [[vaccine]]s.

==Sources and notes==
<div class="references-small"><references /></div>

==Further reading==
*[http://digital.library.unt.edu/govdocs/crs/search.tkl?q=influenza&search_crit=subject&search=Search&date1=Anytime&date2=Anytime&type=form Read Congressional Research Service (CRS) Reports regarding Influenza and vaccines]
*[http://video.google.com/videoplay?docid=2163175142473074044 What's in a Flu Shot?]

{{Influenza}}
{{Vaccines}}

[[Category:Prevention]]
[[Category:Vaccines]]
[[Category:Influenza vaccines]]

[[de:Grippeimpfung]]
[[fi:Influenssarokote]]
{{WikiDoc Sources}}

wikidoc:General disclaimer

2009-10-02T11:23:20Z

Levacher:

'''WikiDoc MAKES NO GUARANTEE OF VALIDITY.'''

'''WikiDoc is not a professional health care provider, nor is it a suitable replacement for a licensed healthcare provider.
'''

'''WikiDoc is intended to be an educational tool, not a tool for any form of healthcare delivery.
'''

'''WikiDoc does not promote the dissemination of copyrighted material or plagiarism. Do not post copyrighted material. You as the submitter of material are responsible for any copyright violation'''.

'''WikiDoc encourages you to contact us [mailto:mgibson@wikidoc.org] if you have identified any potential copyright violation or any content that might be considered to constitute plagiarism so that we may resolve the issue.'''

Below is our statement regarding liability, limitations, warranty, validity, guarantee, negligence, responsibility, damages, product liability, errors, omissions, indemnification, legal action, and contract (or lack thereof of any of the above).

WikiDoc is an online open-content collaborative medical encyclopedia / textbook and news servie, that is a voluntary association of individuals and groups who are developing a common resource of human medical knowledge. The structure of the project allows anyone with an Internet connection and World Wide Web browser to alter its content. Please be advised that nothing found here has necessarily been reviewed by professionals with the expertise required to provide you with complete, accurate or reliable Healthcare information. WikiDoc is not a substitute for a licensed health care professional. WikiDoc is not intended to guide medical decision making, but is instead intended as an educational tool.

That is not to say that you will not find valuable and accurate educational information in WikiDoc; some of the time you will. However, WikiDoc cannot guarantee the validity of the information found here. The content of any given article may recently have been changed, vandalized or altered by someone whose opinion does not correspond with the consensus in the medical field in your country, state, or city.

You can download these articles and present the information contained in the articles. In doing so, you agree to the following terms of use. While the website strives to have the most up to date and accurate data, you agree to consult published medical literature or the package insert for official trial results, dosing information or instructions for use of pharmaceutical products and devices. Off label use of drugs and devices is not encouraged. Articles of a forward looking investigational nature may present data to support the rationale for the use of a variety of pharmacologic agents and devices in both approved and non-approved indications. Actual prescribing information is by intent minimal or completely lacking. These articles has been prepared for scientific educational purposes, and cannot be considered an inducement to use any drug or device in non-registered indications. The site does not recommend the use of any drug or device in any manner inconsistent with that described in the full prescribing information.

In entering the download section, you assume responsibility for the accuracy of the information and its utilization. In entering WikiDoc, you agree to hold the website free of responsibility and/or liability for potential damages or injury to persons or property as a matter of products liability, negligence, copyright infringement or otherwise from any use or operation of any methods, products, instructions or ideas contained in the material herein.

The views expressed in the articles are those of the individuals who contributed the materials and do not necessarily reflect the views of the editorial staff or the founding organization. Inclusion of materials in articles does not constitute a guarantee or endorsement of the organization of the quality or the value of the product or the claim made by the author or any manufacturer. Statements contained herein are those of the person who posted the material.

The website is a free educational service to the healthcare community. All articles on this server are made public by the author(s) who created the articles. The articles are public domain and may be downloaded and used freely for personal, research, scientific, and / or information purposes so long as you credit WikiDoc as the source of the material.

1. LINKS TO THIRD PARTY SITES:

The Editors and their agents, and the contributors to the website may provide, or third parties may provide, links to other World Wide Web sites or resources. The Editors and their agents, and the contributors to the website do not endorse and are not responsible for any data, software or other content available from such sites or resources and you acknowledge and agree that they shall not be liable, directly or indirectly, for any damage or loss relating to your use of or reliance on such data, software or other content.

2. WARRANTY LIMITATIONS:

2.1. You understand and agree that the website is provided on an "AS IS" and “AS AVAILABLE” basis, without warranties of any kind, either express or implied, including, but not limited to, warranties of title, or implied warranties of merchantability or fitness for a particular purpose.

2.2. The use of information on the website is at your own risk.

2.3. Access to the website may be interrupted at any time for any reason to any individual(s) and may not be error free.

2.4. Neither the website, nor anyone else involved in creating, producing or delivering the website or the materials contained therein, shall be liable for any direct, indirect, incidental, special, consequential or punitive damages arising out of your use or inability to use the website. You understand and agree that any material or data obtained through use of the website is at your own discretion and risk and that you will be solely responsible for any resulting damage to your computer system or loss of data.

3. SUPPORT:

Neither the Editors and their agents, nor the contributors to the website shall have any obligation to provide you with any maintenance or support relating the website.

4. DISCLAIMER:

In view of the possibility of human error by the authors, editors, or publishers of the works contained in the website, neither the website, nor any other party involved in the preparation of this work, warrants that the information contained herein is in every respect accurate or complete, and they are not responsible for any errors or omissions or for the results obtained from the use of such. Readers are encouraged to confirm the information contained herein with other sources. Patients and consumers reading articles posted on the website should review the information carefully with their professional healthcare provider. The information is not intended to replace medical advice offered by physicians. The website makes no representations or warranties with respect to any treatment, action, or application of medication or preparation by any person following the information offered or provided within or through the website. The website is not be liable for any direct, indirect, consequential, special, exemplary, or other damages arising there from.

5. NOTICE:

The Editors and their agents, and the contributors to the website are not responsible for errors or omissions or for any consequences from application of the information herein and make no warranty, expressed or implied, with respect to the currency, completeness, or accuracy of the contents of the publication or any of the Services. Application of this information in a particular situation remains the professional responsibility of the practitioner.

Some information on drugs and medical devices presented in this website may be investigational and/or approved for limited use. It is the responsibility of health care providers to ascertain the status of each drug or device planned for use in their clinical practice.

6. INDEMNIFICATION:

You agree to hold harmless and indemnify the website, the Editors and their agents, and the contributors to the website, against any liability for any claims and expenses, including reasonable attorney's fees, relating to any violation of the terms of this Agreement or arising out of any material submitted by or used by you.

7. LINKING TO THE WEBSITE:

You may have a simple link from your website to ours. However, you must first ask our permission if you intend to frame our site or incorporate pieces of it into a different site or product in a way that is not clear to our users. You acknowledge and agree not to link to us if you engage in illegal, obscene, or offensive content, or if the link in any way has a negative impact on our reputation.

8. INFORMATION THAT YOU PUT ON WIKIDOC:

When you place materials or information on the website that are available publicly, you give us an irrevocable, perpetual license to use that information. For example, we have the right to display a comment that you post on one of our discussion boards for as long as we want. We will consider requests to remove information that you make publicly available on our Web sites on an individual basis.

We ask that you not post any messages with misleading, false, or inappropriate language or statements. We reserve the right to remove any offensive or fraudulent content at any time without your consent.

9. GOVERNING LAW; JURISDICTION; STATUTE OF LIMITATIONS:

This agreement shall be governed by the laws of the state of Massachusetts applicable to agreements wholly made and performed in Massachusetts. In the event that you believe you have been irreparably harmed by any cause of action relating to the website, you agree to inform the website in writing and grant the website thirty (30) days to cure the harm before initiating any action. Any legal action, suit or proceeding arising out of or relating to this agreement or a breach thereof, shall be instituted in a court of competent jurisdiction in Boston MA, and you hereby consent and submit to personal jurisdiction of such court, waive any objection to venue in such court and consent to service of process by overnight courier or express mail at your last known address. Any cause of action initiated by you must be initiated within 6 months after the claim or cause of action has arisen or be barred. Publication of information found in WikiDoc may be in violation of the laws of the country or jurisdiction from where you are viewing this information. The WikiDoc database is stored on a server in the United States of America, and is maintained in reference to the protections afforded under local and federal law. Laws in your country or jurisdiction may not protect or allow the same kinds of speech or distribution. WikiDoc does not encourage the violation of any laws; and cannot be responsible for any violations of such laws, should you link to this domain or use, reproduce, or republish the information contained herein. All correspondence should be addressed in writing to Susan Marble, Managing editor, 350 Longwood Avenue, Boston MA 02115.

10. NO FORMAL PEER REVIEW:

We are working on ways to select and highlight reliable versions of articles. Our active community of editors uses tools such as the recent changes tool to monitor new and changing content. However, WikiDoc is not uniformly peer reviewed; while readers may correct errors or engage in casual peer review, they have no legal duty to do so and thus all information read here is without any implied warranty of fitness for any purpose or use whatsoever. Even articles that have been vetted by informal peer review or featured article processes may later have been edited inappropriately, just before you view them.

None of the authors, contributors, sponsors, administrators, sysops, or anyone else connected with WikiDoc in any way whatsoever can be responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these web pages.

11. NO CONTRACT; LIMITED LICENSE:

Please make sure that you understand that the information provided here is being provided freely, and that no kind of agreement or contract is created between you and the owners or users of this site, the owners of the servers upon which it is housed, the individual WikiDoc contributors, any project administrators, sysops or anyone else who is in any way connected with this project or sister projects subject to your claims against them directly. You are being granted a limited license to copy anything from this site; it does not create or imply any contractual or extracontractual liability on the part of WikiDoc or any of its agents, members, organizers or other users.

There is no agreement or understanding between you and WikiDdoc regarding your use or modification of this information beyond the GNU Free Documentation License (GFDL); neither is anyone at WikiDoc responsible should someone change, edit, modify or remove any information that you may post on WikiDoc or any of its associated projects.

12. TRADEMARKS:

Any of the trademarks, service marks, collective marks, design rights, personality rights or similar rights that are mentioned, used or cited in the articles of the WikiDoc are the property of their respective owners. Their use here does not imply that you may use them for any other purpose other than for the same or a similar informational use as contemplated by the original authors of these WikiDoc articles under the GFDL licensing scheme. Unless otherwise stated WikiDoc and Wikimedia sites are neither endorsed nor affiliated with any of the holders of any such rights and as such WikiDoc can not grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.

13. COPYRIGHT INFRINGEMENT:

Should you as a user of the site post material that infringes upon another entities copyright, you are responsible. WikiDoc is not responsible for your negligence in posting copyrighted materials.

14. NOT PROFESSIONAL ADVICE:

If you need specific advice (for example, medical, legal, financial, or risk management) please seek a professional who is licensed or knowledgeable in that area.

'''Thank you for taking the time to read this page, and please enjoy your use of WikiDoc.'''

'''Examples of other encyclopedia disclaimers.''' While other encyclopedias, unlike WikiDoc, are professionally peer reviewed, they still do not guarantee their content.

The britannica.com disclaimer (from the site hosting the Encyclopædia Britannica online): "YOUR USE OF BRITANNICA.COM IS AT YOUR SOLE RISK." The MSN.com disclaimer (from the site hosting Microsoft's Encarta Encyclopedia) "...AND THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY, AND EFFORT IS WITH YOU." The bartleby.com disclaimer (from the site hosting the Columbia Encyclopedia) "YOU EXPRESSLY AGREE THAT USE OF THE SERVICE IS AT YOUR SOLE RISK."

'''Global attribution:''' The language describing WikiDoc throughout these pages is often borrowed and modified with global attribution to Wikipedia and with links to Wikipedia. This statement is a global attribution to wikipedia consistent with copyleft policies.

wikidoc:General disclaimer

2009-10-02T11:21:51Z

Levacher: formating

wikidoc:General disclaimer

2009-10-02T11:12:25Z

Levacher: formating

'''WikiDoc MAKES NO GUARANTEE OF VALIDITY.'''

'''WikiDoc is not a professional health care provider, nor is it a suitable replacement for a licensed healthcare provider.
'''

'''WikiDoc is intended to be an educational tool, not a tool for any form of healthcare delivery.
'''

'''WikiDoc does not promote the dissemination of copyrighted material or plagiarism. Do not post copyrighted material. You as the submitter of material are responsible for any copyright violation'''.

'''WikiDoc encourages you to contact us [mailto:mgibson@wikidoc.org] if you have identified any potential copyright violation or any content that might be considered to constitute plagiarism so that we may resolve the issue.'''

Below is our statement regarding liability, limitations, warranty, validity, guarantee, negligence, responsibility, damages, product liability, errors, omissions, indemnification, legal action, and contract (or lack thereof of any of the above).

WikiDoc is an online open-content collaborative medical encyclopedia / textbook and news servie, that is a voluntary association of individuals and groups who are developing a common resource of human medical knowledge. The structure of the project allows anyone with an Internet connection and World Wide Web browser to alter its content. Please be advised that nothing found here has necessarily been reviewed by professionals with the expertise required to provide you with complete, accurate or reliable Healthcare information. WikiDoc is not a substitute for a licensed health care professional. WikiDoc is not intended to guide medical decision making, but is instead intended as an educational tool.

That is not to say that you will not find valuable and accurate educational information in WikiDoc; some of the time you will. However, WikiDoc cannot guarantee the validity of the information found here. The content of any given article may recently have been changed, vandalized or altered by someone whose opinion does not correspond with the consensus in the medical field in your country, state, or city.

You can download these articles and present the information contained in the articles. In doing so, you agree to the following terms of use. While the website strives to have the most up to date and accurate data, you agree to consult published medical literature or the package insert for official trial results, dosing information or instructions for use of pharmaceutical products and devices. Off label use of drugs and devices is not encouraged. Articles of a forward looking investigational nature may present data to support the rationale for the use of a variety of pharmacologic agents and devices in both approved and non-approved indications. Actual prescribing information is by intent minimal or completely lacking. These articles has been prepared for scientific educational purposes, and cannot be considered an inducement to use any drug or device in non-registered indications. The site does not recommend the use of any drug or device in any manner inconsistent with that described in the full prescribing information.

In entering the download section, you assume responsibility for the accuracy of the information and its utilization. In entering WikiDoc, you agree to hold the website free of responsibility and/or liability for potential damages or injury to persons or property as a matter of products liability, negligence, copyright infringement or otherwise from any use or operation of any methods, products, instructions or ideas contained in the material herein.

The views expressed in the articles are those of the individuals who contributed the materials and do not necessarily reflect the views of the editorial staff or the founding organization. Inclusion of materials in articles does not constitute a guarantee or endorsement of the organization of the quality or the value of the product or the claim made by the author or any manufacturer. Statements contained herein are those of the person who posted the material.

The website is a free educational service to the healthcare community. All articles on this server are made public by the author(s) who created the articles. The articles are public domain and may be downloaded and used freely for personal, research, scientific, and / or information purposes so long as you credit WikiDoc as the source of the material.

1. LINKS TO THIRD PARTY SITES:

The Editors and their agents, and the contributors to the website may provide, or third parties may provide, links to other World Wide Web sites or resources. The Editors and their agents, and the contributors to the website do not endorse and are not responsible for any data, software or other content available from such sites or resources and you acknowledge and agree that they shall not be liable, directly or indirectly, for any damage or loss relating to your use of or reliance on such data, software or other content.

2. WARRANTY LIMITATIONS:

2.1. You understand and agree that the website is provided on an "AS IS" and “AS AVAILABLE” basis, without warranties of any kind, either express or implied, including, but not limited to, warranties of title, or implied warranties of merchantability or fitness for a particular purpose.

2.2. The use of information on the website is at your own risk.

2.3. Access to the website may be interrupted at any time for any reason to any individual(s) and may not be error free.

2.4. Neither the website, nor anyone else involved in creating, producing or delivering the website or the materials contained therein, shall be liable for any direct, indirect, incidental, special, consequential or punitive damages arising out of your use or inability to use the website. You understand and agree that any material or data obtained through use of the website is at your own discretion and risk and that you will be solely responsible for any resulting damage to your computer system or loss of data.

3. SUPPORT:

Neither the Editors and their agents, nor the contributors to the website shall have any obligation to provide you with any maintenance or support relating the website.
4. DISCLAIMER:

In view of the possibility of human error by the authors, editors, or publishers of the works contained in the website, neither the website, nor any other party involved in the preparation of this work, warrants that the information contained herein is in every respect accurate or complete, and they are not responsible for any errors or omissions or for the results obtained from the use of such. Readers are encouraged to confirm the information contained herein with other sources. Patients and consumers reading articles posted on the website should review the information carefully with their professional healthcare provider. The information is not intended to replace medical advice offered by physicians. The website makes no representations or warranties with respect to any treatment, action, or application of medication or preparation by any person following the information offered or provided within or through the website. The website is not be liable for any direct, indirect, consequential, special, exemplary, or other damages arising there from.

5. NOTICE:

The Editors and their agents, and the contributors to the website are not responsible for errors or omissions or for any consequences from application of the information herein and make no warranty, expressed or implied, with respect to the currency, completeness, or accuracy of the contents of the publication or any of the Services. Application of this information in a particular situation remains the professional responsibility of the practitioner.

Some information on drugs and medical devices presented in this website may be investigational and/or approved for limited use. It is the responsibility of health care providers to ascertain the status of each drug or device planned for use in their clinical practice.

6. INDEMNIFICATION:

You agree to hold harmless and indemnify the website, the Editors and their agents, and the contributors to the website, against any liability for any claims and expenses, including reasonable attorney's fees, relating to any violation of the terms of this Agreement or arising out of any material submitted by or used by you.
7. LINKING TO THE WEBSITE:

You may have a simple link from your website to ours. However, you must first ask our permission if you intend to frame our site or incorporate pieces of it into a different site or product in a way that is not clear to our users. You acknowledge and agree not to link to us if you engage in illegal, obscene, or offensive content, or if the link in any way has a negative impact on our reputation.

8. Information that You Put on WikiDoc

When you place materials or information on the website that are available publicly, you give us an irrevocable, perpetual license to use that information. For example, we have the right to display a comment that you post on one of our discussion boards for as long as we want. We will consider requests to remove information that you make publicly available on our Web sites on an individual basis.

We ask that you not post any messages with misleading, false, or inappropriate language or statements. We reserve the right to remove any offensive or fraudulent content at any time without your consent.

9. GOVERNING LAW; JURISDICTION; STATUTE OF LIMITATIONS:

This agreement shall be governed by the laws of the state of Massachusetts applicable to agreements wholly made and performed in Massachusetts. In the event that you believe you have been irreparably harmed by any cause of action relating to the website, you agree to inform the website in writing and grant the website thirty (30) days to cure the harm before initiating any action. Any legal action, suit or proceeding arising out of or relating to this agreement or a breach thereof, shall be instituted in a court of competent jurisdiction in Boston MA, and you hereby consent and submit to personal jurisdiction of such court, waive any objection to venue in such court and consent to service of process by overnight courier or express mail at your last known address. Any cause of action initiated by you must be initiated within 6 months after the claim or cause of action has arisen or be barred. Publication of information found in WikiDoc may be in violation of the laws of the country or jurisdiction from where you are viewing this information. The WikiDoc database is stored on a server in the United States of America, and is maintained in reference to the protections afforded under local and federal law. Laws in your country or jurisdiction may not protect or allow the same kinds of speech or distribution. WikiDoc does not encourage the violation of any laws; and cannot be responsible for any violations of such laws, should you link to this domain or use, reproduce, or republish the information contained herein. All correspondence should be addressed in writing to Susan Marble, Managing editor, 350 Longwood Avenue, Boston MA 02115.

10. No formal peer review. We are working on ways to select and highlight reliable versions of articles. Our active community of editors uses tools such as the recent changes tool to monitor new and changing content. However, WikiDoc is not uniformly peer reviewed; while readers may correct errors or engage in casual peer review, they have no legal duty to do so and thus all information read here is without any implied warranty of fitness for any purpose or use whatsoever. Even articles that have been vetted by informal peer review or featured article processes may later have been edited inappropriately, just before you view them.

None of the authors, contributors, sponsors, administrators, sysops, or anyone else connected with WikiDoc in any way whatsoever can be responsible for the appearance of any inaccurate or libelous information or for your use of the information contained in or linked from these web pages.

11. No contract; limited license. Please make sure that you understand that the information provided here is being provided freely, and that no kind of agreement or contract is created between you and the owners or users of this site, the owners of the servers upon which it is housed, the individual WikiDoc contributors, any project administrators, sysops or anyone else who is in any way connected with this project or sister projects subject to your claims against them directly. You are being granted a limited license to copy anything from this site; it does not create or imply any contractual or extracontractual liability on the part of WikiDoc or any of its agents, members, organizers or other users.

There is no agreement or understanding between you and WikiDdoc regarding your use or modification of this information beyond the GNU Free Documentation License (GFDL); neither is anyone at WikiDoc responsible should someone change, edit, modify or remove any information that you may post on WikiDoc or any of its associated projects.

12. Trademarks Any of the trademarks, service marks, collective marks, design rights, personality rights or similar rights that are mentioned, used or cited in the articles of the WikiDoc are the property of their respective owners. Their use here does not imply that you may use them for any other purpose other than for the same or a similar informational use as contemplated by the original authors of these WikiDoc articles under the GFDL licensing scheme. Unless otherwise stated WikiDoc and Wikimedia sites are neither endorsed nor affiliated with any of the holders of any such rights and as such WikiDoc can not grant any rights to use any otherwise protected materials. Your use of any such or similar incorporeal property is at your own risk.

13. Copyright infringement

Should you as a user of the site post material that infringes upon another entities copyright, you are responsible. WikiDoc is not responsible for your negligence in posting copyrighted materials.

15. Not professional advice. If you need specific advice (for example, medical, legal, financial, or risk management) please seek a professional who is licensed or knowledgeable in that area.

Thank you for taking the time to read this page, and please enjoy your use of WikiDoc.

Examples of other encyclopedia disclaimers. While other encyclopedias, unlike WikiDoc, are professionally peer reviewed, they still do not guarantee their content.

The britannica.com disclaimer (from the site hosting the Encyclopædia Britannica online): "YOUR USE OF BRITANNICA.COM IS AT YOUR SOLE RISK." The MSN.com disclaimer (from the site hosting Microsoft's Encarta Encyclopedia) "...AND THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFORMANCE, ACCURACY, AND EFFORT IS WITH YOU." The bartleby.com disclaimer (from the site hosting the Columbia Encyclopedia) "YOU EXPRESSLY AGREE THAT USE OF THE SERVICE IS AT YOUR SOLE RISK."

Global attribution: The language describing WikiDoc throughout these pages is often borrowed and modified with global attribution to Wikipedia and with links to Wikipedia. This statement is a global attribution to wikipedia consistent with copyleft policies.

User talk:C Michael Gibson

2009-09-30T18:36:53Z

Levacher: /* Wikipedia */

Hi Dr Gibson; I have collected a lot of DICOM based videos (majority of them are complications) from our archieve. How I can make all those videos free of private infos to add?

You can crop the images to that the identifying information is gone or you can put a black box over the information (make sure the black box cannot be removed.)

Hello Michael,
I hope the contributions from wikisurgery are ok.

I have put in more links today, covering toe amputation, anal fissure, anal fistula and anterior resection of rectum with total mesorectal excision.

Some are added to wikidoc pages, some are new wikidocpages. Have I put them in correctly?

Are you happy with them?

I can put in more (50 operation scripts plus patient information)if you like the idea.

Michael
michaeledwardsok@btinternet.com

Dear Michael,

Thank you for your additions! They look great! Please add more.

Mike

==Wikipedia==

I am curious why you guys didn't join wikipedia? It seems this is sort of the same concept and much of the data is just copied and passed from there with out the reference base. Have added a lot to the page on obesity over the last few month if you want to update yours.

I must say these pages are a mess. There are still half functioning tags left over from wikipedia. Some of the refs have been copied over and other have not. It is under the same copy right as wikipedia so why reinvent the wheel?

Cheers --[[User:Jmh649|Jmh649]] 19:59, 28 January 2009 (UTC)

Thank you for your comments. We are building pages that are geared more towards medical professionals rather than laypeople. Cardiology, signs and symptoms pages are greatly expanded / different from Wikipedia. Our differential diagnoses are greatly expanded compared to Wikipedia. We are now inviting clinicians from around the world to help improve and modify the other clinical pages as well. We have many more pathology images, clinical exam images than Wikipedia. We also have different and expanded search tools on the right hand side and the bottom. We have an Amazon like function on the left hand side that lets viewers see what other people viewed before coming to the present page and after the current page. We are adding board review software as well. We have daily news that we email to over 14,000 people. So all in all the audience is different and the depth will in time continue to grow and diverge from that of Wikipedia. I think there is a place for both. Thanks for sharing re the obesity pages! Mike

::Interesting. I guess everything on both is freely usable by either party? Sounds like this is an open version of Uptodate? There is tough competition. --[[User:Jmh649|Jmh649]] 15:07, 30 January 2009 (UTC)

::Yes, consisten with the principles of copyleft all of the content should be freely usable by either. We would be delighted for wikipedia editors to take content, as long as there is attribution. Yes, this is meant to be an open, participatory, free version of something like "Up to Date". Making this type of information freely available and widely distributable is the right thing to do, particularly for health care systems that have fewer resources. Glad to work towards coordinating our efforts for a common good. We would be hard to compete with! There is little competition in the space of credible information that is not funded by drug companies.

::::Agree. There are a few pages you might want to update including [[Obesity]] and [[ADHD]].--Jmh649 [[Special:Contributions/70.64.215.117|70.64.215.117]] 16:31, 28 February 2009 (UTC)

Great!. Will do.

==Wikipedia==
Hey Mike

Will look into things. I guess one of the questions is what sort of combination should take place. I like the fact that this is more health care oriented and has more safe guards against vandalism. Wikipedia of course has all the manuals on how to edit and on what sort of grammar and referencing should be used and of course has a huge audience.--[[User:Jmh649|Jmh649]] 15:38, 7 April 2009 (UTC)

sounds great. We have been targeting docs and nurses, but it would be great to reach a broader audience. Our volume continues to grow where we now have about 25,000 to 35,000 page views each day. We have news. We have a physician coming from China to help launch the Chinese site.[[User:C Michael Gibson|Chief WikiDoc]] 17:57, 7 April 2009 (UTC)

::What sort of arrangement would you be wanting? --[[User:Jmh649|Jmh649]] 16:56, 14 April 2009 (UTC)
A sister project I believe sounds like the right kind of arrangement. Why dont you give me a call at my office at 617-632-7753 and we can chat off line.

:::I am bringing up the discussion again. The first thing that is required however is that both projects keep the same license. Are you able to change your license to Creative Commons Attribution/Share-Alike License?--[[User:Jmh649|Jmh649]] 17:55, 18 July 2009 (UTC)

yes we have adopted the same license as wikipedia. The logo has not been chnaged yet, but yes, we have adapted the same version.

Mike

::BTW Have started a discussion of collaboration at the medicine project page of wikipedia. http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Medicine#Collaboration --[[User:Jmh649|Jmh649]] 13:58, 20 July 2009 (UTC)

== Wikipedia ==

Hello Mike! 
As you know, I opened the French version of WikiDoc. I have already translated numerous articles regarding the manual of the wiki. This has been very useful to better understand how it works. I have now to seek contributors to develop articles specifically dedicated to medicine. I am very interested in all forms of medical encyclopedia project and I appreciate the opportunity to work with your team. Also, I would like to know your current position with respect to Wikipedia. It seems that the "Projet:Médecine" of Wikipedia'''.fr''' is not so developed as the English one! Are you considering a partnership between Wikipedia and WikiDoc? Best regards [[User:Levacher|Maryse LEVACHER]] 10:28, 30 September 2009 (UTC)

==[[Clinical officer]]==
Hi doc. I have started some work on the article above. It is quite different from the initial article on wikipedia. What do you think?

Great job! Thank you for your hard work.
Mike

==[[Assistant Medical Officer]]==
Hi doc. Would like to take over this article as well[[User:Ronns|Ronns]] 06:55, 3 June 2009 (UTC)

Sounds good.

==Imaging Questions==
When performing coronary imaging, are drugs administered that elicit coronary chemo-reflexes such as constriction and dilation of the vessels? If yes, what are the drugs and standard procedures for measuring vessel diameter change, and if no, why not? Patient coronary reflex parameters would be useful to know in patients that are suffering from angina but do not have obstruction, such as patients that have myocardial bridging or idiopathic angina and tachycardia.[[User:Jiwhit01|Jiwhit01]] 16:00, 25 July 2009 (UTC)

Yes, you can see what I have written about this in the chapter on [[Intracoronary Pharmacotherapy]]

User talk:C Michael Gibson

2009-09-30T10:30:27Z

Levacher: /* Wikipedia */

Hi Dr Gibson; I have collected a lot of DICOM based videos (majority of them are complications) from our archieve. How I can make all those videos free of private infos to add?

You can crop the images to that the identifying information is gone or you can put a black box over the information (make sure the black box cannot be removed.)

Hello Michael,
I hope the contributions from wikisurgery are ok.

I have put in more links today, covering toe amputation, anal fissure, anal fistula and anterior resection of rectum with total mesorectal excision.

Some are added to wikidoc pages, some are new wikidocpages. Have I put them in correctly?

Are you happy with them?

I can put in more (50 operation scripts plus patient information)if you like the idea.

Michael
michaeledwardsok@btinternet.com

Dear Michael,

Thank you for your additions! They look great! Please add more.

Mike

==Wikipedia==

I am curious why you guys didn't join wikipedia? It seems this is sort of the same concept and much of the data is just copied and passed from there with out the reference base. Have added a lot to the page on obesity over the last few month if you want to update yours.

I must say these pages are a mess. There are still half functioning tags left over from wikipedia. Some of the refs have been copied over and other have not. It is under the same copy right as wikipedia so why reinvent the wheel?

Cheers --[[User:Jmh649|Jmh649]] 19:59, 28 January 2009 (UTC)

Thank you for your comments. We are building pages that are geared more towards medical professionals rather than laypeople. Cardiology, signs and symptoms pages are greatly expanded / different from Wikipedia. Our differential diagnoses are greatly expanded compared to Wikipedia. We are now inviting clinicians from around the world to help improve and modify the other clinical pages as well. We have many more pathology images, clinical exam images than Wikipedia. We also have different and expanded search tools on the right hand side and the bottom. We have an Amazon like function on the left hand side that lets viewers see what other people viewed before coming to the present page and after the current page. We are adding board review software as well. We have daily news that we email to over 14,000 people. So all in all the audience is different and the depth will in time continue to grow and diverge from that of Wikipedia. I think there is a place for both. Thanks for sharing re the obesity pages! Mike

::Interesting. I guess everything on both is freely usable by either party? Sounds like this is an open version of Uptodate? There is tough competition. --[[User:Jmh649|Jmh649]] 15:07, 30 January 2009 (UTC)

::Yes, consisten with the principles of copyleft all of the content should be freely usable by either. We would be delighted for wikipedia editors to take content, as long as there is attribution. Yes, this is meant to be an open, participatory, free version of something like "Up to Date". Making this type of information freely available and widely distributable is the right thing to do, particularly for health care systems that have fewer resources. Glad to work towards coordinating our efforts for a common good. We would be hard to compete with! There is little competition in the space of credible information that is not funded by drug companies.

::::Agree. There are a few pages you might want to update including [[Obesity]] and [[ADHD]].--Jmh649 [[Special:Contributions/70.64.215.117|70.64.215.117]] 16:31, 28 February 2009 (UTC)

Great!. Will do.

==Wikipedia==
Hey Mike

Will look into things. I guess one of the questions is what sort of combination should take place. I like the fact that this is more health care oriented and has more safe guards against vandalism. Wikipedia of course has all the manuals on how to edit and on what sort of grammar and referencing should be used and of course has a huge audience.--[[User:Jmh649|Jmh649]] 15:38, 7 April 2009 (UTC)

sounds great. We have been targeting docs and nurses, but it would be great to reach a broader audience. Our volume continues to grow where we now have about 25,000 to 35,000 page views each day. We have news. We have a physician coming from China to help launch the Chinese site.[[User:C Michael Gibson|Chief WikiDoc]] 17:57, 7 April 2009 (UTC)

::What sort of arrangement would you be wanting? --[[User:Jmh649|Jmh649]] 16:56, 14 April 2009 (UTC)
A sister project I believe sounds like the right kind of arrangement. Why dont you give me a call at my office at 617-632-7753 and we can chat off line.

:::I am bringing up the discussion again. The first thing that is required however is that both projects keep the same license. Are you able to change your license to Creative Commons Attribution/Share-Alike License?--[[User:Jmh649|Jmh649]] 17:55, 18 July 2009 (UTC)

yes we have adopted the same license as wikipedia. The logo has not been chnaged yet, but yes, we have adapted the same version.

Mike

::BTW Have started a discussion of collaboration at the medicine project page of wikipedia. http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Medicine#Collaboration --[[User:Jmh649|Jmh649]] 13:58, 20 July 2009 (UTC)

::Hello Mike!
::As you know, I opened the French version of WikiDoc. I have already translated numerous articles regarding the manual of the wiki. This has been very useful to know how it works. I have now to seek out contributors to develop articles specifically dedicated to medicine. I am very interested in all forms of medical encyclopedia project and I appreciate the opportunity to work with your team. Also, I would like to know your current position with respect to Wikipedia. It seems that the "Projet:Médecine" of Wikipedia'''.fr''' is not so developed as in English? Are you considering a partnership between Wikipedia and WikiDoc? Best regards [[User:Levacher|Maryse LEVACHER]] 10:28, 30 September 2009 (UTC)

==[[Clinical officer]]==
Hi doc. I have started some work on the article above. It is quite different from the initial article on wikipedia. What do you think?

Great job! Thank you for your hard work.
Mike

==[[Assistant Medical Officer]]==
Hi doc. Would like to take over this article as well[[User:Ronns|Ronns]] 06:55, 3 June 2009 (UTC)

Sounds good.

==Imaging Questions==
When performing coronary imaging, are drugs administered that elicit coronary chemo-reflexes such as constriction and dilation of the vessels? If yes, what are the drugs and standard procedures for measuring vessel diameter change, and if no, why not? Patient coronary reflex parameters would be useful to know in patients that are suffering from angina but do not have obstruction, such as patients that have myocardial bridging or idiopathic angina and tachycardia.[[User:Jiwhit01|Jiwhit01]] 16:00, 25 July 2009 (UTC)

Yes, you can see what I have written about this in the chapter on [[Intracoronary Pharmacotherapy]]

User talk:C Michael Gibson

2009-09-30T10:28:16Z

Levacher: /* Wikipedia */ french project

Hi Dr Gibson; I have collected a lot of DICOM based videos (majority of them are complications) from our archieve. How I can make all those videos free of private infos to add?

You can crop the images to that the identifying information is gone or you can put a black box over the information (make sure the black box cannot be removed.)

Hello Michael,
I hope the contributions from wikisurgery are ok.

I have put in more links today, covering toe amputation, anal fissure, anal fistula and anterior resection of rectum with total mesorectal excision.

Some are added to wikidoc pages, some are new wikidocpages. Have I put them in correctly?

Are you happy with them?

I can put in more (50 operation scripts plus patient information)if you like the idea.

Michael
michaeledwardsok@btinternet.com

Dear Michael,

Thank you for your additions! They look great! Please add more.

Mike

==Wikipedia==

I am curious why you guys didn't join wikipedia? It seems this is sort of the same concept and much of the data is just copied and passed from there with out the reference base. Have added a lot to the page on obesity over the last few month if you want to update yours.

I must say these pages are a mess. There are still half functioning tags left over from wikipedia. Some of the refs have been copied over and other have not. It is under the same copy right as wikipedia so why reinvent the wheel?

Cheers --[[User:Jmh649|Jmh649]] 19:59, 28 January 2009 (UTC)

Thank you for your comments. We are building pages that are geared more towards medical professionals rather than laypeople. Cardiology, signs and symptoms pages are greatly expanded / different from Wikipedia. Our differential diagnoses are greatly expanded compared to Wikipedia. We are now inviting clinicians from around the world to help improve and modify the other clinical pages as well. We have many more pathology images, clinical exam images than Wikipedia. We also have different and expanded search tools on the right hand side and the bottom. We have an Amazon like function on the left hand side that lets viewers see what other people viewed before coming to the present page and after the current page. We are adding board review software as well. We have daily news that we email to over 14,000 people. So all in all the audience is different and the depth will in time continue to grow and diverge from that of Wikipedia. I think there is a place for both. Thanks for sharing re the obesity pages! Mike

::Interesting. I guess everything on both is freely usable by either party? Sounds like this is an open version of Uptodate? There is tough competition. --[[User:Jmh649|Jmh649]] 15:07, 30 January 2009 (UTC)

::Yes, consisten with the principles of copyleft all of the content should be freely usable by either. We would be delighted for wikipedia editors to take content, as long as there is attribution. Yes, this is meant to be an open, participatory, free version of something like "Up to Date". Making this type of information freely available and widely distributable is the right thing to do, particularly for health care systems that have fewer resources. Glad to work towards coordinating our efforts for a common good. We would be hard to compete with! There is little competition in the space of credible information that is not funded by drug companies.

::::Agree. There are a few pages you might want to update including [[Obesity]] and [[ADHD]].--Jmh649 [[Special:Contributions/70.64.215.117|70.64.215.117]] 16:31, 28 February 2009 (UTC)

Great!. Will do.

==Wikipedia==
Hey Mike

Will look into things. I guess one of the questions is what sort of combination should take place. I like the fact that this is more health care oriented and has more safe guards against vandalism. Wikipedia of course has all the manuals on how to edit and on what sort of grammar and referencing should be used and of course has a huge audience.--[[User:Jmh649|Jmh649]] 15:38, 7 April 2009 (UTC)

sounds great. We have been targeting docs and nurses, but it would be great to reach a broader audience. Our volume continues to grow where we now have about 25,000 to 35,000 page views each day. We have news. We have a physician coming from China to help launch the Chinese site.[[User:C Michael Gibson|Chief WikiDoc]] 17:57, 7 April 2009 (UTC)

::What sort of arrangement would you be wanting? --[[User:Jmh649|Jmh649]] 16:56, 14 April 2009 (UTC)
A sister project I believe sounds like the right kind of arrangement. Why dont you give me a call at my office at 617-632-7753 and we can chat off line.

:::I am bringing up the discussion again. The first thing that is required however is that both projects keep the same license. Are you able to change your license to Creative Commons Attribution/Share-Alike License?--[[User:Jmh649|Jmh649]] 17:55, 18 July 2009 (UTC)

yes we have adopted the same license as wikipedia. The logo has not been chnaged yet, but yes, we have adapted the same version.

Mike

::BTW Have started a discussion of collaboration at the medicine project page of wikipedia. http://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Medicine#Collaboration --[[User:Jmh649|Jmh649]] 13:58, 20 July 2009 (UTC)

::Hello Mike!
As you know, I opened the French version of WikiDoc. I have already translated numerous articles regarding the manual of the wiki. This has been very useful to know how it works. I have now to seek out contributors to develop articles specifically dedicated to medicine. I am very interested in all forms of medical encyclopedia project and I appreciate the opportunity to work with your team. Also, I would like to know your current position with respect to Wikipedia. It seems that the "Projet:Médecine" of Wikipedia'''.fr''' is not so developed as in English? Are you considering a partnership between Wikipedia and WikiDoc? Best regards [[User:Levacher|Maryse LEVACHER]] 10:28, 30 September 2009 (UTC)

==[[Clinical officer]]==
Hi doc. I have started some work on the article above. It is quite different from the initial article on wikipedia. What do you think?

Great job! Thank you for your hard work.
Mike

==[[Assistant Medical Officer]]==
Hi doc. Would like to take over this article as well[[User:Ronns|Ronns]] 06:55, 3 June 2009 (UTC)

Sounds good.

==Imaging Questions==
When performing coronary imaging, are drugs administered that elicit coronary chemo-reflexes such as constriction and dilation of the vessels? If yes, what are the drugs and standard procedures for measuring vessel diameter change, and if no, why not? Patient coronary reflex parameters would be useful to know in patients that are suffering from angina but do not have obstruction, such as patients that have myocardial bridging or idiopathic angina and tachycardia.[[User:Jiwhit01|Jiwhit01]] 16:00, 25 July 2009 (UTC)

Yes, you can see what I have written about this in the chapter on [[Intracoronary Pharmacotherapy]]

User:Levacher

2009-09-16T10:33:20Z

Levacher:

'''Docteur Maryse LEVACHER is Managing Editor of the French Language WikiDoc'''

Maître de Conférence des Universités - Praticien Hospitalier 
Pharmacology 
Faculté de Médecine - Université Paris Descartes 
Paris FRANCE 

'''Contact:''' [mailto:maryse.levacher@cch.aphp.fr maryse.levacher@cch.aphp.fr] 

'''Address:''' 
Service de Pharmacologie 
Groupe Hospitalier Cochin-Saint-Vincent de Paul 
75014 Paris 
FRANCE 

[[Category:Pharmacologists]]
[[fr:Utilisateur:Levacher]]

User:Levacher

2009-09-16T10:24:01Z

Levacher: New page: '''Docteur Maryse LEVACHER is Managing Editor of the French Language WikiDoc''' Maître de Conférence des Universités - Praticien Hospitalier Pharmacology Faculté de Médecine ...

Edit summaries

2009-07-01T21:21:57Z

Levacher: category

When [[Help:editing|editing]] an article, there is a small field labeled "Summary" under the main edit-box. It looks like this:

[[Image:Summary_Box.png]]

It is highly recommended that you fill in the edit summary field, as it makes it easier for you and your fellow contributors to understand what was changed on the page, and it can be quite helpful in identifying when a specific change was made to the page.

==Places where the edit summary appears==

The edit summary appears in black italics in the following places:

*[[Help:Page history|Page history]] - list of changes to the page you edited
*[[Help:User contributions|User contributions]] - list of all your edits
*[[Help:Watching pages|Watchlist]]'''<nowiki>*</nowiki>''' - list of recent changes to watched pages ([[Help:Logging in|logged-in]] users only)
*[[Help:Diff|diff page]] - shows the difference between two edits
*[[Help:Recent changes|Recent changes]]'''<nowiki>*</nowiki>''' - list of all recent edits
*[[Help:Related changes|Related changes]]'''<nowiki>*</nowiki>''' - list of recent changes to pages linked to the page you edited

'''<nowiki>*</nowiki>''' These show the edit summary of the last edit. Since one is typically interested in all recent changes in these articles, with all edit summaries, these features are used in conjunction with the page histories of the articles shown.

==Searching==

The [[Help:Searching|search function]] can not search edit summaries, and they are not indexed by external search engines.

==File upload summary==

When uploading an image one can supply an upload summary. This serves multiple purposes:
*as second part of the automatically created edit summary of the upload log (the first part giving the file name)
*as text in the entry of the [[Help:Page history#Image_history|image history]]
*in the case that the file name of the image is new:
**as edit summary for the creation of the image page
**as wikitext for the editable part of the image page, which includes the following possibilities:
***briefly describe the image
***provide internal or external links
***call templates
***specify one or more categories the image is in

The capacity of the upload summary is one line of 250 characters; in the upload log the last part may fall off, because this can contain 255 characters, including "uploaded "''filename''"".

Note that there is no preview function to check the code for the links, template calls and category tags, but of course, if needed one can edit the image page after uploading, to correct errors and also to extend the text.

See also [[Help:Image page]].

==Section title as automatic edit summary==

When applying the [[Help:Section#Section editing|section editing]] feature the section title is automatically inserted as initial version or first part of the edit summary. Put more details after this text. In the case that you provide a long summary yourself you can delete the section title in order to stay within the limit of 200 characters.

=="Post a comment" feature==

When starting a new thread on a Talk page, optionally the "Post a comment" feature can be used (the "+" tab next to the edit tab. Then the edit summary is automatically the same as the new section header.

==Rendering of wikitext; URLs==

Text in edit summaries renders internal links, including [[Help:Links#Internal_Links|piped link]]s, even when enclosed within <nowiki><nowiki> and </nowiki></nowiki>. Therefore, copying wikitext in the edit summary box may be preferable to copying text from the preview, except when one wants to save space.

Other wikitext coding is not interpreted.

When copying an external link from the preview into the edit summary box then, depending on the operating system, the
"printable version" is copied, i.e. how it is normally rendered, and in addition, between parentheses, the URL; hence the same information as in the wikitext, but in a different format, and in addition the possible sequential number.

{{WikiDoc Acknowledgement}}
{{Help Menu}}
[[Category:Help|Summaries]]

Help talk:Create a New Page

2009-06-24T10:27:16Z

Levacher: New page: This content is already edited in Help:Creating Pages, it seems somewhat redundant - ~~~~

This content is already edited in [[Help:Creating Pages]], it seems somewhat redundant - [[User:Levacher|Maryse LEVACHER]] 10:27, 24 June 2009 (UTC)

Web colors

2009-06-18T08:48:26Z

Levacher: /* Understanding WebSafe Colors: The Color Palette Used on WikiDoc: */

{{CMG}}
__NOTOC__
{{Editor Help}}

Here are some colors that you should be able to reference directly by Color Name, rather than having to put in an obscure Hexacode.

==Understanding WebSafe Colors: The Color Palette Used on WikiDoc:==

A number of colors are defined by web browsers such as Internet Explorer or Mozilla Firefox. A particular browser may not recognize all of these colors, but as of 2005 all modern general-use browsers support the full list. Many of these colors are from the list of X11 color names distributed with the X Window System. ... The complete list of web X11 colors from the CSS3 specification, along with their hexadecimal equivalents, are listed below. For an alphabetical list and the original reference, see http://www.w3.org/TR/2001/WD-css3-color-20010305#x11-color. However, according to [http://www.w3schools.com/css/css_colornames.asp w3schools.com], there are only 16 color names supported by the W3C - aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow - and you should use the hexadecimal color values for anything else.

Why this Table has been copied from Wikipedia: '''All of these color words should be safe to use on the {{SITENAME}}.''' If one of these colors does not appear (the colorbox looks white instead of colored), please STRIKETHROUGH the color name and write "broken" in the colorbox, as shown in the first example in the Table. Thanks!

{|border="0" cellpadding="0" cellspacing="2"
!style="background:lightgrey;"|Name!!colspan="3" style="background:lightgrey;"|Hexcode!!width="60%" style="background:lightgrey;"|What It Looks Like
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Non-working colors'''</big>
|-
|<s>TychoFuturesGreen</s> ||61||A7||B1||style="background:tychofuturesgreen;"| (example of a broken color)
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Red colors'''</big>
|-
|IndianRed ||CD||5C||5C||style="background:indianred;"| 
|-
|LightCoral ||F0||80||80||style="background:lightcoral;"| 
|-
|Salmon||FA||80||72||style="background:salmon;"| 
|-
|DarkSalmon ||E9||96||7A||style="background:darksalmon;"| 
|-
|LightSalmon ||FF||A0||7A||style="background:lightsalmon;"| 
|-
|Red ||FF||00||00||style="background:red;"| 
|-
|Crimson ||DC||14||3C||style="background:crimson;"| 
|-
|FireBrick ||B2||22||22||style="background:firebrick;"| 
|-
|DarkRed ||8B||00||00||style="background:darkred;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Pink colors'''</big>
|-
|Pink ||FF||C0||CB||style="background:pink;"| 
|-
|LightPink ||FF||B6||C1||style="background:lightpink;"| 
|-
|PaleVioletRed ||DB||70||93||style="background:palevioletred;"| 
|-
|HotPink ||FF||69||B4||style="background:hotpink;"| 
|-
|DeepPink ||FF||14||93||style="background:deeppink;"| 
|-
|MediumVioletRed||C7||15||85||style="background:mediumvioletred;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Orange colors'''</big>
|-
||LightSalmon ||FF||A0||7A||style="background:lightsalmon;"| 
|-
|Orange ||FF||A5||00||style="background:orange;"| 
|-
|DarkOrange ||FF||8C||00||style="background:darkorange;"| 
|-
|Coral ||FF||7F||50||style="background:coral;"| 
|-
|Tomato ||FF||63||47||style="background:tomato;"| 
|-
|OrangeRed ||FF||45||00||style="background:orangered;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Yellow colors'''</big>
|-
|LightYellow ||FF||FF||E0||style="background:lightyellow;"| 
|-
|LemonChiffon ||FF||FA||CD||style="background:lemonchiffon;"| 
|-
|LightGoldenrodYellow||FA||FA||D2||style="background:lightgoldenrodyellow;"| 
|-
|PapayaWhip ||FF||EF||D5||style="background:papayawhip;"| 
|-
|Moccasin ||FF||E4||B5||style="background:moccasin;"| 
|-
|PeachPuff ||FF||DA||B9||style="background:peachpuff;"| 
|-
|PaleGoldenrod ||EE||E8||AA||style="background:palegoldenrod;"| 
|-
|Khaki ||F0||E6||8C||style="background:khaki;"| 
|-
|Yellow ||FF||FF||00||style="background:yellow;"| 
|-
|Gold ||FF||D7||00||style="background:gold;"| 
|-
|DarkKhaki ||BD||B7||6B||style="background:darkkhaki;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Green colors'''</big>
|-
|GreenYellow ||AD||FF||2F||style="background:greenyellow;"| 
|-
|Chartreuse ||7F||FF||00||style="background:chartreuse;"| 
|-
|LawnGreen ||7C||FC||00||style="background:lawngreen;"| 
|-
|Lime ||00||FF||00||style="background:lime;"| 
|-
|PaleGreen ||98||FB||98||style="background:palegreen;"| 
|-
|LightGreen ||90||EE||90||style="background:lightgreen;"| 
|-
|MediumSpringGreen||00||FA||9A||style="background:mediumspringgreen;"| 
|-
|SpringGreen ||00||FF||7F||style="background:springgreen;"| 
|-
|YellowGreen ||9A||CD||32||style="background:yellowgreen;"| 
|-
|LimeGreen ||32||CD||32||style="background:limegreen;"| 
|-
|MediumSeaGreen ||3C||B3||71||style="background:mediumseagreen;"| 
|-
|SeaGreen ||2E||8B||57||style="background:seagreen;"| 
|-
|ForestGreen ||22||8B||22||style="background:forestgreen;"| 
|-
|Green ||00||80||00||style="background:green;"| 
|-
|OliveDrab ||6B||8E||23||style="background:olivedrab;"| 
|-
|Olive ||80||80||00||style="background:olive;"| 
|-
|DarkOliveGreen ||55||6B||2F||style="background:darkolivegreen;"| 
|-
|DarkGreen ||00||64||00||style="background:darkgreen;"| 
|-
|MediumAquamarine||66||CD||AA||style="background:mediumaquamarine;"| 
|-
|DarkSeaGreen ||8F||BC||8F||style="background:darkseagreen;"| 
|-
|LightSeaGreen ||20||B2||AA||style="background:lightseagreen;"| 
|-
|DarkCyan ||00||8B||8B||style="background:darkcyan;"| 
|-
|Teal ||00||80||80||style="background:teal;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Blue colors'''</big>
|-
|Cyan ||00||FF||FF||style="background:cyan;"| 
|-
|LightCyan ||E0||FF||FF||style="background:lightcyan;"| 
|-
|PaleTurquoise ||AF||EE||EE||style="background:paleturquoise;"| 
|-
|Aqua ||00||FF||FF||style="background:aqua;"| 
|-
|Aquamarine ||7F||FF||D4||style="background:aquamarine;"| 
|-
|Turquoise ||40||E0||D0||style="background:turquoise;"| 
|-
|MediumTurquoise ||48||D1||CC||style="background:mediumturquoise;"| 
|-
|DarkTurquoise||00||CE||D1||style="background:darkturquoise;"| 
|-
|PowderBlue ||B0||E0||E6||style="background:powderblue;"| 
|-
|LightSteelBlue ||B0||C4||DE||style="background:lightsteelblue;"| 
|-
|LightBlue ||AD||D8||E6||style="background:lightblue;"| 
|-
|SkyBlue ||87||CE||EB||style="background:skyblue;"| 
|-
|LightSkyBlue||87||CE||FA||style="background:lightskyblue;"| 
|-
|DeepSkyBlue ||00||BF||FF||style="background:deepskyblue;"| 
|-
|CornflowerBlue||64||95||ED||style="background:cornflowerblue;"| 
|-
|SteelBlue ||46||82||B4||style="background:steelblue;"| 
|-
|CadetBlue ||5F||9E||A0||style="background:cadetblue;"| 
|-
|MediumSlateBlue||7B||68||EE||style="background:mediumslateblue;"| 
|-
|DodgerBlue ||1E||90||FF||style="background:dodgerblue;"| 
|-
|RoyalBlue ||41||69||E1||style="background:royalblue;"| 
|-
|Blue ||00||00||FF||style="background:blue;"| 
|-
|MediumBlue ||00||00||CD||style="background:mediumblue;"| 
|-
|DarkBlue ||00||00||8B||style="background:darkblue;"| 
|-
|Navy ||00||00||80||style="background:navy;"| 
|-
|MidnightBlue ||19||19||70||style="background:midnightblue;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Purple colors'''</big>
|-
|Lavender ||E6||E6||FA||style="background:lavender;"| 
|-
|Thistle ||D8||BF||D8||style="background:thistle;"| 
|-
|Plum ||DD||A0||DD||style="background:plum;"| 
|-
|Violet ||EE||82||EE||style="background:violet;"| 
|-
|Fuchsia ||FF||00||FF||style="background:fuchsia;"| 
|-
|Magenta||FF||00||FF||style="background:magenta;"| 
|-
|Orchid ||DA||70||D6||style="background:orchid;"| 
|-
|MediumOrchid ||BA||55||D3||style="background:mediumorchid;"| 
|-
|MediumPurple ||93||70||DB||style="background:mediumpurple;"| 
|-
|SlateBlue ||6A||5A||CD||style="background:slateblue;"| 
|-
|BlueViolet ||8A||2B||E2||style="background:blueviolet;"| 
|-
|DarkViolet ||94||00||D3||style="background:darkviolet;"| 
|-
|DarkOrchid ||99||32||CC||style="background:darkorchid;"| 
|-
|DarkMagenta ||8B||00||8B||style="background:darkmagenta;"| 
|-
|Purple ||80||00||80||style="background:purple;"| 
|-
|DarkSlateBlue ||48||3D||8B||style="background:darkslateblue;"| 
|-
|Indigo ||4B||00||82||style="background:indigo;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Brown colors'''</big>
|-
|Cornsilk ||FF||F8||DC||style="background:cornsilk;"| 
|-
|BlanchedAlmond ||FF||EB||CD||style="background:blanchedalmond;"| 
|-
|Bisque ||FF||E4||C4||style="background:bisque;"| 
|-
|NavajoWhite ||FF||DE||AD||style="background:navajowhite;"| 
|-
|Wheat ||F5||DE||B3||style="background:wheat;"| 
|-
|BurlyWood ||DE||B8||87||style="background:burlywood;"| 
|-
|Tan ||D2||B4||8C||style="background:tan;"| 
|-
|RosyBrown ||BC||8F||8F||style="background:rosybrown;"| 
|-
|SandyBrown ||F4||A4||60||style="background:sandybrown;"| 
|-
|Goldenrod ||DA||A5||20||style="background:goldenrod;"| 
|-
|DarkGoldenrod ||B8||86||0B||style="background:darkgoldenrod;"| 
|-
|Peru ||CD||85||3F||style="background:peru;"| 
|-
|Chocolate ||D2||69||1E||style="background:chocolate;"| 
|-
|SaddleBrown ||8B||45||13||style="background:saddlebrown;"| 
|-
|Sienna ||A0||52||2D||style="background:sienna;"| 
|-
|Brown ||A5||2A||2A||style="background:brown;"| 
|-
|Maroon ||80||00||00||style="background:maroon;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''White colors'''</big>
|-
|White ||FF||FF||FF||style="background:white;"| 
|-
|Snow ||FF||FA||FA||style="background:snow;"| 
|-
|Honeydew ||F0||FF||F0||style="background:honeydew;"| 
|-
|MintCream ||F5||FF||FA||style="background:mintcream;"| 
|-
|Azure ||F0||FF||FF||style="background:azure;"| 
|-
|AliceBlue ||F0||F8||FF||style="background:aliceblue;"| 
|-
|GhostWhite ||F8||F8||FF||style="background:ghostwhite;"| 
|-
|WhiteSmoke ||F5||F5||F5||style="background:whitesmoke;"| 
|-
|Seashell ||FF||F5||EE||style="background:seashell;"| 
|-
|Beige ||F5||F5||DC||style="background:beige;"| 
|-
|OldLace ||FD||F5||E6||style="background:oldlace;"| 
|-
|FloralWhite ||FF||FA||F0||style="background:floralwhite;"| 
|-
|Ivory ||FF||FF||F0||style="background:ivory;"| 
|-
|AntiqueWhite ||FA||EB||D7||style="background:antiquewhite;"| 
|-
|Linen ||FA||F0||E6||style="background:linen;"| 
|-
|LavenderBlush ||FF||F0||F5||style="background:lavenderblush;"| 
|-
|MistyRose ||FF||E4||E1||style="background:mistyrose;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Grey colors'''</big>
|-
|Gainsboro ||DC||DC||DC||style="background:gainsboro;"| 
|-
|LightGrey ||D3||D3||D3||style="background:lightgrey;"| 
|-
|Silver ||C0||C0||C0||style="background:silver;"| 
|-
|DarkGray ||A9||A9||A9||style="background:darkgray;"| 
|-
|Gray ||80||80||80||style="background:gray;"| 
|-
|DimGray ||69||69||69||style="background:dimgray;"| 
|-
|LightSlateGray ||77||88||99||style="background:lightslategray;"| 
|-
|SlateGray ||70||80||90||style="background:slategray;"| 
|-
|DarkSlateGray ||2F||4F||4F||style="background:darkslategray;"| 
|-
|Black ||00||00||00||style="background:black;"| 
|}
[[Category:Help]]

{{WikiDoc Help Menu}}
{{WS}}

Web colors

2009-06-18T08:39:58Z

Levacher: spelling "hexacode"

{{CMG}}
__NOTOC__
{{Editor Help}}

Here are some colors that you should be able to reference directly by Color Name, rather than having to put in an obscure Hexacode.

==Understanding WebSafe Colors: The Color Palette Used on WikiDoc:==

A number of colors are defined by web browsers such as Internet Explorer or Mozilla Firefox. A particular browser may not recognize all of these colors, but as of 2005 all modern general-use browsers support the full list. Many of these colors are from the list of X11 color names distributed with the X Window System. ... The complete list of web X11 colors from the CSS3 specification, along with their hexadecimal equivalents, are listed below. For an alphabetical list and the original reference, see http://www.w3.org/TR/2001/WD-css3-color-20010305#x11-color." However, according to [http://www.w3schools.com/css/css_colornames.asp w3schools.com], there are only 16 color names supported by the W3C - aqua, black, blue, fuchsia, gray, green, lime, maroon, navy, olive, purple, red, silver, teal, white, and yellow - and you should use the hexadecimal color values for anything else.

Why this Table has been copied from Wikipedia: '''All of these color words should be safe to use on the {{SITENAME}}.''' If one of these colors does not appear (the colorbox looks white instead of colored), please STRIKETHROUGH the color name and write "broken" in the colorbox, as shown in the first example in the Table. Thanks!

{|border="0" cellpadding="0" cellspacing="2"
!style="background:lightgrey;"|Name!!colspan="3" style="background:lightgrey;"|Hexcode!!width="60%" style="background:lightgrey;"|What It Looks Like
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Non-working colors'''</big>
|-
|<s>TychoFuturesGreen</s> ||61||A7||B1||style="background:tychofuturesgreen;"| (example of a broken color)
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Red colors'''</big>
|-
|IndianRed ||CD||5C||5C||style="background:indianred;"| 
|-
|LightCoral ||F0||80||80||style="background:lightcoral;"| 
|-
|Salmon||FA||80||72||style="background:salmon;"| 
|-
|DarkSalmon ||E9||96||7A||style="background:darksalmon;"| 
|-
|LightSalmon ||FF||A0||7A||style="background:lightsalmon;"| 
|-
|Red ||FF||00||00||style="background:red;"| 
|-
|Crimson ||DC||14||3C||style="background:crimson;"| 
|-
|FireBrick ||B2||22||22||style="background:firebrick;"| 
|-
|DarkRed ||8B||00||00||style="background:darkred;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Pink colors'''</big>
|-
|Pink ||FF||C0||CB||style="background:pink;"| 
|-
|LightPink ||FF||B6||C1||style="background:lightpink;"| 
|-
|PaleVioletRed ||DB||70||93||style="background:palevioletred;"| 
|-
|HotPink ||FF||69||B4||style="background:hotpink;"| 
|-
|DeepPink ||FF||14||93||style="background:deeppink;"| 
|-
|MediumVioletRed||C7||15||85||style="background:mediumvioletred;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Orange colors'''</big>
|-
||LightSalmon ||FF||A0||7A||style="background:lightsalmon;"| 
|-
|Orange ||FF||A5||00||style="background:orange;"| 
|-
|DarkOrange ||FF||8C||00||style="background:darkorange;"| 
|-
|Coral ||FF||7F||50||style="background:coral;"| 
|-
|Tomato ||FF||63||47||style="background:tomato;"| 
|-
|OrangeRed ||FF||45||00||style="background:orangered;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Yellow colors'''</big>
|-
|LightYellow ||FF||FF||E0||style="background:lightyellow;"| 
|-
|LemonChiffon ||FF||FA||CD||style="background:lemonchiffon;"| 
|-
|LightGoldenrodYellow||FA||FA||D2||style="background:lightgoldenrodyellow;"| 
|-
|PapayaWhip ||FF||EF||D5||style="background:papayawhip;"| 
|-
|Moccasin ||FF||E4||B5||style="background:moccasin;"| 
|-
|PeachPuff ||FF||DA||B9||style="background:peachpuff;"| 
|-
|PaleGoldenrod ||EE||E8||AA||style="background:palegoldenrod;"| 
|-
|Khaki ||F0||E6||8C||style="background:khaki;"| 
|-
|Yellow ||FF||FF||00||style="background:yellow;"| 
|-
|Gold ||FF||D7||00||style="background:gold;"| 
|-
|DarkKhaki ||BD||B7||6B||style="background:darkkhaki;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Green colors'''</big>
|-
|GreenYellow ||AD||FF||2F||style="background:greenyellow;"| 
|-
|Chartreuse ||7F||FF||00||style="background:chartreuse;"| 
|-
|LawnGreen ||7C||FC||00||style="background:lawngreen;"| 
|-
|Lime ||00||FF||00||style="background:lime;"| 
|-
|PaleGreen ||98||FB||98||style="background:palegreen;"| 
|-
|LightGreen ||90||EE||90||style="background:lightgreen;"| 
|-
|MediumSpringGreen||00||FA||9A||style="background:mediumspringgreen;"| 
|-
|SpringGreen ||00||FF||7F||style="background:springgreen;"| 
|-
|YellowGreen ||9A||CD||32||style="background:yellowgreen;"| 
|-
|LimeGreen ||32||CD||32||style="background:limegreen;"| 
|-
|MediumSeaGreen ||3C||B3||71||style="background:mediumseagreen;"| 
|-
|SeaGreen ||2E||8B||57||style="background:seagreen;"| 
|-
|ForestGreen ||22||8B||22||style="background:forestgreen;"| 
|-
|Green ||00||80||00||style="background:green;"| 
|-
|OliveDrab ||6B||8E||23||style="background:olivedrab;"| 
|-
|Olive ||80||80||00||style="background:olive;"| 
|-
|DarkOliveGreen ||55||6B||2F||style="background:darkolivegreen;"| 
|-
|DarkGreen ||00||64||00||style="background:darkgreen;"| 
|-
|MediumAquamarine||66||CD||AA||style="background:mediumaquamarine;"| 
|-
|DarkSeaGreen ||8F||BC||8F||style="background:darkseagreen;"| 
|-
|LightSeaGreen ||20||B2||AA||style="background:lightseagreen;"| 
|-
|DarkCyan ||00||8B||8B||style="background:darkcyan;"| 
|-
|Teal ||00||80||80||style="background:teal;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Blue colors'''</big>
|-
|Cyan ||00||FF||FF||style="background:cyan;"| 
|-
|LightCyan ||E0||FF||FF||style="background:lightcyan;"| 
|-
|PaleTurquoise ||AF||EE||EE||style="background:paleturquoise;"| 
|-
|Aqua ||00||FF||FF||style="background:aqua;"| 
|-
|Aquamarine ||7F||FF||D4||style="background:aquamarine;"| 
|-
|Turquoise ||40||E0||D0||style="background:turquoise;"| 
|-
|MediumTurquoise ||48||D1||CC||style="background:mediumturquoise;"| 
|-
|DarkTurquoise||00||CE||D1||style="background:darkturquoise;"| 
|-
|PowderBlue ||B0||E0||E6||style="background:powderblue;"| 
|-
|LightSteelBlue ||B0||C4||DE||style="background:lightsteelblue;"| 
|-
|LightBlue ||AD||D8||E6||style="background:lightblue;"| 
|-
|SkyBlue ||87||CE||EB||style="background:skyblue;"| 
|-
|LightSkyBlue||87||CE||FA||style="background:lightskyblue;"| 
|-
|DeepSkyBlue ||00||BF||FF||style="background:deepskyblue;"| 
|-
|CornflowerBlue||64||95||ED||style="background:cornflowerblue;"| 
|-
|SteelBlue ||46||82||B4||style="background:steelblue;"| 
|-
|CadetBlue ||5F||9E||A0||style="background:cadetblue;"| 
|-
|MediumSlateBlue||7B||68||EE||style="background:mediumslateblue;"| 
|-
|DodgerBlue ||1E||90||FF||style="background:dodgerblue;"| 
|-
|RoyalBlue ||41||69||E1||style="background:royalblue;"| 
|-
|Blue ||00||00||FF||style="background:blue;"| 
|-
|MediumBlue ||00||00||CD||style="background:mediumblue;"| 
|-
|DarkBlue ||00||00||8B||style="background:darkblue;"| 
|-
|Navy ||00||00||80||style="background:navy;"| 
|-
|MidnightBlue ||19||19||70||style="background:midnightblue;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Purple colors'''</big>
|-
|Lavender ||E6||E6||FA||style="background:lavender;"| 
|-
|Thistle ||D8||BF||D8||style="background:thistle;"| 
|-
|Plum ||DD||A0||DD||style="background:plum;"| 
|-
|Violet ||EE||82||EE||style="background:violet;"| 
|-
|Fuchsia ||FF||00||FF||style="background:fuchsia;"| 
|-
|Magenta||FF||00||FF||style="background:magenta;"| 
|-
|Orchid ||DA||70||D6||style="background:orchid;"| 
|-
|MediumOrchid ||BA||55||D3||style="background:mediumorchid;"| 
|-
|MediumPurple ||93||70||DB||style="background:mediumpurple;"| 
|-
|SlateBlue ||6A||5A||CD||style="background:slateblue;"| 
|-
|BlueViolet ||8A||2B||E2||style="background:blueviolet;"| 
|-
|DarkViolet ||94||00||D3||style="background:darkviolet;"| 
|-
|DarkOrchid ||99||32||CC||style="background:darkorchid;"| 
|-
|DarkMagenta ||8B||00||8B||style="background:darkmagenta;"| 
|-
|Purple ||80||00||80||style="background:purple;"| 
|-
|DarkSlateBlue ||48||3D||8B||style="background:darkslateblue;"| 
|-
|Indigo ||4B||00||82||style="background:indigo;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Brown colors'''</big>
|-
|Cornsilk ||FF||F8||DC||style="background:cornsilk;"| 
|-
|BlanchedAlmond ||FF||EB||CD||style="background:blanchedalmond;"| 
|-
|Bisque ||FF||E4||C4||style="background:bisque;"| 
|-
|NavajoWhite ||FF||DE||AD||style="background:navajowhite;"| 
|-
|Wheat ||F5||DE||B3||style="background:wheat;"| 
|-
|BurlyWood ||DE||B8||87||style="background:burlywood;"| 
|-
|Tan ||D2||B4||8C||style="background:tan;"| 
|-
|RosyBrown ||BC||8F||8F||style="background:rosybrown;"| 
|-
|SandyBrown ||F4||A4||60||style="background:sandybrown;"| 
|-
|Goldenrod ||DA||A5||20||style="background:goldenrod;"| 
|-
|DarkGoldenrod ||B8||86||0B||style="background:darkgoldenrod;"| 
|-
|Peru ||CD||85||3F||style="background:peru;"| 
|-
|Chocolate ||D2||69||1E||style="background:chocolate;"| 
|-
|SaddleBrown ||8B||45||13||style="background:saddlebrown;"| 
|-
|Sienna ||A0||52||2D||style="background:sienna;"| 
|-
|Brown ||A5||2A||2A||style="background:brown;"| 
|-
|Maroon ||80||00||00||style="background:maroon;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''White colors'''</big>
|-
|White ||FF||FF||FF||style="background:white;"| 
|-
|Snow ||FF||FA||FA||style="background:snow;"| 
|-
|Honeydew ||F0||FF||F0||style="background:honeydew;"| 
|-
|MintCream ||F5||FF||FA||style="background:mintcream;"| 
|-
|Azure ||F0||FF||FF||style="background:azure;"| 
|-
|AliceBlue ||F0||F8||FF||style="background:aliceblue;"| 
|-
|GhostWhite ||F8||F8||FF||style="background:ghostwhite;"| 
|-
|WhiteSmoke ||F5||F5||F5||style="background:whitesmoke;"| 
|-
|Seashell ||FF||F5||EE||style="background:seashell;"| 
|-
|Beige ||F5||F5||DC||style="background:beige;"| 
|-
|OldLace ||FD||F5||E6||style="background:oldlace;"| 
|-
|FloralWhite ||FF||FA||F0||style="background:floralwhite;"| 
|-
|Ivory ||FF||FF||F0||style="background:ivory;"| 
|-
|AntiqueWhite ||FA||EB||D7||style="background:antiquewhite;"| 
|-
|Linen ||FA||F0||E6||style="background:linen;"| 
|-
|LavenderBlush ||FF||F0||F5||style="background:lavenderblush;"| 
|-
|MistyRose ||FF||E4||E1||style="background:mistyrose;"| 
|-
|colspan=5; style="background:whitesmoke; color:slategray; text-align:left;"|<big>'''Grey colors'''</big>
|-
|Gainsboro ||DC||DC||DC||style="background:gainsboro;"| 
|-
|LightGrey ||D3||D3||D3||style="background:lightgrey;"| 
|-
|Silver ||C0||C0||C0||style="background:silver;"| 
|-
|DarkGray ||A9||A9||A9||style="background:darkgray;"| 
|-
|Gray ||80||80||80||style="background:gray;"| 
|-
|DimGray ||69||69||69||style="background:dimgray;"| 
|-
|LightSlateGray ||77||88||99||style="background:lightslategray;"| 
|-
|SlateGray ||70||80||90||style="background:slategray;"| 
|-
|DarkSlateGray ||2F||4F||4F||style="background:darkslategray;"| 
|-
|Black ||00||00||00||style="background:black;"| 
|}
[[Category:Help]]

{{WikiDoc Help Menu}}
{{WS}}

Edit summary

2009-06-16T10:43:03Z

Levacher: French WikiDoc link

It is good practice to fill in the Edit Summary field, or add to it in the case of [[#Section editing|section editing]], as it helps everyone to understand what is changed, such as when perusing the history of the page. It's a good idea to set your user preferences (under Edit) to "Prompt me when entering a blank edit summary".

==Properties==

The edit summary box can hold one line of 200 characters. If you attempt to type or paste more, only the first 200 characters will be displayed - the rest will be disregarded. Also, for example attempting to add 10 new characters (at the end or in between) to a summary already containing 195 characters will result in the first 5 new characters being inserted and the second 5 being disregarded.

The "Show preview" button also provides a preview of the edit summary to facilitate checking links.

==Recommendations==
'''Always fill in the summary field'''. This is considered an important guideline. Even a short summary is better than no summary. An edit summary is even more important if you delete any text; otherwise, people may question your motives for the edit. Also, mentioning one change but not another one can be misleading to someone who finds the other one more important; add "and misc." to cover the other change(s).

Accurate summaries help people decide whether it is worthwhile for them to check a change. We've found that summaries often pique the interest of contributors with expertise in the area. This may not be as necessary for "minor changes", but "fixed spelling" would be nice even then.

In the case of a small addition to an article, it is highly recommended to copy the full text of this addition to the summary field, giving a maximum of information with a minimum of effort. Put ''ft'' in front, as an abbreviation of "full text" (see the [[#Abbreviations|Abbreviations section]] for other abbreviations). This way, readers of the summary will be unlikely to check the page itself as they already know the extent of the edit. These kinds of edits allow users to check Recent changes, Page history and User contributions (see below) very efficiently - this also reduces the load on the servers.

If the addition is more than 200 characters, so it does not fit fully in the edit summary box, you should write a short summary of the changes you have introduced into the article. For an addition of, say, 400 characters you can also save time by simply copying that into the summary field. The excess will fall off, and the first 200 characters will usually be acceptable as a crude "summary".

Unfortunately you can copy only one line of text from the edit box into the edit summary box. The contents of further lines can be pasted at the end of the line. Thus, for example, a bulleted "see also" list is cumbersome to put in the edit summary box. One possible workaround for a new list is putting the list on one line, separated by the asterisks for the bullets, copying it to the edit summary box, and then, in the main edit box, putting the new lines before the asterisks.

In addition to a summary of the change itself, the summary field may also contain an explanation of the change; note that if the reason for an edit is not clear, it is more likely to be reverted, especially in the case that some text is deleted. To give a longer explanation, use the Talk page and put in the edit summary "see Talk".

After saving the page, the summary can not be edited--another reason to avoid spelling errors.

In the case of important omissions or errors in the edit summary, you can make a [[Help:Dummy edit|dummy edit]] just to put the correction in the edit summary.

==Places where the edit summary appears==

The edit summary appears in black italics in the following places:

*[[Help:Page history|Page history]] - list of changes to the page you edited
*[[Help:User contributions|User contributions]] - list of all your edits
*[[Help:Watching pages|Watchlist]]'''<nowiki>*</nowiki>''' - list of recent changes to watched pages ([[Help: Logging in|logged-in]] users only)
*[[Help:Diff|diff page]] - shows the difference between two edits
*[[Help:Recent changes|Recent changes]] - list of all recent edits
*[[w:Wikipedia:IRC channels|Wikipedia IRC channels]] - real time list of all edits
*[[Help:Related changes|Related changes]] - list of recent changes to pages linked to the page you edited
*List of new pages: shows the edit summary of the creation.

'''<nowiki>*</nowiki>''' Use the enhanced watchlist to see all recent changes in the watched pages, not just the last change in each page.

== Abbreviations ==

Experienced users, especially those with many edits to make, will often use abbreviations in edit summaries (as well as [[Special:Log|log]] entries), in order to save time; for example, "rv" for "[[Help:Reverting|revert]]". These should be used with care, as they can be confusing for inexperienced users, but they are generally fine for small edits such as formatting and grammar changes. See [[w:Wikipedia:Edit summary legend|Edit summary legend]] for a list of commonly used abbreviations in edit summaries.

==Searching==

The [[Help:Searching|Wikimedia search function]] can not search edit summaries, and they are not indexed by external search engines.

==File upload summary==

When uploading an image one can supply an upload summary. This serves multiple purposes:
*as second part of the automatically created edit summary of the upload log (the first part giving the file name)
*as text in the entry of the [[Help:Page history#Image_history|image history]]
*in the case that the file name of the image is new:
**as edit summary for the creation of the image page
**as wikitext for the editable part of the image page, which includes the following possibilities:
***briefly describe the image
***provide internal or external links
***call templates
***specify one or more categories the image is in

The capacity of the upload summary is one line of 250 characters; in the upload log the last part may fall off, because this can contain 255 characters, including "uploaded "''filename''"".

Note that there is no preview function to check the code for the links, template calls and category tags, but of course, if needed one can edit the image page after uploading, to correct errors and also to extend the text.

See also [[Help:Image page]].

== Section editing ==

When adding a new section to a discussion page with the "+" button, the section title is used as the edit summary. When [[Help:Section#Section editing|editing an existing section]], the section title is inserted at the beginning of the edit summary, enclosed with /* and */ marks, for example /* External links */. Details of the edit should be added after this text. In the case that you provide a long summary yourself you can delete the section title in order to stay within the limit of 200 characters.

When viewing such an edit summary, the section name will appear in grey, with a small link next to it: [[#Foo|→]] External links. Clicking the link to view the section (if the section no longer exists, the link will just take you to the page).

If you create a new section before or after an existing section by clicking a section "''edit''" link, delete the text between /* and */ marks to avoid confusion. It is possible to manually include links to multiple sections using the /* */ syntax – this may be useful when editing several sections at once.

For example, the edit summary:
/* Foo */ test /* Bar */ test

is rendered as:

[[#Foo|→]]Foo test [[#Bar|→]]Bar test

=="Post a comment" feature==

When starting a new thread on a Talk page, the "Post a comment" feature can be used. Click the plus sign next to the Edit link. A box labelled "''Subject/headline''" appears before the main editing box. Text typed into the subject field becomes both the edit summary and a new heading (which is added to the end of the page), and text entered into the main edit box is inserted below this heading.

== Automatic summaries ==

In certain circumstances, an automatic summary is generated when an edit is saved without one. This is slightly different to the summary added when editing a section, as that can be modified by the user before saving.

{| border class="wikitable"
! Situation !! Page !! Text
|-
| Creating or replacing a page with a redirect ('$1' is replaced with the target of the redirect)
| [[MediaWiki:Autoredircomment]]
| {{#ifexist:MediaWiki:Autoredircomment|{{msgnw:MediaWiki:Autoredircomment}}|<nowiki>Redirecting to [[$1]]</nowiki>}}
|-
| Removing all text from a page
| [[MediaWiki:Autosumm-blank]]
| {{#ifexist:MediaWiki:Autosumm-blank|{{msgnw:MediaWiki:Autosumm-blank}}|Blanking page}}
|-
| Removing most of the text from a page, or editing a short page ('$1' is replaced with the page text)
| [[MediaWiki:Autosumm-replace]]
|{{#ifexist:MediaWiki:Autosumm-replace|{{msgnw:MediaWiki:Autosumm-replace}}|Replacing page with '$1'}}
|-
| Creating a new page ($1 is replaced with the page text)
| [[MediaWiki:Autosumm-new]]
| {{#ifexist:MediaWiki:Autosumm-new|{{msgnw:MediaWiki:Autosumm-new}}|New page: $1}}
|}

With the exception of the automatic summary when creating a redirect, which usually says all that needs to be said, these are not a substitute for a proper edit summary – you should always leave a meaningful summary, even in the above cases. They are, however, useful in providing some context for edits made by inexperienced users who are not aware of the importance of edit summaries, and for spotting vandalism.

==Rendering of wikitext; URLs==

Text in edit summaries renders internal links, including [[Help:Piped link|piped link]]s, and [[Help:Interwiki linking|interwiki]] links, even when enclosed within <nowiki><nowiki> and </nowiki></nowiki>. Therefore, copying wikitext in the edit summary box may be preferable to copying text from the preview, except when one wants to save space.

Other wikitext coding is not interpreted.

When copying an external link from the preview into the edit summary box then, depending on the operating system, the
"printable version" is copied, i.e. how it is normally rendered, and in addition, between parentheses, the URL; hence the same information as in the wikitext, but in a different format, as well as a possible sequential number.

{{WikiDoc Help Menu}}

{{WikiDoc Sources}}

[[Category:Help]]

[[ar:ويكيبيديا:ملخص التحرير]]
[[cs:Wikipedie:Shrnutí editace]]
[[da:Wikipedia:Beskrivelse]]
[[de:Hilfe:Zusammenfassung und Quelle]]
[[fi:Wikipedia:Yhteenveto]]
[[fr:Aide:Résumé des contributions]]
[[id:Wikipedia:Ringkasan]]
[[is:Hjálp:Breytingar ágrip]]
[[ja:Wikipedia:常に要約欄に記入する]]
[[ka:დახმარება:რეზიუმე]]
[[nl:Help:Samenvatting]]
[[ru:Википедия:Описание изменений]]
[[sk:Wikipédia:Zhrnutie úprav]]
[[sl:Wikipedija:Povzetek urejanja]]
[[sv:Wikipedia:Sammanfattning]]
[[yi:הילף:קורץ ווארט]]
[[zh:Help:编辑摘要]]

Images

2009-06-08T08:05:13Z

Levacher: /* How do I get it to insert only 3 pictures across in a galler? */

==Before Inserting an Image into a Chapter, You Must First Upload the Image on the WikiDoc Server==
Images can be ''inserted'' into a WikiDoc page only if they have been uploaded onto the WikiDoc server (the computer that serves up all the pages you view). If the images you want to insert are not yet on the server, you can add them (a process called "uploading" them) onto the server. Each WikiDoc page has a link in its left had margin called [http://en.wikidoc.org/index.php/Special:Upload '''Upload file'''] which has all of the details for adding or uploading the image to the server.

On the Upload file page you will see the following two boxes:

[[Image:Upload-file.jpg]]

Where it says "Source filename:" you will click on the gray button "browse" and find the file on your computer's hard drive that you want to add to WikiDoc.

Where it says "Destination filename:" you will simply type in the name you want the image to have on WikiDoc. Please use a name that is descriptive of the image so that it will be found and cataloged by search engines.

Next, click on the button that says "Upload file".

Next, the uploaded image will apear. '''''Hint:''''' '''copy the name of the file so that you can insert it on the WikiDoc page you would like.'''

Once you are anyone else have added an image to the server, that image can then be inserted on an any number of pages.

You can find the filenames of the images that have been uploaded to WikiDoc on the [[Special:Imagelist|Image file list]]. You will need to know the filename of the image to insert the image.

You can see the images that have been uploaded to WikiDoc on the [[Special:Newimages|Gallery of new images]]

==Basic Instructions for Inserting Images onto a WikiDoc Page==
Only images that have been uploaded to Wiki doc can be used. To upload images, use the [[Special:Upload|upload page]].

===Insert the Image Code===

Images are placed on a page by typing a line of image code along with the other text. As with the typing of text, this is done in the editing window of the page being edited. Selecting the ''edit this page'' tab at the top of the page accesses the editing panel. Sign-on first so that your work will be credited to you in the record keeping.

Before placing the code, first consider the best place for the image. This usually means thinking about how the text will look when it wraps. For example, sometimes the work looks best when the image is level with the start of a section. If you want it to start there, then make an empty line immediately ''under'' the heading or immediately ''above'' it, depending on which you think looks best, and type the image code, (given later). The extra line will be ignored apart from the production of an image.

Press the ''Show preview'' button at the bottom of the editing window and wait for the system to display the reformatted page. If the image was placed on the ''left'' or the ''right'' then the text will be seen to wrap around the image from the very top of the section. If the ''center'' was selected, (or ''none''), then the text ''cannot'' wrap, and the text will move to a point below the image. If the result is not as expected, then the text can be changed as often as necessary, until it is right. When the work ''is'' right, then press the ''Save page'' button at the bottom of the page.

Most images on the Wiki server are simply too big to display in their full sizes. In nearly every case an image reduction will be needed. The server also expects to know ''where'' to place the image, as well as what kind of ''frame'' is required. Does it need a ''caption''? With these common requirements in mind, and to save the user much valuable time, it is proposed to go straight onto the ''recommended'' format; the one having ''all'' of the basic options in it. A selection of common examples using the recommended syntax is given in the "Examples" section below.

===Examples===

{| border="1" cellpadding="2" cellspacing="0"
|-
! What it looks like
! What you type
|- valign="top"
|A picture:
[[Image:humanbody.jpg]]
|<pre>A picture:
<nowiki>[[Image:humanbody.jpg]]</nowiki></pre>

|- valign="top"
|With alternative text:
[[Image:humanbody.jpg|Anatomy]]
|<pre>With alternative text:
<nowiki>[[Image:humanbody.jpg|Anatomy]]</nowiki></pre>
* Alternative text, used when a mouse hovers over the image or when the image is not loaded in a text-only browser, or when spoken aloud, is '''strongly''' encouraged.
|- valign="top"
|Floating to the right side of the page and with a caption:
[[Image:humanbody.jpg|frame|Anatomy]] 
|<pre>Floating to the right side of the page
and with a caption:
<nowiki>[[Image:humanbody.jpg|frame|Anatomy]]</nowiki></pre>
* The frame tag automatically floats the image right.
* The caption is also used as alternate text.

|- valign="top"
|Floating to the right side of the page ''without'' a caption:
[[Image:humanbody.jpg|right|Anatomy]]
|<pre>Floating to the right side of the page
''without'' a caption:
<nowiki>[[Image:humanbody.jpg|right|Anatomy]]</nowiki></pre>
* The help topic on Extended image syntax explains more options.

|- valign="top"
|Linking directly to the description page of an image:
[[:Image:humanbody.jpg]]
|<pre>Linking directly to the description page
of an image:
<nowiki>[[:Image:humanbody.jpg]]</nowiki></pre>
* Clicking on an image displayed on a page
(such as any of the ones above)
also leads to the description page

|- valign="top"
|Linking directly to an image without displaying it:
[[media:humanbody.jpg|Anatomy]]
|<pre>Linking directly to an image
without displaying it:
<nowiki>[[media:humanbody.jpg|Anatomy]]</nowiki></pre>
* To include links to images shown as links instead of drawn on the page, use a "media" link.

|- valign="top"
|Using the div tag to separate images from text (note that this may allow images to cover text):
|<pre><nowiki>Example:
<div style="display:inline;
width:220px; float:right;">
Place images here </div></nowiki></pre>

|- valign="top"
|Using wiki markup to make a table in which to place a vertical column of images (this helps edit links match headers, especially in Firefox browsers):
|<pre><nowiki>Example: {| align=right
|-
|
Place images here
|}
</nowiki></pre>

|}

See the Wikidoc's [[Policies & Guidelines|image use policy]] as a guideline used on Wikidoc. 
All information on this page is attributed to Wikipedia and its contributors

==More Detailed Instructions for Inserting Images and its Syntax==
===Type===
*"thumbnail" or "thumb": Image is scaled down to a standard, user specified width, by default 180 pixels, and a box is added around the image. If a caption is written, it is shown below the image. Image defaults to placement on the 'right' unless overridden with the 'Location' attribute (see above).
*"frame": Original image size is preserved, and a box is added around the image. If a caption is written, it is shown below the image.
*(nothing specified): Original image size is preserved, no border is added around the image. If a caption is written, it is '''not''' shown.
*"border": Same as if nothing is specified, but a border is added around the image.

=== Location===
*"right": Image including its box is placed on the right side of the page. The article text that follows the image flows around the image.
*"left": Image including its box is placed on the left side of the page. The article text that follows the image flows around the image.
*"center": Image including its box is placed in the center of the page. The article text that follows the image is placed below the image.
*"none": Image including its box is placed on the left side of the page. The article text that follows the image is placed below the image.

===Size===
*"100px": Scales the image down to make it 100 pixels wide. Replace any number for 100. If you specify "thumbnail" and a value here, this value will take precedent. If the image is already smaller than your specified value, the image stays at its size.
*"100x200px": Scales the image to be no wider than 100 pixels and no higher than 200 pixels. Image will keep its original aspect ratio

===Caption===
Any element which cannot be identified as one of the above is assumed to be caption text.

==New advanced syntax for inserting images==

[[Image:Humanbody.jpg|thumb|100px|left|Anatomy]]The new syntax is backward compatible, so articles don't have to be changed.
In the syntax <tt><nowiki>[[</nowiki>Image:''filename''|''options''<nowiki>]]</nowiki></tt> (e.g. <tt><nowiki>[[Image:Humanbody.jpg|thumb|100px|left|Anatomy]]</nowiki></tt> shown in the left), several options can be set when including an image. Those affect the placing of the image, its size or the way the image will be presented. The options are <tt>right</tt>, <tt>left</tt>, <tt>center</tt>, <tt>none</tt>, <tt>''size''px</tt>, <tt>thumbnail</tt> (<tt>thumb</tt>), <tt>frame</tt>, and <tt>''alternate (caption) text''</tt>.{{clr}}

[[Image:Humanbody.jpg|thumb|Anatomy|200px|right|Human Body]]
The options can be combined, and vertical bars ("|") are used to separate options from each other. The options can be put in any order. An unknown option is taken as the caption text, but this seems to appear only if <tt>thumbnail</tt> is specified. If there are two or more unknown options, the last one upstages the rest: <tt><nowiki>[[Image:Humanbody.jpg|thumb|Anatomy|200px|right|Human Body]]</nowiki></tt> (shown on the right).{{clr}}

Here is the description of the options other than the caption text:

; <tt>right</tt> : [[Image:Humanbody.jpg|right|70px|]]The image is right-aligned, and text floats to the left of the image: <tt><nowiki>[[Image:Humanbody.jpg|right|70px|]]</nowiki></tt> (shown on the right).{{clr}}
; <tt>left</tt> : [[Image:Humanbody.jpg|left|70px|]]The image is left aligned, and text floats to the right of the image: <tt><nowiki>[[Image:Humanbody.jpg|left|70px|]]</nowiki></tt> (shown on the left).{{clr}}
; <tt>center</tt> : The image is centered, and...[[Image:Humanbody.jpg|center|70px|]]the text following the image starts below it: <tt><nowiki>[[Image:Humanbody.jpg|center|70px|]]</nowiki></tt> (shown above).{{clr}}
; <tt>none</tt> : The image is put at the left, and...[[Image:Humanbody.jpg|none|70px|]]the text following does not float to the right (or to the left, obviously), and starts below it: <tt><nowiki>[[Image:Humanbody.jpg|none|70px|]]</nowiki></tt> (shown above).{{clr}}

:: '''Notes:'''{{clr}}
::[[Image:Humanbody.jpg|none|right|center|left|70px|]]The above four options are incompatible. When used combined, the last one overrides the rest: <tt><nowiki>[[Image:Humanbody.jpg|none|right|center|left|70px|]]</nowiki></tt> (shown on the left).{{clr}}

::[[Image:Humanbody.jpg|70px|right]]What is between the last vertical bar and the closing brackets ("]]"), void or not, is taken as the last option, and works as usual. For instance, when the last option is <tt>right</tt>, the image is right-aligned, and text floats to the left: <tt><nowiki>[[Image:Humanbody.jpg|70px|right]]</nowiki></tt> (shown on the right).{{clr}}

::[[Image:Humanbody.jpg|thumb|This text is not displayed.|70px|left|]][[Image:Humanbody.jpg|thumb|This text is displayed.|70px|right]]In particular, if the last option is the void text (that is, if there is nothing between the last vertical bar and the closing brackets), the caption is not displayed: <tt><nowiki>[[Image:Humanbody.jpg|thumb|This text is not displayed.|70px|left|]]</nowiki></tt> (shown on the left) and <tt><nowiki>[[Image:Humanbody.jpg|thumb|This text is displayed.|70px|right]]</nowiki></tt> (shown on the right).{{clr}}

; <tt>''size''px</tt> : [[Image:Humanbody.jpg|right|50px|]]This option renders a version of the image that's ''[size]'' pixels wide (e.g. <tt><nowiki>[[Image:Humanbody.jpg|right|50px|]]</nowiki></tt> shown on the right). Height is computed to keep [[En:aspect ratio (image)|aspect ratio]] (i.e. the shape of the image){{clr}}

:: '''Notes:'''{{clr}}
::Specifying a size does not just change the apparent image size using HTML; it actually generates a resized version of the image on the fly and links to it appropriately. This happens whether or not you use '''size''' in conjunction with '''thumb'''.''

::This means the server does all the work of changing the image size, not the web browser of the user. By having the server do all the work means faster downloading of pages. It also means that larger images can be stored on the server without any slowdown by the browser (especially on dial up telephone lines.) Only the data for the actual size on the page is transmitted.

::From [[m:MediaWiki 1.5|MediaWiki 1.5]] the default thumbnail width can be set in the preferences, so it is recommended ''not'' to specify "px", in order to respect the users' preferences (unless, for a special reason, a specific size is required regardless of preferences, or a size is specified outside the range of widths 120–300px that can be set in the preferences).

:: If you specify a "frame" option the image will not be scaled, and no size specifiers will be in the HTML. The image will be rendered at full size{{clr}}

:: [[Image:Humanbody.jpg|right|50px|80px]]When there are two or more "size" options, only the last one is valid: <tt><nowiki>[[Image:Humanbody.jpg|right|50px|80px]]</nowiki></tt> (shown on the right).{{clr}}

; <tt>thumbnail</tt>, <tt>thumb</tt> : [[Image:Humanbody.jpg|thumbnail|left|100px|]][[Image:Humanbody.jpg|thumb|Anatomy]]The <tt>thumbnail</tt> (<tt>thumb</tt>) option generates a [[En:thumbnail|thumbnail]] image. It is automatically resized when the "size" attribute is not specified. Without the options <tt>left</tt>, <tt>center</tt>, and <tt>none</tt>, the image is normally on the right. If the image has a caption text, it is displayed in the lower margin. E.g. <tt><nowiki>[[Image:Humanbody.jpg|thumbnail|left|100px|]]</nowiki></tt> (shown on the left) and <tt><nowiki>[[Image:Humanbody.jpg|thumb|Anatomy]]</nowiki></tt> (shown on the right). ''Note: thumbnail (thumb) cannot be used in lists.''
{{clr}}


[[Image:tst.jpg|right|thumb|100px|This is a globe, and take a look at it in [[Media:tst.jpg|the actual size]].]]An "enlarge"-icon is put also in the lower margin of the thumbnail. Both the image itself and the icon link to the image description page with the image in its actual size. The icon shows the link title "Enlarge" in its hoverbox, even in cases where this term does not apply, because it leads from the enlarged image to the one with the actual size. E.g. <tt><nowiki>[[Image:tst.jpg|right|thumb|100px|This is a puzzle, and take a look at it in [[Media:tst.jpg|the actual size]].]]</nowiki></tt> (shown on the right).{{clr}}

; <tt>frame</tt> : [[Image:Humanbody.jpg|frame|thumbnail|50px|Anatomy]]With this option, the embedded image is shown with its actual size enclosed by a frame, regardless of the "thumb" or "size" attribute, and the caption, if any, is visible in the frame. Without the options <tt>left</tt>, <tt>center</tt>, and <tt>none</tt>, the image is normally on the right: <tt><nowiki>[[Image:Humanbody.jpg|frame|thumbnail|50px|Anatomy]]</nowiki></tt>.{{clr}}

With none of the options other than <tt>''size''px</tt> and <tt>''alternate (caption) text''</tt>, an embedded image is rendered inline.

<pre>
text text text text text text
<nowiki>[[Image:Humanbody.jpg|150px|Anatomy]]</nowiki>
text text text text text
<nowiki>[[Image:tst.jpg|100px|This is a puzzle.]]</nowiki>
text text text text
</pre>

gives

text text text text text text
[[Image:Humanbody.jpg|150px|Anatomy]]
text text text text text
[[Image:tst.jpg|100px|This is a puzzle.]]
text text text text

The option <tt>none</tt> can be used to have thumbnails without left- or right-alignment. This is probably most useful for [[Wikipedia:How to use tables|tables]]. This is an example:

{| class="wikitable"
!colspan=3| How to use <tt>none</tt>
|----
!colspan=3| London's palaces
|----
| Palace of Westminster || [[Image:Humanbody.jpg|thumb|none|100px|From the Thames]] || <tt><nowiki>[[Image:Humanbody.jpg|thumb|none|100px|From the Thames]]</nowiki></tt>
|----
| Buckingham Palace || [[Image:Buckingham palace Copyright2003KaihsuTai.jpg|thumb|none|100px|Queen's home]] || <tt><nowiki>[[Image:Buckingham palace Copyright2003KaihsuTai.jpg|thumb|none|100px|Queen's home]]</nowiki></tt>
|}

==Thumbnail with caption text underneath that has one or more links==

It is also possible to include links in the caption text, e.g.:

<nowiki>[[Image:Humanbody.jpg|right|thumbnail|This is the [[Palace of Westminster]] in London]]</nowiki>

[[Image:Humanbody.jpg|right|thumbnail|This is a picture of the [[humanbody]] on wikidoc]]

 

Just make sure the number of opening and closing square brackets are right. One extra or missing would mean the entire image syntax line would not work.

==Additional caption formatting options==

Additional caption formatting options are possible.

<nowiki>[[Image:Humanbody.jpg|right|thumbnail|<div align="center">This is the [[Palace of Westminster]] '''in London'''</div>]]
</nowiki>

[[Image:Humanbody.jpg|right|thumbnail|<div align="center">This is the [[Palace of Westminster]] '''in London'''</div>]]

 
All of the normal text formatting options work.

==How Do I Insert a Whole Bunch of Pictures in Gallery like format?==
If you use the following text below, the image below this will appear:

<nowiki><gallery>
Image:humanbody.jpg

Image:Femoral artery and branches.jpg

Image:Femoral-triangle.jpg

Image:Femoral-traingle-2.jpg

Image:Femoral-artery1.jpg
</gallery></nowiki>

This code generates the following image:

<gallery>
Image:humanbody.jpg
Image:Femoral artery and branches.jpg
Image:Femoral-triangle.jpg
Image:Femoral-traingle-2.jpg
Image:Femoral-artery1.jpg
</gallery>
==How do I get it to insert only 3 pictures across in a galler?==

<nowiki><gallery perRow="3">
Image:humanbody.jpg

Image:Femoral artery and branches.jpg

Image:Femoral-triangle.jpg

Image:Femoral-traingle-2.jpg

Image:Femoral-artery1.jpg
</gallery></nowiki>

Displays the following
<gallery perRow="3">
Image:humanbody.jpg

Image:Femoral artery and branches.jpg

Image:Femoral-triangle.jpg

Image:Femoral-traingle-2.jpg

Image:Femoral-artery1.jpg
</gallery>

==How Do I Keep All The Text From Floating Around The Image? How Can I Get The Text To Begin Again Below the Image? Cancelling The Floating-Around-Image Mode==

After having had an image floating next to text, putting further text below it and again using the full width can be done with the following markup. This blocks an image from appearing next to the material following this markup, possibly due to aesthetic reasons or a change in topics.

: '''<nowiki> </nowiki>'''

For legacy <tt>align="right"</tt> (etc.) floating this
isn't good enough; legacy browsers would ignore inline
CSS. To cancel floating under all conditions the
following markup (valid XHTML 1.0 transitional) works:

: '''<nowiki> </nowiki>'''

The same code can be issued by using template
'''<nowiki>{{Clr}}</nowiki>''' or '''<nowiki>{{-}}</nowiki>'''
in certain namespaces (En, meta).

==How Do I Align the Gallery to the right or left and have text float around it?==
'''To achieve the format below:'''
<gallery
align="right"
>
Image:Arteriole-normal.jpg|Normal arteriole
Image:Arteriole-hypertensive.jpg|Hypertensive arteriole with wall thickening and myocyte hypertrophy
Image:Arteriole-hcm.jpg|Arteriole in HCM patient with periarteriole fibrosis and thicknening
</gallery>
Compared to normal arterioles on the left, the arterioles from a patient with hyertension (middle) show moderate periarteriolar thickening and fibrosis. Shown on the right is a patient with HCM in which there is even more signficant periarteriolar thickening and fibrosis. This thickening of the wall of the intramyocardial arterioles leads to an increased wall/lumen ratio, subendocardial ischemia and impaired coronary flow reserve.
{{clr}}

Use this code:
<nowiki><gallery
align="right"
>
Image:Arteriole-normal.jpg|Normal arteriole
Image:Arteriole-hypertensive.jpg|Hypertensive arteriole with wall thickening and myocyte hypertrophy
Image:Arteriole-hcm.jpg|Arteriole in HCM patient with periarteriole fibrosis and thicknening
</gallery>
Compared to normal arterioles on the left, the arterioles from a patient with hyertension (middle) show moderate periarteriolar thickening and fibrosis. Shown on the right is a patient with HCM in which there is even more signficant periarteriolar thickening and fibrosis. This thickening of the wall of the intramyocardial arterioles leads to an increased wall/lumen ratio, subendocardial ischemia and impaired coronary flow reserve.</nowiki>

==Linking To A Page That Has A Detailed Description Of The Image==

If you want to make a link to the description page for an image, use a leading colon before "image:" in an intra-wiki link, like this: <nowiki>[[:image:humanbody.jpg|humanbody]]</nowiki> which yields: [[:image:humanbody.jpg|humanbody]]

==How To Insert a You Tube Video==
#Log on to [http://www.Youtube.com YouTube]
#Upload your video onto YouTube
#Look at the url of your video that you uploaded, you can find it on the right hand side of the page on YouTube, an example would be <nowiki>http://www.youtube.com/watch?v=7TWu0_Gklzo</nowiki>
#Enter the exact letters and numbers in the web address on the YouTube page following the v= into your WikiDoc page in the code listed below. Thats is all you need to do to insert a video.
<nowiki><youtube v=7TWu0_Gklzo/></nowiki>
<youtube v=7TWu0_Gklzo/>

==Google Video==
#Log on to [http://www.video.google.com Google Video]
#Upload your video onto Google Video
#Look at the url of your video that you uploaded, you can find it in the url in the address bar, an example would be <nowiki>http://video.google.com/videoplay?docid=3819381457261079277&q=medical+imaging&total=215&start=0&num=10&so=0&type=search&plindex=0</nowiki>
#Enter the exact letters and numbers in the web address on the Google Video page following the docid= into your WikiDoc page in the code listed below. Thats is all you need to do to insert a video.
<nowiki><googlevideo>3819381457261079277</googlevideo></nowiki>
<googlevideo>3819381457261079277</googlevideo>

[[category:Help]]
{{WikiDoc Help Menu}}
{{WikiDoc Sources}}

References

2009-06-02T13:26:34Z

Levacher: /* Using the WikiDoc reference manager */ spelling

__NOTOC__
==Introduction==
WikiDoc has a reference manager that allows you to insert references based upon their PubMed ID number. If you move the text, the reference moves with it! All the references are automatically inserted at the bottom. You click on the reference and you go to the article. It is simple to do!

==Where do I type in the references?==
Usually you would type a number in the text like this (1) or this 1 which refers to a reference you would like to cite. You would then type in the reference at the end of the article. '''This is not the preferred method in WikiDoc.'''

WikiDoc features an automated reference manager. The advantages of this reference manager are that:
:#The references are numbered automatically!
:#When you move the text, the reference moves with it!
:#You can click on the reference and go directly to the article!

Unlike the usual format where you type in the references at the end of the article, when you use the WikiDoc reference manager, you insert code for the reference right after the material you want to add a reference to. You use a software program to add in the references. The next section describes how to use the software program.

==Using the WikiDoc reference manager==
One goal of WikiDoc is to create reference lists that allow you to click on the PubMed ID number at the end of the reference and go to the primary article itself. This greatly facilitates locating references. Therefore, the preferred method of citing references includes the use of a reference manager that uses the PubMed ID number to create the reference. The reference manager uses not only PubMed IDs but also DrugBank ID, HGNC ID, ISBN, PubMed ID, PubMed Central ID, PubChem ID, or URLs.

The preferred method for inserting a reference is as follows:

'''Step 1:''' Use PubMed to locate the article you are interested in [http://www.ncbi.nlm.nih.gov/pubmed/ by clicking here]

'''Step 2:''' Copy the PubMed ID number from the article. The word PubMed ID is often abbreviated PMID and this number is located at the bottom of the abstract. You can use the search function on Firefox or Internet explorer to locate the word PMID and the number will follow this abbreviation. It will look something like this:

<nowiki>PMID: 19032997</nowiki>

'''Step 3:''' Paste the PubMed ID number (PMID) into a software program that creates the Wiki language code for the reference you are going to paste into the text of your article. You can access software for converting a pubmed ID number into a reference [http://diberri.dyndns.org/cgi-bin/templatefiller/?type=&id= by clicking here]

'''Step 4:''' When using the reference manager, make sure the button that says '''add ref tag''' is checked

'''Step 5:''' Press '''submit''' to generate the Wiki language that can be inserted in your article.

'''Step 6:''' Copy the Wiki language from the software program. For example, the output for the PMID above (19032997) is as follows:

<nowiki><ref name="pmid19032997">{{cite journal |author=Gibson CM, Pride YB, Frederick PD, ''et al'' |title=Trends in reperfusion strategies, door-to-needle and door-to-balloon times, and in-hospital mortality among patients with ST-segment elevation myocardial infarction enrolled in the National Registry of Myocardial Infarction from 1990 to 2006 |journal=Am. Heart J. |volume=156 |issue=6 |pages=1035–44 |year=2008 |month=December |pmid=19032997 |doi=10.1016/j.ahj.2008.07.029 |url=}}</ref></nowiki>

'''Step 7:''' Paste this output from the reference manager software right where you want the superscript number to appear in the text.

For example, using the above reference, you might type something like this:

<nowiki>Gibson et al recently summarized the improvements made in clincial outcomes as a result of 15 years of quality improvement efforts in the NRMI registry <ref name="pmid19032997">{{cite journal |author=Gibson CM, Pride YB, Frederick PD, ''et al'' |title=Trends in reperfusion strategies, door-to-needle and door-to-balloon times, and in-hospital mortality among patients with ST-segment elevation myocardial infarction enrolled in the National Registry of Myocardial Infarction from 1990 to 2006 |journal=Am. Heart J. |volume=156 |issue=6 |pages=1035–44 |year=2008 |month=December |pmid=19032997 |doi=10.1016/j.ahj.2008.07.029 |url=}}</ref></nowiki>

This would generate text that looks like this:

Gibson et al recently summarized the improvements made in clincial outcomes as a result of 15 years of quality improvement efforts in the NRMI registry <ref name="pmid19032997">{{cite journal |author=Gibson CM, Pride YB, Frederick PD, ''et al'' |title=Trends in reperfusion strategies, door-to-needle and door-to-balloon times, and in-hospital mortality among patients with ST-segment elevation myocardial infarction enrolled in the National Registry of Myocardial Infarction from 1990 to 2006 |journal=Am. Heart J. |volume=156 |issue=6 |pages=1035–44 |year=2008 |month=December |pmid=19032997 |doi=10.1016/j.ahj.2008.07.029 |url=}}</ref>

{{reflist|2}}

==What if I don't want to use the reference manager? What if I just want to type the references in myself?==
You are not required to use the reference manager. You can do the following:

'''Step 1:''' Place a '''<nowiki><ref> ... </ref></nowiki>''' immediately after the sentence where you want a footnote number to appear.

'''Step 2:''' Type the text of the note between the ref tags. For example if I typed this

This was on of the first articles I published <nowiki><ref>J Fam Pract. 2000 Oct;49(10):921-3.</ref> </nowiki>

It would appear as this

This was on of the first articles I published <ref>J Fam Pract. 2000 Oct;49(10):921-3.</ref>

==How do I make the references appear at the bottom of the article?==
===The preferred method===

Put the following code in:

<nowiki>==References==
</nowiki>

<nowiki>{{reflist|2}}</nowiki>

This will generate your references in small font, in two columns, with links to the original article and abstract. It will return text that looks like this:

{{reflist|2}}

===Alternate "old school" method===
Place the following code in:

<nowiki>==References==</nowiki>

<nowiki><references/></nowiki>

This generates one column output that looks like this:

<references/>

{{WH}}

{{WS}}

What is a wiki

2009-05-28T14:40:00Z

Levacher: spelling

__NOTOC__
==What is WikiDoc?==
'''WikiDoc''' ''( <wee-kee doc> or <wick-ey doc> )'': WikiDoc is an open source website that allows an international community of healthcare professionals to add and edit medical content in a process termed co-creation. WikiDoc is designed to facilitate collaborative authoring.

WikiDoc allows a community of healthcare professionals to 'co-create' webpages in a way that does not require knowledge of HTML language or computer programming. As a result, numerous people can collaborate in writing articles, textbook chapters or news stories. Prior versions of webpages are stored, and at any time, a page can be reverted to any of its previous states. The 'Discussion' tab allows the community of users to discuss rapidly evolving issues so that a consensus can be reached regarding WikiDoc content. WikiDoc members can choose to be alerted by email when changes are made to a topic they are interested in by clicking on the 'Watch' tab. You can watch a video describing a Wiki in plain English below:
<youtube v=-dnL00TdmLY/>

==Why Did You Create WikiDoc?==
''"The tribe is smarter than any one"'' '''[[C. Michael Gibson]], M.S., M.D.
'''

[[image:Goldenbook encyclopedia.jpg|right|thumb|The Golden Book Encyclopedia that my mom got from the Safeway Grocery store]] I grew up as an only child in Oklahoma. One of the only books I had was a single volume of a blue encyclopedia from the 1920s that I bought at a garage sale when I was in second grade. I remember reading as much of that one volume of the encyclopedia as I could, over and over again. I kept it right next to my bed and was mesmerized by it. Eventually Safeway grocery stores gave kids volumes from the Golden Book Encyclopdia once your mom bought enough groceries. If just one young person is inspired by our blue medical textbook/encyclopedia like I was by an outdated encyclopedia, it will have been worth the effort.

Please read "The World is Flat" by Thomas L. Friedman. One of the premises of this book is that information technology has leveled the playing field of knowledge workers. Silos of knowledge are coming down. Knowledge workers are sharing information freely. Copyright is out, copyleft is in. Those communities that share knowledge most freely, grow and innovate most rapidly. Distributed learning and collaboration are the keys to success in the future. Knowledge workers are demanding free access to shared knowledge.

The "world is flat", but "medicine is flat" as well. It is in the spirit of fostering collaboration among health care providers in sharing medical knowledge that WikiDoc was created. WikiDoc is a global textbook or encyclopedia of medicine that anyone can add to and edit. It is also a source of healthcare news stories. Launched by C. Michael Gibson, M.S., M.D. of Harvard Medical School in 2006, WikiDoc is the first and largest wiki dedicated to medicine on the internet with an initial focus on cardiovascular disease.

As a student I struggled to find information for rounds in the morning. As a former Chief Resident at the Brigham and Womens' Hospital, I remember struggling daily to find the latest information for morning report. As a fellow, finding materials for cardiac cath conference was always a challenge at the end of a long, busy day. Learning is a life long struggle and journey. As long as you are learning about a disease state, why not share what you have learned with others?

WikiDoc is intended to be a shared resource for housestaff (in preparation for morning report), medical students (in preparation for morning rounds) and fellows (in preparation for conferences). Nurses and attending physicians may find it valuable to share and improve upon their fund of general medical knowledge.

==WikiDoc is Copyleft as Opposed to Copyright==
WikiDoc contributions are voluntarily given under the GNU Free Documentation License (GFDL). This is a legal principle known as copyleft, a way of using the copyright process to prevent information being controlled by any one person, and ensure it remains freely accessible forever. All of the information in WikiDoc is free for anyone to copy, modify for their own purposes, and redistribute or use as they see fit, as long as the new version grants the same freedoms to others and acknowledges the authors of the WikiDoc article used (a credit or backlink to the original article is sufficient for this). For full information see the copyright page or the text of the GNU Free Documentation License. For example, some portions of the text on this page were borrowed from and modified from www.wikipedia.org.

==Strengths, Weaknesses and Article Quality in WikiDoc==

WikiDoc's greatest strengths, weaknesses and differences arise because it is open to anyone, has a large contributor base, and articles are written by consensus according to editorial guidelines and policies.

*WikiDoc is open to a large contributor base, -- therefore it is less susceptible to retaining bias, is very hard for any group to censor, and is far more rapidly responsive to new information. On the otherhand, it is more easily vandalized or susceptible to unchecked information later requiring editing.

*WikiDoc is written by consensus -- therefore eventually for most articles, through successive editorial iterations, most viewpoints achieve balance, and a acceptably neutral stance can be achieved even on emotive subjects. On the other hand, reaching a consensus takes considerably longer than a simple drafting, and is occasionally made harder by contributors with extreme-viewpoints. Articles tend to be more fluid or changeable for a longer period of time compared to other reference sources until they find a balanced presentation of data or information or a "neutral consensus" that all parties can agree to.

===Key strengths of WikiDoc:===

* An unlimited number of health care professionals contribute to WikiDoc rather than a few select editors. Our current mailing list numbers 9,700, and there are 37,000 unique users of the site so far during 2007.

* Having a very large number of active writers and editors in many languages, WikiDoc often provides unparalleled access and breadth on subject matter that is otherwise inaccessible or poorly documented.

* WikiDoc often produces topics of interest within hours or days of their occurrence.

* WikiDoc provides neutral, objective, and encyclopedic coverage of medicine and is reviewed by medical experts (Editors-In-Chief).

* In comparison with most web-based resources, WikiDoc's open approach tremendously increases the chances that any particular factual error or misleading statement will be relatively promptly corrected.

* Likewise, censorship cannot be imposed, and therefore censorship by any given group, restriction to "officially reported" sources, or "pushing" of any particular viewpoint, whether official or unofficial, is difficult to achieve and almost always fails after a time.

* Because the pages are archived, information added to wiki doc never "vanishes", and is never "lost" or deleted.

* Disagreeemnts can be voiced in the talk or discussion pages that accompany each page or topic.

===Key weaknesses of WikiDoc:===

* WikiDoc's radical openness means that any given article may be in the middle of a large edit, a rewrite, or recently vandalized. Some topics have not yet been populated.

* Likewise, articles may be incomplete in ways that would be less frequently encountered in a more tightly controlled reference work, for example some aspects may be well covered but others briefly or not at all.

* Citations to published literature may be less robust than published textbooks.

==Monitoring and Correcting Content==

* WikiDoc has been designed with the goal of making it easy to correct mistakes, rather than making it difficult to make them. WikiDoc provides two means to verify the validity of recent additions to the body of pages.

===The Recent Changes Page:===
*The tool most often used to monitor recently added content is the "Recent Changes" pageâa specific list numbering recent edits, or a list of all the edits made within a given time frame. From the change log, other functions are accessible:
*#'''The Revision History''' shows previous page versions. Using the Revision History, an editor can view and restore a previous version of the article.
*#'''The Diff Feature''' highlights changes between two revisions. The Diff Feature can be used to determine if a change to a page is an acceptable or unacceptable edit. If the edit is unacceptable, the previous version can be restored.

===Watch Pages:===
*By clicking on 'Watch' at the top of the page, a user can be alerted by email when pages of interest are changed.

==History of Wikis==
The WikiWikiWeb was the first wiki, established by Ward Cunningham on March 25, 1995. He invented the wiki name and concept, and implemented the first wiki engine. Cunningham coined the term wiki after the "wiki wiki" or "quick" shuttle buses at Honolulu Airport. Wiki wiki was the first Hawaiian term he learned on his first visit to the islands, when the airport counter agent directed him to take the wiki wiki bus between terminals. According to Cunningham, "I chose wiki-wiki as an alliterative substitute for 'quick' and thereby avoided naming this stuff quick-web."

In the late 1990s, wikis were recognized as a way to develop private- and public-knowledge bases, and this potential inspired the founders of the Nupedia encyclopedia project, Jimbo Wales and Larry Sanger, to use wiki technology as a basis for an electronic encyclopedia: wikipedia was launched in January 2001. In the early 2000s, wikis were increasingly adopted as collaborative software. Today some companies use wikis as their only collaborative software and as a replacement for static intranets. The open philosophy of most wikisâof allowing anyone to edit contentâdoes not ensure that editors are well intentioned. Wiki vandalism is a constant problem for wikis, though its danger is, to at least some extent, exaggerated. Studies from IBM claim that most vandalism to many wikis is reverted in 5 minutes or less.

==References==

1. Aigrain, Philippe (2003). The Individual and the Collective in Open Information Communities. Invited talk at the 16th Bled Electronic Commerce Conference, Bled, Slovenija, June 11, 2003.

2. Aronsson, Lars (2002). Operation of a Large Scale, General Purpose Wiki Website: Experience from susning.nu's first nine months in service. Paper presented at the 6th International ICCC/IFIP Conference on Electronic Publishing, November 8, 2002, Karlovy Vary, Czech Republic.

3. Benkler, Yochai (2002). Coase's penguin, or, Linux and The Nature of the Firm. The Yale Law Journal. v.112, n.3, pp.369-446.

4. Cunningham, Ward and Leuf, Bo (2001): The Wiki Way. Quick Collaboration on the Web. Addison-Wesley, ISBN 0-201-71499-X.

5. Delacroix, Jérôme (2005): Les wikis, espaces de l'intelligence collective, M2 Editions, Paris, ISBN 2-9520514-4-5.

6. Ebersbach, Anja, Glaser, Markus and Heigl, Richard (2005): Wiki. Web Collaboration. Springer, ISBN 3-540-25995-3.

7. Jansson, Kurt (2002): "Wikipedia. Die Freie EnzyklopÃ¤die." Lecture at the 19th Chaos Communications Congress (19C3), December 27, 2002 Berlin, Germany.

8. Lange, Christoph (ed., 2005). Wiki - Planen, Einrichten, Verwalten. Computer- und Literaturverlag, ISBN 3-936546-28-2.

9. Mattison, David (2003). "QuickiWiki, Swiki, TWiki, ZWiki, and the Plone Wars: Wiki as PIM and Collaborative Content Tool." Searcher: The Magazine for Database Professionals, v. 11, no. 4 (April 2003): 32-48

10. Möller, Erik (2003). Loud and clear: How Internet media can work. Presentation at the Open Cultures conference, June 5 & 6, 2003 Vienna, Austria.

11. Möller, Erik (2003). Tanz der Gehirne. Telepolis, May 9-30. Four parts: (i) "Das Wiki-Prinzip", (ii) "Alle gegen Brockhaus", (iii) "Diderots Traumtagebuch", und (iv) "Diesen Artikel bearbeiten".

12. Nakisa, Ramin (2003). "Wiki Wiki Wah Wah". Linux User and Developer v.29, pp.42-48.

13. Remy, Melanie. (2002). Wikipedia: The Free Encyclopedia. Online Information Review. v.26, n.6, p.434.

{{WikiDoc Help Menu}}
{{WikiDoc Sources}}
[[Category:Help]]