神刀安全网

Red Hat JBoss Fuse – Healthcare integration demo Part One

Red Hat JBoss Fuse - Healthcare integration demo Part One Continue on with the topic from last week, I want to try to demonstrate how JBoss Fuse can help to build a more robust, and agile healthcare integration solution. In this blog I will explain what the demo is about, how to install and play with the demo. You can access the code base here: https://github.com/weimeilin79/healthcaredemo I tried to mimic a common situation when we visit a clinic or hospital. Lets start by looking at the departments. There are 5 different parties involve. As you can see, these are commonly found in healthcare and they uses different data format and talks in various protocol. just like what it would be in real life. 

  • Front Registration Desk
    • Responsible for patient registration 
    • Sending registered patient to all departments
    • Storing patient registration data
    • Talks in HL7 v2
  • Doctor Clinic 
    • Red Hat JBoss Fuse - Healthcare integration demo Part One
    • Receives registration info
    • For clinical prescriptions 
    • Doctor sending patients to eithe lab test or radiology x-ray
    • Recording paitent condition
    • HL7
    • Messaging broker
  • Laboratories
    • Receives registration info
    • Schedule Lab test for patients
    • FHIR
    • Restful Endpoint
  • Radiology 
    • Red Hat JBoss Fuse - Healthcare integration demo Part One
    • Receives registration info
    • Schedule x-ray test for patients
    • HL7
    • MLLP socket
  • Pharmacies  
    • Ask for patient prescriptions data
    • JSON
    • Restful Endpoint
  • Insurance company
    • Get all patient registration data

We first by registering ourselves in the front desk, the front desk will get the registration information, and system will store these data for insurance company that will later be collect via their batch system. Then the register data are sent to all the departments in the hospitals. After that the patient is then sent to doctor clinic for quick diagnose, this is when the doctor will decide to either send them on to more detailed test, radiology scan or simply give prescription. For the lab in the hospital, it will receive both the registration administration data and the request for different test coming from clinic. Same applies to Radiology system. Lastly when the patients tries to get their prescription from the pharmacy, it’s application will link back to the hospital to check the validity and content of the prescribed medicines. 

To make this demo more real, these department application does not speak the same language, below is the diagram that shows what context of data format each department expect. 

Red Hat JBoss Fuse - Healthcare integration demo Part One

Both the clinic and Radiology department uses the most common HL7 v2 format, HL7 is the most common standards for transfer of clinical and administrative data between software applications by healthcare providers. The messages use a non-XML encoding syntax based on segments (lines) and one-character delimiters. It’s a very complex data because not only it tries to cover many aspect in healthcare industry, but since the evolution of technology, many customization was implemented over the years, making it hard to decode and read. Even using this format, many vendors interoperate it differently. And we also have FHIR, which is the new data format pushing by the same community by trying to address the problem HL& v2 and 3 has. It supports better with the mobile and uses the concepts of hierarchical resources. And we also have pharmacy which is an outside vendor that requires a specific data format.   

To install the demo, please make sure you have installed Vagrant and Virtual Box beforehand. Go to my repository and clone the project by running 

 git clone MY_REPO_URL 

Go to the project directory and run

init.sh 

Start build and deploy JBoss Fuse Camel services by goingu nder project directory ./projects/healthcaredemo and run

mvn -Pf8-local-deploy

After projects are depolyed, go back to the demo root directory (where the init.sh is) we want to create two extra services 

oc create -f support/clinichl7service.json

  oc create -f support/labrestservice.json

Also expose a new route for the Lab Rest API Service 

oc create -f support/labrestapi.json 

You can take a look at the pods and service that are running inside OpenShift, by login to OpenShift console with USERNAME/PWD admin/admin

https://10.1.2.2:8443/console/

Red Hat JBoss Fuse - Healthcare integration demo Part One

Red Hat JBoss Fuse - Healthcare integration demo Part One

And start playing with the demo by registering your info, by going into the page you will see different sections, 

Red Hat JBoss Fuse - Healthcare integration demo Part One Red Hat JBoss Fuse - Healthcare integration demo Part One

You can start by registering your patient information then schedule different test by entering different fields. 

Next week, I will be talking about my approach to break this problem done into microservices. 

转载本站任何文章请注明:转载至神刀安全网,谢谢神刀安全网 » Red Hat JBoss Fuse – Healthcare integration demo Part One

分享到:更多 ()

评论 抢沙发

  • 昵称 (必填)
  • 邮箱 (必填)
  • 网址