Medicine Redirect‑class
This redirect is within the scope of WikiProject Medicine. Please visit the project page for details or ask questions at Wikipedia talk:WikiProject Medicine.MedicineWikipedia:WikiProject MedicineTemplate:WikiProject Medicinemedicine articles Redirect This redirect does not require a rating on Wikipedia's content assessment scale.

Archives

Archive 1 Archive 2 Archive 3 Archive 4

I support placing clinical information within this template, contrary to what has been done before. This information can include:

• Class(es) of disease (i.e. virus, autoimmune disorder)
• Age groups most commonly affected
• Gender most commonly affected
• (Common) symptoms
• (Common) causes
• (Common) methods of diagnosis
• (Common) methods of treatment
• Possible outcomes —Preceding unsigned comment added by Tatterfly (talk • contribs) 18:51, 15 February 2008 (UTC)[reply]

The ICD-10 links from the disease infobox at Dysmenorrhea do not work. Can anyone explain why this is? If you fix it, would you explain, here? Thank you. 98.217.45.218 (talk) 14:34, 24 March 2008 (UTC)[reply]

I have fixed the links. (The explanation is complex, but if you want the details: first read the documentation at at Template:ICD10 and Template talk:ICD10. Then, go to the WHO ICD10 site, and search for "Dysmenorrhea", and click on the "Primary dysmenorrhoea" link. Then scroll to the top of the page. You'll see that "N80" is the first code on the page, so that's the value that needs to be in the last parameter.) --Arcadian (talk) 17:25, 24 March 2008 (UTC)[reply]

Thank you, I understand. 98.217.45.218 (talk) 17:32, 24 March 2008 (UTC)[reply]

I've mildly highlighted this distinction (the code of the condition and the code at the top of the webpage that this is listed under) a little stronger in the description with underlining of "LinkMajor - The major coding at the top of webpage in which ..." - hope this helps with the WHO's complex addressing system and this external link template :-) David Ruben ^Talk 21:12, 24 March 2008 (UTC)[reply]

{{editprotected}}
To avoid editors having to type in "Name = {PAGENAME}", please replace every instance of

{{{Name}}}

with

{{{Name|{{PAGENAME}}}}}

Thanks, Smith609 Talk 17:28, 22 May 2008 (UTC)[reply]

Every instance (the one) of the {{{name}}} parameter in this template already defaults to {{PAGENAME}}. Nihiltres^{t.l} 06:14, 23 May 2008 (UTC)[reply]

Template:Infobox Disease → Template:Infobox condition — A better name for many uses that are not diseases. -- Ned Scott 04:36, 26 September 2008 (UTC) — Ned Scott 04:36, 26 September 2008 (UTC)[reply]

Survey

Feel free to state your position on the renaming proposal by beginning a new line in this section with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's naming conventions.

• Suppport, per discussion above. --Arcadian (talk) 08:40, 26 September 2008 (UTC)[reply]
• (very) Weak oppose - not needed. As previous discussion above highlighted (#Disease is inapropriate for many symptom-based neuropsychiatric conditions) the name of the template is immaterial as not shown to readers. I would (weakly) equally feel uneasy calling pneumonia a condition (on a par with baldness, freckles, obesity) rather than a disease. Clearly "Infobox medical conditions disorders and diseases" is just overpedantic and not needed, and "Infobox medical problem" feels awkward and perhaps limited to just social shyness or discomfort of having to wear a plaster cast in midst of summer. David Ruben ^Talk 11:08, 26 September 2008 (UTC)[reply]
• Oppose. WP Naming conventions don't apply as this is an editor-only name. No satisfactory catch-all PC term is available. Colin°^Talk 11:30, 26 September 2008 (UTC)[reply]

• How is that a valid reason to oppose? We re-name editor-only items all the time. Less experienced editors are likely to be confused by the template name, making this "editor only issue" worthy of a rename. A rename would require absolutely no effort from us and have several positive effects, so what's the hang up here? -- Ned Scott 04:34, 28 September 2008 (UTC)[reply]

• Oppose unnecessary --WS (talk) 21:03, 28 September 2008 (UTC)[reply]

• Honestly, what's with the sticks in the mud here? I've been pretty good with making popular templates, maybe I'll just make a duplicate and make it substantially better, at the new name. Less confusion and less offensive. I don't really mean to be rude, but where does "unnecessary" come from? -- Ned Scott 03:42, 29 September 2008 (UTC)[reply]

• And this new template will have hookers.. and blackjack!.. aaaa, forget the blackjack... -- Ned Scott 04:12, 29 September 2008 (UTC)[reply]

Well you ask for our opinion here, and I don't think it is needed to move it. I don't think it is a problem at all if psychiatric conditions have a disease infobox, but that is just my opinion. And even if you rename it, it still links to the diseases database and two international classifications of diseases. To rename the template would just be trying to be overly political correct I think. I don't have any problem with the suggested other names either, but the current name is just as good so I would prefer keeping the current name. --WS (talk) 18:10, 5 October 2008 (UTC)[reply]

Fair enough. -- Ned Scott 23:55, 6 October 2008 (UTC)[reply]

• Support "Infobox medical condition" as suggested below. Also agree with Ned Scott that there's no harm in relisting the discussion if he can't get in touch with the opposing editors. Dekimasuよ! 02:41, 2 October 2008 (UTC)[reply]
• Oppose - my daily life is centered on using the ICD in its various forms (back to the sixth revision) and there is no title for this infobox that comes anywhere near describing all the different codable concepts covered by the ICD. To pick a few: Bronchopneumonia NOS (J18.0) [a disease]; Congenital absence of ovary (Q50.0) [an anomaly]; Alcohol dependence (F10.2) [a disorder]; Delayed delivery after artificial rupture of membranes (O75.5) [a condition]; Fall from tree (W14} [an external cause of injury]; Kidney donor (Z52.4) [a reason for health encounter]. There just simply isn't one overarching word that covers all of these and there are others. However, "disease" covers most of the chapters of the ICD and therefore (remembering the purpose of this infobox is indicate classification) disease is the least inappropriate background name. Beeswaxcandle (talk) 08:00, 28 December 2008 (UTC)[reply]

Discussion

Any additional comments:

Perhaps Template:Infobox Medical condition might be less ambiguous? — Twas Now ( talk • contribs • e-mail ) 04:46, 26 September 2008 (UTC)[reply]

Note prior discussion #Disease is inapropriate for many symptom-based neuropsychiatric conditions, where point that name of template is hidden from reader makes this relatively unimportant. "Infobox Medical condition" indeed better disampiguation, howeverer as only 1st word normally capitalised then as "Infobox medical condition". I can still envisage some objecting to their situation being a "medical condition" at all, but as templates are not shown to readership, what counts is ease of use for editors (likewise {{fact}}-tagging is used not as an assertion that a point is true, but to highlight that a point needs a citation to verify). David Ruben ^Talk 10:57, 26 September 2008 (UTC)[reply]

No one is claiming this is a life or death situation. Being a back-burner issue is no reason to oppose a rename that requires no effort at all. The only reason I'm making a formal proposal is because the template is protected. Redirects cover all old uses, software automatically fixes any double redirects, so one only needs to press the button once. Given that this can and will help reduce editor confusion and avoid offending a great many others, I don't see why we shouldn't consider this. -- Ned Scott 04:37, 28 September 2008 (UTC)[reply]

I'm not going to say support or oppose (not yet anyway), but do feel that Template:Infobox condition doesn't cut it. If Template:Infobox Disease is to be moved, I consider Template:Infobox medical condition a much better option. Perhaps this could be updated on the WP:RM page? Maedin\^talk 07:24, 8 October 2008 (UTC)[reply]

Throwing this out there.. how about Template:Infobox Medical diagnosis? -- Ned Scott 03:49, 29 September 2008 (UTC)[reply]

Two of the editors opposing this are now on Wikibreak. I doubt anyone will close this early, but just in case anyone is thinking of doing so, please wait until they are active again. I honestly want to understand the objections here, and see if there is a way to find a solution that is satisfactory to them. -- Ned Scott 04:04, 29 September 2008 (UTC)[reply]

OK, is it worth adding a DSM IV TR field to the template? If so, how do I do it? Cheers, Casliber (talk · contribs) 14:14, 8 January 2009 (UTC)[reply]

As discussed at Template_talk:Infobox_Disease#DSM_and_ICD9, I'm of the opinion that we should keep that information with the ICD9/ICD9CM, and in the few cases where there are differences, we can notate that directly in the box. --Arcadian (talk) 14:32, 8 January 2009 (UTC)[reply]

Yes for adding DSM codes. DSM-IV-TR codes match ICD-9 codes (see DSM-IV-TR), than maybe we could change the name to e.g. ICD-9 (DSM-IV-TR): 296 (296)? Or just add corrections if the code is different? Or in different way mention the differences between those two. (es_uomikim (talk) 14:32, 26 January 2010 (UTC))[reply]

I don't think it would be a good idea to change the name of ICD-9 in the infobox to include DSM-IV-TR. DSM covers only a small subset of the many conditions, diseases and disorders that are covered in ICD-9. I agree with Arcadian's opinion above. Beeswaxcandle (talk) 07:24, 28 January 2010 (UTC)[reply]

The eMedicine website has been restructured. The old use of the eMedicineSubj & eMedicineTopic parameters still works as the eMedicine website internally redirects to the new URLs

Hence in the past for the url http://www.emedicine.com/emerg/topic43.htm# we would set eMedicineSubj as 'emerg' and eMedicineTopic as '43'.

However anyone now searching for a suitable eMedicine article is going to be confronted with a rather different eMedicine url to use: http://emedicine.medscape.com/article/806890-overview and so now set the eMedicineSubj parameter always to the fixed literal text of 'article' and eMedicineTopic gets set to the article page number of '806890'.

I was tempted to consider providing a new single parameter name of perhaps eMedicine but I think not as:

• For backwards compatablity {{eMedicine}} and {{eMedicine2}} must still require at least 2 obligatory parameters to be defined, and this template should be consistant with the approach those templates use
• Indeed this template's eMedicine_mult parameter is normally defined using the {{eMedicine2}} template and so may have a mix of existing {{eMedicine2|<<field>>|<<topic number>>}} use, as well as now additional links using a {{eMedicine2|article|<<article number>>}} style. Just too confusing to have this infobox with variable & mixed parameter numbers
• Easier, IMHO, to maintain for existing users of this template (who wont all come looking to this template discussion page) an expectation to see in general at eMedicine a "<space name>/<number value>" ending to the URL they find at eMedicine.
• Finally we still need to allow for the option of linking to a seach list at eMedicine if too many individual articles to include. So as at present: eMedicineSubj is set to 'search' and eMedicineTopic is the search expression to be used (as set out in point 9 of the this template's documentation).

If people really, really feel that it would be better to code the infobox for new eMedicine structure by use of just a single eMedicine parameter, despite my objection points above, please let me know quickly before we need undo too many instances of others using the curent modified template. David Ruben ^Talk 06:31, 10 January 2009 (UTC)[reply]

This banner has been added to the top of the page for Cluster headache, but there is no way to add an ICHD-2 Classification to the Disease Infobox. Could this be added? I have searched long and hard to find out how to add this and have seen no other way than through official modification from higher power above. Thanks.

Link to the official classification from IHS for ICHD-2: http://ihs-classification.org/en/02_klassifikation/02_teil1/03.01.00_cluster.html

---Johngallias (talk) 00:05, 13 February 2009 (UTC)[reply]

CommentI don't think that it is appropriate to add ICHD (in either edition) to this template. It's only going to be useful for a handful of articles. The classifications that are in the template have a broad use across multiple disciplines and applications. Beeswaxcandle (talk) 05:59, 13 February 2009 (UTC)[reply]

please add interlink to italian wikipedia: [[it:Template:Infobox Malattia]] --Luckyz^{Tell Me} 10:08, 27 March 2009 (UTC)[reply]

I've created a new sandbox for this template which contains some tweaks to the styling of this template to bring it into line with the defaults of other infoboxes. A comparison of old versus new can be found at the test cases page. Comments? Chris Cunningham (not at work) - talk 14:01, 22 April 2009 (UTC)[reply]

Support. (I'd also recommending updating Template:Infobox Symptom, as they are essentially the same.) --Arcadian (talk) 17:23, 22 April 2009 (UTC)[reply]

Already done. I'd actually prefer if this template moved to the header styling of {{Infobox Symptom}} as well, but that can be discussed afterwards. Chris Cunningham (not at work) - talk 09:10, 23 April 2009 (UTC)[reply]

How would it work for code ranges such as the ICD-9 one on the Pneumonia article. I wouldn't be keen to have the ends of a range on different lines. Beeswaxcandle (talk) 08:27, 24 April 2009 (UTC)[reply]

Example added to the test cases page. Chris Cunningham (not at work) - talk 11:43, 27 April 2009 (UTC)[reply]

Support. Standing the text off from the edge of the box is an improvement on the old version. Beeswaxcandle (talk) 08:54, 29 April 2009 (UTC)[reply]

Requesting sync, then, as this helps on the road to further consistency / maintainability fixes. Chris Cunningham (not at work) - talk 09:21, 29 April 2009 (UTC)[reply]

Now that the previous change has been rolled out, I've made a few more tweaks to the layout to bring it into line with other infobox templates (and to make it look more like {{infobox Symptom}}. Comparison is on the test cases page again. After that it's just a cases of moving over to use {{infobox}} directly, which will be straightforward. Chris Cunningham (not at work) - talk 09:15, 30 April 2009 (UTC)[reply]

What are you gently leading us to? I'm not sure where (and why) we are heading. Beeswaxcandle (talk) 09:09, 2 May 2009 (UTC)[reply]

Agreed. Please clarify. --Arcadian (talk) 19:20, 2 May 2009 (UTC)[reply]

The {{infobox}} base template makes it much easier to maintain and update templates based on it than hand-coding them out of wikitables - take a look at the code for {{infobox Symptom}}, which I've just converted, to see this. There won't be any further changes in actual output. Chris Cunningham (not at work) - talk 11:37, 3 May 2009 (UTC)[reply]

Arcadian, you have been de facto the maintainer of this and its sister templates (symptoms and procedures). How do you feel/think about moving across to to the {{infobox}} base template? From my perspective as a classification expert, as long as it continues to work and behave well, then the code behind it doesn't worry me. Beeswaxcandle (talk) 09:52, 7 May 2009 (UTC)[reply]

Support. Arcadian (talk) 12:52, 7 May 2009 (UTC)[reply]

{{editprotected}} Requesting sync with the sandbox again as there has is consensus for this change. Chris Cunningham (not at work) - talk 08:16, 11 June 2009 (UTC)[reply]

 Done with a few tweaks of my own. — Martin (MSGJ · talk) 09:09, 11 June 2009 (UTC)[reply]

Could we add NHS Direct Online? Someone has been spamming it, but I think it should be in the infobox. Problem is their links aren't uniform... I've made some test edits but the problem was with two words, the link malfunctioned. --Steven Fruitsmaak (Reply) 18:48, 6 May 2009 (UTC)[reply]

I think the usual precedent for the life cycle is to first build dedicated templates for use in the external links section, which gives us experience about how to parameterize. I agree that the NHS Direct Online are of an extraordinarily high quality, and if the URL templates proved stable and scalable, I could see myself supporting this addition to the infobox (though I'd want to see some examples of exactly what was being added.) --Arcadian (talk) 19:50, 6 May 2009 (UTC)[reply]

Questions What particular information will be added to the infobox through adding links to NHS Direct Online? And how will adding this information to the infobox complement what is already there? Beeswaxcandle (talk) 09:46, 7 May 2009 (UTC)[reply]

{{editprotected}} As per WP:ALT I just now added alt attributes to all but one of the images in Autism, but since {{Infobox Disease}} doesn't support this I couldn't do it for the lead image. I earlier ran into a similar problem with Philitas of Cos and {{Infobox Writer}} and made the obvious change to that template, which works; please see Template talk:Infobox Writer #Alt attribute can now be correctly supported. To do the same thing here, please make the following change to {{Infobox Disease}}:

! colspan=2 style="text-align: center" {{!}} [[File:{{{Image}}}|{{{Width|190}}}px|alt={{{Alt|}}}]]

I made the change to the sandbox and tested it there, using a new test case that I just added to Template:Infobox Disease/testcases. You can just install the current sandbox to the template. Thanks.

By the way, is there some procedure for saying "add alt attribute support to all infobox templates"? Perhaps I should post a request at Wikipedia talk:WikiProject Infoboxes? It's a bit tedious to have to compose these change requests for each individual infobox template. Eubulides (talk) 20:23, 17 June 2009 (UTC)[reply]

Insomuch as the actual code changes required may vary from template to template, I think they need to be requested manually. Pinging the project would be a good way of bringing this to the wider attention of the community though. Chris Cunningham (not at work) - talk 08:20, 18 June 2009 (UTC)[reply]

 Done, although this could use some further thought. Presumably, if no alt is specified then it would be better to use the caption (if specified) rather than nothing? — Martin (MSGJ · talk) 09:26, 18 June 2009 (UTC)[reply]

That would result in screen readers reading both the caption and the alt text, no? Chris Cunningham (not at work) - talk 11:39, 18 June 2009 (UTC)[reply]

Oh. Maybe! Still think it needs proper discussion somewhere. I may bring it up at Village Pump. — Martin (MSGJ · talk) 11:20, 26 June 2009 (UTC)[reply]

There's currently a thread at Wikipedia talk:Featured article candidates #Alt text in images. I agree with Chris Cunningham that the duplication wouldn't be helpful. It's not clear that we have the best solution now, though. Eubulides (talk) 19:00, 26 June 2009 (UTC)[reply]

{{editprotected}}

I've now converted the sandbox to use {{infobox}}. Comparison between old and new is on the test cases page as before. Requesting sync as this is a low-impact change which helps considerably in future maintenance of the template. Chris Cunningham (not at work) - talk 10:18, 29 July 2009 (UTC)[reply]

Done. - Trevor MacInnis (Contribs) 13:38, 29 July 2009 (UTC)[reply]

Sadly it's now broken the work-around that allowed an mw:Extension:ImageMap by writing it as a caption without an image. See Nitrogen narcosis. I suppose I can't complain because the caption is not meant to hold images, but it means I could put an imagemap in the article infobox before, and now I don't know how to. Is this really improving the encyclopedia? --RexxS (talk) 18:01, 30 July 2009 (UTC)[reply]

Well, that was an ugly hack, not merely because of its abuse of "|Caption=", but because it presented textual tabular data as an image instead of as natural form, which is a table. As per WP:OUTBOX, often a better way to present info that isn't naturally supported by an infobox is to put a do-it-yourself infobox after the main infobox. I've just now done this for Nitrogen narcosis. One hacky example isn't a powerful argument against the change to this template, though of course if hacks like this are common that would be a different matter. Eubulides (talk) 19:31, 30 July 2009 (UTC)[reply]

It was an ugly hack from an editing point of view—and not my idea, as I originally used just an image—but the change to an imagemap was clearly an improvement. Obviously, it's a pity that these templates don't accept imagemaps, even though maps often have an "easter-egg" quality to them. I have tried many times to present information like this as a table, but HTML is inherently incapable of displaying a column of figures with aligned decimal points (as you can see in Nitrogen narcosis). It just doesn't look right in the same way that a well-crafted, optimised image (with proper alt text) can do. I'm tempted to just write the whole thing in HTML, but I suspect that the templates provide metadata that would then be lost. --RexxS (talk) 20:16, 30 July 2009 (UTC)[reply]

In my experience the hassle of maintaining an image like that far outweighs any trivial advantages in appearance. But we may have differing opinions about appearance: to my eye the current version has a table that is uglier than the version I put in, mostly because it unnecessarily expands the table to be the same width as the infobox. And if you compare the imagemap (on the left below) with a mildly altered version of the table I put in (on the right), to my eye the table version is just as readable, is more compact, and is much more usable by a naive reader (wikilinks easily seen; you can cut text from the table, etc.). (And the decimal points are just as nicely aligned, at least in my browser.) To each their own, I guess. Eubulides (talk) 09:40, 31 July 2009 (UTC)[reply]

Gas	Relative narcotic potency
Ne	0.3
H2	0.6
N2	1.0
O2	1.7
Ar	2.3
Kr	7.1
CO2	20.0
Xe	25.6

I guess I'm biased by working on websites where the look is dictated by graphic designers who think that presentation is paramount. Knowing when to use a good image is the solution. I'd certainly be criticised for presenting a table where a column of figures don't have their decimal points aligned. Your table, despite the padding, still has the last two rows too far out for my eye (on my browser). But of course, with text, we can't control the font rendering in the client, since users may override our choice of font. I'm amazed that you find the wider infobox uglier - it looks so much better to me <grin>. Appearance is, of course, always a question of taste. Disclaimer: I'm viewing at 1920x1200 with the contents box shown, so I get a lot of horrible white space, that means keeping the height of the infobox down improves the appearance for me. That's the clincher, by the way; the original image is striking, but far too tall (in my eye), so presenting the information as a table now has all the advantages. As I can now move it out of the lead, I may try that, and then I would agree that the compact version you made would be better (although I'd still prefer to right-align + margin the numbers, rather than center and pad them). Thanks again! --RexxS (talk) 14:18, 31 July 2009 (UTC)[reply]

It's trivial to add a new attribute for image maps; have a look at template:infobox Disease/testcases#Image map support for an implementation I just cooked up. This is a far better solution than hacking the caption element. But if you want the current hack to continue to work, all you need to do is ensure that an image is also specified (or the caption element won't be shown) - file:blank.svg along with Width=0 is a good choice. Chris Cunningham (not at work) - talk 08:28, 31 July 2009 (UTC)[reply]

That's a great solution - thank you for suggesting it. I did consider setting "|Image=" to a blank file, after I studied the recent changes, but as I also disapproved of putting the imagemap in the caption, I considered that would be a "hack-too-far". Possibly, this has already been discussed and rejected, but when I create databases, I often add an extra "blob" field because the client will always think of something they want which wasn't in the original spec; perhaps templates might benefit from a "|Data-extra=" parameter for those situations where something unusual may be required? --RexxS (talk) 14:18, 31 July 2009 (UTC)[reply]

That's what the new diagram attribute I've added to the sandbox code is for: I could change the title if you want. In general, though, I think there's consensus that wildcard attributes shouldn't be used in infobox templates because it encourages users to add, well, random data to them. Chris Cunningham (not at work) - talk 14:53, 31 July 2009 (UTC)[reply]

I suspected that would be the case. There's always a delicate tension in making templates between catering for common possibilities and defeating the point of the template in the first place. I can see that "|diagram" would be an alias for "|data10", but I'm not going to suggest any change in that. It should settle any need for additional imagemaps in the infoxbox quite nicely. Thanks once more. --RexxS (talk) 20:08, 31 July 2009 (UTC)[reply]

.../MB_cgi?field=uid&term={{{MeshID|}MeshID}}}]}}
Trevor MacInnis,[1] There's a small bug; the MeshID only displays the link, excluding the number; should be {{{MeshID|}}}{{!}}{{{MeshID}}}] ChyranandChloe (talk) 22:22, 5 August 2009 (UTC)[reply]

+1 --84.44.177.67 (talk) 11:43, 6 August 2009 (UTC)[reply]

It seems there's some kind of problem with this template when the eMedicine tags are missing, as at Neurasthenia. Can someone have a look at the issue? Thanks! --RobinHood70 (talk) 00:30, 12 August 2009 (UTC)[reply]

I just came here to report this. Someone should fix it (I don't have the knowledge). Nazgul02 (talk) 12:24, 12 August 2009 (UTC)[reply]

Based upon the feedback above, I will be reverting this template to the last working version if the new version isn't fixed in the next week or so. --Arcadian (talk) 02:32, 13 August 2009 (UTC)[reply]

{{editprotected}}

Fixed in the sandbox. Chris Cunningham (not at work) - talk 10:55, 13 August 2009 (UTC)[reply]

 Done —TheDJ (talk • contribs) 18:14, 13 August 2009 (UTC)[reply]

Looks good! Thanks, guys. --RobinHood70 (talk) 19:28, 13 August 2009 (UTC)[reply]

The Mesh link is still broken. --Arcadian (talk) 01:24, 22 August 2009 (UTC)[reply]

And obviously fixed now, by you (just to get this off my radar). Chris Cunningham (not at work) - talk 11:08, 15 October 2009 (UTC)[reply]

It's still broken (the link still is a bare numbered link). I'm hesitant to revert back to the last working version, though, since there have been so many subsequent edits. --Arcadian (talk) 11:52, 15 October 2009 (UTC)[reply]

Try the sandbox now; looks like a slip of the fingers at some point. Chris Cunningham (not at work) - talk 14:09, 15 October 2009 (UTC)[reply]

Looks good to me -- thanks. I've updated it from the sandbox. --Arcadian (talk) 19:09, 17 October 2009 (UTC)[reply]

{{editprotected}} When I used Special:Preferences to set my default thumb size to 250px, and then visited Autism, I noticed that the infobox image did not change in size, which meant that the relative sizes of images in that article were out of whack: the lead image in the infobox (because it remained at 190px) incorrectly appeared to be less important than the other images (which had grown from 180px to 250px), even though the lead image is the best image in the article and should appear to be more important.

To fix this, I modified this template (in the sandbox) to default the size to "|frameless|upright=1.06|" instead of to "|190px|". This way, the image size is now 1.06 times the default thumb size, and therefore adjusts more gracefully to changes in the default thumb size. There is no change in behavior unless the user has selected a thumb size other than the 180px default. Also, there is no change in behavior if the invoker of the template uses |Width= to specify a size. Could you please install the sandbox patch? Thanks. Eubulides (talk) 03:23, 6 October 2009 (UTC)[reply]

No problem, done.  Skomorokh, barbarian  03:52, 6 October 2009 (UTC)[reply]

{{editprotected}}

An IP address added a GeneReviews external link to FG syndrome, and after looking at it I thought that it'd be nicer to put this kind of link into the disease infobox. I propose adding support for GeneReviews to {{Infobox disease}}. To help implement this I've made a patch to the sandbox and have tested the result in the autism infobox in the test cases. Eubulides (talk) 20:55, 4 December 2009 (UTC)[reply]

No further comment so I added an {{editprotected}}. Eubulides (talk) 01:47, 12 December 2009 (UTC)[reply]

 Done, I'll leave the change to the documentation field to yourself.  Ronhjones  ^(Talk) 02:31, 12 December 2009 (UTC)[reply]