Monday Jun 04, 2007

Where should the Heathcare systems go?

In this post I talk about the issues that should be solved in the health care domain in the near future where interoperability amongst different health care systems is going to be a main concern.[Read More]

Where should the Heathcare systems go?

Recently while having a look at the HL7 BC at the open-esb I felt that there are several issues and challenges that are not yet solved in this domain.

From a philosophical perspective too if we look at, the globalization is happening at great speed and we need interoperability amongst the standards for accessing a patient's record who is diagonalized for a particular disease to be treated at a different geo-political location. Why I m talking about political here is to emphasize the disparate systems via which the patient records pass and heterogeneous health care and insurance systems we have in different geo-political regions.

The following list is not complete. This is only a start for looking at the things. :-) . I might be writing you more if we continue to do work.
Have a look and give your feed back.

  1. Arden Syntax, which is a language for encoding medical knowledge. HL7 adopted and oversees the standard beginning with Arden syntax 2.0. These Medical Logic Modules (MLMs) are used in the clinical setting as they can contain sufficient knowledge to make single medical decisions. They can produce alerts, diagnoses, interpretations, and contain a quality assurance function and administrative support. An MLM must be run on a computer that meets the minimum system requirements and has the correct program installed. Once this is provided, the MLM can give advice when and where it is needed.

  2. The HL7 Clinical Document Architecture (CDA) is an XML based markup standard intended to specify the encoding, structure and semantics clinical documents for exchange. It is based on the HL7 Reference Information Model (RIM) and the HL7 Version 3 Data Types,

  3. Interoperability with Clinical Data Interchange Standards Consortium (CDISC)

2 and 3 seem to be pervasive in the Health care domain. Supporting these things would certainly enhance the marketability etc.. Apart from above if we were to be leaders we need to do have the following to with interoperability amongst these protocols in mind (Why interoperability ??? --- for flexibility and transforming one kind of data to the other kind offering seamless transfer of data from one system to another system. This has potential of One kind of record to be looked from another kind of system without the user being switching from one kind of domain to the other kind). Have a look at Open Healthcare, Good European Healthcare Record (GEHR) and Electronic Health Record (EHR) and Electronic Medical Record (EMR).

Without inter-operable EMRs, practicing physicians, pharmacies and hospitals cannot share patient information, which is 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.Office of the National Coordinator for Health Information Technology (ONC), works to address interoperability issues and to establish a National Health Information Network (NHIN) in US. Under the ONC, Regional Health Information Organizations (RHIOs) have been estabilshed in many states in order to promote the sharing of health information. US Congress is currently working on legislation to increase funding to these and similar programs.

Wednesday May 02, 2007

Check out latest Script SE in Open-esb

The latest JSR 223 compliant Scripting Service Engine is checked into the the open-jbi-components. Check it out.

[Read More]

Tuesday Apr 10, 2007

Reflection on Interoperability

The greatness of SOA lies in its power of interoperability amongst heterogeneous systems. SOA and "Web-Services" are not synonymous. There are several ways in the programming world to solve the issue of interoperability like the REST, CORBA, .NET remoting etc apart from WS, each of the approach having its own merits and demerits.  This post delves on what is the definition of interoperability and whats the meaning of it and what components in the computing world makes this possible.[Read More]

Friday Apr 06, 2007

Karen Tegan Padir's talk to the SOA/BI team.

A brief summery of Karen's talk to the SOA/BI team.[Read More]

Wednesday Apr 04, 2007

Using Scripting Service in open-esb

1st part of the writeup on Scripting Service Engine. This note delves on how is scripting important for Java platform, what is JSR223 and a bit of internals on the same as a precursor to the usage of Scripting Service Engine in open-esb.[Read More]

Sunday Apr 01, 2007

Using transactions in JDBC BC

This post talks about utilizing the XATransactions in JDBC BC of open-esb. It also talks about a bit about the internals of how its implemented. [Read More]

Back to writing after a Heitus

It has been a long time since I wrote something. When I look back the reasons are inertia and not able to motivate myself for posting something. I resolved today that I devout sometime on weekly basis for writing.

Tuesday Dec 19, 2006

Clustering in JBI Components 2

A sequel to the writeup of   making your JBI components cluster aware this post discusses the ways for handling clustering for a particular component in open-esb[Read More]

Thursday Dec 14, 2006

Implementing Transactions in JBI Components

Implementing distributed transaction in a component is always a tough job. JBI specification though give the handle to Transaction Manager via the Component Context interface does not tell any thing about implementation of the same. Different implementation have different ways of addressing the issue. The series in this post talks from the perspective of open-esb.

In doing so I have tried to talk about different standards which comes generally in an Integration Scenario and how each of them addressed in open-esb.

[Read More]

Wednesday Dec 06, 2006

Making your JBI Component Cluster aware in Glassfish

The aim of note is to peek at the Glassfish’s implementation with respect to clustering and load balancing and to formulate a strategy for the JBI components to be cluster aware. This will go into 2 separate notes one with respect to peeking the AppServer and the other one exploring the ways and means to make a JBI component cluster aware.[Read More]

Thursday Nov 23, 2006

Notes on BPEL

This note is primarily about the way I understand Orchestration of Business Processes from BPEL4WS stand point. [Read More]

Tuesday Nov 21, 2006

Understanding SOAP Encoding

Encoding section of SOAP specification often the most confused one. In this entry I tried to explain the why's and what's of SOAP encoding and how to apply the same and where to apply. [Read More]

Wednesday Nov 15, 2006

Secure Web Services

Due to vendor agreement and some diligent work in standards organizations such as OASIS and the W3C. Mature specifications have emerged and have become (or are now on their way to becoming) standards. As a
result, many standards-based Web service security toolkits and
implementations have been shipped that allow developers to build solutions quickly.

Now that there are accepted standards -
such as WS-Security and its associated token profiles used for identity
propagation (WS-Security SAML Token Profile, WS-Security X.509 Token
Profile, WS-Security Username Token Profile) - as well as emerging
specifications in standards bodies (WS-SecureConversation, etc.), there
should no longer be any reason to create a home-grown security
messaging syntax. Certainly, you must be able to understand the purpose and use of these standards and specifications in order to meet your security requirements. In addition to the problems that you will have down the
road involving lack of interoperability with other systems, any
nonstandard solution created by wannabe cryptographers will most likely have security vulnerabilities that could come back to haunt you in very ugly ways.

We have standards for a reason - embrace them.

[Read More]

I was part of Sun R&D in Java CAPS and later Glassfish ESB. I moved from R&D to Consulting. I am currently working as a Solution Architect in Oracle Consulting Services (India). I was sharing my experience w.r.t. Java CAPS and other technologies during Sun period. Now in Oracle world I share my experiences with Oracle FMW product line as well as other Oracle Technologies and products.


« June 2016