Tuesday, December 17, 2013

Celebrus v8

Six months have flown past since I joined Celebrus, and with no further ado I think it’s time to post some information on our latest product release, namely Celebrus v8. This release is hugely important to our clients, rolling together an incredible amount of work over the last couple of years. Given that we’re only a small company, we punch way above our weight. Not heard of us? Well we provide customer analytics on 20K+ web sites worldwide. We sell almost entirely through our channels partners (OnMarc, SAS and Teradata to name but three). 

A very brief summary of what’s new in our latest release:

Real-Time Event Stream

The most important feature in this release. We have for many years provided an analytics facility to crunch data in Celebrus and then push the summarized information out into data warehouses for reporting (Oracle, MySQL, Teradata et al). With this release we can push the detailed event data out in real-time (CSV is often the data format of choice).

This approach is perfect for the new range of data crunching applications like Teradata Aster and Hadoop. Ultra low latency is the key to making this fly. Teradata Aster enables a wide range of data discovery capabilities including path and graph analysis.


Semantic Configuration

One of the unique features of Celebrus is that we turn low level events (clicks, form submits, field interactions et al) into meaningful business events like checkout, basket add, product views, marketing campaign attribution, customer behaviours and much more.

Furthermore, this isn't just for web site users, but is across all channels.

We do this without any tedious, costly and error prone web page tagging. How do we do this? The solution is to configure the Celebrus system with the meaning of certain events, our so-called semantic configuration. You simply configure the system with how to interpret user actions and we turn those low level form submits into a set of meaningful search terms and so on. Easy to do and quick to change as your customer channels evolve.

Real-Time Decision Management

There is some very smart event processing software out there. A good example is Teradata RTIM. RTIM enables you to push personalised messages to your customers in real time through Celebrus. Celebrus provides the customer identification (who) and the reliable delivery platform (where/how) and RTIM does the really interesting part of deciding the content (what/when). Blend into that an understanding of what has worked in the past and RTIM can use its integrated predictive models to fine tune the offers.

Performance

With this release we’ve pushed the envelope way out. Even on some fairly run-of-the-mill multi-core hardware (by today’s standards) we can process 25K+ events per second, sustained. The performance graph below is from one of our test  machines running in a Jenkins cluster. Wondering about the uptick half way through? The result of some tuning around the Java CMS Garbage Collector, but that's another story.




Integrated Security and Management

A single place to manage users and roles across the system. Many of our clients deploy Celebrus to cope with huge event rates (10K+ events per second sustained is common) and so not surprisingly there is a need to scale for performance and reliability reasons. With our latest release, a Celebrus cluster can be managed through a single smart client interface.

I’ve posted some slides here which explain a little more about our company and technology.



Sunday, April 7, 2013

Healthcare Analytics with Message Broker

One feature I would like to call out in the new version of the Healthcare Connectivity Pack is our healthcare analytics capability. This feature makes it incredibly easy to find, search and extract meaningful data from a range of healthcare data sources (HL7 v2, DICOM and CDA). The tooling can do this because it understands these healthcare formats, not just at a syntactic level but the semantics as well. This knowledge of a standard is encapsulated in what we call a Data Analysis Profile (DAP).

For example, in the case of clinical documents, the CDA DAP understands the HL7 v3 RIM and structural attributes (such as templateID and root). With this understanding the tooling can pick apart clinical documents and show you the meaning of different sections (medications, procedures etc). This is just the tip of the iceberg, the tooling makes it a breeze to do really complex work with clinical documents.

Another example are HL7 v2 observation results, the HL7 DAP understands where the coding system is stored in the OBX segment. Armed with this information the tooling deciphers LOINC codes to present user friendly display names when you are working with your data. In fact you can plug in your own bespoke coding systems as well (a common requirement in providers).


Understanding and working with these healthcare standards is one big step forward, but the tooling goes way further. The tooling builds for you the Message Broker solution to validate inbound messages and extract the data you want. The data can be extracted into a simpler XML message format. This is the ideal approach if you want to send some extract of the healthcare data to a downstream application. Alternatively, the tooling can extract the data directly into database tables. In fact, the tooling will even design you the database table layout, key selection and everything else!

If you are interested to learn more, take a look through these slides I have posted.

Medical Imaging (DICOM) with Message Broker

One of the key things we focus on with the Healthcare Connectivity Pack is to have a single healthcare ESB which can work with a wide range of protocols, standards, transports and formats. This focus is becoming ever more important as healthcare organisations seek to join up more sources of data whether they be clinical, financial or anything else for that matter.

In many healthcare organisations I talk to DICOM has traditionally been kept separate from the main line integration of clinical applications (often using HL7). This legacy is quickly disappearing though accelerated by many factors not least of which is work being done by IHE (for example, the scheduled workflow profile which requires integration between HL7 and DICOM modalities).

The latest version of the Healthcare Connectivity Pack includes support for medical imaging (DICOM). This enables a wide range of high value use cases. The diagram below shows an example walk through of how the Healthcare Connectivity Pack can route DICOM instances to external experts for a second opinion. This scenario comes in various flavours. For example, perhaps you have several radiologists and you want to work load balance between them. Alternatively, radiologists with specialist skills might be geographically dispersed and so DICOM images can be routed to the correct location.


Another use case is to pre-fetch DICOM instances when a patient is admitted to a hospital:


This scenario uses the Healthcare Connectivity Pack to pull down DICOM images to the local PACS so that the right information is in the right place for a patient's effective treatment. These scenarios uses a range of DICOM capabilities including C-FIND, C-STORE and C-MOVE.

I've posted some slides here which walk through all the technical details of the DICOM integration.

Healthcare Integration with Message Broker

We have just released our latest and greatest healthcare integration product, the Message Broker Healthcare Connectivity Pack. In the last three years we have made huge steps forward in the healthcare integration space, indeed we have had four product releases in the last two years alone.

This new release comes packed with a host of new features:


The new capabilities augment the existing capabilities of the Healthcare Connectivity Pack:


I've posted some slides here which walk through the high level features now available.