Sinforsa - SIMRS

Rumus Tetesan DOPAMIN

2010-06-22T20:27:00.000-07:00

DOPAMIN

Kandungan Obat 1 Vial = 200 mg / 5 cc ―》dilarutkan dlm 500 cc NaCl

= 200 mg/500 cc NaCl

= 400 mg/1000 cc NaCl

= 0,4 mg/cc NaCl

= 400 mcq/cc NaCl

bila 1 cc = 20 tts

= 20 mcq/tts

々Kebutuhan

Dosis = 4 mcq/kgbb/mnt

BB = 50 Kg

RUMUS = DOSIS X BB

= 4 X 50

= 200 mcq/mnt

* CONTOH

Dosis = 5 mcq/kgbb/mnt

BB = 50 Kg

Volume = 500 cc NaCl

RUMUS TETESAN = DOSIS X BB / (200/jmlh volume X 1000/20)

= 5 X 50 / (200/500 X 1000/20)

= 250 / 20

= 12,5 tts/mnt

Berikut adalah link untuk aplikasi rumus tetes Dopamin yang dapat dijalankan pada ponsel/HP dengan fitur Java
http://www.ziddu.com/download/10403129/TetesDopamin.jar.html

sumonggo dipun donlot...

Alternatif Software INA-DRG

2009-08-26T20:25:00.001-07:00

http://ina-drg.blogspot.com/2009/08/alternatif-software-ina-drg.html

Alternatif Software INA-DRG

2009-08-26T20:25:00.000-07:00

http://ina-drg.blogspot.com/2009/08/alternatif-software-ina-drg.html

WALK IN INTERVIEW

2009-06-01T21:12:00.001-07:00

ARISTA MITRA LESTARI, PT (HONDA MANGGA DUA)

Company Description

WALK IN INTERVIEW

Arista Group adalah perusahaan yang bergerak di bidang penjualan automotif baik mobil dan motor. Saat ini Perusahaan merupakan salah satu group dealer motor Yamaha yang terbesar dengan daerah pemasaran di DKI Jakarta, Jawa Barat dan Lampung. Perusahaan juga mempunyai beberapa dealer resmi mobil Honda di daerah DKI Jakarta, Depok dan Medan.

Saat ini Perusahaan sedang berkembang pesat dan membutuhkan para profesional berkualitas yang mempunyai motivasi tinggi untuk bergabung bersama Perusahaan untuk menjawab tantangan sebagai berikut :

STAFF IT

(Programmer / Support)

STAFF IT (Programmer / Support)

Post Date: 01 Jun 09

Persyaratan :

Pria usia maksimal 30 tahun.
Pendidikan S1 - komputer (Teknik Informatika / Teknik komputer / Mngm Informatika)
Mengusai RDBMS ( Sybase, SQL Server); Aplikasi database server : MySQL, SQL2000, MS Access; tool programming PC; Aplikasi Web Base : Visual Basic, C-Sharp, Delphi, HTML, ASP, PHP, Javascript; Aplikasi reporting : Crystal Report (IT-Programmer)
Menguasai LAN/WAN Environment untuk Enterprise configuration : switching Layer2/3, routing, VoIP, Firewall, Security; Wireless Environment : Access point, Wireless Client, Point to Point (IT-Support)
Lebih disukai jika memiliki ijazah/sertifikasi keahlian/pelatihan dari ventor IT : Microsoft, Cisco, Novell, SCO, Linux dengan titik berat pada sisi Software/Aplikasi Development (IT-Programmer); Memiliki kemampuan dasar mengelola : query, backup, dan restore database : SQL, MySQL (IT-Support)
Menguasai Aplikasi-aplikasi penunjang pekerjaan : MS Office, MS Project, Vision; Aplikasi Desktop Operation System : Window98, ME 2000 Professional, XP dan Windows Server (IT-Programmer / IT- Support)
Memiliki kemampuan administrasi dan dapat membuat laporan hasil kerja dengan baik (IT-Programmer / IT- Support)
Pengalaman minimal 1 thn diposisi yang sama sebagai programmer atau technical support (IT-Programmer / IT- Support)
Bersedia ditugaskan diluar kota (IT-Support)
Memiliki motivasi kerja yang tinggi, sanggup bekerja keras, dapat bekerja secara individu ataupun team work, serta memiliki integritas yang tinggi.

Bagi yang memenuhi persyaratan : kami memberikan gaji, Kompensasi & benefit, pelatihan, jenjang karir, yang menarik bagi yang terpilih.

Datang & bawalah Surat Lamaran, Daftar Riwayat Hidup, Copy KTP, dan Pas Photo terbaru.

Hari : Kamis

Tanggal : 4 Juni 2009

Waktu : 08.30 – 11.00 WIB

Tempat : Gedung Yamaha ARISTA Kalimalang

Jl. Raya Kalimalang No. 19

Jakarta Timur 13440

CAREER OPPORTUNITIES

2009-06-01T21:09:00.000-07:00

SINERGI DAYA MITRA, PT

Company Description

CAREER OPPORTUNITIES

SDM, a brand name of PT Sinergi Daya Mitra, is a fast growing national company specializing in providing innovative solutions in Human Capital Management.

We urgently required Experienced and Potential Candidates for project-based (contract)assignments (extendable) for the following position:

Application Support (AS)

Post Date: 02 Jun 09

Requirements:

Male / Female
Minimum Bachelor Degree (S1) in computer science and management information system
Minimum 2 years of experience as Programmer/ Application Support
Having knowledge in Banking business process/ knowledge
Have good knowledge in MS SQL Server
Have good knowledge in oracle
Have good knowledge in java
Have knowledge in VB
Have knowledge in C++

Only short-listed candidates will be notified

If you meet above requirements, send your application letter and resume along with expected remuneration to karir@dayamitra.com with position code on the subject line. Or send to

PT SINERGI DAYA MITRA

Menara KADIN Indonesia 30^th Floor

Jl. H.R. Rasuna Said X-5 Kav.2-3

Jakarta 12950

Software INA-DRG Depkes dapat digunakan dalam jaringan LAN

2009-05-18T20:51:00.000-07:00

Software INA-DRG Depkes dapat digunakan dalam jaringan LAN

Software entry data INA-DRG Depkes dapat digunakan dalam lingkup jaringan LAN.
Selengkapnya klik link berikut:
http://ina-drg.blogspot.com/2009/05/software-ina-drg-depkes-dapat-digunakan.html

Exploring Security Fundamentals

2009-05-13T18:41:00.000-07:00

Exploring Security Fundamentals

A “secure network” is a moving target. As new vulnerabilities and new methods of attack are discovered, a relatively unsophisticated user can potentially launch a devastating attack against an unprotected network. This section begins by describing the challenges posed by the current security landscape. You will learn about the three primary goals of security:

confidentiality, integrity, and availability.

This section also explains traffic classification and security controls. You will learn how to respond to a security violation and consider the legal and ethical ramifications of network security.

Why Network Security Is a Necessity

Network attacks are evolving in their sophistication and in their ability to evade detection.

Also, attacks are becoming more targeted and have greater financial consequences for their victims.

Types of Threats

Connecting a network to an outside network (for example, the Internet) introduces the possibility that outside attackers will exploit the network, perhaps by stealing network data or by impacting the network’s performance (for example, by introducing viruses).

However, even if a network were disconnected from any external network, security threats (in fact, most of the probable security threats) would still exist.

Specifically, according to the Computer Security Institute (CSI) in San Francisco, California, approximately 60 to 80 percent of network misuse incidents originate from the inside network. Therefore, although network isolation is rarely feasible in today’s e-business environment, even physical isolation from other networks does not ensure network security.

Based on these factors, network administrators must consider both internal and external threats.

Internal Threats

Network security threats originating inside a network tend to be more serious than external threats. Here are some reasons for the severity of internal threats:

¦ Inside users already have knowledge of the network and its available resources.

¦ Inside users typically have some level of access granted to them because of the nature of their job.

¦ Traditional network security mechanisms such as Intrusion prevention Systems (IPS)and firewalls are ineffective against much of the network misuse originating internally.

External Threats

Because external attackers probably do not have intimate knowledge of a network, and because they do not already possess access credentials, their attacks tend to be more technical in nature. For example, an attacker could perform a ping sweep on a network to identify IP addresses that respond to the series of pings. Then, those IP addresses could be subjected to aport scan , in which open services on those hosts are discovered. The attacker could then try to exploit a known vulnerability to compromise one of the discovered services on a host. If the attacker gains control of the host, he could use that as a jumping-off point to attack other systems in the network.

Fortunately, network administrators can mitigate many of the threats posed by external attackers. In fact, the majority of this book is dedicated to explaining security mechanisms that can defeat most external threats.

National IT Consultant seeks Software Dev. Manager

2009-01-12T03:40:00.000-08:00

SOFTWARE DEVELOPMENT MANAGER

A Pioneer in medical healthcare software development company currently requires software development manager with the following requirements :

Detail knowledge of software development life cycle and methodologies is a must. Furthermore, knowledge of software configuration management and product lifecycle management will be a definite advantage.

Previous hands-on experience in developing client and server side components for 3-tier client/server or web based application, network/socket programming, Java (Enterprise Edition), BEA WebLogic, JSP, HTML is a must.

Knowledgeable in Power Builder.

Proven track record in developing mission critical - enterprise grade, preferably ERP software application.

Having excellent management skill is must, driven, result oriented but also a good team-player.

Bachelor or master degree from a reputable university majoring in Computer Science/Engineering or business.

Mature, age between 30-40 years old with min. 5-10 years experience in managing software development projects.

Please send your CV to hrd@bvk.co.id. Strict confidentiality is maintained.

Common Errors in Patient Education

2008-12-30T17:46:00.001-08:00

One of the most important aspects of the nurse’s role is to educate patients. To do that effectively, there are a couple of points that nurses (as well as other health care professionals) should be aware of.

One is that health care illiteracy affects over one half of all Americans. Regardless of their ability to read and write, or their level of education, Americans don’t understand the health care system and how it works. They don’t even understand enough most of the time to know that they don’t understand.

The other point is that as a result of this problem, the Institute for Health Care Advancement (IHA)points out that costs are continuing to rise to the point of, “as much as $236 billion in unnecessary health care expenses annually due to the inability of patients to understand what medical providers are communicating to them.”

The IHA has complied a guide for health care professionals and consumers to help eliminate some of these problems. This list is composed of the 10 Most Common Errors Medical Professionals Make When Communicating with Their Patients.

Some of the points in this document include:

Prescription drug instructions are often written at a 10th or 11th grade reading level. Most of the population reads at a 5th grade level.
Communicating with patients using medical or other technical jargon such as “otitis media” or “myocardial infarction” instead of using laypersons’ terms such as “ear ache” or heart attack.”
Telling patients to go read about their condition, treatments or medications on the Internet when this information might be too complex, might disagree with the physician’s course of treatment, or the patient may not have access or know how to search the Internet.
Handing out reading material which is printed in too small a font to be easily read, especially by seniors who represent the largest portion of the population.
Not using simple graphics or other visual aids to enhance the patient’s understanding.
Not recognizing that the patient is nodding or saying “yes” as more of a means to be polite and not necessarily because s/he understands what is being said.

Providers should always ask patients to repeat back to them in their own words what they interpret to be the information or instructions given to them. Tis is the best way for the provider to be sure the patient understands correctly and then to make clarifications as needed.

Not demonstrating cultural awareness and how cultural differences may affect the patient’s ability to comply and to succeed with a treatment or other regimen.

Speaking too quickly and not allowing the patient time to formulate or ask questions.
Not providing the information and instructions in the patient’s first language.
Not taking time to adequately explain the meaning of terms on prescription drug labels. For example, “Take With Food,” is written at a 1st or 2nd grade level, but what does it really mean? Studies have shown that some patients have interpreted this as meaning stuffing the pill into a piece of solid food and swallowing it without taking any liquid. This could have varying degrees of problems depending upon the drug and even the size of the pill.

Other problems patients typically have difficulty with include how and when to make follow up appointments, where to go for tests, and even which medications should be refilled and continued versus a course of antibiotics.

Even the most highly educated patients may not understand medical information. Nurses, as the primary health educators, need to understand how to educate patients as well as how to evaluate the patient’s understanding before they leave.

Resources:
IHA (http://iha4health.org)
Helen Osborne M.Ed.,OTR/L, Health Literacy Consulting (http://healthliteracy.com)
By Kathy Quan RN BSN. Kathy is the author of The Everything New Nurse Book and the author/owner of TheNursingSite.com

Issues in health information

2008-12-28T23:05:00.000-08:00

Improving the use of information for health care decision-making: what is needed
World Health Organization / World Health Organization (WHO) (2005)

This paper, published by the World Health Organization, describes how health information systems work and considers how countries can reform them. It argues that some types of data are oversupplied whilst in other areas there are large unmet needs of information. Although many countries now have relatively good data on levels of (and trends in) child mortality, health services coverage, and health determinants, information on adult mortality and cause of death is not generally available. Other areas where better information is needed include: morbidity; coverage and costs of interventions; and equity. The use of information to inform decision- making is also weak at all levels of the healthcare system.
The paper calls for investment in sustainable national and sub-national health information systems and argues that countries will benefit greatly if such systems are based upon a national plan with a policy framework; core indicators; and data-collection, analysis and dissemination strategies. It also calls for national bodies to guide and oversee the implementation of the plan,
with full participation of stakeholders, users, and technical experts. International investors in health information should buy in to and support the country strategies. Collaborative efforts at the international level, such as the recently launched Health Metrics Network, are also important.

Available online at: http://www.who.int/healthmetrics/library/issue_1_05apr.doc

Why Health Care Information Systems Succeed or Fail

2008-12-28T22:59:00.000-08:00

Heeks, R.; Mundy, D.; Salazar, A. / Institute for Development Policy and Management (IDPM), Manchester (1999)
This document offers an understanding and model of why health care information systems succeed or fail, and with general guidance on how to avoid HCIS failure.

Some health care information systems (HCIS) do succeed, but the majority are likely to fail in some way. To explain why this happens, and how failure rates may be reduced, this paper describes the 'ITPOSMO' model of conception-reality gaps. This argues that the greater the change gap between current realities and the design conceptions (i.e. requirements and assumptions) of a new health care information system, the greater the risk of failure. Three archetypal large design-reality gaps affect the HCIS domain and are associated with an increased risk of failure:
• Rationality-reality gaps: that arise from the formal, rational way in which many HCIS are conceived, which mismatches the behavioural realities of some health care organisations

• Private-public sector gaps: that arise from application in public sector contexts of HCIS developed for the private sector.
• Country gaps: that arise from application in one country of HCIS developed in a different country.
Some generic conclusions can be drawn about successful approaches to HCIS development. Examples include the need for more reality-oriented techniques and applications, and greater use of participative approaches to HCIS. More specifically, techniques can be identified for each of the seven ITPOSMO dimensions that will help close the gap between conception and reality. This can include the freezing of one or more dimensions of change. Such techniques will help improve the contribution that information systems can make in health care organisations. [author]

Available online at: http://www.sed.manchester.ac.uk/idpmpublications/wp/igov/igov_wp09.shtml

Using a simple health care information system for health sector reform and health system management

2008-12-28T22:54:00.000-08:00

A guide to using the InHCC health management information system

Shankle, C.G.; Shiroma, M.G.; Gonzalez, J.G. / International Health Care Consultants (InHCC) (2002)

This paper, published by International Health Care Consultants (InHCC), presents a simple health management information system (HMIS) for collecting data to be used in the management of health sector reform policy. The system is intended to be easy to use and inexpensive. It focuses on the collection of information that measures six key dimensions of health system performance: access, effectiveness, efficiency, equity, quality, and sustainability. The paper argues that the information collected can be used not only to guide national policies, but also to direct the day-to-day management of the individual clinic or health centre and provide quality of care to the client.
The paper’s chapters cover: the purpose, definitions and framework for the InHCC system; a description of the system itself; dealing with client, household, and medical system information; and programming the system’s software. The system proposed involves rural clients using a low-cost computer system connected to the internet, and storing data in a centralised "data warehouse". Specialised computer applications for data processing can then be used to provide useful information for decision makers from the local level up to national and international level without the need for further processing.

Available online at: http://www.shetu.com/InHCc-Documentation.pdf

Virtual Private Networks

2008-12-28T17:43:00.000-08:00

Background

Virtual private networks (VPNs) are a fairly quixotic subject; there is no single defining product, nor even much of a consensus among VPN vendors as to what comprises a VPN. Consequently, everyone knows what a VPN is, but establishing a single definition can be remarkably difficult. Some definitions are sufficiently broad as to enable one to claim that Frame Relay qualifies as a VPN when, in fact, it is an overlay network. Although an overlay network secures transmissions through a public network, it does so passively via logical separation of the data streams.

VPNs provide a more active form of security by either encrypting or encapsulating data for transmission through an unsecured network. These two types of security—encryption and encapsulation—form the foundation of virtual private networking. However, both encryption and encapsulation are generic terms that describe a function that can be performed by a myriad of specific technologies. To add to the confusion, these two sets of technologies can be combined in different implementation topologies. Thus, VPNs can vary widely from vendor to vendor.

This chapter provides an overview of building VPNs using the Layer 2 Tunneling Protocol (L2TP), and it explores the possible implementation topologies.

Layer 2 Tunneling Protocol

The Internet Engineering Task Force (IETF) was faced with competing proposals from Microsoft and Cisco Systems for a protocol specification that would secure the transmission of IP datagrams through uncontrolled and untrusted network domains. Microsoft's proposal was an attempt to standardize the Point-to-Point Tunneling Protocol (PPTP), which it had championed. Cisco, too, had a protocol designed to perform a similar function. The IETF combined the best elements of each proposal and specified the open standard L2TP.

The simplest description of L2TP's functionality is that it carries the Point-to-Point Protocol (PPP) through networks that aren't point-to-point. PPP has become the most popular communications protocol for remote access using circuit-switched transmission facilities such as POTS lines or ISDN to create a temporary point-to-point connection between the calling device and its destination.

L2TP simulates a point-to-point connection by encapsulating PPP datagrams for transportation through routed networks or internetworks. Upon arrival at their intended destination, the encapsulation is removed, and the PPP datagrams are restored to their original format. Thus, a point-to-point communications session can be supported through disparate networks. This technique is known as tunneling.

Operational Mechanics

In a traditional remote access scenario, a remote user (or client) accesses a network by directly connecting a network access server (NAS). Generally, the NAS provides several distinct functions: It terminates the point-to-point communications session of the remote user, validates the identity of that user, and then serves that user with access to the network. Although most remote access technologies bundle these functions into a single device, L2TP separates them into two physically separate devices: the L2TP Access Server (LAS) and the L2TP Network Server (LNS).

As its names imply, the L2TP Access Server supports authentication, and ingress. Upon successful authentication, the remote user's session is forwarded to the LNS, which lets that user into the network. Their separation enables greater flexibility for implementation than other remote access technologies.

Implementation Topologies

L2TP can be implemented in two distinct topologies:

•Client-aware tunneling

•Client-transparent tunneling

The distinction between these two topologies is whether the client machine that is using L2TP to access a remote network is aware that its connection is being tunneled.

Client-Aware Tunneling

The first implementation topology is known as client-aware tunneling. This name is derived from the remote client initiating (hence, being "aware" of) the tunnel. In this scenario, the client establishes a logical connection within a physical connection to the LAS. The client remains aware of the tunneled connection all the way through to the LNS, and it can even determine which of its traffic goes through the tunnel.

Client-Transparent Tunneling

Client-transparent tunneling features L2TP access concentrators (LACs) distributed geographically close to the remote users. Such geographic dispersion is intended to reduce the long-distance telephone charges that would otherwise be incurred by remote users dialing into a centrally located LAC.

The remote users need not support L2TP directly; they merely establish a point-to-point communication session with the LAC using PPP. Ostensibly, the user will be encapsulating IP datagrams in PPP frames. The LAC exchanges PPP messages with the remote user and establishes an L2TP tunnel with the LNS through which the remote user's PPP messages are passed.

The LNS is the remote user's gateway to its home network. It is the terminus of the tunnel; it strips off all L2TP encapsulation and serves up network access for the remote user.

Adding More Security

As useful as L2TP is, it is important to recognize that it is not a panacea. It enables flexibility in delivering remote access, but it does not afford a high degree of security for data in transit. This is due in large part to the relatively nonsecure nature of PPP. In fairness, PPP was designed explicitly for point-to-point communications, so securing the connection should not have been a high priority.

An additional cause for concern stems from the fact that L2TP's tunnels are not cryptographic. Their data payloads are transmitted in the clear, wrapped only by L2TP and PPP framing. However, additional security may be afforded by implementing the IPSec protocols in conjunction with L2TP. The IPSec protocols support strong authentication technologies as well as encryption.

Summary

VPNs offer a compelling vision of connectivity through foreign networks at greatly reduced operating costs. However, the reduced costs are accompanied by increased risk. L2TP offers an open standard approach for supporting a remote access VPN. When augmented by IPSec protocols, L2TP enables the realization of the promise of a VPN: an open standard technology for securing remote access in a virtually private network.

Review Questions

Q—What is a VPN?

A—A VPN is a generic term that describes any combination of technologies that can be used to secure a connection through an otherwise unsecured or untrusted network.

Q—Explain the difference between L2TP's LAC and LSN.

A—The LAC provides authentication and access concentration for remote users. After a remote user is authenticated, that user's communications session is then forwarded to the LSN, which provides access to that user's home network.

Q—What additional functionality does IPSec offer an L2TP implementation?

A—L2TP's native security mechanisms build on the assumption that the nature of a
point-to-point connection satisfies most of a remote user's security requirements. IPSec complements L2TP by offering a more robust set of technologies for authenticating remote users and for securing data in transit through foreign networks by encrypting data.

Q—What is a tunnel?

A—A tunnel is a logical structure that encapsulates the frame and data of one protocol inside the Payload or Data field of another protocol. Thus, the encapsulated data frame may transit through networks that it would otherwise not be capable of traversing.

EMR Standards

2008-11-13T19:52:00.000-08:00

EMR Standards

Though there are few standards for modern day EMR systems as a whole, there are many standards relating to specific aspects of EHRs and EMRs. These include:

ASTM International Continuity of Care Record - a patient health summary standard based upon XML, the CCR can be created, read and interpreted by various EHR or EMR systems, allowing easy interoperability between otherwise disparate enities.^[21]
ANSI X12 (EDI) - A set of transaction protocols used for transmitting virtually any aspect of patient data. Has become popular in the United States for transmitting billing information, because several of the transactions became required by the Health Insurance Portability and Accountability Act (HIPAA) for transmitting data to Medicare.
CEN - CONTSYS (EN 13940), a system of concepts to support continuity of care.
CEN - EHRcom (EN 13606), the European standard for the communication of information from EHR systems.
CEN - HISA (EN 12967), a services standard for inter-system communication in a clinical information environment.
DICOM - a heavily used standard for representing and communicating radiology images and reporting
HL7 - HL7 messages are used for interchange between hospital and physician record systems and between EMR systems and practice management systems; HL7 Clinical Document Architecture (CDA) documents are used to communicate documents such as physician notes and other material.
ISO - ISO TC 215 has defined the EHR, and also produced a technical specification ISO 18308 describing the requirements for EHR Architectures.
openEHR - next generation public specifications and implementations for EHR systems and communication, based on a complete separation of software and clinical models.

Various factors involving the timing, the right players, market history, utility, and governance play a key role in the overall enrichment of the standard and certification development. The standardization and certification even though seem to bring uniformity in the EMR development, do not guarantee their acceptability and sustainability in the long run. ^[22] In 2005 the US Federal Government awarded a contract to CCHIT - Certification Commission for Healthcare Information Technology to develop certification criteria for EMR. Starting in early 2007 vendors began to utilize these certification criteria for their EMR systems.

Electronic medical record

2008-11-12T19:34:00.000-08:00

Definition

The term has sometimes included other (HIT, or Health Information Technology) systems which keep track of medical information, such as the practice management system which supports the electronic medical record.

Issues

As of 2006, adoption of EMRs and other health information technology, such as computer physician order entry (CPOE), has been minimal in the United States, in spite of studies (such as Development of a Module for Point-of-care Charge Capture and Submission Using an Anesthesia Information Management System by David L. Reich, Ronald A. Kahn and David Wax, et al PMID 16810010) showing revenue gains after implementation. Fewer than 10% of American hospitals have implemented health information technology,^[2] while a mere 16% of primary care physicians use EHRs.^[3] The vast majority of healthcare transactions in the United States still take place on paper, a system that has remained unchanged since the 1950s. The healthcare industry spends only 2% of gross revenues on HIT, which is meager compared to other information intensive industries such as finance, which spend upwards of 10%.^[4] The following issues are behind the slow rate of adoption:

Interoperability

In healthcare, interoperability is the ability of different information technology systems and software applications to communicate, to exchange data accurately, effectively, and consistently, and to use the information that has been exchanged. ^[5]

In the United States, the development of standards for EMR interoperability is at the forefront of the national health care agenda.[3] EMRs, while an important factor in interoperability, are not a critical first step to sharing data between practicing physicians, pharmacies and hospitals. Many physicians currently have computerized practice management systems that can be used in conjunction with health information exchange (HIE), allowing for first steps in sharing share patient information(lab results, public health reporting) which are necessary for timely, patient-centered and portable care. There are currently multiple competing vendors of EHR systems, each selling a software suite that in many cases is not compatible with those of their competitors. Only counting the outpatient vendors, there are more than 25 major brands currently on the market. In 2004, President Bush created the Office of the National Coordinator for Health Information Technology (ONC), originally headed by David Brailer, in order to address interoperability issues and to establish a National Health Information Network (NHIN). Under the ONC, Regional Health Information Organizations (RHIOs) have been established in many states in order to promote the sharing of health information. Congress is currently working on legislation to increase funding to these and similar programs.

The Center for Information Technology Leadership described four different categories (“levels”) of data structuring at which health care data exchange can take place. ^[6] While it can be achieved at any level, each has different technical requirements and offers different potential for benefits realization.

The four levels are^[7]:

Level	Data Type	Example
1	Non-electronic data	Paper, mail, and phone call.
2	Machine transportable data	Fax, email, and unindexed documents.
3	Machine organizable data (structured messages, unstructured content)	HL7 messages and indexed (labeled) documents, images, and objects.
4	Machine interpretable data (structured messages, standardized content)	Automated transfer from an external lab of coded results into a provider’s EHR. Data can be transmitted (or accessed without transmission) by HIT systems without need for further semantic interpretation or translation.

Older record incorporation

To attain the wide accessibility, efficiency, patient safety and cost savings promised by EMR, older paper medical records ideally should be incorporated into the patient's record. The digital scanning >

Privacy

A major concern is adequate confidentiality of the individual records being managed electronically. According to the LA Times, roughly 150 people (from doctors and nurses to technicians and billing clerks) have access to at least part of a patient's records during a hospitalization, and 600,000 payers, providers and other entities that handle providers' billing data have some access.^[8] Multiple access points over an open network like the Internet increases possible patient data interception. In the United States, this class of information is referred to as Protected Health Information (PHI) and its management is addressed under the Health Insurance Portability and Accountability Act (HIPAA) as well as many local laws.^[9] In the European Union (EU), several Directives of the European Parliament and of the Council protect the processing and free movement of personal data, including for purposes of health care.^[10] The organizations and individuals charged with the management of this information are required to ensure adequate protection is provided and that access to the information is only by authorized parties. The growth of EHR creates new issues, since electronic data may be physically much more difficult to secure, as lapses in data security are increasingly being reported.^[11] Information security practices have been established for computer networks, but technologies like wireless computer networks offer new challenges as well.

Social and organizational barriers

According to the Agency for Healthcare Research and Quality's National Resource Center for Health Information Technology, EMR implementations follow the 80/20 rule; that is, 80% of the work of implementation must be spent on issues of change management, while only 20% is spent on technical issues related to the technology itself. Such organizational and social issues include restructuring workflows, dealing with physicians' resistance to change (or, alternatively, software engineers' evolving research in deep modeling of the physician's knowledge and workflow domains), as well as IT personnels' resistance to design and implementation flexibility needed in the complex healthcare environment, and creating a collaborative environment that fosters communication between physicians and information technology project managers. Exemplifying this need are several highly publicized HIT implementation failures, such as one at Cedars Sinai Medical Center in Los Angeles, in which physicians revolted and forced the administration to scrap a $34 million CPOE system ^[12] as well as others compiled at a collection of cases of health IT difficulties by medical informatics specialists.^[13] There are, however, several successful examples of EMR implementations in large hospitals, usually hospital systems that have had years of experience developing custom EMRs, for example the Veterans Administration hospital system, Kaiser Permanente's HealthConnect and the VistA EMR.

Technology limitations

Limitations in software, hardware and networking technologies has made EMR difficult to affordably implement in small, budget conscious, multiple location healthcare organizations. Until recently most EMR systems were developed using older programming languages such as Visual Basic and C++; however with many systems now being developed using Microsoft .NET Framework and Java technology EMRs can be securely implemented across multiple locations with greater performance and interoperability.^[14] Prior to the recent introduction of IEEE 802.11 g and n wireless technology access to large files such as MRI and X-Ray images was slow. With these new wireless technologies data can be securely transferred at speeds of up to 108 Mbit/s, across extended distances and in older buildings built with brick or concrete walls. Tablet PC technology has significantly improved over the recent years, Li-Ion/polymer batteries for battery life of up to 8 hours, biometric security, low-voltage processors and lighter weight solutions. For the new generation of Tablet PC, there are now EMRs that are fully handwriting capable^[15]

Preservation

Under data protection legislation and the law generally responsibility for patient records (irrespective of the form they are kept in) is always on the creator and custodian of the record, usually a health care practice or facility. The physical medical records are the property of the medical provider (or facility) that prepares them. This includes films and tracings from diagnostic imaging procedures such as X-ray, CT, PET, MRI, ultrasound, etc. The patient, however, according to HIPAA, owns the information contained within the record and has a right to view the originals, and to obtain copies under law.^[16] Additionally, those responsible for the management of the EMR are responsible to see the hardware, software and media used to manage the information remain usable and not degraded. This requires backup of the data and protection being provided to copies. It will also require the planned periodic migration of information to address concerns of media degradation from use.^[17]

Legal status

Medical records, such as physician orders, exam and test reports are legal documents, which must be kept in unaltered form and authenticated by the creator.

Digital signatures Most national and international standards accept electronic signatures.^[18] According to the American Bar Association, "A signature authenticates a writing by identifying the signer with the signed document. When the signer makes a mark in a distinctive manner, the writing becomes attributable to the signer."^[19] With proper security software, electronic authentication is more difficult to falsify than the handwritten doctor's signature. However, as the recent rise in identity theft demonstrates, no security method can totally prevent fraud, so auditing information security will continue to be prudent when using EMR.
Digital records such as EHR create difficulties ensuring that the content, context and structure are preserved when the records do not have a physical existence. As of 2006, national and state archives authorities are still developing open, non-proprietary technical standards for electronic records management (ERM).^[20]

from : wikipedia

Manajemen Proyek - Project Management

2008-10-12T21:05:00.000-07:00

Satu hal yang perlu diperhatikan dalam rangka membangun suatu sistem informasi rumah sakit yang handal adalah adanya dukungan dokumentasi melalui langkah atau proses manajemen proyek (Project Management). Jika anda mempertimbangkan sistim manajemen bisnis yang baru, anda mungkin akan perhatian terhadap waktu yang akan dihabiskan untuk mengimplementasikannya. Banyak sekali cerita cerita horor tentang implementasi yang melebihi anggaran dan tidak memenuhi kebutuhan bisnis mereka.
Metodologi implementasi yang menggunakan metode manajemen proyek yang keras, sehingga anda dapat melihat kemajuan dari proyek anda dalam setiap langkah. Dengan manajemen proyek yang tepat, akan senantiasa memberikan informasi terkini yang lengkap, risiko, anggaran yang telah terpakai, dan kritikal dari sistem metrik lainnya dari implementasi anda yang berlangsung terus-menerus. Dengan demikian dapat mempromosikan kesuksesannya melalui :

Transparency – Aktivitas dan jadwal sehingga anda dapat memantau apa yang terjadi dalam implementasi proyek.
Information – Komunikasi, laporan, dan pertemuan pertemuan reguler
Cooperation – Pengawasan dan pendelegasian tanggung-jawab
Setting and meeting requirements – Persetujuan, dokumentasi dan spesifikasi pelanggan

Manajemen proyek meliputi semua tahap, aktivitas dan tugas yang diperlukan melalui siklus implementasi. Tugas-tugas yang kami implementasikan kepada anda meliputi :

Planning - Penjadwalan dan prioritas bekerja dengan menggambarkan perencanaan termasuk estimasi dan alokasi dan sumber penghasilan.
Risk Management – Analisa dan monitoring resiko untuk mengurangi imbasnya dari keadaan yang tak terduga sebaliknya .
Issue Management – Manajemen yang tepatguna dan pengawasan dari setiap masalah proyek.
Status Reporting – Koordinasi komunikasi diantara anda, tim proyek, dan para supplier sebagai pihak ketiga.
Project Administration - Administrasi proyek yang menggunakan tools proyek manajemen.
Project Change Management - Evaluasi, penjadwalan dan pengaturan untuk setiap perubahan order yang muncul.

Unified Modeling Language

2008-10-10T22:14:00.000-07:00

One important step in development of hospital information system is to model the system with appropriate tool. The right tool is Unified Modeling Language (UML). Here is a short definition of UML :

Unified Modeling Language (UML) is a standardized general-purpose modeling language in the field of software engineering. UML includes a set of graphical notation techniques to create abstract models of specific systems, referred to as UML model.

There are many UML products, one of them can be downloaded from here: http://www.visual-paradigm.com/download/

Computer Simulation of Hospital Patient Scheduling Systems

2008-09-28T19:37:00.000-07:00

Gordon H. Robinson, Paul Wing, and Louis E. Davis

Abstract

A method of analyzing alternative systems of scheduling hospital admissions by means of a computer simulation is described. The simulation is divided into three programs, dealing sequentially with requests for admission, scheduling, and evaluation of costs of three basic scheduling systems and using the output of each phase of the simulation as input to the following phase. The feasibility of using the scheduling program in a real-time automated patient-scheduling system is discussed, with indications of adaptations required and additional functions that could be handled by the system.

Full text

Full text is available as a scanned copy of the original print version. Get a printable copy (PDF file) of the complete article (1.2M)

CARE2X | Open Source Healthcare System

2008-08-31T20:23:00.000-07:00

Care2x integrates data, functions and workflows in a healthcare environment. It is currently composed of four major components. Each of these components can also function individually.

HIS - Hospital/Healthservice Information System

PM - Practice (GP) management

CDS - Central Data Server

HXP - Health Xchange Protocol

The mission : to develop the most useful and practical integrated healthcare information system which is open for others to develop further.

The "Team" The development team has currently more than 100 members with different skills and backgrounds. They come from more than 20 nations. [ Credits list ][ Credits list with pictures ]
The Infrastructure The project development is supported by a solid infrastructure comprising several components which play important specific roles. See here.	History The project was started back in 2002 by a nurse with the public release of the first beta version. Detailed history can be read here.

Official release

This is the maintenance release of the 2nd Generation Deployment version 2.2. The release was made by Kaloyan Raev from Bulgaria. The most noticeable things it features are:

New graphical installer (based on MirrorMed's installer)

MySQL 5 support

Main menu visibility according to the user's permissions

Improved Arabian and Italian translations

Improved Turkish ICD10

There are many other improvements and fixes that can be found in the full change log:.

To download 2nd Generation 2.2 click here.

PHARMACY INFORMATION SYSTEMS

2008-07-07T06:30:00.000-07:00

Pharmacy information systems (PIS) are complex computer systems that have been designed to meet the needs of a pharmacy department. Through the use of such systems, pharmacists can supervise and have inputs on how medication is used in a hospital.

Some of the activities which Pharmacy Information Systems have been employed in pharmacy departments include:

Clinical Screening: The Pharmacy Information System can assist in patient care by the monitoring of drug interactions, drug allergies and other possible medication-related complications.

When a prescription order is entered, the system can check to see if there are any interactions between two or more drugs taken by the patient simultaneously or with any typical food, any known allergies to the drug, and if the appropriate dosage has been given based on the patient’s age, weight and other physiologic factors. Alerts and flags come up when the system picks up any of these.

Prescription Management: The Pharmacy Information System can also be use to mange prescription for inpatients and/or outpatients. When prescription orders are received, the orders are matched to available pharmaceutical products and then dispensed accordingly depending on whether the patient is an inpatient or outpatient.
It is possible to track all prescriptions passed through the system from who prescribed the drug, when it was prescribed to when it was dispensed.
It is also possible to print out prescription labels and instructions on how medication should be taken based on the prescription.
Inventory Management: Pharmacies require a continuous inventory culture in order to ensure that drugs do not go out of stock. This is made even more difficult when there are multiple dispensing points. When don manually it is very difficult to maintain an accurate inventory.
Pharmacy Information Systems aid inventory management by maintaining an internal inventory of all pharmaceutical products, providing alerts when the quantity of an item is below a set quantity and providing an electronic ordering system that recommends the ordering of the affected item and with the appropriate quantity from approved suppliers.
Patient Drug Profiles: These are patient profiles managed by the Pharmacy Information System and contain details of their current and past medications, known allergies and physiological parameters. These profiles are used for used for clinical screening anytime a prescription is ordered for the patient.
Report Generation: Most Pharmacy Information Systems can generate reports which range from determining medication usage patterns in the hospital to the cost of drugs purchased and /or dispensed.
Interactivity with other systems: It is important that Pharmacy Information Systems should be able to interact with other available systems such as the clinical information systems to receive prescription orders and financial information system for billing and charging.

NURSING INFORMATION SYSTEM

2008-07-07T06:28:00.000-07:00

Nursing information systems (NIS) are computer systems that manage clinical data from a variety of healthcare environments, and made available in a timely and orderly fashion to aid nurses in improving patient care.

To achieve this, most Nursing Information Systems are designed using a database and at least one nursing classification language such as North American Nursing Diagnosis (NANDA), Nursing Intervention Classification (NIC) and Nursing Diagnosis Extension and Classification (NDEC).

Some of the features that are provided by Nursing Information Systems include:

Patient Charting: A patient’s vital signs, admission and nursing assessments, care plan and nursing notes can be entered into the system either as structured or free text. These are the stored in a central repository and retrieved when needed.
Staff Schedules: Nurse can self schedule their shifts using scheduling rules provided in shift modules. The shifts can later be confirmed or changed by a scheduling coordinator or manager. Shift modules are designed to handle absences, overtime, staffing levels and cost-effective staffing.
Clinical Data Integration: Here clinical information from all the disciplines can be retrieved, viewed and analysed by nursing staff and then integrated into a patient’s care plan.
Decision Support: Decision support module can be added to Nursing Information Systems, and they provide prompts and reminders, along with guides to disease linkages between signs/symptoms, etiologies/related factors and patient populations. Online access to medical resources can also be made available.

There are benefits to be enjoyed by implementing Nursing Information Systems and they include:

Improved workload functionality: Staffing levels and appropriate skill mix per shift can be more easily determined by the shift modules. This leads to less time spent in designing and amending rosters.
Better care planning: Time spent on care planning is reduced, while the quality of what is recorded is improved. This makes for more complete care plans and more complete assessments and evaluations.
Better drug administration: Electronically prescribed drugs are more legible, thus making it less likely that drugs would be wrongly administered to patients.

Despite the benefits Nursing Information Systems have to offer, they are not widely used in healthcare and where they have been installed, they have not been readily accepted. This could probably due to lack of adequate training and failure of educate the end-user what the reasons are for its introduction. Moreover, very little research has been done to determine the cost benefits or cost effectives of such information systems.

CLINICAL INFORMATION SYSTEM

2008-07-07T06:23:00.000-07:00

A Clinical Information System (CIS) is a computer based system that is designed for collecting, storing, manipulating and making available clinical information important to the healthcare delivery process.

Clinical Information Systems may be limited in extent to a single area (e.g. laboratory systems, ECG management systems) or they may be more widespread and include virtually all aspects of clinical information (e.g. electronic medical records).

Clinical Information Systems provide a clinical data repository that stores clinical data such as the patient’s history of illness and the interactions with care providers. The repository encodes information capable of helping physicians decide about the patient’s condition, treatment options, and wellness activities as well as the status of decisions, actions undertaken and other relevant information that could help in performing those actions.

Some of the areas addressed by Clinical Information Systems are:

Clinical Decision Support: This provides users with the tools to acquire, manipulate, apply and display appropriate information to aid in the making of correct, timely and evidence-based clinical decisions.
Electronic Medical Records (EMRs): this contains information about the patient, from their personal details, such as their name, age, address and sex to details of every aspect of care given by the hospital (from routine visits to major operations)

.
Training and Research: Patient information can be made available to physicians for the purpose of training and research. Data mining of the information stored in databases could provide insights into disease states and how best to manage them.

For years, research has been done to show the value of Clinical Information Systems, and these have highlighted not just the benefits but also the barriers that might be faced by hospitals who implement such systems.

Some of the benefits are:

Easy Access to Patient Data: Clinical Information Systems can provide convenient access to medical records at all points of care. This is especially beneficial at ambulatory points, hence enhancing continuity of care. Internet-based access improves the ability to remotely access such data.
Structured Information: The clinical information captured in Clinical Information Systems is well organised, thus making I easier to maintain and quicker to search through for relevant information. The information is also legible, making it less likely that mistakes would be made due to illegible writing.
Improved Drug Prescription and Patient Safety: Clinical Information Systems improve drug dosing and this leads to the reduction of adverse drug interactions while promoting more appropriate pharmaceutical utilisation.

Despite the benefits being offered by Clinical Information Systems, they are not without the barriers that prevent them from being rolled out in every hospital. These include some of the following:

Initial cost of acquisition: the high cost of basic infrastructure of clinical information technology can be a stumbling block to many healthcare organisations.
Privacy and Security: There are still huge concerns in the healthcare industry about the privacy of patient data on computer systems and how to keep such information secure. The HIPAA and Data Protection Act passed by respective governments in the US and the UK were introduced to address some of these concerns.
Clinician Resistance: Clinicians usually have 10-20 minutes to see their patients and if their interactions with a CIS during these sessions proves to be counterintuitive by taking up more time than is necessary, there is bound to resistance to it use.
Integration of Legacy Systems: This poses a stiff challenge to many organisations.

source : biohealthmatics.com

HOSPITAL INFORMATION SYSTEMS

2008-07-07T06:19:00.000-07:00

A hospital information systems (HIS) is a computer system that is designed to manage all the hospital’s medical and administrative information in order to enable health professional perform their jobs effectively and efficiently.

Hospital information systems were first developed in the 1960s and have been an essential part in hospital information management and administration. Early systems consisted of large central computers connected to by dumb terminals, which are now being replaced by networked microcomputers. The systems were used to manage patient finance and hospital inventory.

Hospital information systems now focus on the integration of all clinical, financial and administrative applications and thus could also be called an integrated hospital information processing systems (IHIPS).

Components of a hospital information system consist of two or more of the following:

A look at the list above shows how complex a hospital information system can be. Advancement in computer technology and the development of information exchange standards such HL7 and DICOM, make the task administering and integrating such systems a little more easier.

No hospital information system can be regarded as a success unless it has the full participation of its users. Thus human and social factors would have to be considered in its design, more often than not, they can be easily addressed by providing adequate training and education about the system.

source : www.biohealthmatics.com

Recovery Data Secara Gratis & Mudah

2008-06-23T19:55:00.000-07:00

Sekarang banyak sekali bermunculan software recovery bahkan sebagian gratis, sampai kadang bingung ingin menggunakan aplikasi yang mana. Satu hal yang menggembirakan, bahwa banyak aplikasi recovery yang bersifat portable. Kita tinggal copy paste saja filenya dan bisa langsung jalan dari removable media seperti flashdisk, jadi tidak perlu proses instalasi khusus, sehingga bisa kita letakkan di flashdisk untuk persiapan bila suatu saat anda kehilangan data.

Di bawah ini akan diulas 3 dari sekian banyak software yang bersifat portable dan gratis.

Recover Files

Merupakan software recovery yang dapat digunakan untuk mengembalikan data yang sudah terhapus, baik dari recylce bin, network drive, compact flash card, portable drive, dari Window DOS, maupun Windows Explorer ketika menghapus dengan menekan tombol shift.

Sepertinya mustahil bukan? Memang benar jika anda belum mengetahui rahasianya. Saat kita memerintah Windows menghapus sebuah file, pada prinsipnya Windows tidak 'menghapus' file tersebut, tetapi menunggu sampai Windows perlu menulis kembali space hard drive yang sebelumnya ditempati oleh file tadi.

Recover Files melakukan scan secara seksama file-file yang masih 'tertinggal' pada hard drive dan/atau file-file yang masih punya cukup data tersisa untuk diselamatkan.

Oleh karena itu, keberhasilan recovery semakin besar jika anda semakin cepat me-recover file yang terhapus; juga semakin kecil ukuran file semakin besar kemungkinan diselamatkan. Recover Files sangat berguna ketika anda akan mengembalikan data yang baru saja terhapus.

Recover Files memiliki keunggulan ukuran kecil (553 KB), proses cepat, tampilan sederhana dan mudah dipahami serta praktis karena hanya single exe saja.

Aplikasi ini bisa berjalan di Windows 95, 98, Me, NT, 2000, XP, 2003, Vista, dan mendukung format partisi NTFS dan FAT.
Software ini dapat didonload klik di sini atau di sini.

Recuva-File Recovery

Recuva (diucapkan "recover") merupakan freeware windows utility untuk merestore files yang sudah terhapus dari komputer, termasuk dari recycle bin, memory card atau MP3 player. Dapat juga diakibatkan karena komputer crash, virsu dan sebagainya.

Seperti Recover Files, aplikasi ini juga hanya single exe, tinggal copy paste saja, ukurannya relatif kecil (776 KB), proses juga cepat. Untuk tampilan tidak selengkap Recover Files.
Software ini dapat didonload dengan klik di sini atau di sini.

DataRecovery

DataRecovery merupakan freeware yang dibuat oleh programmer TOKIWA (dari Jepang) untuk recovery aplikasi yang telah terhapus, misalnya dari recycle bin. Aplikasi ini hanya single exe, dengan ukuran sekitar 199 KB dan tampilan sederhana, tapi proses scan sangat cepat.

Sistem operasi yang didukung adalah Windows 9x, Me, NT4, 2000, XP dan Vista.

Fasilitas utama yang disediakan adalah:
- Mendukung FAT12, FAT16, FAT32, NTFS
- Undelete NTFS compressed files
- Undelete EFS encrypted files
- Fasilitas wipe out files, untuk menghapus file supaya tidak bisa direcovery lagi
- Pencarian sebagian string/ text dalam file
Software ini dapat didonload dengan klik di sini atau di sini.

Kemandirian dalam Software Development :: Mampukah?

2008-06-17T20:06:00.000-07:00

Seperti layaknya sebuah sistem pada umumnya, sistem informasi di rumah sakit juga memiliki kesamaan dalam beberapa hal. Dalam hal ini point yang sangat penting adalah bahwa sistem informasi rumah sakit akan selalu berubah mengikuti perkembangan. Ada hal-hal atau permasalahan yang dulunya belum muncul kemudian pada saatnya nanti menjadi masalah yang keberadaannya akan mempengaruhi kinerja sistem. Sebagai contoh, mungkin pada awalnya sistem yang sangat vital adalah billing system, di mana pada prinsipnya adalah merupakan dokumentasi transaksi perawatan dan pengobatan dari pasien. Adalah tidak begitu sulit untuk merekapitulasi semua tindakan perawatan dan pengobatan yang dilakukan terhadap pasien dan tidak memandang atau memperhatikan clinical pathway, atau yang selama ini sudah berjalan yaitu fee for service. Kemudian tentunya akan menjadi masalah terutama bagi penanggung biaya pihak ketiga, yaitu asuransi kesehatan, karena menurut pandangan mereka bisa jadi dengan konsep perawatan yang tertata dengan baik (seperti clinical pathway) akan dapat menurunkan jumlah biaya perawatan pasien.

Seandainya suatu rumah sakit sudah menerapkan software komputer (billing) dengan konsep pembiayaan fee for service, tentunya juga akan mengalami banyak kendala dan permasalahan untuk melakukan perubahan seperti yang diinginkan oleh pihak asuransi misalnya, karena bisa jadi software yang sudah ada harus dirombak total untuk dapat berjalan sesuai dengan yang dikehendaki. Masalah yang timbul diantaranya adalah siapa yang akan mengubah software tersebut, berapa biaya yang diperlukan, dan perlu waktu berapa lama untuk menyelesaikan.

Dari sini lah muncul gagasan agar setiap rumah sakit dapat mengembangkan software secara mandiri. Kemandirian ini tentunya perlu didukung adanya fasilitas-fasilitas yang memadai baik infrastruktur hardware dan software development tool dan yang tak kalah penting tentunya sumber daya manusia yang memadai. Diharapkan dengan adanya kemandirian ini, rumah sakit dapat dengan tidak susah payah untuk selalu mengikuti perubahan baik internal maupun eksternal.

Beberapa hal yang perlu diperhatikan dalam mewujudkan kemandirian ini adalah:

Kebutuhan hardware (komputer dan jaringan) yang perlu perencanaan yang baik karena selalu mengalami perubahan.
Kebutuhan software dasar (terutama sistem operasi dan RAD Tool) guna mengembangkan aplikasi sistem informasi rumah sakit itu sendiri. Harus ada pilihan apakah akan menggunakan lisensi atau open source semacam Linux.
Adanya sumberdaya manusia yang cakap dan profesional yang minimal terdiri dari network and harware specialist, system and database analyst, serta programmer
Adanya sarana untuk mengembangkan kemampuan sumber daya manusia dalam bidang TI misalnya dengan pelatihan
Perencanaan anggaran dan biaya yang baik.

Kalau kita perhatikan, memang sangat tidak mudah untuk mewujudkan hal seperti di atas. Namun apakah kita ingin berada di satu posisi untuk selamanya?

Bux.to

2008-06-16T23:02:00.001-07:00

Before you create an account at bux.to you must create an account at Alertpay.com

Welcome to Bux.to

At Bux.to, you get paid to click on ads and visit websites. The process is easy! You simply click a link and view a website for 30 seconds to earn money. You can earn even more by referring friends. You'll get paid $0.01 for each website you personally view and $0.01 for each website your referrals view. Payment requests can be made every day and are processed through AlertPay. The minimum payout is $10.00.

Earnings Example
» You click 10 ads per day = $0.10
» 20 referrals click 10 ads per day = $2.00
» Your daily earnings = $2.10
» Your weekly earnings = $14.70
» Your monthly earnings = $63.00

Open Source?

2008-05-09T22:18:00.000-07:00

The Open Source Definition

Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply with the following criteria:

1. Free Redistribution

The license shall not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license shall not require a royalty or other fee for such sale.

Rationale: By constraining the license to require free redistribution, we eliminate the temptation to throw away many long-term gains in order to make a few short-term sales dollars. If we didn't do this, there would be lots of pressure for cooperators to defect.

2. Source Code

The program must include source code, and must allow distribution in source code as well as compiled form. Where some form of a product is not distributed with source code, there must be a well-publicized means of obtaining the source code for no more than a reasonable reproduction cost preferably, downloading via the Internet without charge. The source code must be the preferred form in which a programmer would modify the program. Deliberately obfuscated source code is not allowed. Intermediate forms such as the output of a preprocessor or translator are not allowed.

Rationale: We require access to un-obfuscated source code because you can't evolve programs without modifying them. Since our purpose is to make evolution easy, we require that modification be made easy.

3. Derived Works

The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software.

Rationale: The mere ability to read source isn't enough to support independent peer review and rapid evolutionary selection. For rapid evolution to happen, people need to be able to experiment with and redistribute modifications.

4. Integrity of The Author's Source Code

The license may restrict source-code from being distributed in modified form only if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software.

Rationale: Encouraging lots of improvement is a good thing, but users have a right to know who is responsible for the software they are using. Authors and maintainers have reciprocal right to know what they're being asked to support and protect their reputations.

Accordingly, an open-source license must guarantee that source be readily available, but may require that it be distributed as pristine base sources plus patches. In this way, "unofficial" changes can be made available but readily distinguished from the base source.

5. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

Rationale: In order to get the maximum benefit from the process, the maximum diversity of persons and groups should be equally eligible to contribute to open sources. Therefore we forbid any open-source license from locking anybody out of the process.

Some countries, including the United States, have export restrictions for certain types of software. An OSD-conformant license may warn licensees of applicable restrictions and remind them that they are obliged to obey the law; however, it may not incorporate such restrictions itself.

6. No Discrimination Against Fields of Endeavor

The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research.

Rationale: The major intention of this clause is to prohibit license traps that prevent open source from being used commercially. We want commercial users to join our community, not feel excluded from it.

7. Distribution of License

The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.

Rationale: This clause is intended to forbid closing up software by indirect means such as requiring a non-disclosure agreement.

8. License Must Not Be Specific to a Product

The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution.

Rationale: This clause forecloses yet another class of license traps.

9. License Must Not Restrict Other Software

The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software.

Rationale: Distributors of open-source software have the right to make their own choices about their own software.

Yes, the GPL is conformant with this requirement. Software linked with GPLed libraries only inherits the GPL if it forms a single work, not any software with which they are merely distributed.

10. License Must Be Technology-Neutral

No provision of the license may be predicated on any individual technology or style of interface.

Rationale: This provision is aimed specifically at licenses which require an explicit gesture of assent in order to establish a contract between licensor and licensee. Provisions mandating so-called "click-wrap" may conflict with important methods of software distribution such as FTP download, CD-ROM anthologies, and web mirroring; such provisions may also hinder code re-use. Conformant licenses must allow for the possibility that (a) redistribution of the software will take place over non-Web channels that do not support click-wrapping of the download, and that (b) the covered code (or re-used portions of covered code) may run in a non-GUI environment that cannot support popup dialogues.

Sistem :: Sekumpulan Prosedur/ Elemen

2008-05-04T23:07:00.000-07:00

Sebelum diulas tentang pengertian dari sistem informasi perlu dijelaskan dulu pengertian sistem. Untuk memaparkan pengertiansistem, ada dua pendekatan yang dapat ditempuh, yaitu yang pertama menggunakan pendekatan yang menekankan pada prosedur dan yang kedua menekankan pada elemen atau komponen yang terlibat dalam sistem.

Pengertian sistem menggunakan pendekatan yang menekankan pada prosedur yaitu bahwa sistem adalah suatu aringan kerja dari prosedur-prosedur yang saling berhubungan bersama-sama untuk melakukan suatu kegiatan atau untuk menyelesaikan suatu sasaran tertentu. Contoh penerapan dalam rumah sakit misalnya prosedur pendaftaran pasien, prosedur pemeriksaan pasien di klinik, prosedur rawat inap, prosedur pemberian resep obat, prosedur pembayaran di kasir dan lain-lain.

Sedangkan pengertian sistem menggunakan pendekatan yang menekankan pada elemen atau komponen dari sistem yaitu bahwa sistem adalah sekumpulan unsur atau elemen yang saling berkaitan dan saling memepengaruhi dalam melakuka kegiatan bersama untuk mencapai suatu tujuan. Contoh dalam rumah sakit misalnya ada unsur pasien itu sendiri, petugas medis, ruang perawatan, penunjang medis, petugas administrasi dan lain-lain.

Biasanya pendekatan sistem yang menekankan pada elemen atau komponen akan lebih mudah untuk tujuan analisis dan perancangan sistem.

Hospital information system implementation is not all about information technology; it is about transforming clinical and business practices.

Sistem Informasi di rumah sakit merupakan sekumpulan dari banyak sub sistem dapat disamakan seperti pengabungan dari sistem informasi perbankan, sistem informasi inventori, sistem informasi perhotelan dan sebagainya. Sungguh komplek.

Kita mulai dari Rumah Sakit

2008-04-29T22:00:00.000-07:00

Rumah sakit saat ini adalah lembaga pelayanan, bermotif sosial dengan pendekatan korporasi yang menggunakan prinsip organisasi modern dan berpatokan pada:

Efisien

Efektif

Keselamatan pasien

Kegiatan rumah sakit sangat dipengaruhi oleh dinamika lingkungan (internal maupun eksternal) dan selalu berupaya tetap survive.

Selain itu rumah sakit juga merupakan sebentuk organisasi dengan sistem yang kompleks terdiri atas berbagai subsitem dan juga merupakan bagian dari sistem yang lebih besar serta merupakan organisasi padat modal yang terdiri dari modal kapital, material, SDM, sosial dan informasi. Maka dari itulah rumah sakit pun mulai mengadopsi metode dan teknologi untuk mengelola informasi yang pada ujungnya bertujuan agar lebih efektif, efisien dan menjamin keselamatan pasien.

Teknologi informasi adalah metode dan teknik yang digunakan untuk pengelolaan dan penarikan informasi secara otomatis. Teknologi ini dapat melakukan transformasi dari sekumpulan data menjadi sebentuk informasi yang berguna dan dapat digunakan sebagai suatu pengetahuan yang bermanfaat. Komponen dari teknologi informasi yang dapat dimanfaatkan khususnya di rumah sakit minimal ada tiga hal yaitu, perangkat keras, perangkat lunak, dan media jaringan dan komunikasi yang dapat untuk mengintegrasikan keseluruhan subsistem yang ada.

Satu hal yang terpenting adalah bahwa TI ini hanyalah salah satu bagian dari sistem informasi yang ada di rumah sakit. Komponen yang mempengaruhi sistem informasi rumah sakit adalah SDM, data yang akan diolah, prosedur yang berlaku, manajemen rumah sakit itu sendiri dan TI.

Ada enam komponen penting TI di rumah sakit yaitu:

Pelayanan
Penelitian
Kehidupan dan pengalaman dokter, perawat
Keamanan dan reliabilitas akses data
Struktur TI, tata kelola, dan pendanaan
Otimisasi keahlian TI bagi SDM di rumah sakit

Sumber : Anis Fuad

Sinforsa :: Sistem Informasi Rumah Sakit (SIMRS)

2008-04-22T23:28:00.000-07:00

Salam.
Sinforsa :: Sistem Informasi Rumah Sakit (SIMRS)
Di sini kita akan berbicara dan diskusikan tentang sistem yang berjalan di rumah sakit pada umumnya, terutama rumah sakit di Indonesia.
Berikut saya kutipkan artikel dari sebuah blog milik saudara Anjar Priandoyo (priandoyo.wordpress.com)

Sistem informasi rumah sakit terbaik?

Mei 4, 2007 — priandoyo

Ceritanya begini, suatu hari saya terlibat diskusi dengan seorang teman (sebut saja Jono umur 40-an, menikah 2 anak) yang kebetulan bekerja di Health Science Industry, dalam hal ini Rumah Sakit ternama. Iseng-iseng saya tanya kenapa pakai aplikasi XXX ini? kebetulan RS teman saya ini punya budget yang hampir unlimited untuk membeli tetek bengek keperluan rumah sakit.

“Waktu itu udah beauty contest juga, terus yang paling OK ya aplikasi XXX ini mas”
“Oh gitu, emang market leadernya di SI rumah sakit ini apa pak?” Rasa ingin tahuku kembali muncul.
“Engg siapa ya…” Jono terdiam sebentar, berpikir.
“Repot ya pak kalau industri spesifik seperti ini, nyari market leadernya aja ga ada” Saya bercanda sekenanya.
“Oh ada pak, NovaSprint, paling bagus itu untuk RS. Kita panggil juga dia di beauty contest, dah overview segala. Tapi punya Novasprint tergolong mahal, jadi kita ga pake dia” Pak Jono kemudian mendongeng sedikit tentang cerita vendor selection di RS-nya
“Saya tahu Novasprint pak, yang singapore punya itu ya? saya dengar memang bagus, leader dia”

Dalam prakteknya dilapangan, masalah vendor selection ini merupakan masalah yang cukup pelik. Beda kalau produk yang dibeli harganya sudah fix, semisal mobil 4WD untuk ditambang. Meskipun dalam skala mass project pun angka mobil 4WD ini masih bisa dibayangkan. Tapi kalau harus Sistem Informasi, kalau harus konsultasi marketing, kalau harus strategic management. Masalah pricing seharusnya berapa ini bisa jadi rumit.

Lha wong jangankan SI kelas gurem, major ERP macem Oracle atau SAP pun berani banting-bantingan harga biar bisa masuk ke satu perusahaan.
“Ya kita berani rugi Njar, biar dapet untung lebih gede belakangan”

Sebenarnya ada satu cara yang paling gampang yaitu menyewa konsultan untuk proses pembelian, vendor selection dkk. Contoh, Pemerintah Amerika menyewa Accenture, untuk menjadi konsultan, biar pemerintah Amerika bisa dapet barang yang kualitasnya bagus. Tapi apa yang terjadi, justru Accenture melakukan penipuan dengan bekerja sama dengan vendor. Jreng-jreng Accenture dituntut $30 juta. Detail ceritanya di tulisannya Aresto. Repot kan, ini untuk dikampung orang, apalagi di Indonesia kan, harusnya hal beginian lebih parah disini. Ga perlu diajarin lah ma Accenture luar.

Nah berkaitan dengan itu, kalau pertanyaan ini ditujukan kepada saya. Bagaimana cara vendor selection yang paling baik, saya jawab:
“…Cari aja forum, asosiasi atau independent yang bisa kasih review dan pricing strategi aplikasi tersebut. Suruh mereka buka harganya berapa. Dalilnya dalam industri yang sama tidak mungkin terjadi gap yang besar…”

Berikut sedikit (sekali) data yang saya miliki tentang peta Sistem Informasi Rumah Sakit. Setahu saya, sebagian besar SI RS didevelop sendiri oleh rumah sakit tersebut. Mungkin ada yang ingin menambahkan?

Buy / Package
1. Novasprint (Successfull client: RS Pondok Indah)
Price: IDR 1.5M, Unlimited user, Hospital Transactional Only

2. Qpro Sukses Mandiri (Best ISV by Microsoft Indonesia)
Price: <>

In house Development
1. RS Pertamina Jaya, Cempaka Putih: Suse, Postgre
Price: IDR?

Ditulis dalam My Work.

22 Tanggapan ke “Sistem informasi rumah sakit terbaik?”

Ranggi Berkata:
Mei 4, 2007 pukul 3:54 am
wah mas… utk pembahasan massalah yg ini saya bener-bener ngga ngerti sama istilah-istilah nya… hehehehehe
idrianita Berkata:
Mei 4, 2007 pukul 6:03 am
Sepertinya hal ini masalah klasik terjadi dalam pembelian barang IT ya Mas. Mungkin tidak cuman di RS. Sudah mau milih vendor , spec yang dibutuhkan belum jelas. Berhubung budget unlimited semua dibeli…..maunya yang terbagus……tapi menurut siapa, kriterianya apa?, Ini lah awal kejadian resource IT berlebih tapi ga bisa support kegiatan bisnis. Alias pengadaan IT tidak selaras dengan tujuan bisnis he…..he….
Yang begini bakal jadi proyeknya Mas Anjar….
Tonny - PT.Rent@Soft Berkata:
Mei 5, 2007 pukul 4:01 am
Menurut saya, baik buruknya suatu sistem RS, tidak bisa dintinjau melulu dari sisi feature sistem tsb.

Antara 1 RS dan RS lainnya, berbeda SOP-nya. SIM RS yang baik menurut saya adalah yg paling match dengan SOP rumah sakit bersangkutan.

Karena saya juga sudah sering dengar baik NOVA maupun QPRO juga ada success story tapi juga ada sad story di-mana2. Jadi gak bisa dipukul rata penilainnya…….

SAP aja juga blm tentu bisa selalu sukses implementasinya. Dan harga di atas juga tidak bisa dijadikan patokan, karena biasanya yg paling mahal bukan harga softwarenya, tapi implementation cost-nya. Nah, ini yang sering dilupakan.

Kenapa implementation cost RS di Indonesia tinggi, salah satu penyebabnya menurut saya adalah karena SOP yang tidak standard dan baku.

Kalo SOP-nya saja bermasalah, gimana bisa punya IT yang bagus. Nah di dalam kasus RS bermasalah SOP tsb, saya yakin NOVA pun bisa fail…………………….

Terima kasih atas kesempatannya Mas Anjar, good article…………….
defindal Berkata:
Mei 5, 2007 pukul 9:59 am
tergantung sapa yang bisa ngasi persenan lebih gede kan ? :D
Tonny Loekito, PT.Rent@Soft Berkata:
Mei 6, 2007 pukul 1:57 pm
Menurut saya sim-rs terbaik, adalah yg match dengan kebutuhan dan SOP di RS bersangkutan.
Jadi antara 1 RS dan RS lainnya, bisa berbeda.
Kalo melulu hanya melihat merk, blm tentu menjamin keberhasilan juga.

Kalo dari segi features, saya setuju NOVARTIS bagus, tapi kalo dari segi implementasi, saya juga sudah sering mendengar ttg success story maupun sad story ttg software2 ini, termasuk QPRO.

Kalo dari segi harga, kebanyakan proyek sim-rs di Indonesia, kurang memperhatikan ttg implementation costs. Padahal cost inilah yang biasanya membengkak.

Harga softwarenya gak seberapa, tapi implementation cost bisa membludak sampe 4/5 x harga softwarenya.
Jadi sekali lagi harga software gak bisa untuk patokan cost.

Inti permasalahan adalah karena kebanyakan SOP RS di Indonesia gak baku dan standard. Sehingga implementasinya bisa painfull, karena proses customizing yang rumit.
Research INDC cukup memberi bukti bahwa implementasi application software –> 70% fail (fail to meet the deadline, etc).

Ttg hire konsultan untuk pembelian, saya setuju banget. Jadi bisa lebih obyektif, moga2, gak melulu ngeliat amplopnya……….he9x

Semoga bisa memberi pencerahan.
For Mas Anjar : good article……………………..
Dr. Andien Berkata:
Oktober 2, 2007 pukul 3:24 am
Saya dari rumah-sakit swasta yang sudah menggunakan jasa dan produk SIM-RS dari QPRO dan semua berjalan dengan lancar dan dalam tempo kurang dari 6 bulan sistem tersebut sudah running well. Kami salut dengan metoda implementasi yang digunakan oleh QPRO sehingga pihak kami dengan mudah mengikuti proses implementasi tersebut. Dalam pertemuan dengan kolega di rumah sakit malahan ada yang menyebutkan produk QPRO kualitas internasional harga lokal. Bravo untuk QPRO dan tim
Dr. Lastri Berkata:
Oktober 4, 2007 pukul 11:11 pm
Saya salah satu pengembang SIM RS lokal , dan alhamdulillah sudah sukses dipakai di 17 Rumah Sakit di Jabodetabek , menyusul beberapa rumah sakit yang lagi taraf negosiasi . SIM RS tidak dibuat hanya untuk mengcover front office saja ( transaction modul only ) tetapi memuat proses back office ( sampai GL /payroll ) dan terutama report medis yang berbasis patient base (electronic medical record , RL 1-6 , BOR , LOS , dll ) . Setiap RS punya SOP sendiri - sendiri yang rata - rata tidak sama , karena itu saya menyediakan fasilitas customizasi sebelum implementasi disesuaikan dengan proses bisnis masing masing rumah sakit . Fitur - fitur yang ada tidak kalah dengan vendor dari luar , justru kami mendevelopnya disesuaikan dengan iklim bisnis Rumah Sakit di Indonesia . Selain design dalam windows kami juga menyediakan dalam webbase didukung oleh teknologi .NET . Multiuser , Multitarif , Full Integrated System , dan masih banyak fasilitas lain yang tidak Anda dapatkan di SIM RS yang lain . Implementasi biasanya antara 2 sampai 6 bulan tergantung kemampuan rumah sakit . Harga cukup ekonomis dibandingkan vendor diatas , bahkan saya menyediakan sistem KSO untuk klinik atau rumah sakit yang berminat .Saya berharap kedepan , semua pelayanan kesehatan di Indonesia dapat mengakses SIM RS dengan harga terjangkau dan aplicable . Untuk informasi lebih lanjut bisa kontak langsung ke 0813 8001 88 80 ( dr_lastri ).
haryanto Berkata:
Oktober 22, 2007 pukul 8:49 am
yang namanya jualan pasti yang ditampilkan adalah sukses story dan pasti menutup-nutupi fail storynya, tidak dipungkiri kami dari amandasoft (www.amandasoft.net) juga pernah mengalami kegagalan implementasi (kemoloran waktu) itu karena kita dihadapkan pada SOP rs yang cenderung tidak sama antara satu rs dan rs yang lain seperti yang diungkapkan oleh pak Tonny Loekito, PT.Rent@Soft, tapi kita juga pernah implementasi rs sudah jalan dalam waktu 2 bulan dari Front office sampai backoffice dikarenakan dukungan dari pihak management.
menurut saya ada beberapa yang menjadi faktor pendukung dari keberhasilan implementasi rs yaitu
1. tentu softwarenya harus bagus dan modulnya lengkap.
2. dukungan full dari pihak management.
3. kecakapan user dalam menggunakan sim rs
4. penyesuaian sop rs sebelum implementasi.
5. Dukungan tenaga medis konsultan (terutama dokter) dari vendor pembuat sim rs tersebut.

apabila kelima aspek itu terpenuhi maka SIM RS akan berjalan dengan baik dan benar, masalah SOP RS diindonesia sebenarnya hampir sama, mungkin hanya beda istilah saja antara satu rs dengan rs yang lain.

sekedar informasi untuk produk SIM-RS yang baik silahkan lihat di http://www.amandasoft.net
hawking Berkata:
Desember 26, 2007 pukul 12:08 pm
Ada beberapa aplikasi lain, jika berkeinginan menggunakan web based untuk produk teramedik. kalo nggak salah lihat di http://www.terakorp.com
I Made Arimbawa Berkata:
Januari 24, 2008 pukul 4:33 am
Saya adalah salah satu pengembang SIMRS sejak tahun 2003, dan saat ini produk yang kami kembangkan mempunyai brand “Medifirst2000″ dengan 18 modul terintegrasi.

Saya juga melihat bahwa SOP dari masing2 rumah sakit berbeda2 terutama masalah kebijakan di keuangan. Mungkin untuk masalah rekam medis pasien, mempunyai kemiripan dan biasanya implementasi di bagian ini (rekam medis pasien) bisa cuman 1 minggu. Tapi jika sudah masuk ke bagian keuangan, terutama Billing Pasien, apalagi sampai ke pembagian jasa dan REMUNERASI, itu akan memakan waktu. Yang saya lihat selama ini, disebabkan 3 faktor :
1. Perlakuan keuangan per rumah sakit mempunyai kebijakan sendiri, apalagi perbedaan antara RS Pemerintah (Baku tapi kadang tak sama untuk akuntansi) dengan RS Swasta pasti berbeda

2. Faktor SDM ; adalah faktor yang sangat menentukan. Operator dilapangan (entry data) adalah ujung tombak untuk jalannya SIMRS ini. Saya banyak melihat dilapangan karena ada “faktor-faktor tersembunyi” data pasien apalagi pembayaran (validasi) tidak diinput.

3. Software SIMRS yg baku tidak akan bs masuk, mengcover karakteristik rmah sakit. Jadi harusnya “Tailor Made”, customize sesuai karakteristik RS bersangkutan. Tapi kelemahan “Tailor Made” adalah proses pembuatan yg tidak singkat.

Kesimpulan terakhir saya :
Apabila RS pengen implementasi SIMRS, ada baiknya menggunakan sistem berikut :
1. KSO selama beberapa tahun, sehingga karakteristik RS tersebut tercover dan RS mempunyai kemandirian dengan mengembangkan personel/sdm di SIMRS tersebut. Intinya SIMRS memjadi produktif (software house), apalagi sekarang udah BLU
2. Jika ada suatu tender, ada baiknya RS menyiapkan Konsultan Perencana terlebih dahulu untuk mengakomodasi selama pengembangan. Klo tidak…bs cuman pasang…beres..bayar…berantakan.

Sebagai informasi tambahan, saya di PT Jasamedika Saranatama sejak tahun 2003 telah mengcover beberapa RS di JKT dan jawa barat (cianjur/cirebon). Yang terbaru, telah kami implementasikan di RSUD Karawang (kebayang rumsah sakitnya sebesar apa ?)- Sistem KSO 10 thn.
Kemudian RS Haji Surabaya ( 2006) sistem tender, dan berjalan dengan sangat baik, sekarang masuk masa maintenance. Kemudian RSU Kota Semarang(ketileng) tahun 2006 dengan sistem KSO 5 thn. Terakhir RSU Timika, akhir 2007, dengan sistem tender.

Melalui forum ini saya juga berharap, sistem IT di rumah sakit menjadi semakin baik yang tentunya akan lebih memuaskan pelayanan pasien.
Klo ada partner yg bisa sharing dengan saya bs via japri 08170298530 / 022-5436559

thx
Ferry ZK Berkata:
Januari 28, 2008 pukul 2:47 am
weks kenalnya koq sama qpro ma nova duank…

klo soal features sama sukses history yang paling bagus ya TrakHelath di sini dah implement di RS gropnya Ramsey seperti RSMI, RS Bintaro & RSSI, lom lagi di thailand, brazil, Afsel, Timteng, dll…

cuma masalahnya ya itu harganya selangit he.. he..
bsans Berkata:
Februari 6, 2008 pukul 6:58 am
komitmen yang tinggi dan tetap tinggi adalah modal dasar dari terlaksananya SIMRS-IT secara berkesinambungan. apapun software aplikasinya & seberapa lengkap modul ( jika dapat dikatakan modul ) yang ada didalamnya jika komitmen manajemen & pegawai tetapi tinggi maka SIMRS-IT akan tetap berjalan dengan baik.
apakah yakin dengan implementasi software aplikasi yang selama beberapa bulan saja dapat dikatakan sebagai suatu prestasi ? emang nya siapa yang menggunakan software tersebut ? pengembang atau pegawai ? pengembang dapat dikatakan berprestasi jika telah membina hubungan yang tidak lagi berdasarkan nilai - nilai di atas kertas. jumlah rumah sakit yang telah terimplementasi bukan suatu ukuran keberhasilan ( kalo pengalaman boleh lah … ).
bagi rumah sakit yang akan mengembangkan SIMRS-IT, saat ini belum ada standar biaya secara untuk software aplikasi SIMRS-IT, jadi berhati - hati lah…jalan keluarnya saat ini adalah menggunakan standar pembiayaan yang dikeluarkan oleh bapenas ( umumnya pengembang mmooohhh )
bagi pengembang SIMRS-IT, gunakan lah software aplikasi yang bebas lisensi…karena umumnya menggunakan software bajakan, contoh software yang sering dibajak adalah : Borland Dephi, Visual Basic, Visual .Net, Access, Clipper, Foxpro, dll ( software yang berbasiskan GUI ). jika anda menggunakan software bajakan dalam membuat program aplikasi SIMRS-IT maka anda ikut menjerumuskan orang lain ke dalam jurang ( itu baru software aplikasi nya loh belom lagi OS & Database ) … jadi jangan bangga jika masih menggunakan software bajakan !
orang yang paling mengerti tentang rumah sakit adalah pegawai rumah sakit itu sendiri … bukan orang lain …
haryanto Berkata:
Maret 1, 2008 pukul 2:09 am
memang setiap vendor SIMRS punya kelebihan dan kekurangan masing masing. Menurut pengamatan saya ada beberapa vendor yang sukses implementasi di rumah sakit tapi hanya bagian front office saja (pendaftaran pasien, rekam medis, r/j,r/i, farmasi dan penunjang medis ) dan sekedar informasi billinglah, tapi begitu menginjak backoffice seperti klaim, hutang, dan gl pada mentok. ini yang saya temui di beberapa rumah sakit. faktornya adalah mereka tidak melibatkan ahli akuntansi dalam implementasi ini, untuk implementasi backoffice programmer atau analyst yang jago koding tdklah cukup untuk melakukannya, harus ada mediator akunting yang pintar dalam melaksanakan implementasi, ini baru bisa berhasil.

sekedar informasi untuk produk SIM-RS yang baik silahkan lihat di http://www.amandasoft.net
haryanto Berkata:
Maret 1, 2008 pukul 2:15 am
saya tambahkan seperti komentar pak bsans, gunakan software lisensi, ada vendor yang jual SIMRS sangat mahal software databasenya masih memakai software bajakan, ini jelas melanggar dan mau untung sendiri, kalau Saya jualan biasanya saya paketin misalnya paket 10 pc sudah termasuk software original baik server maupun klient, dan ini memang menguntungkan kedua belah pihak.

sekedar informasi untuk produk SIM-RS yang baik silahkan lihat di http://www.amandasoft.net
henri_greenleaft Berkata:
Maret 4, 2008 pukul 6:45 am
sya juga termasuk pengembang lokal..meneurut saya pembuatab SIRS bukan cuma SIM RS harus melihat RSnya juga.. saya yakin kebutuhan setiap RS akan berbeda..kebutuhan tersebut tentu akan menentukan bugdet yang akan di keluarkan..terimakasih.
boed Berkata:
Mei 26, 2008 pukul 12:43 am
SIMRS terbaik itu tidak bisa dibandingkan.Sama seperti membandingkan mobil balap di sirkuit yang berbeda, cuaca yang berbeda. Mungkin mobil balap A sesuai dengan sirkuit yang sehingga menjadi nomor satu, akan tetapi belum tentu di sirkuit B. Untuk lebih mantap, tanyakan kepada lebih dari satu rumah sakit yang berhasil mengimplementasikan SIMRS, sehingga tidak terpaku pada satu vendor saja. Kumpulkan data - data yang lengkap dari internet atau dari media lain. Cari yang cocok dengan “sirkuit” (baca:rumah sakit) anda. Sehingga anda bisa mencari “setting mesing” yang cocok agak dapat maksimal dipacu di “sirkuit” anda. Sukses selalu
robert Berkata:
Mei 27, 2008 pukul 8:52 am
saya seorang pengembang SIM-RS Saya setuju denga Bp. I made. menurut pengalaman saya pembuatan aplikasi SIM-RS harus mengikutsertakan pihak manajemen rumah sakit itu sendiri, bukan sekedar budget yang besar, tanpa adanya kerjasama dan keterbukaan manajemen dengan pihak develop maka SIM-RS yang dibuat akan sia-sia saja. banyak terjadi beberapa rumah sakit mebuat SIM-RS padahal sebelumnya mereka sudah pernah membuat tapi tidak cocok dengan sistem manajemn rumah sakit yg ada.
jadi menurut saya pembuatan software Rumah sakit tidak harus fdari luar karena dari pengembang lokal pun sudah banyak yg memahami. dan harganya pun dapat terjangkau oleh pihak rumah sakit tinggal bagaimana kesepakan kerjasama antara pihak RS dengan pengembang sistem.
EDWARD HALIMI Berkata:
Juni 13, 2008 pukul 2:27 am
Rumah Sakit Kanker Dharmais sudah beberapa kali gagal membangun SIM-RS, sekarang ini sedang mencari calon-calon Vendor yang haldal. Jika anda berminat silahkan ajukan Proposal ke Direksi RS Kanker Dharmais Jakarta, siapa tau anda beruntung…..
M. Yaasiin Fadhilah Berkata:
Juli 15, 2008 pukul 5:20 am
Namanya juga marketing, apa lagi marketing freelance yang ga ngerti ttg software SIM-RS, biasanya selalu memberikan angin surga bagi setiap cln pembeli/phk owner Rumah Sakit, padahal ybs sendiri belum tentu sudah koordinasi terelebih dahulu dengan pihak yang mendevolp software tsb. Karena, mereka hanya mengeruk keuntungan berdasarkan fee belaka.

Artinya terkadang software sebagus apapun, kalo marketingnya tdk profesional, sungguh sangat merepotkan.
Good luck buat Amanandasoft Mitra Development
sudiono@MEDEEVA Berkata:
Juli 18, 2008 pukul 10:29 am
70% sistem rumah sakit yang masih berjalan dengan sistem manual walaupun ada sistem yang sudah diaplikasikan.

kendala ini terjadi dikarenakan integrasi yang tidak berjalan dan budget yang tidak diperhatikan dengan bijaksana.

dalam hal ini, diperlukan awareness dari team IT, jajaran Direksi dan Owner. terkait dengan itu adalah sejauh mana kebutuhan sistem tersebut diperlukan.
Kang Paku Berkata:
September 12, 2008 pukul 3:50 pm
baik bagusnya sebua softare SIM-RS akan tergantung pada pemegang regulasi pelaporan kesehatan di indonesia itu sendiri, kadang kala satu sistem berjalan dengan baik di rumah sakit a , tidak menjamin itu akan terjadi pada rumah sakit b, karena SOP yang ada dari tiap2 rumah sakit belum distandarkan yang akhirnya setiap pengadaan sistem informasi yang timbul adalkah mafia mafia tender dengan berbagai cara akhirnya masukal sebuah software tanpa memikirkan dampak yag lebih luas, software dalam negeri pun banyak yang bagus bahkanberjalan di skala rumah kaliber nasionaldan internasional masalahnya koneksitas, dan kekerabatan, saya punya pengelaman di rumah sakit aini jakarta…. masalahnya bisa cair dan bisa bubar oleh seorang pimpinan yayasan .
salam
dr rusmilah malati Berkata:
September 21, 2008 pukul 8:21 am
saya pengamat simrs di beberapa rumah sakit di indonesia,
saya mengamati beberapa vendor besar simrs yang sudah terkenal (exist di rumah2 sakit besar) katanya,

tapi kenyataaanya aplikasi mereka tidak berjalan baik di rumah-rumah sakit tersebut, aplikasi mereka hanya berjalan di bagian FRONT OFFICE saja. pada waktu implementasi backoffice mereka pada mentok dan banyak yang gagal. alasan mereka (vendor simrs red) pihak rumah sakit tidak koperatif, padahal menurut pengamatan saya pihak rumah sakit sudah cukup koperatif menerjunkan team terbaiknya.

Saran saya untuk membeli SIMRS TERBAIK, jangan terpaku demo dari vendor-vendor tersebut, carilah aplikasi yang benar benar sudah siap, lakukan test software tersebut sebelum memutuskan untuk membeli

salam.