Last updated June 16, 2009 21:12, by Bernie Thuman
Feedicon  

Functional Description

A high-level description of HIEOS functional capabilities is provided in this section.

IHE Cross Enterprise Document Sharing (XDS.b)

Actors (XDS.b)

HIEOS provides support for the following IHE XDS.b actors:

Actor Description HIEOS?
Document Registry Acts as a record locator service. Stores meta-data describing documents resident in federated repositories. Yes
Document Repository Storage location for documents. Documents can be PDF, images, XML, text documents, etc. Yes
Patient Identity Source Source of patient identities that must be known to the Document Registry before meta-data submissions are allowed. Yes (Client)
Document Consumer Client application (could be an EMR system) that is interested in viewing shared patient records. Yes (Client)
Document Source Client application (typically an EMR system) that publishes documents for sharing within a broader community. Yes (Client)

Transactions (XDS.b)

HIEOS implements each IHE XDS.b transaction as indicated in the diagram below:

IHE Cross Community Access (XCA)

Actors (XCA)

HIEOS provides support for the following IHE XCA actors:

Actor Description HIEOS?
Initiating Gateway Responds to document requests within a health information sharing community. Retrieves documents within local and remote communities. Yes
Responding Gateway Responds to document requests from remote health information sharing communities. Yes
Document Registry Acts as a record locator service. Stores meta-data describing documents resident in federated repositories. Yes
Document Repository Storage location for documents. Documents can be PDF, images, XML, text documents, etc. Yes
Document Consumer Client application (could be an EMR system) that is interested in viewing shared patient records. Yes (Client)

Transactions (XCA)

HIEOS implements each IHE XCA transaction (implementing the XDS Affinity Domain Option) as indicated in the diagram below:

Technical Description

Layered Architecture Diagram

HIEOS is implemented following a layered architecture pattern as depicted in the diagram below:

Component Descriptions

The table below provides a brief description of each key HIEOS component:

Component Description Category
xtest Client test harness provided by HIEOS. Applications
xwebtools Web application that includes an XDS.b Registry and Repository viewer. Applications
logbrowser Web application that provides a means to view HIEOS transaction logs. Applications
XDS.b Registry XDS.b Registry Axis2 Web Service. Services
XDS.b Repository XDS.b Repository Axis2 Web Service. Services
XCA Gateway XCA Gateway (Initiating and Responding) Axis2 Web Service. Services
OMAR freebXML Registry XDS.b Registry ebXML v3 storage mechanism. Database Access Components
ADT Stores patient registration data in support of XDS.b Registry operations. Database Access Components
XLog Message driven bean that logs HIEOS transactions asynchronously. Database Access Components
RepoImpl XDS.b Repository storage mechanism. Currently configured to store XDS.b documents in an RDBMS. Database Access Components
Web Service Framework
(Axis2)
Provides web services infrastructure used by HIEOS. Infrastructure
Java Database Connectivity
(JDBC)
Provides database access layer to underlying RDBMS for all HIEOS storage requests. Infrastructure
Application Server
(GlassFish ESB)
Provides J2EE-compliant web application server environment. Infrastructure
RDBMS
(MySQL, PostGres)
Provides RDBMS storage mechanism for HIEOS. Infrastructure
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2013, Oracle Corporation and/or its affiliates
(revision 20140418.2d69abc)
 
 
Close
loading
Please Confirm
Close