Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » OHF » Mesa testing and OHF
Mesa testing and OHF [message #42052] Tue, 25 March 2008 21:06 Go to next message
Eclipse UserFriend
Originally posted by: ralkire.ndorange.com

http://wiki.eclipse.org/OHF_MESA_Test_Status

I am particularly interested in the XDS.a and XDS.b tests. How are these
run and where is the documentation for running them?

============================================================ ==============================

For testing using xdstest2 tool:

http://ihewiki.wustl.edu/wiki/index.php/XDS_Transactions#Pro vide_and_Register_Document_Set-a
lists several transactions for which I find no corresponding WS;
http://localhost:8080/bridge/services lists the services available:
a.. QueryDocumentsByPatientId
b.. QueryDocumentsFind
c.. QueryDocumentsGet
d.. QueryDocumentsFind
e.. RetrieveDocumentByUrl
f.. RetrieveDocumentSet
g.. WrapInCdaAndSubmitDocument
h.. SubmitDocument
i.. SearchPatient
j.. AdmitInpatient
k.. RegisterOutpatient
l.. PreAdmitInpatient
m.. UpdateOutPatient
n.. UpdateInPatient
o.. MergePatient
p.. AuditPhiImport
q.. UpdateInPatient
r.. AuditPhiExport
s.. AuditActorStartEvent
t.. AuditActorStopEvent
u.. AuditUserAuthenticationLoginEvent
v.. AuditUserAuthenticationLogoutEvent
w.. AuditQueryEvent
x.. AuditPatientRecordReadEvent
y.. AuditPatientRecordCreateEvent
z.. AuditPatientRecordUpdateEvent
aa.. AuditPatientRecordDeleteEvent
ab.. GetRhios
ac.. GetMyLog
Those services are available here however:
http://129.6.24.109:9080/axis2/services/listServices

I suppose no one is using xdstest2 tool to run Mesa tests; thus the reason I
am requesting how to run those tests...

Thanks
Re: Mesa testing and OHF [message #42114 is a reply to message #42052] Tue, 25 March 2008 23:31 Go to previous message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Robert,

About MESA Testing
------------------
XDS MESA tests cover all of the actors with specific tools used for
specific actors. Think of it simply in four major parts:

- Document Registry
- Document Repository
- Document Source
- Document Consumer

Registry and Repository are server-side / infrastructure actors. Source
and Consumer are generally client-side actors.

OHF IHE component provides an implementation of the Document Source and
Document Consumer actors. Additionally, the OHF Bridge provides an
aggregated interface that provides access to the Source and Consumer
actors (primary purpose of the Bridge is to enable non-Java applications
to use the IHE components).

From a MESA testing point of view, all four actors are tested. The
tests here
(http://ihewiki.wustl.edu/wiki/index.php/XDS_Test_Kit_2006-2 007_Test_Descriptions)
are classified by their actor(s). In general:
- Infrastructure actor implementations (registry/repository) are tested
with the xdstest tool. Server-side exampls are the IBM XDS.a/b
Registry/Repository, the Tiani-Spirit XDS.a/b Registry/Repository, the
Microsoft XDS.b Registry/Repository. This enables validation of those
server-side implementations from a de-facto IHE source/consumer client
(xdstest2).

- Client actors (source/consumer) are tested using the NIST XDS
registry/repository as the infrastructure server. An example of this
is... using the OHF XDS Consumer, you would query for a specific patient
ID by giving the NIST XDS Registry's URL as the Web service endpoint.
This again enables validation of the client-side implementations via a
de-facto IHE registry/repository implementation (NIST).


Using OHF For MESA Testing
--------------------------
OHF provides examples of source code (Plugin and Bridge) that can be
used to pass 2007-2008 MESA for the XDS.a/XDS.b Source, XDS.a/XDS.b
Consumer, PIX Source, PIX Consumer, PDQ Consumer, and ATNA Secure Node
actor tests. Those tests are enumerated here:
http://wiki.eclipse.org/OHF_MESA_Test_Status

What these code snippets represent are generic uses of OHF in a way to
model your application to pass MESA. They can also be used *directly*
to pass the MESA tests as-is or you can apply them to workflow cases in
your application.

The OHF source code examples for MESA testing are in each of the
individual actor's source code directories. See the "src_test" folder
under the individual projects in CVS. Note that they are numbered by
the MESA test they implement.

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.bridge.ws/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.xds.source/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.xds.consumer/?root=Technology_Proje ct
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pix.source/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pix.consumer/?root=Technology_Proje ct
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pdq.consumer/?root=Technology_Proje ct

As far as I know, the xdstest tool should not be used in conjunction
with OHF, with the exception being test 11170 that is a configuration
only test (and does not use OHF at all).

Also, OHF only provides MESA source examples for tests that test the
functionality of OHF. What I mean is... for tests that are outside of
the scope of OHF, such as content source/consumer tests, we do not
provide an example implementation, as OHF does not directly provide a
content source/consumer implementation. The way we base this is - the
tests that were marked "R" on our MESA todo list from NA Connectathon
2008 as a document source, document consumer, pix feed, pix query, and
atna secure node Connectathon participant is what we provide source
code, in addition to a few ones marked "O".

I really do hope this helps. Please let me know if you have any other
questions about MESA testing and OHF.

Thanks,
-Matt




Robert Alkire wrote:
> http://wiki.eclipse.org/OHF_MESA_Test_Status
>
> I am particularly interested in the XDS.a and XDS.b tests. How are these
> run and where is the documentation for running them?
>
> ============================================================ ==============================
>
> For testing using xdstest2 tool:
>
> http://ihewiki.wustl.edu/wiki/index.php/XDS_Transactions#Pro vide_and_Register_Document_Set-a
> lists several transactions for which I find no corresponding WS;
> http://localhost:8080/bridge/services lists the services available:
> a.. QueryDocumentsByPatientId
> b.. QueryDocumentsFind
> c.. QueryDocumentsGet
> d.. QueryDocumentsFind
> e.. RetrieveDocumentByUrl
> f.. RetrieveDocumentSet
> g.. WrapInCdaAndSubmitDocument
> h.. SubmitDocument
> i.. SearchPatient
> j.. AdmitInpatient
> k.. RegisterOutpatient
> l.. PreAdmitInpatient
> m.. UpdateOutPatient
> n.. UpdateInPatient
> o.. MergePatient
> p.. AuditPhiImport
> q.. UpdateInPatient
> r.. AuditPhiExport
> s.. AuditActorStartEvent
> t.. AuditActorStopEvent
> u.. AuditUserAuthenticationLoginEvent
> v.. AuditUserAuthenticationLogoutEvent
> w.. AuditQueryEvent
> x.. AuditPatientRecordReadEvent
> y.. AuditPatientRecordCreateEvent
> z.. AuditPatientRecordUpdateEvent
> aa.. AuditPatientRecordDeleteEvent
> ab.. GetRhios
> ac.. GetMyLog
> Those services are available here however:
> http://129.6.24.109:9080/axis2/services/listServices
>
> I suppose no one is using xdstest2 tool to run Mesa tests; thus the reason I
> am requesting how to run those tests...
>
> Thanks
>
>
Re: Mesa testing and OHF [message #585203 is a reply to message #42052] Tue, 25 March 2008 23:31 Go to previous message
Matthew DavisFriend
Messages: 269
Registered: July 2009
Senior Member
Robert,

About MESA Testing
------------------
XDS MESA tests cover all of the actors with specific tools used for
specific actors. Think of it simply in four major parts:

- Document Registry
- Document Repository
- Document Source
- Document Consumer

Registry and Repository are server-side / infrastructure actors. Source
and Consumer are generally client-side actors.

OHF IHE component provides an implementation of the Document Source and
Document Consumer actors. Additionally, the OHF Bridge provides an
aggregated interface that provides access to the Source and Consumer
actors (primary purpose of the Bridge is to enable non-Java applications
to use the IHE components).

From a MESA testing point of view, all four actors are tested. The
tests here
(http://ihewiki.wustl.edu/wiki/index.php/XDS_Test_Kit_2006-2 007_Test_Descriptions)
are classified by their actor(s). In general:
- Infrastructure actor implementations (registry/repository) are tested
with the xdstest tool. Server-side exampls are the IBM XDS.a/b
Registry/Repository, the Tiani-Spirit XDS.a/b Registry/Repository, the
Microsoft XDS.b Registry/Repository. This enables validation of those
server-side implementations from a de-facto IHE source/consumer client
(xdstest2).

- Client actors (source/consumer) are tested using the NIST XDS
registry/repository as the infrastructure server. An example of this
is... using the OHF XDS Consumer, you would query for a specific patient
ID by giving the NIST XDS Registry's URL as the Web service endpoint.
This again enables validation of the client-side implementations via a
de-facto IHE registry/repository implementation (NIST).


Using OHF For MESA Testing
--------------------------
OHF provides examples of source code (Plugin and Bridge) that can be
used to pass 2007-2008 MESA for the XDS.a/XDS.b Source, XDS.a/XDS.b
Consumer, PIX Source, PIX Consumer, PDQ Consumer, and ATNA Secure Node
actor tests. Those tests are enumerated here:
http://wiki.eclipse.org/OHF_MESA_Test_Status

What these code snippets represent are generic uses of OHF in a way to
model your application to pass MESA. They can also be used *directly*
to pass the MESA tests as-is or you can apply them to workflow cases in
your application.

The OHF source code examples for MESA testing are in each of the
individual actor's source code directories. See the "src_test" folder
under the individual projects in CVS. Note that they are numbered by
the MESA test they implement.

http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.bridge.ws/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.xds.source/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.xds.consumer/?root=Technology_Proje ct
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pix.source/?root=Technology_Project
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pix.consumer/?root=Technology_Proje ct
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ohf/plu gins/org.eclipse.ohf.ihe.pdq.consumer/?root=Technology_Proje ct

As far as I know, the xdstest tool should not be used in conjunction
with OHF, with the exception being test 11170 that is a configuration
only test (and does not use OHF at all).

Also, OHF only provides MESA source examples for tests that test the
functionality of OHF. What I mean is... for tests that are outside of
the scope of OHF, such as content source/consumer tests, we do not
provide an example implementation, as OHF does not directly provide a
content source/consumer implementation. The way we base this is - the
tests that were marked "R" on our MESA todo list from NA Connectathon
2008 as a document source, document consumer, pix feed, pix query, and
atna secure node Connectathon participant is what we provide source
code, in addition to a few ones marked "O".

I really do hope this helps. Please let me know if you have any other
questions about MESA testing and OHF.

Thanks,
-Matt




Robert Alkire wrote:
> http://wiki.eclipse.org/OHF_MESA_Test_Status
>
> I am particularly interested in the XDS.a and XDS.b tests. How are these
> run and where is the documentation for running them?
>
> ============================================================ ==============================
>
> For testing using xdstest2 tool:
>
> http://ihewiki.wustl.edu/wiki/index.php/XDS_Transactions#Pro vide_and_Register_Document_Set-a
> lists several transactions for which I find no corresponding WS;
> http://localhost:8080/bridge/services lists the services available:
> a.. QueryDocumentsByPatientId
> b.. QueryDocumentsFind
> c.. QueryDocumentsGet
> d.. QueryDocumentsFind
> e.. RetrieveDocumentByUrl
> f.. RetrieveDocumentSet
> g.. WrapInCdaAndSubmitDocument
> h.. SubmitDocument
> i.. SearchPatient
> j.. AdmitInpatient
> k.. RegisterOutpatient
> l.. PreAdmitInpatient
> m.. UpdateOutPatient
> n.. UpdateInPatient
> o.. MergePatient
> p.. AuditPhiImport
> q.. UpdateInPatient
> r.. AuditPhiExport
> s.. AuditActorStartEvent
> t.. AuditActorStopEvent
> u.. AuditUserAuthenticationLoginEvent
> v.. AuditUserAuthenticationLogoutEvent
> w.. AuditQueryEvent
> x.. AuditPatientRecordReadEvent
> y.. AuditPatientRecordCreateEvent
> z.. AuditPatientRecordUpdateEvent
> aa.. AuditPatientRecordDeleteEvent
> ab.. GetRhios
> ac.. GetMyLog
> Those services are available here however:
> http://129.6.24.109:9080/axis2/services/listServices
>
> I suppose no one is using xdstest2 tool to run Mesa tests; thus the reason I
> am requesting how to run those tests...
>
> Thanks
>
>
Previous Topic:Mesa testing and OHF
Next Topic:XCA on the bridge
Goto Forum:
  


Current Time: Sat Nov 17 15:00:08 GMT 2018

Powered by FUDForum. Page generated in 0.01878 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top