Urged for tighter restrictions on cosmetic surgery

A summary of responses from patients, the public and industry has been published as part of the review set up after the PIP breast implant scandal.
A final report, by Sir Bruce Keogh, the NHS medical director leading the English review, is due in March 2013.
Cosmetic surgeons said procedures should not be sold as "a commodity".

For more information visit this link http://www.bbc.co.uk/news/uk-20850284

Is The Traditional PC Dead?

Personal Computer makers late to the mobile game were the big losers in 2012, as CNN's Maggie Lake reports.

Increasing Time Spent With Patients And Improving Relationships : A Better Bedside Manner With iPad

Bedside care is a vital part of health care professionals' relationships with their patients at the hospital. But the staff at hospital found that modern technology sometimes made those interactions more difficult. When Apple introduced iPad, physicians at the hospital knew they'd found a solution.
A custom iPad app enables physicians and nurses to perform important tasks from the bedside, increasing time spent with patients and improving relationships.
The inability to bring information to the bedside meant physicians had to constantly shuttle between patients and tethered PCs to get status updates, schedule surgeries, prescribe drugs, view X-rays, and perform other important tasks. Since the introduction of technology in this industry physicians have been tethered to devices like PCs and forced to go seek information. Even a laptop wasn't truly mobile.
With iPad, the hospital's doctors and nurses have bedside access to everything they need, and can remain in contact with patients and their families while viewing information that is critical to their care. They can answer patients' questions immediately and make decisions about what's going to be done, with the most current information available. Nothing beats being able to use an app to pull up an X-ray on the device.
Not only has iPad increased efficiency from a provider perspective—it's increased engagement between the provider and patient.

Drug And Medical Information Apps For iDevices

This article describes Apps for the iPod Touch, iPhone, and iPad that may be beneficial to pharmacy education and pharmacy practice. The purpose is to provide examples of the types of Apps available through the App Store to support teaching, learning, and practice and to help you become familiar with the various uses of an iDevice.

APP Description Cost
ACC Pocket
Guidelines
ACC Pocket Guidelines is a clinical practice support tool set from the American College of Cardiology Foundation that provides concise, portable reference tools for clinicians. Free

Antibiotic
Pharmacology
Antibiotic Pharmacology is a fully featured flash card app that helps you learn about antibiotic pharmacology.
Included in this app are:
+ Main Deck
+ Faves Deck
+ Ignore Feature
+ Shuffle Ability
+ Choice of Primary Side
+ Search Feature
+ Index
+ Beautiful, Easy-to-Use Interface
2.99

Davis’s Drug Guide
Davis’s Drug Guide for Mobile and Web delivers up‐to‐date, comprehensive, and practical information on over 5,000 trade name and generic drugs.
PLEASE NOTE: Application requires a paid subscription to the online Davis’s Drug Guide service.
Davis’s Drug Guide for Mobile + Web includes:
• Over 5,000 trade name and generic drug listings
• High-alert notices
• Risk Evaluation and Mitigation Strategies (REMS), highlighted by an icon
• Drug-drug, drug-natural, and drug-food interactions
• Discontinued drug list
• Unique optimization for iPad, iPhone, and iPod touch interfaces
• Universal Index Search – find terms across all indexes
• “Favorites” for bookmarking important entries
• Regular updates and Web access for one year
Free

Drugs and Meds: Pill and Drug
Identification
Drugs and Meds: Pill and Drug Identification is a glossary of the most common prescription drugs (USA‐based), with images of many of the drugs (in pill form mostly) to help you identify them based on image. 0.99

Epocrates
ePocrates is a mobile drug reference used by healthcare providers at the point of care. 0.99

The iPad’s Pros And Cons In A Health Care Setting

The iPad has been popular with health care providers. This is not too surprising, as doctors, nurses and other practitioners have been using the iPad's older sibling, the iPhone, for several years, for everything from voice recording to clinical data entry. Many argue that the iPad's larger screen sets the stage for even more clinical uses.
The iPad has pros and cons associated with its use in health care. Several characteristics explain the rapid pace of iPad adoption among health care providers:
• The iPad is roughly the same size as patient charts.
• It has a large screen that can be used to share information with patients.
• The price makes it affordable for physicians.
• It can run all the medical apps available on the iPhone.
• It can be used to enter data into EHR and computerized physician order entry (CPOE) systems.

On the other hand, problems associated with iPad use in health care include the following:
• It might not be durable enough, and is difficult to disinfect.
• It does not run Flash, the Adobe Systems Inc. platform on which the majority of the Web's video is developed.
• It does not support USB devices or printers.
• It has no camera.
• Its free-form factor could give rise to ergonomic issues and security breaches -- though these issues could arise with the use of any tablet device.

Architecture of Android OS



Android uses Linux for its memory management, process management, networking, and other operating system services. The Android phone user will never see Linux or in other words our application will not make Linux calls directly.
Some parts of Android will be familiar, such as the Linux Kernel, OpenGL, and the SQL database. Others may be completely foreign, such as Android's idea of the application life cycle. You'll need a good understanding of these key concepts in order to write well-behaved Android applications. 

The Android OS is roughly divided into five sections in four main layers:
  • Linux kernel — This is the kernel on which Android is based. This layer contains all the lowlevel device drivers for the various hardware components of an Android device. Android uses Linux for its device drivers, memory management, process management, and networking. However you will never be programming to this layer directly.
  • Libraries — These contain all the code that provides the main features of an Android OS. Forexample, the SQLite library provides database support so that an application can use it fordata storage. The WebKit library provides functionalities for web browsing. They are all written in C/C++ internally, but you'll be calling them through Java interfaces.
  • Android runtime — At the same layer as the libraries, the Android runtime provides a set of corelibraries that enable developers to write Android apps using the Java programming language. The Android runtime also includes the Dalvik virtual machine, which enables every Android application to run in its own process, with its own instance of the Dalvik virtual machine (Android applications are compiled into the Dalvik executables). Dalvik is a specialized virtual machine designed specifically for Android and optimized for battery-powered mobile devices with limited memory and CPU.
  • Application framework — Exposes the various capabilities of the Android OS to application developers so that they can make use of them in their applications.
  • Applications — At this top layer, you will find applications that ship with the Android device (such as Phone, Contacts, Browser, etc.), as well as applications that you download and installfrom the Android Market. Any applications that you write are located at this layer.

Android Devices in the Market



Android devices come in all shapes and sizes. The Android OS can be seen powering the following types of devices:
  • Smartphones
  • Tablets
  • E-reader devices
  • Netbooks
  • MP4 players
  • Internet TVs
Chances are good that you own at least one of the preceding devices. The Samsung Galaxy S, the HTC Desire HD, and the LG Optimus One smartphones.
Another popular category of devices that manufacturers are rushing out is the tablet. Tablet sizes typically start at seven inches, measured diagonally.The Samsung Galaxy Tab and the Dell Streak, which is a fiveinch phone tablet.
Besides smartphones and tablets, Android is also beginning to appear in dedicated devices, such as e-book readers. The Barnes and Noble’s NOOKcolor, which is a color e-Book reader running the Android OS.
In addition to these popular mobile devices, Android is also slowly finding its way into your living room. People of Lava, a Swedish company, has developed an Android-based TV, call the Scandinavia Android TV.

What is Android?

Android is a free phone operating system that aims to get all kinds of phones running like computers and, most importantly, connecting to the web. It's been developed primarily by Google, though others have helped, and it's a project that's constantly updating, growing, and getting a new look. In this chapter, you'll learn what makes Android different from iPhones, BlackBerry phones, and other so-called smartphones.
Android is a version of the very free and open Linux operating system, but tailored for a computer that has just a few buttons and a touch-sensitive screen. It's not a single phone or line of phones, like Apple's iPhone, though the Verizon/Motorola Droid model might make you think that. Put simply, Android is a bundle of code, mostly developed by Google, that allow phones with small screens and tiny chips to do great things.

Android Features
You can have the My Tracks app follow you via GPS and record your progress on a map, or in a spreadsheet. You can listen to your MP3s or streaming podcasts, read and respond to emails, and get turn-by-turn directions as you walk around a city you don't know—all at the same time. If you can't do something, there's a good chance an app in the Android Market can do it, and you can download it at any time.
Sure, you can browse the web, make phone calls, and send text messages (or SMS, for the purposes of this guide), but you can do that on most any phone these days. What makes Android different are the features such as sync with Google, true multi-tasking, get totally customized, and use open software.
As Android is open source and freely available to manufacturers for customization, there are no fixed hardware and software configurations. However, Android itself supports the following features:
  • Storage — Uses SQLite, a lightweight relational database, for data storage.
  • Connectivity — Supports GSM/EDGE, IDEN, CDMA, EV-DO, UMTS, Bluetooth (includesA2DP and AVRCP), WiFi, LTE, and WiMAX.
  • Messaging — Supports both SMS and MMS.
  • Web browser — Based on the open-source WebKit, together with Chrome’s V8 JavaScript engine
  • Media support — Includes support for the following media: H.263, H.264 (in 3GP or MP4container), MPEG-4 SP, AMR, AMR-WB (in 3GP container), AAC, HE-AAC (in MP4 or3GP container), MP3, MIDI, Ogg Vorbis, WAV, JPEG, PNG, GIF, and BMP
  • Hardware support — Accelerometer Sensor, Camera, Digital Compass, Proximity Sensor, and GPS
  • Multi-touch — Supports multi-touch screens
  • Multi-tasking — Supports multi-tasking applications
  • Flash support — Android 2.3 supports Flash 10.1.
  • Tethering — Supports sharing of Internet connections as a wired/wireless hotspot

After a few days with an Android phone—about a week of inquisitive use—you'll probably get used to how Android wants to get your data to you, and how you can get at the things you want.

HIS : Splitting A Large and Complex System Into Simpler Sub-systems

In the development of the hospital information system would be better if done through a modularization into several sub-systems. For example, in this paper we split into the following subsystems:
- Personlia
- Registration of patients coming
- Outpatient and / or ER
- Radiology and Laboratory Examination
- Inpatient
- Pharmacy
- Cashier
Modularization aims to facilitate the management of the hospital information system to be developed. By splitting a large and complex systems into simpler sub-systems will certainly be developed by several different teams at the same time, which would certainly speed up the development process. Surely that must be considered is the integration of sub-systems are interconnected.
Of the sub-system that we have designed the above will be used to construct an appropriate database schema. Each sub-system is expected to be made of the database schema, and will be even better, for further development, if in each sub-system create the database schema on each server hardware.
In an upcoming article, we try to create a database schema for above sub systems using MySQL Workbench.

Calculation of Inventory Through The Trigger Mechanism on The Transaction Table

This time we will discuss about the computerization of inventory in the warehouse (location) is done automatically at the time the transaction is entered into a purchase transaction table, into the sales transaction table, as well as mutations in the transaction table movement of goods between warehouses (locations). The assumption of this discussion is about the stock of drugs in the hospital pharmacy, the location of the drug in some places.
For the above, the following is the syntax of SQL that is run on Microsoft SQL Server 2000 Personal Edition.
CREATE TABLE [dbo].[Master_Obat] (
    [Kode_Kelompok] [varchar] (3) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
    [Kode_Obat] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [Nama_Obat] [varchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
    [Satuan] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
    [Harga_beli] [money] NULL ,
    [Harga_Jual] [money] NULL ,
    [Kode_Pabrik] [varchar] (4) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Master_Obat] ADD
    CONSTRAINT [PK_Master_Obat] PRIMARY KEY  CLUSTERED
    (
        [Kode_Obat]
    )  ON [PRIMARY]
GO
---------------------------------------------------
Master_obat tables are used to store master data medicine overall. In this table has a field that is drug code, drug name, unit, purchase price, sales price, and several other fields as needed.
---------------------------------------------------

CREATE TABLE [dbo].[Gudang] (
    [kode_gudang] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [Nama_gudang] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
    [Is_GudangUtama] [bit] NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Master_Obat] ADD
    CONSTRAINT [PK_Master_Obat] PRIMARY KEY  CLUSTERED
    (
        [Kode_gudang]
    )  ON [PRIMARY]
GO
---------------------------------------------------

CREATE TABLE [dbo].[StokGudang] (
    [kode_gudang] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [kode_obat] [nvarchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [stok] [int] NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Master_Obat] ADD
    CONSTRAINT [PK_Master_Obat] PRIMARY KEY  CLUSTERED
    (
        [Kode_gudang]
        [Kode_obat]
    )  ON [PRIMARY]
GO
----------------------------------------------
Both of the above table is used to store information drug stocks at each location.
----------------------------------------------

Next is a purchase transaction table as shown below. At the time of the purchase transaction information is stored in two tables, namely, purchase table and table purchase details.

CREATE TABLE [dbo].[Pembelian] (
    [Nomor_Pembelian] [varchar] (12) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [Nomor_Faktur] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
    [Tanggal_Pembelian] [datetime] NULL ,
    [pemasok] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL
) ON [PRIMARY]
GO
ALTER TABLE [dbo].[Master_Obat] ADD
    CONSTRAINT [PK_Master_Obat] PRIMARY KEY  CLUSTERED
    (
        [Nomor_Pembelian]
    )  ON [PRIMARY]
GO

-------------------------------------------------------
CREATE TABLE [dbo].[Pembelian_Detail] (
    [Nomor_Pembelian] [varchar] (12) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [Kode_Obat] [nvarchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
    [quantity] [int] NOT NULL ,
    [Harga_beli] [money] NULL ,
    [harga_jual] [money] NULL
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[Pembelian_Detail] ADD
    CONSTRAINT [PK_Pembelian_Detail] PRIMARY KEY  CLUSTERED
    (
        [Nomor_Pembelian],
        [Kode_Obat]
    )  ON [PRIMARY]
GO

ALTER TABLE [dbo].[Pembelian_Detail] ADD
    CONSTRAINT [FK_Pembelian_Detail_Pembelian] FOREIGN KEY
    (
        [Nomor_Pembelian]
    ) REFERENCES [dbo].[Pembelian] (
        [Nomor_Pembelian]
    )
GO

Drug stocks counting mechanism through trigger on the table purchase details, as described below. Trigger occurs when the INSERT, DELETE, and UPDATE.

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

CREATE TRIGGER tbl_PembelianDetail_Trigger1
ON dbo.Pembelian_Detail
FOR INSERT
AS
    declare @no_beli     varchar(12)
    declare @kod_obt     nvarchar(8)
      declare @qty     int
    declare @stk     int
    declare @hrg_beli    money
    declare @hrg_jual    money

    SELECT     @no_beli  = ins. nomor_pembelian,
        @kod_obt = ins.kode_obat,
        @qty = ins.quantity,
        @hrg_beli = ins.harga_beli,
        @hrg_jual = ins.harga_jual
    FROM inserted ins

    SELECT @stk = Stok
    FROM StokGudang
    WHERE (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obt)

    UPDATE StokGudang
    SET stok = @stk + @qty
    WHERE  (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obt)

    UPDATE master_obat
    SET harga_beli = @hrg_beli, harga_jual = @hrg_jual
    WHERE kode_obat = @kod_obt


GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

CREATE TRIGGER tbl_PembelianDetail_Trigger2
ON dbo.Pembelian_Detail
FOR DELETE
AS
    declare @no_beli     varchar(12)
    declare @kod_obt     nvarchar(8)
      declare @qty     int
    declare @stk     int

    SELECT     @no_beli  = del. nomor_pembelian,
        @kod_obt = del.kode_obat,
        @qty = del.quantity
    FROM deleted del

    SELECT @stk = Stok
    FROM StokGudang
    WHERE  (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obt)

    UPDATE StokGudang
    SET stok = @stk - @qty
    WHERE  (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obt)

GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

CREATE TRIGGER tbl_PembelianDetail_Trigger3
ON dbo.Pembelian_Detail
FOR UPDATE
AS
    declare @no_beli     varchar(12)
    declare @kod_obtIns     nvarchar(8)
    declare @kod_obtDel     nvarchar(8)
      declare @qtyIns     int
    declare @qtyDel     int
    declare @stk     int
    declare @hrg_beliIns    money
    declare @hrg_jualIns    money
    declare @hrg_beliDel    money
    declare @hrg_jualDel    money

     SELECT     @no_beli  = ins. nomor_pembelian,
        @kod_obtDel = del.kode_obat,
        @kod_obtIns = ins.kode_obat,
        @qtyDel = del.quantity,
        @qtyIns = ins.quantity,
        @hrg_beliDel = del.harga_beli,
        @hrg_beliIns = ins.harga_beli,
        @hrg_jualDel = del.harga_jual,
        @hrg_jualIns = ins.harga_jual
    FROM deleted del, inserted ins

    SELECT @stk = Stok
    FROM StokGudang
    WHERE (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obtDel)

    UPDATE StokGudang
    SET stok = @stk - @qtyDel
    WHERE (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obtDel)

    SELECT @stk = Stok
    FROM StokGudang
    WHERE (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obtIns)

    UPDATE StokGudang
    SET stok = @stk + @qtyIns
    WHERE (kode_gudang = (SELECT Kode_Gudang
                   FROM Gudang
                   WHERE Is_gudangUtama = 1))
         AND (kode_obat = @kod_obtIns)
   
    UPDATE master_obat
    SET harga_beli = @hrg_beliDel, harga_jual = @hrg_jualDel
    WHERE kode_obat = @kod_obtDel

    UPDATE master_obat
    SET harga_beli = @hrg_beliIns, harga_jual = @hrg_jualIns
    WHERE kode_obat = @kod_obtIns


GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
-----------------------------------------------

Database Object Naming Standards

A naming standard is a collection of rules, which, when applied to data, results in a set of data objects named in a logical and standardized way. These names convey some information about the named objects; an element name, for example, indicates the set of possible valid values (its data domain), and its usage. Having naming standards helps to achieve efficient use and reuse of data through better understanding of what data is in the system. Standardized names enhance communications about data within the BI community, from source application developers to BI experts to end users.
These standards apply to database objects created explicitly for Business Intelligence. Use reasonably meaningful names for tables and fields. If they get too long then try to use fairly standard (but consistent) abbreviations. If in doubt, just remove the vowels (a, e, i, o, u).
For each table also have a three letter acronym. Then if you have an 'ID' field that is used in foreign key relationships, then put the three letter acronym before the '_ID' name in ALL the tables that use it including the owning table.
Develop a list of standard suffixes, for example:
_FL for flags (usually only Y and N)
_IND for indicators (typically single byte varchar2 fields)
_NO for numeric numbers
_NUM for character numbers
_DT for dates
_TS for date-time stamps
 
If you have a set of tables that are closely related then SERIOUSLY consider giving them the same prefix or name root.
As far as object naming standards go, the advice above is as good as any. Most important is to BE CONSISTENT. Google "Database Naming Standards" and look at some of the documents you find - especially those on domains with .edu. - universities are red-hot on this sort of thing.
Also search for Oracle Database Design Standards, or variants of that phrase. Someone has done this already and will have published them on the web.
 

Pharmacology Clinical Decision Support System Software

Information technology has made a significant impact on the healthcare sector. The past decade has witnessed the foray of numerous information systems and their resultant products into the hospital scenario. The number of investments in computers and types of hospital systems has increased. This is because paper medical records are cumbersome, bulky to use and difficult to manage. On the other hand digital records are much easier to handle and improve the workflow efficiency by integrating various tasks.
A Hospital Information System (HIS) can be defined as a computerized system that is designed to meet all the information needs within a hospital. This includes diverse data types such as patient information, billing, finance and accounting, staffing and scheduling, pharmacy ordering, prescription handling, supplies, inventory, maintenance and orders management, diagnostic reports related to laboratory, radiology and patient monitoring as well as providing decision support. 
Pharmacology Clinical Decision Support System, as a sub system of Hospital Information System, increases patient safety by alerting the physicians to potential errors and providing them with requested counseling information. It integrates with all computerized solutions for medicine prescription such as e-prescribing, EMR (Electronic Medical Record), PIS (Pharmacy Information system) and CPOE (Computerized Physician Order Entry). Pharmacology CDSS should consists of the following elements:
  • Alerts - Alerts the user to various types of errors involved in the prescription of medications. 
  • Counselor - on demand clinical advises related to drug therapy.
  • CCMS - Brings in-house clinical content to the point of care.
  • Tools - Provides tools for local adaptation, report generation, system configuration, etc.
  • Interface - Interfaces the prescription application and provides the information to the users via the prescription/EHR applications.
Some benefits for healthcare organizations:

·         Increases patient safety by reducing medication errors
·         Protects the goodwill of healthcare organizations and physicians
·         Simple, seamless and swift integration to existing EMR/CPOE/PIS/e-prescription solutions
·         Increases efficiency- reduces operational costs and efforts invested in law suits