Configuration Management Issues in IHE

1
Configuration Management Issues in IHE

• Asuman Dogac, SRDC, METU, Turkey
• asuman_at_srdc.metu.edu.tr

2
Standards and Interoperability Profiles

• Standards are essential both for integration and
  for interoperability
• However, any actual implementation of a standard
  requires some form of tailoring
• Therefore, in developing practical and effective
  interoperability solutions, the industry relies
  on Interoperability Profiles

I still dont understand!
3
IHE Interoperability Profiles

• IHE Interoperability Profiles are
• Business processes describing selected real-world
  scenarios (use-cases)
• They specify the IT systems or applications
  involved in a use case (Actors)
• They specify the Transactions involved in a use
  case
• They specify interfaces by restricting the use of
  the existing standards such as HL7 or DICOM to
  accomplish a specific transaction
• They specify the choreography of the involved
  transactions

4
IHE Profiles and ebBP

• An IHE Profile is, in fact, a Business Process
• Configuration management in IHE is not easy
  especially when Actors are grouped to produce
  combined business processes!
• Therefore configuration management should be
  delegated as much as possible to the computers
  since they process fast and are less error prone
  than humans
• This can only be possible by describing the IHE
  Profiles through
• A standard, and
• A machine processable business process
  specification language
• We propose ebBP (ebXML Business Process
  Specification Schema) for this purpose

5
An Example IHE XDS Profile
Provide Register Document Set (ITI-15)
XDS Document Source
XDS Document Repository
Register Document (Set ITI-14)
Retrieve Document (ITI-17)
XDS Document Registry
Query Registry (ITI-16)
Patient Identity Feed (ITI-08)
Document Consumer
Patient Identity Source
6
The Corresponding ebBP Code

• ebBP Definition of a profile is very verbose!
  Therefore not given in this slide
• Available from ebBP Packages for IHE Profiles,
  http//www.srdc.metu.edu.tr/ihe/ebBP/packages/
• Why worry? The software will process it!
• Even better, there is a software which produces
  such codes automatically when the process is
  defined through a graphical interface ebBP
  Editor
• ebBP Editor is available at http//freebxmlbp.sour
  ceforge.net/

7
All the code can be automatically generated
through the ebBP Editor Available in Public Domain
8
IHE Actor Grouping
1 Provide Register Document Set
XDS Document Source
XDS Document Source/ ATNA Secure Node
XDS Document Repository
XDS Document Repository/ ATNA Secure Node
2 Provide Register Document Set
2 Register Document Set
4 Register Document Set
3 Register Document Set
3 Record Audit Event
XDS Document Registry
grouped
grouped
grouped
1 Record Audit Event
Any IHE Actor or PHI Application
Audit Record Repository
Audit Record Repository
ATNA Secure Node
ATNA Secure Node
1 Node Authentication
9
Configuration Issues in IHE

• IHE Actors communicate within the scope of a
  business process, which can be
• A single IHE Profile such as IHE XDS, or
• A combined business process where several IHE
  Actors are grouped
• For two IHE Actors to communicate within the
  scope of a given business process
• Each Actor needs to know the business
  collaboration they are taking part
• Each Actor needs to know their roles in the
  business collaboration
• Each Actor need to know the transaction it will
  execute
• Each Actor needs to know the choreography of the
  transactions
• Each Actor needs the configuration details about
  how the other Actor sends and receives Messages,
  which include
• Network addresses
• Certificates used for security purposes
• Document types

10
What does ebBP Provide to IHE Profiles?
Consider the Business combined Process for IHE
XDS, ATNA and PIX obtained through grouping
related Actors

• When an IHE business process is defined through
  ebBP, an Actor taking part in the process knows
  in a machine processable way
• The business collaborations it will be a part of
• Its roles in the collaborations
• The Actors it will communicate with
• The documents it will send and receive
• The choreography of all the transactions it will
  execute

XDS Document Source
The Business Collaborations involving ITI-19,
ITI-8, ITI-15
XDS Document Source, PIX Consumer, ATNA Secure
Node
XDS Document Repository, PIX Manager

Defined in Business Collaborations
11
Collaboration-Protocol Profile (CPP)

• An ebBP specification of an IHE Business Process
  reveals a lot of information very helpful for
  automation, but we need more
• We need to be able to describe each IHE Actor
  specific run time configuration issues, such as
• The transport and security protocols it
  recognizes
• The messaging protocols that it recognizes
• The business processes that the Actor recognizes
• All of the technical information such as URLs,
  time-outs, certificates to establish electronic
  relationships, document types
• CPPs provide for this!

12
CPP Editor in the Expert Mode
13
A Screenshot from CPP Editor Wizard
14
Collaboration Protocol Agreement (CPA)

• CPAs set the terms for automated collaboration
• A CPA between two Actors are obtained by
  processing their Collaboration Protocol Profiles
  (CPPs)
• A CPA involves the following
• Matching business processes and the roles
• Matching transport and transport security
• Matching document packaging and document security

15
CPA Editor in the Expert Mode
16
The CPA Editor Wizard
17
Realizing Connect-a-thons over the WebLogin
18
VCP Registration
19
VCP Welcome Page
20
VCP Actor Grouping
21
VCP Invitation
22
Thank you very much for your attention!