<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Introduction</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>Recent changes to Introduction</description><atom:link href="https://sourceforge.net/p/pcehrvendor/wiki/Introduction/feed" rel="self"/><language>en</language><lastBuildDate>Wed, 22 Feb 2012 06:20:25 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pcehrvendor/wiki/Introduction/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v11 
+++ v12 
@@ -16,7 +16,6 @@
  
 •Generation of client stubs based on the Apache CXF Framework
 •Creation of service invocation layer that wraps the raw client stubs
-•Configuration for WS-Addressing
 •Transport Layer Security (TLS) mutual authentication configuration 
 •Loosely coupled User Interface based on the Java Swing framework (Can be easily decoupled from the service invocation layer)
 •Basic logging to capture SOAP requests and responses
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Wed, 22 Feb 2012 06:20:25 -0000</pubDate><guid>https://sourceforge.neted33f6e6658d2a7060a701ac1a32fdade9f7793a</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v10 
+++ v11 
@@ -27,18 +27,17 @@
 PCEHR Java Connector future releases are planned to include:
 •Dynamically generated CDA documents
 •Multi-threading framework – allowing documents to be uploaded without impacting concurrent usage of the UI
-•Smart stubs – to enable simulation of PCEHR B2B web service response. 
+•Smart stubs – to enable simulation of PCEHR B2B web service response. This would allow vendors to confirm their end to end impmlementation without requiring connection to a PCEHR test environment.
 •Enhanced error handling and logging
-•Enhanced UI 
+•Enhanced UI to more closely represent a CIS system (rather than a test harness for individual services)
 •Improved validation of request /response messages
 
 Feedback on priority of enhancements is welcome 
 
 
 A description of the JConnector implementation can be found at : [Building a client web service consumer]
 
 
 [[download_button]]
  
-
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Mon, 20 Feb 2012 02:15:36 -0000</pubDate><guid>https://sourceforge.netdc995c054b3792e82a1bb11bc73a15ddfe981750</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v9 
+++ v10 
@@ -1,41 +1,41 @@
-Welcome to PCEHR Connector application!
-
+Welcome to PCEHR JConnector application!
+
 The PCEHR JConnector is an open source reference implementation of a PCEHR System client. The scope of the project includes:
 
 1.Providing sample code for connecting a client application to the PCEHR System via the   PCEHR B2B Gateway.
 2.Providing an online forum, where questions about connecting to the PCEHR System can be raised and answered.
 3.Using feedback to continuously improve the sample code, as well as the general experience of software vendors looking to integrate with the PCEHR System.
 
 The sample code brings to life the technical specifications published by Nehta, by demonstrating how a Clinical Information System (CIS) would interact with the PCEHR System. The sample code will be updated to incorporate future technical specification publications by Nehta.
 
 The intent is for a software vendor to use this sample code as a guide for implementing products that integrate with the PCEHR System. During the implementation process, a vendor can register for Notice of Connection (NOC) testing with DHS Medicare. As part of the welcome pack for that registration, a vendor will receive a set of NASH certificates, test data and information on web service end points to connect to PCEHR system. This open source site does not include NOC environment information or NASH certificates.
 
 The PCEHR JConnector project is a Java based implementation, released under the permissive Apache 2.0 open source license. A .NET sample client is also under development.
 
 The implementation is available on a web-based source code repository SourceForge at https://sourceforge.net/projects/pcehrvendor/ . It provides a step by step guide for implementing connectivity to PCEHR system using the PCEHR JConnector classes. The current release (v1.0) includes -
  
 •Generation of client stubs based on the Apache CXF Framework
 •Creation of service invocation layer that wraps the raw client stubs
 •Configuration for WS-Addressing
 •Transport Layer Security (TLS) mutual authentication configuration 
 •Loosely coupled User Interface based on the Java Swing framework (Can be easily decoupled from the service invocation layer)
 •Basic logging to capture SOAP requests and responses
 •JUnit test suite and test results for key transactions
 •The first iteration of this tool is focused on invoking the PCEHR services. It reads a prepared CDA document from file. Generating the CDAs dynamically to pass into these services will be provided in a later release.
 •Supporting artefacts such as WSDLs, class diagrams, JConnector developer guide, UI input parameters guide, links and references to published specifications, and mapping of PCEHR JConnector to the transactions described in Nehta’s Logical Service Specification (LSS) and Technical Service Specification (TSS) documents.
 
 PCEHR Java Connector future releases are planned to include:
 •Dynamically generated CDA documents
 •Multi-threading framework – allowing documents to be uploaded without impacting concurrent usage of the UI
 •Smart stubs – to enable simulation of PCEHR B2B web service response. 
 •Enhanced error handling and logging
 •Enhanced UI 
 •Improved validation of request /response messages
 
 Feedback on priority of enhancements is welcome 
 
 
-A description of the jConnector implementation can be found at : [Building a client web service consumer]
+A description of the JConnector implementation can be found at : [Building a client web service consumer]
 
 
 [[download_button]]
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Mon, 20 Feb 2012 01:19:35 -0000</pubDate><guid>https://sourceforge.net6af65f9ac6e8aad466d04d87c39c314fa4d8471f</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v8 
+++ v9 
@@ -1,16 +1,39 @@
 Welcome to PCEHR Connector application!
 
-**Overview: **
-This is a sample implementation showcasing connectivity to PCEHR system via B2B Gateway Channel.  The scope of this implementation is limited to implementing the key interaction scenarios exposed via B2B gateway channel and the operations utilised within those scenarios to interact with the PCEHR system.  The sample implementation is an attempt to demonstrate how a local CIS might trigger a set of interactions between a CIS and the PCEHR system. This application does not intend to elaborate on the internal workings of CIS, but is intended to help guide and contextualise interactions between CIS and PCEHR.
-
-**High Level Design:** 
-The application architecture consists of loosely coupled layers as described below -  
-
-*User Interface (UI) Layer** – This layer provides the user interface for to enter request information pertaining to the PCEHR web services exposed via B2B Gateway channel implemented in the PCEHR system. The UI layer is developed based on the Model View Controller (MVC) design pattern and consists of multiple views, models and controllers. The technology used for developing the UI layer is Java Swing.
-
-*Service Invocation (SI) Layer** – This layer provides the interfaces between the UI layer and Web Services. It provides an interface to pass the request object and receive the response object. The logic obtains references to the web service clients and invokes web service methods. The service invocation layer receives the request from the controller in the UI layer, validates the request, applies the business logic in order to process the request and provides the response to the controller. The service invocation layer encapsulates the implementation details of the specific web services to the UI layer. 
-
-*Web Services Stubs (WSS) Layer** – This layer contains the actual proxy stubs generated from the WSDLs of the web services exposed via B2B Gateway channel. This layer includes the WSDL files and the schemas used to generate the stubs. The stubs are in turn used by the SI layer to invoke the web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall/unmarshall the data from the web services.
+The PCEHR JConnector is an open source reference implementation of a PCEHR System client. The scope of the project includes:
+
+1.Providing sample code for connecting a client application to the PCEHR System via the   PCEHR B2B Gateway.
+2.Providing an online forum, where questions about connecting to the PCEHR System can be raised and answered.
+3.Using feedback to continuously improve the sample code, as well as the general experience of software vendors looking to integrate with the PCEHR System.
+
+The sample code brings to life the technical specifications published by Nehta, by demonstrating how a Clinical Information System (CIS) would interact with the PCEHR System. The sample code will be updated to incorporate future technical specification publications by Nehta.
+
+The intent is for a software vendor to use this sample code as a guide for implementing products that integrate with the PCEHR System. During the implementation process, a vendor can register for Notice of Connection (NOC) testing with DHS Medicare. As part of the welcome pack for that registration, a vendor will receive a set of NASH certificates, test data and information on web service end points to connect to PCEHR system. This open source site does not include NOC environment information or NASH certificates.
+
+The PCEHR JConnector project is a Java based implementation, released under the permissive Apache 2.0 open source license. A .NET sample client is also under development.
+
+The implementation is available on a web-based source code repository SourceForge at https://sourceforge.net/projects/pcehrvendor/ . It provides a step by step guide for implementing connectivity to PCEHR system using the PCEHR JConnector classes. The current release (v1.0) includes -
+ 
+•Generation of client stubs based on the Apache CXF Framework
+•Creation of service invocation layer that wraps the raw client stubs
+•Configuration for WS-Addressing
+•Transport Layer Security (TLS) mutual authentication configuration 
+•Loosely coupled User Interface based on the Java Swing framework (Can be easily decoupled from the service invocation layer)
+•Basic logging to capture SOAP requests and responses
+•JUnit test suite and test results for key transactions
+•The first iteration of this tool is focused on invoking the PCEHR services. It reads a prepared CDA document from file. Generating the CDAs dynamically to pass into these services will be provided in a later release.
+•Supporting artefacts such as WSDLs, class diagrams, JConnector developer guide, UI input parameters guide, links and references to published specifications, and mapping of PCEHR JConnector to the transactions described in Nehta’s Logical Service Specification (LSS) and Technical Service Specification (TSS) documents.
+
+PCEHR Java Connector future releases are planned to include:
+•Dynamically generated CDA documents
+•Multi-threading framework – allowing documents to be uploaded without impacting concurrent usage of the UI
+•Smart stubs – to enable simulation of PCEHR B2B web service response. 
+•Enhanced error handling and logging
+•Enhanced UI 
+•Improved validation of request /response messages
+
+Feedback on priority of enhancements is welcome 
+
 
 A description of the jConnector implementation can be found at : [Building a client web service consumer]
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Sun, 19 Feb 2012 08:45:58 -0000</pubDate><guid>https://sourceforge.netc7ae32f8827ff88df95991f30fe8e25ae7f6d5f9</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v7 
+++ v8 
@@ -15,7 +15,6 @@
 A description of the jConnector implementation can be found at : [Building a client web service consumer]
 
 
-[[project_admins]]
 [[download_button]]
  
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Thu, 16 Feb 2012 00:15:08 -0000</pubDate><guid>https://sourceforge.net154c71c3b2342a2b85ac7c9fcd9fa6ada7b7c271</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;--- v6 
+++ v7 
@@ -12,9 +12,11 @@
 
 *Web Services Stubs (WSS) Layer** – This layer contains the actual proxy stubs generated from the WSDLs of the web services exposed via B2B Gateway channel. This layer includes the WSDL files and the schemas used to generate the stubs. The stubs are in turn used by the SI layer to invoke the web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall/unmarshall the data from the web services.
 
-
+A description of the jConnector implementation can be found at : [Building a client web service consumer]
+
+
 [[project_admins]]
 [[download_button]]
-
+ 
 
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Thu, 16 Feb 2012 00:14:32 -0000</pubDate><guid>https://sourceforge.net22a24ed629e449b7fd0473e7340b400f5561e7c1</guid></item><item><title>WikiPage Introduction modified by pcehr_JConnector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Introduction/</link><description>&lt;pre&gt;&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_JConnector</dc:creator><pubDate>Wed, 15 Feb 2012 07:42:03 -0000</pubDate><guid>https://sourceforge.net420e286dc0a1a0016112eaa4591a90ea55a95a35</guid></item><item><title>WikiPage Home modified by pcehr_Connector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Home/</link><description>&lt;pre&gt;--- v4 
+++ v5 
@@ -1,18 +1,16 @@
-Welcome to PCEHR Connector Sample application!
-
+Welcome to PCEHR Connector application!
+
 **Overview: **
 This is a sample implementation showcasing connectivity to PCEHR system via B2B Gateway Channel.  The scope of this implementation is limited to implementing the key interaction scenarios exposed via B2B gateway channel and the operations utilised within those scenarios to interact with the PCEHR system.  The sample implementation is an attempt to demonstrate how a local CIS might trigger a set of interactions between a CIS and the PCEHR system. This application does not intend to elaborate on the internal workings of CIS, but is intended to help guide and contextualise interactions between CIS and PCEHR.
 
-*High Level Design:** 
+**High Level Design:** 
 The application architecture consists of loosely coupled layers as described below -  
 
-**User Interface (UI) Layer** – This layer provides the user interface for to enter request information pertaining to the PCEHR web services exposed via B2B Gateway channel implemented in the PCEHR system. The UI layer is developed based on the Model View Controller (MVC) design pattern and consists of multiple views, models and controllers. The technology used for developing the UI layer is Java Swing.
-
-**Service Invocation (SI) Layer** – This layer provides the interfaces between the UI layer and Web Services. It provides an interface to pass the request object and receive the response object. The logic obtains references to the web service clients and invokes web service methods. The service invocation layer receives the request from the controller in the UI layer, validates the request, applies the business logic in order to process the request and provides the response to the controller. The service invocation layer encapsulates the implementation details of the specific web services to the UI layer. 
-
-**Web Services Stubs (WSS) Layer** – This layer contains the actual proxy stubs generated from the WSDLs of the web services exposed via B2B Gateway channel. This layer includes the WSDL files and the schemas used to generate the stubs. The stubs are in turn used by the SI layer to invoke the web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall/unmarshall the data from the web services.
-
-*Each of the layers above are further composed of components which implement different parts of the layer. *
+*User Interface (UI) Layer** – This layer provides the user interface for to enter request information pertaining to the PCEHR web services exposed via B2B Gateway channel implemented in the PCEHR system. The UI layer is developed based on the Model View Controller (MVC) design pattern and consists of multiple views, models and controllers. The technology used for developing the UI layer is Java Swing.
+
+*Service Invocation (SI) Layer** – This layer provides the interfaces between the UI layer and Web Services. It provides an interface to pass the request object and receive the response object. The logic obtains references to the web service clients and invokes web service methods. The service invocation layer receives the request from the controller in the UI layer, validates the request, applies the business logic in order to process the request and provides the response to the controller. The service invocation layer encapsulates the implementation details of the specific web services to the UI layer. 
+
+*Web Services Stubs (WSS) Layer** – This layer contains the actual proxy stubs generated from the WSDLs of the web services exposed via B2B Gateway channel. This layer includes the WSDL files and the schemas used to generate the stubs. The stubs are in turn used by the SI layer to invoke the web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall/unmarshall the data from the web services.
 
 
 [[project_admins]]
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_Connector</dc:creator><pubDate>Fri, 27 Jan 2012 05:53:04 -0000</pubDate><guid>https://sourceforge.net71b9dcf6db4e8288da352a4f466bc10d057f16bb</guid></item><item><title>WikiPage Home modified by pcehr_Connector</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Home/</link><description>&lt;pre&gt;--- v3 
+++ v4 
@@ -1,23 +1,16 @@
-Welcome to PCEHR B2B WebService Connector Sample application!
-
+Welcome to PCEHR Connector Sample application!
+
 **Overview: **
-The B2B Inbound Services Test Harness is an open source application being developed to provide the PCEHR vendors with a reference implementation for XDS.b and custom B2B inbound services currently implemented in PCEHR. The list of services planned to be implemented is provided in Appendix A.
-
-**High Level Design:** 
-The application is being built as several layers which are loosely coupled to provide the flexibility to reuse the layers in multiple ways to build client applications. 
-
-
-The layers of the application are described below:
-
-**UI Layer ** 
-This layer provides the user interface for users to enter request information pertaining to the different B2B Inbound services implemented in the PCEHR system. The UI layer is developed based on the MVC design pattern and consists of multiple views, models and controllers. The technology used for developing the UI layer is Java Swing.
-
-
-**Service Invocation Layer ** 
-This layer provides the interfaces for the UI layer to obtain references to the web service clients and invoke methods on them to execute the web services and obtain the response. The service invocation layer receives the request from the controller in the UI layer, validates the request, processes the request using business logic and sends the response back to the controller. The service layer encapsulates the implementation details of the specific web services to the UI layer and provides a interface to pass the request and receive the response from the web services.
-
-**Web Services Stubs** 
-This layer contains the actual proxy stubs generated from the WSDLs of the B2B Inbound web services. This layer also includes the WSDL files and the Schema used to generate the stubs. These stubs are in turn used by the Service Invocation layer to invoke the different web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall and unmarshall the data from the web services.
+This is a sample implementation showcasing connectivity to PCEHR system via B2B Gateway Channel.  The scope of this implementation is limited to implementing the key interaction scenarios exposed via B2B gateway channel and the operations utilised within those scenarios to interact with the PCEHR system.  The sample implementation is an attempt to demonstrate how a local CIS might trigger a set of interactions between a CIS and the PCEHR system. This application does not intend to elaborate on the internal workings of CIS, but is intended to help guide and contextualise interactions between CIS and PCEHR.
+
+*High Level Design:** 
+The application architecture consists of loosely coupled layers as described below -  
+
+**User Interface (UI) Layer** – This layer provides the user interface for to enter request information pertaining to the PCEHR web services exposed via B2B Gateway channel implemented in the PCEHR system. The UI layer is developed based on the Model View Controller (MVC) design pattern and consists of multiple views, models and controllers. The technology used for developing the UI layer is Java Swing.
+
+**Service Invocation (SI) Layer** – This layer provides the interfaces between the UI layer and Web Services. It provides an interface to pass the request object and receive the response object. The logic obtains references to the web service clients and invokes web service methods. The service invocation layer receives the request from the controller in the UI layer, validates the request, applies the business logic in order to process the request and provides the response to the controller. The service invocation layer encapsulates the implementation details of the specific web services to the UI layer. 
+
+**Web Services Stubs (WSS) Layer** – This layer contains the actual proxy stubs generated from the WSDLs of the web services exposed via B2B Gateway channel. This layer includes the WSDL files and the schemas used to generate the stubs. The stubs are in turn used by the SI layer to invoke the web services and handle the response. Apache CXF is used as the run time to generate the web service stubs and marshall/unmarshall the data from the web services.
 
 *Each of the layers above are further composed of components which implement different parts of the layer. *
 
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">pcehr_Connector</dc:creator><pubDate>Fri, 27 Jan 2012 05:51:45 -0000</pubDate><guid>https://sourceforge.net5c1c220fdd24f64fd1e1026d19d403ba5ec506bb</guid></item><item><title>WikiPage Home modified by PCEHR</title><link>https://sourceforge.net/p/pcehrvendor/wiki/Home/</link><description>&lt;pre&gt;--- v2 
+++ v3 
@@ -1,4 +1,4 @@
-Welcome to PCEHR Vendor Sample application!
+Welcome to PCEHR B2B WebService Connector Sample application!
 
 **Overview: **
 The B2B Inbound Services Test Harness is an open source application being developed to provide the PCEHR vendors with a reference implementation for XDS.b and custom B2B inbound services currently implemented in PCEHR. The list of services planned to be implemented is provided in Appendix A.
&lt;/pre&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PCEHR</dc:creator><pubDate>Fri, 27 Jan 2012 04:17:24 -0000</pubDate><guid>https://sourceforge.net65167ac72dcda333984d264706298b1c072fde5d</guid></item></channel></rss>