Warung Bebas

Jumat, 12 Oktober 2012

Download .Net Framework All Version

Download .Net Framework All Version - Apa itu .Net Framework? ya, Microsoft .NET Framework (dibaca Microsoft Dot Net Framework) atau lebih dikenal dengan singkatan dot net merupakan sebuah perangkat lunak kerangka kerja yang berjalan utamanya pada sistem operasi Microsoft Windows, saat ini .NET Framework umumnya telah terintegrasi dalam distribusi standar Windows (mulai dari Windows Server 2003 dan versi-versi Windows yang lebih baru). 

Download .NEt framework
.Net Framework


Kerangka kerja ini menyediakan sejumlah besar pustaka pemrograman komputer dan mendukung beberapa bahasa pemrograman serta interoperabilitas yang baik sehingga memungkinkan bahasa-bahasa tersebut berfungsi satu dengan lain dalam pengembangan sistem. Berbeda halnya dengan tipikal aplikasi konvensional umumnya, program yang ditulis dengan memanfaatkan .NET Framework berjalan pada lingkungan perangkat lunak melalui Common Language Runtime, dan bukan perangkat keras secara langsung. 

Hal ini memungkinkan aplikasi yang dibuat di atas .NET secara teoritis dapat berjalan pada perangkat keras apapun yang didukung oleh .NET Framework. Perangkat lunak ini adalah kunci penawaran utama dari Microsoft, dan dimaksudkan untuk digunakan oleh sebagian besar aplikasi-aplikasi baru yang dibuat untuk platform Windows. Untuk lebih jelasnya, kawan-kwan bisa baca referensi disini dijamin lengkap - Apa itu .Net Framework ?

Tanggal rilis semua software .Net Framework :

.NET Framework 1.0 released on 13 February 2002
.NET Framework 1.1 released on 3 April 2003
.NET Framework 2.0 released on 22 January 2006
.NET Framework 3.0 released on 21 November 2006
.NET Framework 3.5 released on 19 November 2007
.NET Framework 3.5 SP1 released on 11 August 2008
.NET Framework 4.0 released on 20 May 2009


Sesuai janji, Link Download nya ada dibawah sini lengkap dari versi lama ke versi yang paling baru tinggal pilih aja sesuai kebutuhan laptop anda !


.NET Framework 4

Supported Operating Systems :
Windows 7, Windows Server 2003 Service Pack 2, Windows Server 2008, Windows Server 2008 R2, Windows Vista Service Pack 1, Windows XP Service Pack 3.

Link Download : Download Here !


.NET Framework Client Profile Offline Installer

Supported Operating Systems :
Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP.

Link Download : Download Here !


.NET Framework 3.5 Setup

Supported Operating Systems :
Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP.

Link Download : Download Here !

.NET Framework 3.5 Setup Service Pack 1

Supported Operating Systems :
Windows Server 2003, Windows Server 2008, Windows Vista, Windows XP.

Link Download : Download Here !

.NET Framework 3.0 Setup

Supported Operating Systems :
Longhorn (Windows Code Name), Windows Server 2003 Service Pack 1, Windows Vista, Windows XP Service Pack 2.

Link Download : Download Here (x86) | Download Here (x64)

.NET Framework 3.0 Service Pack 2

Supported Operating Systems :
Longhorn (Windows Code Name), Windows Server 2003 Service Pack 1, Windows Vista, Windows XP Service Pack 2.

Link Download : Download Here (x86) | Download Here (x64)

.NET Framework 2.0 Setup

Supported Operating Systems :
Windows 2000 Service Pack 3, Windows 98, Windows 98 Second Edition, Windows ME, Windows Server 2003, Windows XP Service Pack 2

Required Software :
Windows Installer 3.0 (except for Windows 98/ME, which require Windows Installer 2.0 or later). Windows Installer 3.1 or later is recommended. IE 5.01 or later: You must also be running Microsoft Internet Explorer 5.01 or later for all installations of the .NET Framework.

Link Download : Download Here (x86) | Download Here (x64)

.NET Framework 1.1 Redistributable Package

Supported Operating Systems :
Windows 2000, Windows Server 2003 Service Pack 1 for Itanium-based Systems, Windows Server 2003 x64 editions, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 for Itanium-based Systems, Windows Server 2008 Standard, Windows Vista Business,Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Starter, Windows Vista Ultimate, Windows XP, Windows XP Professional x64 Edition, Microsoft Windows NT 4.0 requires Service Pack 6a.

Link Download : Download Here !

.NET Framework 1.0 Service Pack 3

Supported Operating Systems :
Windows 2000, Windows 2000 Advanced Server, Windows 2000 Professional Edition, Windows 2000 Server, Windows 2000 Service Pack 2, Windows 2000 Service Pack 3, Windows 2000 Service Pack 4, Windows 98, Windows 98 Second Edition, Windows ME, Windows NT, Windows Server 2003, Windows XP, Windows XP Home Edition, Windows XP Professional Edition, Windows XP Service Pack 1, Windows XP Service Pack 2.

Link Download : Download Here !

UPDATE : Ada sedikit tambahan Tool yang bisa mendeteksi .Net Framework berapa saja yang sudah terinstall di Laptop kita, jika anda berminat bisa mendownload nya DISINI !

Back to the Future - Another Medical Device Company Accused of Hiding ICD Defects

Suppression of data about defects in and failures of implantable cardiac defibrillators (ICDs) was one of the big issues we featured in the early days of Health Care Renewal (2005-06). 

At that time, Guidant, later acquired by Boston Scientific, was accused of hiding data that certain of its defibrillator models failed, possibly leading to preventable patient deaths (see this post and follow links backward).  Boston Scientific, which acquired Guidant, settled a civil lawsuit and was put on probation in 2011 after it pleaded guilty to misdemeanor charges of failing to file required reports with the US Food and Drug Administration (see post here).   Similarly, in 2010, Medtronic settled multiple patients' lawsuits charging that it knowingly marketed a faulty ICD (see post here).

St Jude and the Obscure Riata Data

Now in 2012, A Wall Street Journal article suggested that St Jude Medical Inc hid problems with its Riata implanted cardiac defibrillator (ICD) for years.   

In December, 2010, St Jude Medical Inc issued a warning letter to doctors: Wires inside Riata defibrillator leads—cables that connect the heart to implantable defibrillators—were sometimes breaking through their insulation from the inside out.


The problem, which ultimately led to a recall last year, could cause defibrillators to send unnecessary jolts to the heart or fail to deliver lifesaving shocks to return chaotic heart rhythms back to normal. The company said it had identified dozens of cases with visible signs of the problem, and pulled Riata from the market.

For many doctors, this was the first notice of a problem with Riata.

But before that 2010 warning, physicians including Alan Cheng, director of Johns Hopkins Medicine's arrhythmia service; Samir Saba, chief of electrophysiology at the University of Pittsburgh Medical Center; and Ernest Lau at the Royal Victoria Hospital in Belfast, Ireland, say they had encountered this so-called "inside-out abrasion" in their own practices between 2006 and 2009. When these doctors brought the incidents to the attention of St. Jude they say they were told by company officials and field representatives that the incidents were isolated. The malfunctions described by the doctors didn't result in deaths.

St. Jude had been tracking the problem for several years, according to company documents collected by the Food and Drug Administration and reviewed by The Wall Street Journal. Cases involving the so-called inside-out abrasion date to at least October 2005, the documents show. Inside-out abrasion became a focus of an internal St. Jude audit, which examined multiple cases of the failure before April 2008.
The Journal article noted that more transparency about device failures might allow physicians to spot problems earlier and prevent harm to patients.
more than a dozen physicians and device-safety experts say that if St. Jude had acknowledged the inside-out failure earlier, physicians might have identified the scope of the problem sooner.


In some cases, doctors concede that they, too, believed the failures were isolated and therefore didn't act quickly to report problems to St. Jude or the FDA, which may have made it harder to spot the growing trend of failures. The leads were implanted in more than 13,000 patients since July 2008.

'Every time you have a failed lead, you assume it's an isolated event, but, you start to string together isolated events, and then you have a recall,' said Dr. Saba.
Summary

So, for Health Care Renewal, this is a straightforward case, at least so far.  Yet another health care organization, this time, a medical device company, failed to reveal data that might have reflected unfavorably on one of its products, and hence lead to decreases in short-term revenue.  However, by suppressing the information, the company may have allowed doctors to keep implanting a potentially faulty device, and exposed patients to risk, possibly of fatality. 

We have discussed many at least somewhat parallel cases of suppression of research (here), and many cases of other kinds of deception by health care organizations (here).  Yet these cases continue to occur, physicians and other health care professionals continue to be fooled by secrecy and data suppression, and patients continue to be harmed by drugs, devices, or other interventions made by people who knew, or ought to have known that they were more dangerous than they appeared to be. 

One problem may be that the people with the most influence on medical practice and health policy continue to cheer lead for the veracity of information about drugs, devices, and other health care interventions supplied by the people who most stand to gain from selling same.  A few weeks ago, the editor of the august New England Journal of Medicine, Dr Jeffrey M Drazen MD, scoffed at physicians' skepticism of pharmaceutical industry funded clinical research, claiming that there were only "a few examples of industry misuse of publications...." [Drazen JM. Believe the data. N Engl J Med 2012;  367:1152-1153.  Link here.]  In doing so, Dr Drazen seemed to ignore all the stories about suppression of medical research (some of which we have discussed here), manipulation of medical research (some discussed here), and deception (some discussed here) and secrecy (some discussed here) practiced by large health care organizations, including but not limited to drug, device, biotechnology, and health care information technology companies.

Instead, the possibility that St Jude kept hidden data about the failings of one of its ICD models reminds us how skeptical we ought to be about the information provided, or not provided by those with vested interests in selling health care goods or services.  Physicians, health care professionals, those interested in health policy, and the public at large need to collectively exert pressure on the leaders of health care organizations to promote greater transparency, especially about data reflecting on benefits and harms of health care goods and services.  . 

Download Free 2000 Brush for Photoshop


Download Free 2000 Brush for Photoshop - Brush adalah salah satu fasilitas yang disediakan oleh photoshop untuk mengedit dan membuat suatu gambar dari media Photoshop, jadi jika anda membuka Photoshop versi berapapun coba anda lihat di Bar samping kirinya Photoshop pasti ada sebuah icon seperti gambar kuas, itulah dia Brush

Nah jika anda menggunakan brush itu baru ada bawaannya saja, masih banyak lagi brush-brush cantik lainnya yang bisa anda download contohnya pada posting saya kali ini akan memberikan anda sebanyak kurang lebih 2000 Brush cantik untuk memodifikasi gambar layaknya editor professional. Mau dikemanain Brush sebanyak itu??

Contoh Brush :


 



Nah silahkan dinikmati dan jangan lupa credit to uploader. 
Terima kasih sudah berkunjung.

Link Download via MediaFire :





A Response to the NY Times Article "Ups and Downs of EMRs" So Full Of The Usual Refrains, I Am Using It To Throw A Spotlight On Those Endlessly-Repeated Memes

My Google search alert turned up a response to the Oct. 8, 2012 NY Times article The Ups and Downs of Electronic Medical Records by Milt Freudenheim.

It was posted on the blog of a company Medical-Billing.com and is filled with the usual rhetoric and perverse excuse-making.

It is, in fact, so laden with typical industry refrains and excuse-making that I am using it to throw a spotlight on the misconceptions and canards proffered by that industry in defense of its uncontrolled practices:

A Response to the NY Times on Electronic Medical Records
Posted on October 10, 2012 by Kathy McCoy

A recent article by the New York Times entitled “The Ups and Downs of Electronic Medical Records” has generated a lot of discussion among the HIT community and among healthcare professionals.

It’s an excellent article, looking at concerns that a number of healthcare professionals have about the efficiency, accuracy and reliability of EMRs. One source quoted, Mark V. Pauly, professor of health care management at the Wharton School, said the health I.T. industry was moving in the right direction but that it had a long way to go before it would save real money.

“Like so many other things in health care,” Dr. Pauly said, “the amount of accomplishment is well short of the amount of cheerleading.”

Seriously? I can’t believe we’re still having this conversation.  [Emphasis in the original - ed.] 

I can believe it -- and quite seriously -- as it's a "conversation" long suppressed by the health IT industry and its pundits.

Seriously, I can't believe the comment about "it's an excellent article"; that comment appears to merely be a distraction for the interjection of attacks upon the substance of selfsame "excellent" article.

In a world where I can go to Lowe’s and they can tell me what color paint I bought a year ago, or I can call Papa John’s and they know what my usual pizza order is, how can we expect less from our healthcare systems?

Because healthcare is not at all like buying paint and ordering a pizza, being several orders of magnitude more demanding and complex and on many different planes (e.g, educational, organizational, social and ethical to name a few).  Only the most avid IT hyper-enthusiast (or those prone to ignoratio elenchi) would make such a risible comparison.

I recently joined a new healthcare system, and I have been impressed and pleased by their use of EMR and technology. I no longer have to worry about whether I told the new specialist everything he or she needed to know about my health history; it’s in my record. I no longer have to remember when I had my last tetanus shot; it’s in my record.

My care is coordinated between doctors, labs, etc., better than it ever has been before. In the past, I felt as though my healthcare was a giant patchwork quilt—and some of the stitches were coming loose, frankly. This new system with a widely used EMR, to me, is a huge improvement.

The problem with this argument is that n=1, and the going's not yet gotten tough, such as it had for people injured or killed as a result of the experimental state of current health IT.

Granted, the problems cited in the article are real and need to be addressed. 

Another dubious statement to be followed with excuses ... here it is:

However, the article itself mentions some redundancies that are in place to insure that a system going down doesn’t throw the entire Mayo Clinic into freefall. And certainly, additional redundancies may be needed to insure that prescriptions aren’t incorrectly sent to a pharmacy for the wrong patient, etc.

Those "redundancies" are not complete, do not cover for all aspects of enterprise health IT when it is down, and necessarily compromise patient care when they have to be called upon.   I, for one, a physician, would not enjoy being a patient nor taking care of patients when the "IT lights" go out.

Do doctors and medical staff need to learn how to code correctly so that they aren’t accused of cloning? Yes—but that’s a relatively easy problem to fix. The problem has already been identified, and training has already begun to address the issue.

Cloning of notes and "coding correctly" are two entirely different issues.  Easy to fix?  The health IT industry has been saying all its problems are easy to fix, i.e., in version 2.0 ... for the past several decades, when few if any problems have been.

I have been through this type of problem before, as have many of you, with new systems. It’s called a learning curve, and it’s relatively easy to work through with patience and determination. I have encountered situations before where the team I was working with threw up their hands when they ran into problems learning a new database system and said “It doesn’t work.” Yet in time, they learned to love the system—and some of the biggest doubters became the experts on it.

I surmise that since they were forced into using it, the Stockholm Syndrome was likely at work.  However, speculation aside, the seemingly banal statement that "it’s called a learning curve" is an ethical abomination.  The subjects of these systems are human beings, not lab rats.

Further, health IT is not a "database system."  It is an enterprise clinical resource and clinician workflow control and regulation deviceThis statement illustrates the dangers of having personnel of a technical focus in any kind of authority role in health ITTheir education and worldview is far too narrow.


Healthcare professionals overcome more difficult challenges than this every day; they bring people back from the dead, for Pete’s sake! I have no doubt that they will adapt and learn to utilize EMRs so that they improve healthcare and take patient care to levels currently unimaginable.

Wrong solution, completely ignoring (or perhaps I should say willfully ignorant of) the fact that there's good health IT and bad health IT (GHIT/BHIT).  The IT industry needs to adapt to healthcare professionals, not the other way around, by producing GHIT and banishing BHIT.  This point needs to be frequently repeated, I surmise, due to tremendous disrespect for healthcare professionals by the industry.

And to say, as was quoted in the article: “The technology is being pushed, with no good scientific basis”? Ridiculous, with all due deference to Dr. Scot M. Silverstein, a health I.T. expert at Drexel University who reports on medical records problems on the blog Health Care Renewal and made the statement.

The only thing "ridiculous" is that Ms. McCoy was clearly too lazy to check the very blog she cites, as conspicuously cited in the NY Times article itself.  (That assumes she has the education and depth to understand its arguments and copious citations.)

Lack of RCT's, supportive studies weak at best with literature conflicting on value, National Research Council indicating current health IT does not support clinician cognitive processes, known harms but IOM/FDA both admitting the magnitude of EHR-related harms is unknown, usability poor and in need of significant remediation, cost savings in doubt - these are just a few examples of where the science (as medicine knows it) does not in 2012 support hundreds of billions of dollars for a national rollout of experimental health IT.

I wish it were not so, but alas, that is the current reality.

Database management of information has been proven to be an improvement on paper records in just about every industry there is; healthcare will not be an exception.

Ignoring the repeated "database" descriptor, I agree, eventually, that electronic information systems will improve upon paper.  That's why I began a postdoctoral fellowship in Medical Informatics two decades ago.  However, the technology in its present form interferes with care and is an impediment to the collection and accuracy of that data, and the well being of its subjects, e.g.:  

  • Next-generation phenotyping of electronic health records, George Hripcsak,David J Albers, J Am Med Inform Assoc, doi:10.1136/amiajnl-2012-001145 .  The national adoption of electronic health records (EHR) promises to make an unprecedented amount of data available for clinical research, but the data are complex, inaccurate, and frequently missing, and the record reflects complex processes [economic, social, political etc. that bias the data - ed.] aside from the patient's physiological state.

As I've written before, a good or even average paper system is better for patients than bad health IT, and the latter prevails over good health IT in 2012.

These issues seem chronically to be of little interest to the hyper-enthusiasts as I've written here and here (perhaps the author of the Medical Billing blog post could use her wrist and eyes and navigate there and read).

Is it hard? Yes, it’s hard. To quote the movie A League of Their Own, “If it were easy, everyone would do it.”

It's even harder to do when apologists make excuses shielding a very dysfunctional industry.

Everyone can’t do it. But I have no doubt that healthcare professionals will do it. Remember that part about bringing people back from the dead? This is a lesser miracle.

If qualified healthcare professionals were in charge of the computerization efforts, there would be a smoother path.

However, that is sadly not the case.  It will not happen until enough pressure is brought to bear on the IT industry and its apologists, which I believe will most likely only happen though coercion, not debate.

Finally, the endless stream of excuses and rhetoric that confuse non-healthcare professionals, such as typical patients who are the subjects of today's premature grand health IT experiment and our decision-makers in Washington, needs to be relentlessly challenged.  The stakes are the well being of anyone needing medical care.

-- SS

Note:  my formal reply to the Medical Billing blog post above awaits moderation.  I am reproducing it here:

  1. Your comment is awaiting moderation.

    Dear Ms. McCoy,

    Will all due deference, your own experience with EHR’s is obviously limited.

    Your comments demonstrate an apparent lay level of understanding of medicine and healthcare informatics.

    “Ridiculous?” “Learning curve?” I.e., experimentation on non-consenting human subjects putting them at risk with an unregulated, unvetted medical technology? That is, as kindly as I can put it, a perverse statement.

    Perhaps I am too harsh. You clearly didn’t check the link to the Healthcare Renewal blog conspicuously placed in the NYT article by Milt Freudenheim.

    I suggest you should educate yourself on the science and ethics of medicine and healthcare informatics.

    I am posting the gist of your comments, and my reply, at that blog.

    I do not think most truly informed patients would agree to being guinea pigs as your comments suggest is simply part of the “leaning curve.”

    Scot Silverstein, M.D.

I'll bet the author of the Medical-Billing.com post never heard critique like this coming from today's typical abused-into-submission, learned helplessness-afflicted physicians.

A bit harsh?  Lives are at stake.

-- SS
 

ZOOM UNIK::UNIK DAN UNIK Copyright © 2012 Fast Loading -- Powered by Blogger