<?xml version="1.0"?><!-- RSS generated by Radio UserLand v8.2.1 on Sun, 28 Jan 2007 18:57:41 GMT --><rss version="2.0">	<channel>		<title>Jax WWPP - Web info</title>		<link>http://www.wwpp.org/users/0000028/</link>		<description>This is our Web development and information area</description>		<language>en</language>		<copyright>Copyright 2007 Jack F. Mancilla</copyright>		<lastBuildDate>Sun, 28 Jan 2007 18:57:41 GMT</lastBuildDate>		<docs>http://backend.userland.com/rss</docs>		<generator>Radio UserLand v8.2.1</generator>		<managingEditor>iJak@mac.com</managingEditor>		<webMaster>iJak@mac.com</webMaster>		<category domain="http://www.weblogs.com/rssUpdates/changes.xml">rssUpdates</category> 		<skipHours>			<hour>0</hour>			<hour>1</hour>			<hour>3</hour>			<hour>4</hour>			<hour>2</hour>			<hour>5</hour>			<hour>23</hour>			<hour>17</hour>			</skipHours>		<cloud domain="www.wwpp.org" port="8080" path="/RPC2" registerProcedure="xmlStorageSystem.rssPleaseNotify" protocol="xml-rpc"/>		<ttl>60</ttl>		<item>			<title>Websites too complicated?</title>			<link>http://www.wwpp.org/users/0000028/2004/09/13.html#a155</link>			<description>&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/09/13/bbcStoryDiabetes.jpg&quot; width=&quot;231&quot; height=&quot;202&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named bbcStoryDiabetes.jpg&quot;&gt;&lt;hr&gt;&lt;i&gt;I was reading this article this morning. All the websites mentioned here are in the UK, but I was wondering how the questions raised in the article applies to the way websites for medical information are built in the U.S.? One thing I did notice is that all the sites are different. Each site requires learning new navigational information. There are no standard rules for presentation on the web. Would it not be better to find a way to optimize the presentation of certain types of information? Should there not be a medical group, in concert with a web design group, be working to create a &quot;Roberts Rules of Order&quot; for the presentation of medical information on the web. &amp;mdash; Jack&lt;/i&gt;&lt;hr&gt;&lt;p&gt;&lt;a href=&quot;http://news.bbc.co.uk/2/hi/health/3641634.stm&quot;&gt;BBC NEWS | Health | Diabetes websites too complicated&lt;/a&gt;: &lt;br /&gt;Diabetes websites too complicated&lt;br /&gt;Language used was beyond average comprehension&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Online health advice for people with diabetes is often too complex to understand, analysis suggests.&lt;/b&gt;&lt;br /&gt;A scientist at Bath University looked at pages about diabetes on 15 internet health sites run mainly by charities and official bodies.He found people would need a reading ability of an educated 11 to 17-year-old to understand the sites.However, he said the average reading age of people in the UK was equivalent to an educated nine-year-old.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Complicated language&lt;/b&gt;&lt;br /&gt;Dr Maged Boulos from Bath University found the NHS Direct Online site was the hardest to understand.People would need the reading ability of an educated person aged 16 to comprehend information, he estimated.Other difficult sites were NetDoctor.co.uk, Juvenile Diabetes Research Foundation UK, and the British Diabetic Association which required a reading age of at least 15.&quot;&lt;/p&gt;(Related link &lt;a href=&quot;http://www.diabetes.org.uk/&quot;&gt;Diabetes UK&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.nhsdirect.nhs.uk/&quot;&gt;NHSdirect&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.netdoctor.co.uk/&quot;&gt;netdoctor.co.uk&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.jdrf.org.uk/cgi-bin/cms/RunScript.asp?page=32&amp;banner=Banner1&amp;banner2=Banner3&amp;Banner9=Banner10&amp;Search=Search&amp;p=ASP%5CPg32.asp&quot;&gt;Juvenile Diabetes&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.prodigy.nhs.uk/&quot;&gt;Prodigy.Net&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.uclh.org/&quot;&gt;University College London Hospitals&lt;/a&gt;.)&lt;br  /&gt;(Related link &lt;a href=&quot;http://www.besttreatments.co.uk/btuk/home.html&quot;&gt;BestTreatments&lt;/a&gt;.)&lt;br  /&gt;</description>			<guid>http://www.wwpp.org/users/0000028/2004/09/13.html#a155</guid>			<pubDate>Mon, 13 Sep 2004 15:29:12 GMT</pubDate>			</item>		<item>			<title>Medical Records May Go Online - Yahoo! News</title>			<link>http://story.news.yahoo.com/news?tmpl=story2&amp;u=/pcworld/20040823/tc_pcworld/117479</link>			<description>&lt;p&gt;Medical Records May Go Online&lt;br /&gt;Mon Aug 23, 3:00 AM ET&lt;br /&gt;Mark S. Sullivan, Medill News Service&lt;br /&gt;&lt;hr&gt;&lt;i&gt;This is the kind of story that may spark the imagination of some people. &amp;mdash; Jack&lt;/i&gt;&lt;hr&gt;It&apos;s five in the morning. You&apos;re in a hotel room having a serious allergic reaction to something you ate. Do you know where your medical records are?&lt;br /&gt;&lt;br /&gt;If you&apos;re like most Americans, they&apos;re resting peacefully in a manila folder at your doctor&apos;s office. And the writing inside looks something like Sanskrit.&lt;br /&gt;&lt;br /&gt;Someday, that information could be only a modem away--or closer, perhaps in a keychain drive in your luggage. The Bush administration has released a strategic plan for every U.S. citizen&apos;s health information to be stored in an &quot;electronic health record&quot; central database within ten years. Each person would have a &quot;personal health record,&quot; an electronic file the individual would manage, that could exchange information with the EHR database.&lt;br /&gt;&lt;br /&gt;The PHR would contain information on a person&apos;s insurance plan, prescriptions, allergies, medical history, and conditions such as asthma or diabetes.&quot;&lt;/p&gt;&lt;p&gt;(Via &lt;a href=&quot;http://story.news.yahoo.com/news?tmpl=story2&amp;u=/pcworld/20040823/tc_pcworld/117479&quot;&gt;Yahoo! News&lt;/a&gt;.)&lt;/p&gt;</description>			<guid>http://www.wwpp.org/users/0000028/2004/08/23.html#a154</guid>			<pubDate>Mon, 23 Aug 2004 11:37:04 GMT</pubDate>			</item>		<item>			<title>Wired News: Dragging Doctors to the Info Age</title>			<link>http://www.wired.com/news/medtech/0,1286,63899,00.html?tw=wn_story_page_prev2</link>			<description>&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/06/18/wwppSmlPge.jpg&quot; width=&quot;250&quot; height=&quot;214&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named wwppSmlPge.jpg&quot;&gt;&lt;br /&gt;&lt;i&gt;This is an article I found very interesting. I include an image of our site, because I think this is one of the things where we are leading with our concept for tomorrow.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Frustrated by the hospital industry&apos;s achingly slow adoption of basic technological safeguards, the Bush administration and Congress are gearing up to put more pressure on doctors and administrators. For perhaps a decade or more, however, millions of patients will continue to endure the high risk of deadly medical mistakes because there&apos;s no computer to catch the errors. Internal Revenue Service. Physicians can spend entire days without touching a keyboard, and nurses routinely track patients&apos; progress through a series of handwritten notes passed from person to person.&quot;It&apos;s this huge, ridiculous game of telephone,&quot; said surgeon Dr. Robert Wachter, co-author of a new book exploring why medical errors kill tens of thousands of Americans each year.More potential disaster looms on the medication front, where the &quot;chicken scratch&quot; on prescription forms often confuses pharmacists, who end up providing the wrong drugs and, in some cases, killing people.</description>			<guid>http://www.wwpp.org/users/0000028/2004/06/18.html#a152</guid>			<pubDate>Fri, 18 Jun 2004 19:12:49 GMT</pubDate>			<category>My Organization</category>			</item>		<item>			<title>Writing for the Web (Alertbox March 15, 1997)</title>			<link>http://www.useit.com/alertbox/9703b.html</link>			<description>&lt;a href=&quot;http://www.useit.com/jakob/&quot;&gt;&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/02/25/jakobN.jpg&quot; width=&quot;189&quot; height=&quot;224&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named jakobN.jpg&quot; /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;i&gt;This is another writer I respect. Jakob Nielsen is a well respected web usability guru. He writes a monthly article on various aspects of the web. This is an article from 1997 about writing for the web. I used this article to help teach my students in Denmark.&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Jakob Nielsen&apos;s Alertbox for March 15, 1997:&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;Be Succinct! (Writing for the Web)&lt;/strong&gt;&lt;br /&gt;The three main guidelines for writing for the Web are:&lt;br /&gt;Be succinct: write no more than 50% of the text you would have used in a hardcopy publication&lt;br /&gt;Write for scannability: don&apos;t require users to read long continuous blocks of textUse hypertext to split up long information into multiple pages&lt;br /&gt;&lt;br /&gt;Short Texts&lt;br /&gt;Reading from computer screens is about 25% slower than reading from paper. Even users who don&apos;t know this human factors research usually say that they feel unpleasant when reading online text. As a result, people don&apos;t want to read a lot of text from computer screens: you should write 50% less text and not just 25% less since it&apos;s not only a matter of reading speed but also a matter of feeling good. We also know that users don&apos;t like to scroll: one more reason to keep pages short.&lt;br /&gt;&lt;br /&gt;The screen readability problem will be solved in the future, since screens with 300 dpi resolution have been invented and have been found to have as good readability as paper. High-resolution screens are currently too expensive (high-end monitors in commercial use have about 110 dpi), but will be available in a few years and common ten years from now.&lt;br /&gt;</description>			<guid>http://www.wwpp.org/users/0000028/2004/02/25.html#a145</guid>			<pubDate>Wed, 25 Feb 2004 20:38:07 GMT</pubDate>			</item>		<item>			<title>Easy on the Adverbs, Exclamation Points and Especially Hooptedoodle </title>			<link>http://elmore.edition.net/index.lasso?template=excerpt&amp;id=86</link>			<description>&lt;i&gt;Marc asked me about some rules for writing. &lt;br /&gt; My main focus is that a story should have three things, a beginning, a middle, and an end. It should start with a premise, contain justification, and then resolve. It is unnecessary that the resolutions be the expected conclusion. &lt;br /&gt; &lt;br /&gt;But after that, I found this article. It is also useful to think about this article. This is just a very small start. Go to the article and there are 10 rules that may be helpful.&lt;/i&gt; &lt;br /&gt; &lt;br /&gt;&lt;strong&gt;Easy on the Adverbs, Exclamation Points and Especially Hooptedoodle &lt;/strong&gt; &lt;br /&gt;Elmore&apos;s Rules of Writing  &lt;br /&gt;By ELMORE LEONARD ( Series ) 1170 words  &lt;br /&gt; &lt;br /&gt;These are rules I&apos;ve picked up along the way to help me remain invisible when I&apos;m writing a book, to help me show rather than tell what&apos;s taking place in the story. If you have a facility for language and imagery and the sound of your voice pleases you, invisibility is not what you are after, and you can skip the rules. Still, you might look them over. &lt;br /&gt; &lt;br /&gt;1. Never open a book with weather.  &lt;br /&gt;If it&apos;s only to create atmosphere, and not a character&apos;s reaction to the weather, you don&apos;t want to go on too long. The reader is apt to leaf ahead looking for people. There are exceptions. If you happen to be Barry Lopez, who has more ways to describe ice and snow than an Eskimo, you can do all the weather reporting you want.  &lt;br /&gt; &lt;br /&gt;2. Avoid prologues.  &lt;br /&gt;They can be annoying, especially a prologue following an introduction that comes after a foreword. But these are ordinarily found in nonfiction. A prologue in a novel is backstory, and you can drop it in anywhere you want. </description>			<guid>http://www.wwpp.org/users/0000028/2004/02/23.html#a144</guid>			<pubDate>Tue, 24 Feb 2004 07:39:23 GMT</pubDate>			</item>		<item>			<title>We have updated our Frontier/Manila server</title>			<link>http://www.wwpp.org/users/0000028/</link>			<description>&lt;table width=&quot;95%&quot; border=&quot;0&quot; align=&quot;right&quot;&gt;  &lt;tr&gt;    &lt;td rowspan=&quot;2&quot; valign=&quot;top&quot;&gt;&lt;p&gt;We have updated our Manila Software. This is        good for all weblogs because the Manila server actually hosts the Radio    Weblogs Radio Community Server, as well as all of the Manila Weblogs. &lt;/p&gt;    &lt;p&gt;Many thanks to Marc Pierson and Tom Bromet, and Lori, and whoever else    had a hand in its upgrading. &lt;/p&gt;    &lt;p&gt;As we move forward, the developments in Manila 9.1 will give us some great      new cross-platform browser editing tools.&lt;/p&gt;    &lt;/td&gt;    &lt;td width=&quot;11&quot;&gt;&amp;nbsp;&lt;/td&gt;    &lt;td&gt;&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/02/16/manila01.jpg&quot; width=&quot;430&quot; height=&quot;110&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named manila01.jpg&quot; /&gt;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td width=&quot;11&quot;&gt;&amp;nbsp;&lt;/td&gt;    &lt;td width=&quot;460&quot;&gt;&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/02/16/manila02.jpg&quot; width=&quot;382&quot; height=&quot;200&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named manila02.jpg&quot; /&gt;&lt;/td&gt;  &lt;/tr&gt;&lt;/table&gt;</description>			<guid>http://www.wwpp.org/users/0000028/2004/02/16.html#a143</guid>			<pubDate>Mon, 16 Feb 2004 21:20:28 GMT</pubDate>			<category>My Profession</category>			<category>test</category>			</item>		<item>			<title>BBC NEWS | Health | Beams cut need for cancer surgery</title>			<link>http://news.bbc.co.uk/2/hi/health/3492231.stm</link>			<description>&lt;img src=&quot;http://www.wwpp.org/users/0000028/images/2004/02/16/bbcCancer.jpg&quot; width=&quot;227&quot; height=&quot;176&quot; border=&quot;0&quot; align=&quot;right&quot; hspace=&quot;15&quot; vspace=&quot;5&quot; alt=&quot;A picture named bbcCancer.jpg&quot;&gt;&lt;br /&gt;&lt;i&gt;I noticed this took place in Seattle. I was wondering if any of the WWPP people got a chance to see any of this?&lt;/i&gt;&lt;br /&gt;&lt;br /&gt;Beams cut need for cancer surgeryCancer cells can be selectively targetedScientists are perfecting a &apos;virtual scalpel&apos; which uses ultrasound beams to kill cancer cells without the need for surgery. Unlike radiotherapy and drugs, the technique also leaves healthy tissue next to a tumour undamaged. Preliminary trials in the UK and China show it is effective - and has fewer side effects than traditional treatment. Details were presented at the American Association for the Advancement of Science annual meeting in Seattle.Read the entire article -&gt; &lt;a href=&quot;http://news.bbc.co.uk/2/hi/health/3492231.stm&quot;&gt;BBC article&lt;/a&gt;</description>			<guid>http://www.wwpp.org/users/0000028/2004/02/16.html#a142</guid>			<pubDate>Mon, 16 Feb 2004 17:13:21 GMT</pubDate>			<category>My Interests</category>			</item>		</channel>	</rss>