Skip to Content

Dear blog readers,

welcome to this weblog about demo scenarios for collaborative health networks. This blog starts along with the Public Services Ecosystem summit in Mannheim and serves as a supporting medium for our hands-on session “G1 Hands On: The Business Process Platform in Healthcare”. The third part within this G1 session is about Enterprise Services in a real healthcare application: CHN.

New product in ramp-up 

“Connection Package for Collaborative Health Networks 1.0” (CHN) is our product for CHN/eHealth scenarios that is in ramp-up since mid of December 2007. The purpose of this blog is to give you insight into to the Business Process Platform (BPP). CHN is one key contributor to the BPP, but it is important to understand that CHN in itself consist of services and is not an end-user application (unlike SAP Patient Management).

CHN in a synchronous integration scenario 

So now let’s start and have a look into CHN. One key scenario that we encounter almost everywhere is appointment scheduling across the network. In the following scenario, we think of an end-user system (service consumer, e.g. SAP Patient Management) and an information platform (service supplier, CHN). First step of the scenario is to search for a specific patient in the network, i.e. in CHN. The following screenshot shows you the synchronous version of the patient search service, viewed with Web Service (WS) Navigator.

This way of consuming a service is also part of our software testing. With the WS Navigator, you are now able to enter some test data in the provided fields. By clicking on execute, the data is sent to the interface and the enterprise service executes its logic, in this case performs a search for patient “Peter Jones”. 

This service can either be consumed by a composite application running in a portal or by an end-user system that knows the enterprise service definition, like SAP Patient Management.

CHN and HL7 Version 3 

Additional to the synchronous service, CHN provides each service as a HL7 V3 flavoured asynchronous version. The second scenario would be triggered from an existing non-SAP information system that knows how to speak HL7 v3. The message is sent to XI, the HL7 message is mapped to the internal service interface, and then the same logic applies as for the synchronous case.

image

The response message to this HL7 search request is sent back to XI, mapped to an HL7 response message and then sent to the requesting system. In our case – as we use a development tool to simulate a non-SAP hospital information system – the response is stored on a central folder to show the behaviour of the system. 

 

These two examples should give you an indication how communcation with CHN looks like. Now check your own requirements:

– what are scenarios that you, your partner or your customer are looking for?
– is HL7 as a communication standard relevant in your scenario? Which version of HL7?
– what system landscape exists in your case and how could it fit to a network scenario using CHN?

 

If you are interested in further topics, please check also the following sources:

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. This was an eye-opener for me. Excellent blog. My mind is now crackling with all kinds of scenarios. How can we make SAP MDM syndication and import HL7 v3 compliant? Can a future release of SAP MDM have standard business content for Patient master data?Is SAP MDM HIPAA compliant? Is there a special field type that can be used for masking social security numbers? I am feeling dizzy, need to sit down now…
    (0) 

Leave a Reply