openmed-developer — Developers discussion list

Re: [OpenEMed-developer] OpenORB Trader problem

[David F. <dw...@la...>]

I checked in the OpenORB 1.40BETA 2 jar files into lib/orb in OpenEMed and =
it does seem that the =0D
Trader problem is now fixed. ( I hope that other problems haven't been crea=
ted).=0D
=0D
Dave=0D
=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li..., "Polar Humenn" <po...@sy...>=
=0D
Date: Fri, Aug-6-2004 9:00 PM=0D
Subject: [OpenEMed-developer] OpenORB Trader problem=0D
I upgraded my OpenORB to 1.4.0 BETA2 (with compiler debug on) and the Trade=
r problem seems disappear now.=0D
=0D
Joncheng=0D
=0D
David Forslund wrote:=0D
=0D
Hmm.   This is what I see. It used to work.  I'll try to upgrade to the new=
 OpenORB soon and see if this fixes the problem.  I'm actually using=0D
some intermediate version from CVS.   I thought it was working when I teste=
d it.=0D
=0D
Dave=0D
=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li..., "Polar Humenn" <po...@sy...>=
=0D
Date: Tue, Aug-3-2004 10:02 PM=0D
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer=0D
David Forslund wrote:=0D
=0D
I'm having some problem at the moment getting using the Trader with PIDS, b=
ut I think this is an unrelated issue.=0D
=0D
I have a problem too. Every time before I restart the PIDS server, I have t=
o restart the Trader as well. If not, my PIDS client will not access the Tr=
ader. I suspect it's a Trader implementation problem because the Trader thr=
ows an UNKNOWN exception, meaning that the Trader servant throws a non-CORB=
A exception that is caught by the ORB.=0D
=0D
I don't have time for this problem now. I may try OpenORB 1.4.0 BETA2 later=
.=0D
=0D
Joncheng=0D
=0D
=0D
=0D
Dave

[OpenEMed-developer] OpenORB Trader problem

[Joncheng K. <ck...@sy...>]

I upgraded my OpenORB to 1.4.0 BETA2 (with compiler debug on) and the 
Trader problem seems disappear now.

Joncheng

David Forslund wrote:

> Hmm.   This is what I see. It used to work.  I'll try to upgrade to 
> the new OpenORB soon and see if this fixes the problem.  I'm actually 
> using
> some intermediate version from CVS.   I thought it was working when I 
> tested it.
>  
> Dave
>  
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li..., "Polar Humenn"
>     <po...@sy...>
>     Date: Tue, Aug-3-2004 10:02 PM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     David Forslund wrote:
>
>>     I'm having some problem at the moment getting using the Trader
>>     with PIDS, but I think this is an unrelated issue.
>
>
>     I have a problem too. Every time before I restart the PIDS server,
>     I have to restart the Trader as well. If not, my PIDS client will
>     not access the Trader. I suspect it's a Trader implementation
>     problem because the Trader throws an UNKNOWN exception, meaning
>     that the Trader servant throws a non-CORBA exception that is
>     caught by the ORB.
>
>     I don't have time for this problem now. I may try OpenORB 1.4.0
>     BETA2 later.
>
>     Joncheng
>
>>      
>>     Dave
>>      
>>
>>

Re: [OpenEMed-developer] Re: Your contributions

[David F. <dw...@la...>]

I'm interested in what you did to deal with existing database schema.  This=
 is what Gerrit had to do with the "pass thru" COAS implementation.  I thin=
k it could be improved along the lines you describe.=0D
=0D
Dave=0D
=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Thu, Aug-5-2004 1:05 PM=0D
Subject: Re: [OpenEMed-developer] Re: Your contributions=0D
David Forslund wrote:=0D
=0D
The implementation of query interfaces in PidServer and COAS isn't that tie=
d to a specific persistence implemention.  It only uses the interfaces prov=
ided by the DatabaseMgr.=0D
I know, but several issues came up when I tried to reuse the OpenEMed imple=
mentation for some existing database schema. For example, the making of Sea=
rchFilter is schema specific because you have to refer to the column names.=
 An other example is about traits. Traits are stored in a seperate table in=
 OpenEMed but are stored as columns of the Identity table in our case. Thus=
, the access of traits has to be replaced too.=0D
=0D
I'm not saying that we always want general implementations, but there seems=
 a way to create a persistent access layer based on the conceptual model of=
 observations and identities/traits and implement this layer using the data=
base layer of OpenEMed.=0D
=0D
=0D
A potentially big advantage of using the model is the inheritance that is p=
resent in the model but is not reflected in the COAS IDL.  =0D
=0D
That's right.=0D
=0D
Cheers,=0D
Joncheng=0D
=0D
=0D
=0D
Dave=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Thu, Aug-5-2004 9:42 AM=0D
Subject: Re: [OpenEMed-developer] Re: Your contributions=0D
David Forslund wrote:=0D
=0D
Don't worry too much about it, but people have been asking for a Web Servic=
es interface to OpenEMed.   One way I have begun accommodating that is to t=
reat the CORBA layer has a translation from simple Java rather than having =
CORBA embedded too deeply in the code.   This way it is fairly easy to expo=
se the Java code to Web Services.   The CORBA layer could be translated to =
Web Services, too, but this is somewhat less efficient.=0D
OpenEMed has a persistent layer (gov.lanl.Database) that is indepedent from=
 specific persistent storage. However, the implementation of query interfac=
es in PidServer and COAS is somewhat tied into the specific presistent obje=
ct implementation. On the other hand, the non-persistent object returned by=
 PersistentObject.toObject() is basically tied into CORBA specific data str=
ucture (e.g., ObservationDataStruct) or interfaces (e.g., IdentityCore). A =
better approach will be to create an interface (or framework of interfaces)=
 that is based the conceptual model of the non-persistent object such as th=
e COAS Information Model described in COAS Chapter 2.=0D
=0D
Joncheng=0D
=0D
=0D
=0D
Dave=0D
=0D
=0D
Joncheng=0D
=0D
Thanks,=0D
=0D
Dave=0D
=0D
  =0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Wed, Aug-4-2004 9:29 PM=0D
Subject: [OpenEMed-developer] Re: Your contributions=0D
=0D
David Forslund wrote:=0D
=0D
    =0D
it might be a good idea if you pass by me the structure that you are =0D
      =0D
going to submit, so I can make sure that it fits it with the overall =0D
design (that might not be that clear).=0D
    =0D
I will. I've been thinking about the design and changes needed for a =0D
few =0D
days. Here are some thoughts that I'm considering.=0D
=0D
1. Create an interface called "PersistentObservationAccess" (see the =0D
attached file).=0D
This interface is neutral to specific database schema. It is basically =0D
the replacement for the retrieveObservations() method in =0D
QueryAccessImpl. In this way, QueryAccessImpl will be independent from =0D
any particular database schema. We can configure the actual class =0D
implementing this interface depending on any specific database =0D
schema/structure.=0D
=0D
2. Create a "remote" package under gov.lanl.COAS and implement =0D
interfaces related to ObservationRemote such as ObservedSubject, =0D
ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl =0D
class will be still under gov.lanl.COAS, but it'll use classes =0D
implemented in this "remote" package.=0D
=0D
Besides, I found that the done() method is not adequately implemented. =0D
We have to deactivate objects like ObservationDataIterator from their =0D
POA or they never get removed. Both COAS and PIDS will need to use this =
=0D
=0D
deactivate code.=0D
=0D
Joncheng=0D
=0D
    =0D
Thanks,=0D
=0D
Dave=0D
=0D
=0D
=0D
=0D
=0D
 =0D
=0D
      =0D
// PersistentObservationAccess.java=0D
=0D
/**=0D
 * ***********************************=0D
 * Copyright Notice=0D
 * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of =0D
California. All rights reserved.=0D
 *=0D
 * DISCLAIMER=0D
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' =0D
AND ANY EXPRESS=0D
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED =0D
WARRANTIES OF=0D
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. =
=0D
IN NO EVENT=0D
 * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, =0D
INDIRECT, INCIDENTAL,=0D
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT =0D
LIMITED TO,=0D
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR =0D
PROFITS; OR=0D
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF =0D
LIABILITY, WHETHER IN=0D
 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR =0D
OTHERWISE) ARISING IN=0D
 * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE =0D
POSSIBILITY OF SUCH=0D
 * DAMAGE.=0D
 * ************************************=0D
 */=0D
package gov.lanl.COAS;=0D
=0D
import org.omg.CORBA.Any;=0D
import org.omg.DsObservationAccess.*;=0D
import org.omg.PersonIdService.QualifiedPersonId;=0D
=0D
import java.util.ArrayList;=0D
=0D
/**=0D
 * This interface specifies the methods for accessing the persistent =0D
storage=0D
 * of observations. It provides an interface that is indepedant from =0D
actual=0D
 * database schema for storing observations.=0D
 */=0D
public interface PersistentObservationAccess=0D
{=0D
    /**=0D
     * Initialize this observation access object.=0D
     */=0D
    public void init(=0D
        gov.lanl.Database.DatabaseMgr dbMgr,=0D
        gov.lanl.Database.PersistentObjectFactory persObjFact,=0D
        gov.lanl.Database.CodeMapper codeMapper,=0D
        gov.lanl.COAS.PolicyMgr policyMgr);=0D
=0D
    /**=0D
     * Retrieve one observation with its observation ID.=0D
     * @param observation_id   the observation ID=0D
     * @return the observation that matches the given observation ID.=0D
     * @exception InvalidOids  if the observation cannot be found.=0D
     */=0D
    public PersistentCOAS retrieveObservation(=0D
        ObservationId observation_id=0D
    ) throws=0D
        InvalidOids;=0D
=0D
    /**=0D
     * Count observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return the number of observations satisfying the specified =0D
policy=0D
     */=0D
    public int countObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy=0D
    ) throws=0D
        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,=0D
        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,=0D
        InvalidPolicies, DuplicatePolicies;=0D
=0D
    /**=0D
     * Retrieve observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return a vector of objects implementing the {@link =0D
PersistentCOAS}=0D
     *         interface.=0D
     */=0D
    public ArrayList retrieveObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy);=0D
=0D
}=0D
=0D
=0D
    =0D
=0D
=0D
=0D
=0D
-------------------------------------------------------=0D
This SF.Net email is sponsored by OSTG. Have you noticed the changes on=0D
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,=0D
one more big change to announce. We are now OSTG- Open Source Technology=
=0D
Group. Come see the changes on the new OSTG site. www.ostg.com=0D
_______________________________________________=0D
OpenMed-developer mailing list=0D
Ope...@li...=0D
https://lists.sourceforge.net/lists/listinfo/openmed-developer=0D
=0D
=0D
=0D
  =

Re: [OpenEMed-developer] Re: Your contributions

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> The implementation of query interfaces in PidServer and COAS isn't 
> that tied to a specific persistence implemention.  It only uses the 
> interfaces provided by the DatabaseMgr.

I know, but several issues came up when I tried to reuse the OpenEMed 
implementation for some existing database schema. For example, the 
making of SearchFilter is schema specific because you have to refer to 
the column names. An other example is about traits. Traits are stored in 
a seperate table in OpenEMed but are stored as columns of the Identity 
table in our case. Thus, the access of traits has to be replaced too.

I'm not saying that we always want general implementations, but there 
seems a way to create a persistent access layer based on the conceptual 
model of observations and identities/traits and implement this layer 
using the database layer of OpenEMed.

> A potentially big advantage of using the model is the inheritance that 
> is present in the model but is not reflected in the COAS IDL. 

That's right.

Cheers,
Joncheng

>  
>  
> Dave
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Thu, Aug-5-2004 9:42 AM
>     Subject: Re: [OpenEMed-developer] Re: Your contributions
>     David Forslund wrote:
>
>>     Don't worry too much about it, but people have been asking for a
>>     Web Services interface to OpenEMed.   One way I have begun
>>     accommodating that is to treat the CORBA layer has a translation
>>     from simple Java rather than having CORBA embedded too deeply in
>>     the code.   This way it is fairly easy to expose the Java code to
>>     Web Services.   The CORBA layer could be translated to Web
>>     Services, too, but this is somewhat less efficient.
>
>     OpenEMed has a persistent layer (gov.lanl.Database) that is
>     indepedent from specific persistent storage. However, the
>     implementation of query interfaces in PidServer and COAS is
>     somewhat tied into the specific presistent object implementation.
>     On the other hand, the non-persistent object returned by
>     PersistentObject.toObject() is basically tied into CORBA specific
>     data structure (e.g., ObservationDataStruct) or interfaces (e.g.,
>     IdentityCore). A better approach will be to create an interface
>     (or framework of interfaces) that is based the conceptual model of
>     the non-persistent object such as the COAS Information Model
>     described in COAS Chapter 2.
>
>     Joncheng
>
>>      
>>     Dave
>>
>>
>>     Joncheng
>>
>>>Thanks,
>>>
>>>Dave
>>>
>>>  
>>>
>>>>------------Original Message------------
>>>>From: Joncheng Kuo <ck...@sy...>
>>>>To: "David Forslund" <dw...@la...>
>>>>Cc: ope...@li...
>>>>Date: Wed, Aug-4-2004 9:29 PM
>>>>Subject: [OpenEMed-developer] Re: Your contributions
>>>>
>>>>David Forslund wrote:
>>>>
>>>>    
>>>>
>>>>>it might be a good idea if you pass by me the structure that you are 
>>>>>      
>>>>>
>>>>going to submit, so I can make sure that it fits it with the overall 
>>>>design (that might not be that clear).
>>>>    
>>>>
>>>>I will. I've been thinking about the design and changes needed for a 
>>>>few 
>>>>days. Here are some thoughts that I'm considering.
>>>>
>>>>1. Create an interface called "PersistentObservationAccess" (see the 
>>>>attached file).
>>>>This interface is neutral to specific database schema. It is basically 
>>>>the replacement for the retrieveObservations() method in 
>>>>QueryAccessImpl. In this way, QueryAccessImpl will be independent from 
>>>>any particular database schema. We can configure the actual class 
>>>>implementing this interface depending on any specific database 
>>>>schema/structure.
>>>>
>>>>2. Create a "remote" package under gov.lanl.COAS and implement 
>>>>interfaces related to ObservationRemote such as ObservedSubject, 
>>>>ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl 
>>>>class will be still under gov.lanl.COAS, but it'll use classes 
>>>>implemented in this "remote" package.
>>>>
>>>>Besides, I found that the done() method is not adequately implemented. 
>>>>We have to deactivate objects like ObservationDataIterator from their 
>>>>POA or they never get removed. Both COAS and PIDS will need to use this 
>>>>
>>>>deactivate code.
>>>>
>>>>Joncheng
>>>>
>>>>    
>>>>
>>>>>Thanks,
>>>>>
>>>>>Dave
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>>      
>>>>>
>>>>// PersistentObservationAccess.java
>>>>
>>>>/**
>>>> * ***********************************
>>>> * Copyright Notice
>>>> * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of 
>>>>California. All rights reserved.
>>>> *
>>>> * DISCLAIMER
>>>> * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' 
>>>>AND ANY EXPRESS
>>>> * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
>>>>WARRANTIES OF
>>>> * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
>>>>IN NO EVENT
>>>> * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
>>>>INDIRECT, INCIDENTAL,
>>>> * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
>>>>LIMITED TO,
>>>> * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
>>>>PROFITS; OR
>>>> * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
>>>>LIABILITY, WHETHER IN
>>>> * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR 
>>>>OTHERWISE) ARISING IN
>>>> * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
>>>>POSSIBILITY OF SUCH
>>>> * DAMAGE.
>>>> * ************************************
>>>> */
>>>>package gov.lanl.COAS;
>>>>
>>>>import org.omg.CORBA.Any;
>>>>import org.omg.DsObservationAccess.*;
>>>>import org.omg.PersonIdService.QualifiedPersonId;
>>>>
>>>>import java.util.ArrayList;
>>>>
>>>>/**
>>>> * This interface specifies the methods for accessing the persistent 
>>>>storage
>>>> * of observations. It provides an interface that is indepedant from 
>>>>actual
>>>> * database schema for storing observations.
>>>> */
>>>>public interface PersistentObservationAccess
>>>>{
>>>>    /**
>>>>     * Initialize this observation access object.
>>>>     */
>>>>    public void init(
>>>>        gov.lanl.Database.DatabaseMgr dbMgr,
>>>>        gov.lanl.Database.PersistentObjectFactory persObjFact,
>>>>        gov.lanl.Database.CodeMapper codeMapper,
>>>>        gov.lanl.COAS.PolicyMgr policyMgr);
>>>>
>>>>    /**
>>>>     * Retrieve one observation with its observation ID.
>>>>     * @param observation_id   the observation ID
>>>>     * @return the observation that matches the given observation ID.
>>>>     * @exception InvalidOids  if the observation cannot be found.
>>>>     */
>>>>    public PersistentCOAS retrieveObservation(
>>>>        ObservationId observation_id
>>>>    ) throws
>>>>        InvalidOids;
>>>>
>>>>    /**
>>>>     * Count observations based on the specified policy.
>>>>     *
>>>>     * @param who
>>>>     * @param what
>>>>     * @param when
>>>>     * @param qualifiers
>>>>     * @param policy
>>>>     *
>>>>     * @return the number of observations satisfying the specified 
>>>>policy
>>>>     */
>>>>    public int countObservationsWithPolicy(
>>>>        QualifiedPersonId[] who, String[] what,
>>>>        TimeSpan when, Any[] qualifiers,
>>>>        NameValuePair[] policy
>>>>    ) throws
>>>>        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,
>>>>        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,
>>>>        InvalidPolicies, DuplicatePolicies;
>>>>
>>>>    /**
>>>>     * Retrieve observations based on the specified policy.
>>>>     *
>>>>     * @param who
>>>>     * @param what
>>>>     * @param when
>>>>     * @param qualifiers
>>>>     * @param policy
>>>>     *
>>>>     * @return a vector of objects implementing the {@link 
>>>>PersistentCOAS}
>>>>     *         interface.
>>>>     */
>>>>    public ArrayList retrieveObservationsWithPolicy(
>>>>        QualifiedPersonId[] who, String[] what,
>>>>        TimeSpan when, Any[] qualifiers,
>>>>        NameValuePair[] policy);
>>>>
>>>>}
>>>>
>>>>
>>>>    
>>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by OSTG. Have you noticed the changes on
>>>Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
>>>one more big change to announce. We are now OSTG- Open Source Technology
>>>Group. Come see the changes on the new OSTG site. www.ostg.com
>>>_______________________________________________
>>>OpenMed-developer mailing list
>>>Ope...@li...
>>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>>
>>>
>>>
>>>  
>>>

Re: [OpenEMed-developer] Re: Your contributions

[David F. <dw...@la...>]

The implementation of query interfaces in PidServer and COAS isn't that tie=
d to a specific persistence implemention.  It only uses the interfaces prov=
ided by the DatabaseMgr.   Using the COAS information model would be a good=
 idea.  I've removed some of the CORBA dependencies, but haven't taken on t=
he larger task of using the conceptual model.  A potentially big advantage =
of using the model is the inheritance that is present in the model but is n=
ot reflected in the COAS IDL.   =0D
=0D
=0D
Dave=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Thu, Aug-5-2004 9:42 AM=0D
Subject: Re: [OpenEMed-developer] Re: Your contributions=0D
David Forslund wrote:=0D
=0D
Don't worry too much about it, but people have been asking for a Web Servic=
es interface to OpenEMed.   One way I have begun accommodating that is to t=
reat the CORBA layer has a translation from simple Java rather than having =
CORBA embedded too deeply in the code.   This way it is fairly easy to expo=
se the Java code to Web Services.   The CORBA layer could be translated to =
Web Services, too, but this is somewhat less efficient.=0D
OpenEMed has a persistent layer (gov.lanl.Database) that is indepedent from=
 specific persistent storage. However, the implementation of query interfac=
es in PidServer and COAS is somewhat tied into the specific presistent obje=
ct implementation. On the other hand, the non-persistent object returned by=
 PersistentObject.toObject() is basically tied into CORBA specific data str=
ucture (e.g., ObservationDataStruct) or interfaces (e.g., IdentityCore). A =
better approach will be to create an interface (or framework of interfaces)=
 that is based the conceptual model of the non-persistent object such as th=
e COAS Information Model described in COAS Chapter 2.=0D
=0D
Joncheng=0D
=0D
=0D
=0D
Dave=0D
=0D
=0D
Joncheng=0D
=0D
Thanks,=0D
=0D
Dave=0D
=0D
  =0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Wed, Aug-4-2004 9:29 PM=0D
Subject: [OpenEMed-developer] Re: Your contributions=0D
=0D
David Forslund wrote:=0D
=0D
    =0D
it might be a good idea if you pass by me the structure that you are =0D
      =0D
going to submit, so I can make sure that it fits it with the overall =0D
design (that might not be that clear).=0D
    =0D
I will. I've been thinking about the design and changes needed for a =0D
few =0D
days. Here are some thoughts that I'm considering.=0D
=0D
1. Create an interface called "PersistentObservationAccess" (see the =0D
attached file).=0D
This interface is neutral to specific database schema. It is basically =0D
the replacement for the retrieveObservations() method in =0D
QueryAccessImpl. In this way, QueryAccessImpl will be independent from =0D
any particular database schema. We can configure the actual class =0D
implementing this interface depending on any specific database =0D
schema/structure.=0D
=0D
2. Create a "remote" package under gov.lanl.COAS and implement =0D
interfaces related to ObservationRemote such as ObservedSubject, =0D
ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl =0D
class will be still under gov.lanl.COAS, but it'll use classes =0D
implemented in this "remote" package.=0D
=0D
Besides, I found that the done() method is not adequately implemented. =0D
We have to deactivate objects like ObservationDataIterator from their =0D
POA or they never get removed. Both COAS and PIDS will need to use this =
=0D
=0D
deactivate code.=0D
=0D
Joncheng=0D
=0D
    =0D
Thanks,=0D
=0D
Dave=0D
=0D
=0D
=0D
=0D
=0D
 =0D
=0D
      =0D
// PersistentObservationAccess.java=0D
=0D
/**=0D
 * ***********************************=0D
 * Copyright Notice=0D
 * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of =0D
California. All rights reserved.=0D
 *=0D
 * DISCLAIMER=0D
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' =0D
AND ANY EXPRESS=0D
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED =0D
WARRANTIES OF=0D
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. =
=0D
IN NO EVENT=0D
 * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, =0D
INDIRECT, INCIDENTAL,=0D
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT =0D
LIMITED TO,=0D
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR =0D
PROFITS; OR=0D
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF =0D
LIABILITY, WHETHER IN=0D
 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR =0D
OTHERWISE) ARISING IN=0D
 * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE =0D
POSSIBILITY OF SUCH=0D
 * DAMAGE.=0D
 * ************************************=0D
 */=0D
package gov.lanl.COAS;=0D
=0D
import org.omg.CORBA.Any;=0D
import org.omg.DsObservationAccess.*;=0D
import org.omg.PersonIdService.QualifiedPersonId;=0D
=0D
import java.util.ArrayList;=0D
=0D
/**=0D
 * This interface specifies the methods for accessing the persistent =0D
storage=0D
 * of observations. It provides an interface that is indepedant from =0D
actual=0D
 * database schema for storing observations.=0D
 */=0D
public interface PersistentObservationAccess=0D
{=0D
    /**=0D
     * Initialize this observation access object.=0D
     */=0D
    public void init(=0D
        gov.lanl.Database.DatabaseMgr dbMgr,=0D
        gov.lanl.Database.PersistentObjectFactory persObjFact,=0D
        gov.lanl.Database.CodeMapper codeMapper,=0D
        gov.lanl.COAS.PolicyMgr policyMgr);=0D
=0D
    /**=0D
     * Retrieve one observation with its observation ID.=0D
     * @param observation_id   the observation ID=0D
     * @return the observation that matches the given observation ID.=0D
     * @exception InvalidOids  if the observation cannot be found.=0D
     */=0D
    public PersistentCOAS retrieveObservation(=0D
        ObservationId observation_id=0D
    ) throws=0D
        InvalidOids;=0D
=0D
    /**=0D
     * Count observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return the number of observations satisfying the specified =0D
policy=0D
     */=0D
    public int countObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy=0D
    ) throws=0D
        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,=0D
        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,=0D
        InvalidPolicies, DuplicatePolicies;=0D
=0D
    /**=0D
     * Retrieve observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return a vector of objects implementing the {@link =0D
PersistentCOAS}=0D
     *         interface.=0D
     */=0D
    public ArrayList retrieveObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy);=0D
=0D
}=0D
=0D
=0D
    =0D
=0D
=0D
=0D
=0D
-------------------------------------------------------=0D
This SF.Net email is sponsored by OSTG. Have you noticed the changes on=0D
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,=0D
one more big change to announce. We are now OSTG- Open Source Technology=
=0D
Group. Come see the changes on the new OSTG site. www.ostg.com=0D
_______________________________________________=0D
OpenMed-developer mailing list=0D
Ope...@li...=0D
https://lists.sourceforge.net/lists/listinfo/openmed-developer=0D
=0D
=0D
=0D
  =

Re: [OpenEMed-developer] Re: Your contributions

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> Don't worry too much about it, but people have been asking for a Web 
> Services interface to OpenEMed.   One way I have begun accommodating 
> that is to treat the CORBA layer has a translation from simple Java 
> rather than having CORBA embedded too deeply in the code.   This way 
> it is fairly easy to expose the Java code to Web Services.   The CORBA 
> layer could be translated to Web Services, too, but this is somewhat 
> less efficient.

OpenEMed has a persistent layer (gov.lanl.Database) that is indepedent 
from specific persistent storage. However, the implementation of query 
interfaces in PidServer and COAS is somewhat tied into the specific 
presistent object implementation. On the other hand, the non-persistent 
object returned by PersistentObject.toObject() is basically tied into 
CORBA specific data structure (e.g., ObservationDataStruct) or 
interfaces (e.g., IdentityCore). A better approach will be to create an 
interface (or framework of interfaces) that is based the conceptual 
model of the non-persistent object such as the COAS Information Model 
described in COAS Chapter 2.

Joncheng

>  
> Dave
>
>
> Joncheng
>
>>Thanks,
>>
>>Dave
>>
>>  
>>
>>>------------Original Message------------
>>>From: Joncheng Kuo <ck...@sy...>
>>>To: "David Forslund" <dw...@la...>
>>>Cc: ope...@li...
>>>Date: Wed, Aug-4-2004 9:29 PM
>>>Subject: [OpenEMed-developer] Re: Your contributions
>>>
>>>David Forslund wrote:
>>>
>>>    
>>>
>>>>it might be a good idea if you pass by me the structure that you are 
>>>>      
>>>>
>>>going to submit, so I can make sure that it fits it with the overall 
>>>design (that might not be that clear).
>>>    
>>>
>>>I will. I've been thinking about the design and changes needed for a 
>>>few 
>>>days. Here are some thoughts that I'm considering.
>>>
>>>1. Create an interface called "PersistentObservationAccess" (see the 
>>>attached file).
>>>This interface is neutral to specific database schema. It is basically 
>>>the replacement for the retrieveObservations() method in 
>>>QueryAccessImpl. In this way, QueryAccessImpl will be independent from 
>>>any particular database schema. We can configure the actual class 
>>>implementing this interface depending on any specific database 
>>>schema/structure.
>>>
>>>2. Create a "remote" package under gov.lanl.COAS and implement 
>>>interfaces related to ObservationRemote such as ObservedSubject, 
>>>ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl 
>>>class will be still under gov.lanl.COAS, but it'll use classes 
>>>implemented in this "remote" package.
>>>
>>>Besides, I found that the done() method is not adequately implemented. 
>>>We have to deactivate objects like ObservationDataIterator from their 
>>>POA or they never get removed. Both COAS and PIDS will need to use this 
>>>
>>>deactivate code.
>>>
>>>Joncheng
>>>
>>>    
>>>
>>>>Thanks,
>>>>
>>>>Dave
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 
>>>>
>>>>      
>>>>
>>>// PersistentObservationAccess.java
>>>
>>>/**
>>> * ***********************************
>>> * Copyright Notice
>>> * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of 
>>>California. All rights reserved.
>>> *
>>> * DISCLAIMER
>>> * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' 
>>>AND ANY EXPRESS
>>> * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
>>>WARRANTIES OF
>>> * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
>>>IN NO EVENT
>>> * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
>>>INDIRECT, INCIDENTAL,
>>> * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
>>>LIMITED TO,
>>> * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
>>>PROFITS; OR
>>> * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
>>>LIABILITY, WHETHER IN
>>> * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR 
>>>OTHERWISE) ARISING IN
>>> * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
>>>POSSIBILITY OF SUCH
>>> * DAMAGE.
>>> * ************************************
>>> */
>>>package gov.lanl.COAS;
>>>
>>>import org.omg.CORBA.Any;
>>>import org.omg.DsObservationAccess.*;
>>>import org.omg.PersonIdService.QualifiedPersonId;
>>>
>>>import java.util.ArrayList;
>>>
>>>/**
>>> * This interface specifies the methods for accessing the persistent 
>>>storage
>>> * of observations. It provides an interface that is indepedant from 
>>>actual
>>> * database schema for storing observations.
>>> */
>>>public interface PersistentObservationAccess
>>>{
>>>    /**
>>>     * Initialize this observation access object.
>>>     */
>>>    public void init(
>>>        gov.lanl.Database.DatabaseMgr dbMgr,
>>>        gov.lanl.Database.PersistentObjectFactory persObjFact,
>>>        gov.lanl.Database.CodeMapper codeMapper,
>>>        gov.lanl.COAS.PolicyMgr policyMgr);
>>>
>>>    /**
>>>     * Retrieve one observation with its observation ID.
>>>     * @param observation_id   the observation ID
>>>     * @return the observation that matches the given observation ID.
>>>     * @exception InvalidOids  if the observation cannot be found.
>>>     */
>>>    public PersistentCOAS retrieveObservation(
>>>        ObservationId observation_id
>>>    ) throws
>>>        InvalidOids;
>>>
>>>    /**
>>>     * Count observations based on the specified policy.
>>>     *
>>>     * @param who
>>>     * @param what
>>>     * @param when
>>>     * @param qualifiers
>>>     * @param policy
>>>     *
>>>     * @return the number of observations satisfying the specified 
>>>policy
>>>     */
>>>    public int countObservationsWithPolicy(
>>>        QualifiedPersonId[] who, String[] what,
>>>        TimeSpan when, Any[] qualifiers,
>>>        NameValuePair[] policy
>>>    ) throws
>>>        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,
>>>        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,
>>>        InvalidPolicies, DuplicatePolicies;
>>>
>>>    /**
>>>     * Retrieve observations based on the specified policy.
>>>     *
>>>     * @param who
>>>     * @param what
>>>     * @param when
>>>     * @param qualifiers
>>>     * @param policy
>>>     *
>>>     * @return a vector of objects implementing the {@link 
>>>PersistentCOAS}
>>>     *         interface.
>>>     */
>>>    public ArrayList retrieveObservationsWithPolicy(
>>>        QualifiedPersonId[] who, String[] what,
>>>        TimeSpan when, Any[] qualifiers,
>>>        NameValuePair[] policy);
>>>
>>>}
>>>
>>>
>>>    
>>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by OSTG. Have you noticed the changes on
>>Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
>>one more big change to announce. We are now OSTG- Open Source Technology
>>Group. Come see the changes on the new OSTG site. www.ostg.com
>>_______________________________________________
>>OpenMed-developer mailing list
>>Ope...@li...
>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>
>>
>>
>>  
>>

Re: [OpenEMed-developer] Re: Your contributions

[David F. <dw...@la...>]

=0D
=0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Thu, Aug-5-2004 7:20 AM=0D
Subject: Re: [OpenEMed-developer] Re: Your contributions=0D
David Forslund wrote:=0D
=0D
It sounds like you want the interface to help combine=0D
some common code that might exist between QueryAccess and ObservationRemote=
.=0D
Yes, most operations implemented in QueryAccessImpl delegate their job to g=
etObservationsWithPolicy(). This method is basically the same between Query=
AccessImpl and BrowseAccessImpl except for the output format, although Brow=
seAccessImpl can be more efficient by not collecting all sub-observations a=
t once.=0D
=0D
    Is that=0D
correct?  One thing to think about, is the ability to use a POJO (Plain Old=
 Java Object) call=0D
for the case (which seems to be coming up) of using COAS (and PIDS) with We=
b Services.=0D
Sorry, I don't get it.=0D
=0D
Don't worry too much about it, but people have been asking for a Web Servic=
es interface to OpenEMed.   One way I have begun accommodating that is to t=
reat the CORBA layer has a translation from simple Java rather than having =
CORBA embedded too deeply in the code.   This way it is fairly easy to expo=
se the Java code to Web Services.   The CORBA layer could be translated to =
Web Services, too, but this is somewhat less efficient.=0D
=0D
Dave=0D
=0D
=0D
Joncheng=0D
=0D
Thanks,=0D
=0D
Dave=0D
=0D
  =0D
------------Original Message------------=0D
From: Joncheng Kuo <ck...@sy...>=0D
To: "David Forslund" <dw...@la...>=0D
Cc: ope...@li...=0D
Date: Wed, Aug-4-2004 9:29 PM=0D
Subject: [OpenEMed-developer] Re: Your contributions=0D
=0D
David Forslund wrote:=0D
=0D
    =0D
it might be a good idea if you pass by me the structure that you are =0D
      =0D
going to submit, so I can make sure that it fits it with the overall =0D
design (that might not be that clear).=0D
    =0D
I will. I've been thinking about the design and changes needed for a =0D
few =0D
days. Here are some thoughts that I'm considering.=0D
=0D
1. Create an interface called "PersistentObservationAccess" (see the =0D
attached file).=0D
This interface is neutral to specific database schema. It is basically =0D
the replacement for the retrieveObservations() method in =0D
QueryAccessImpl. In this way, QueryAccessImpl will be independent from =0D
any particular database schema. We can configure the actual class =0D
implementing this interface depending on any specific database =0D
schema/structure.=0D
=0D
2. Create a "remote" package under gov.lanl.COAS and implement =0D
interfaces related to ObservationRemote such as ObservedSubject, =0D
ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl =0D
class will be still under gov.lanl.COAS, but it'll use classes =0D
implemented in this "remote" package.=0D
=0D
Besides, I found that the done() method is not adequately implemented. =0D
We have to deactivate objects like ObservationDataIterator from their =0D
POA or they never get removed. Both COAS and PIDS will need to use this =
=0D
=0D
deactivate code.=0D
=0D
Joncheng=0D
=0D
    =0D
Thanks,=0D
=0D
Dave=0D
=0D
=0D
=0D
=0D
=0D
 =0D
=0D
      =0D
// PersistentObservationAccess.java=0D
=0D
/**=0D
 * ***********************************=0D
 * Copyright Notice=0D
 * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of =0D
California. All rights reserved.=0D
 *=0D
 * DISCLAIMER=0D
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' =0D
AND ANY EXPRESS=0D
 * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED =0D
WARRANTIES OF=0D
 * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. =
=0D
IN NO EVENT=0D
 * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, =0D
INDIRECT, INCIDENTAL,=0D
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT =0D
LIMITED TO,=0D
 * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR =0D
PROFITS; OR=0D
 * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF =0D
LIABILITY, WHETHER IN=0D
 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR =0D
OTHERWISE) ARISING IN=0D
 * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE =0D
POSSIBILITY OF SUCH=0D
 * DAMAGE.=0D
 * ************************************=0D
 */=0D
package gov.lanl.COAS;=0D
=0D
import org.omg.CORBA.Any;=0D
import org.omg.DsObservationAccess.*;=0D
import org.omg.PersonIdService.QualifiedPersonId;=0D
=0D
import java.util.ArrayList;=0D
=0D
/**=0D
 * This interface specifies the methods for accessing the persistent =0D
storage=0D
 * of observations. It provides an interface that is indepedant from =0D
actual=0D
 * database schema for storing observations.=0D
 */=0D
public interface PersistentObservationAccess=0D
{=0D
    /**=0D
     * Initialize this observation access object.=0D
     */=0D
    public void init(=0D
        gov.lanl.Database.DatabaseMgr dbMgr,=0D
        gov.lanl.Database.PersistentObjectFactory persObjFact,=0D
        gov.lanl.Database.CodeMapper codeMapper,=0D
        gov.lanl.COAS.PolicyMgr policyMgr);=0D
=0D
    /**=0D
     * Retrieve one observation with its observation ID.=0D
     * @param observation_id   the observation ID=0D
     * @return the observation that matches the given observation ID.=0D
     * @exception InvalidOids  if the observation cannot be found.=0D
     */=0D
    public PersistentCOAS retrieveObservation(=0D
        ObservationId observation_id=0D
    ) throws=0D
        InvalidOids;=0D
=0D
    /**=0D
     * Count observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return the number of observations satisfying the specified =0D
policy=0D
     */=0D
    public int countObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy=0D
    ) throws=0D
        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,=0D
        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,=0D
        InvalidPolicies, DuplicatePolicies;=0D
=0D
    /**=0D
     * Retrieve observations based on the specified policy.=0D
     *=0D
     * @param who=0D
     * @param what=0D
     * @param when=0D
     * @param qualifiers=0D
     * @param policy=0D
     *=0D
     * @return a vector of objects implementing the {@link =0D
PersistentCOAS}=0D
     *         interface.=0D
     */=0D
    public ArrayList retrieveObservationsWithPolicy(=0D
        QualifiedPersonId[] who, String[] what,=0D
        TimeSpan when, Any[] qualifiers,=0D
        NameValuePair[] policy);=0D
=0D
}=0D
=0D
=0D
    =0D
=0D
=0D
=0D
=0D
-------------------------------------------------------=0D
This SF.Net email is sponsored by OSTG. Have you noticed the changes on=0D
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,=0D
one more big change to announce. We are now OSTG- Open Source Technology=
=0D
Group. Come see the changes on the new OSTG site. www.ostg.com=0D
_______________________________________________=0D
OpenMed-developer mailing list=0D
Ope...@li...=0D
https://lists.sourceforge.net/lists/listinfo/openmed-developer=0D
=0D
=0D
=0D
  =

Re: [OpenEMed-developer] Re: Your contributions

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

>It sounds like you want the interface to help combine
>some common code that might exist between QueryAccess and ObservationRemote.
>
Yes, most operations implemented in QueryAccessImpl delegate their job 
to getObservationsWithPolicy(). This method is basically the same 
between QueryAccessImpl and BrowseAccessImpl except for the output 
format, although BrowseAccessImpl can be more efficient by not 
collecting all sub-observations at once.

>    Is that
>correct?  One thing to think about, is the ability to use a POJO (Plain Old Java Object) call
>for the case (which seems to be coming up) of using COAS (and PIDS) with Web Services.
>
Sorry, I don't get it.

Joncheng

>
>Thanks,
>
>Dave
>
>  
>
>>------------Original Message------------
>>From: Joncheng Kuo <ck...@sy...>
>>To: "David Forslund" <dw...@la...>
>>Cc: ope...@li...
>>Date: Wed, Aug-4-2004 9:29 PM
>>Subject: [OpenEMed-developer] Re: Your contributions
>>
>>David Forslund wrote:
>>
>>    
>>
>>>it might be a good idea if you pass by me the structure that you are 
>>>      
>>>
>>going to submit, so I can make sure that it fits it with the overall 
>>design (that might not be that clear).
>>    
>>
>>I will. I've been thinking about the design and changes needed for a 
>>few 
>>days. Here are some thoughts that I'm considering.
>>
>>1. Create an interface called "PersistentObservationAccess" (see the 
>>attached file).
>>This interface is neutral to specific database schema. It is basically 
>>the replacement for the retrieveObservations() method in 
>>QueryAccessImpl. In this way, QueryAccessImpl will be independent from 
>>any particular database schema. We can configure the actual class 
>>implementing this interface depending on any specific database 
>>schema/structure.
>>
>>2. Create a "remote" package under gov.lanl.COAS and implement 
>>interfaces related to ObservationRemote such as ObservedSubject, 
>>ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl 
>>class will be still under gov.lanl.COAS, but it'll use classes 
>>implemented in this "remote" package.
>>
>>Besides, I found that the done() method is not adequately implemented. 
>>We have to deactivate objects like ObservationDataIterator from their 
>>POA or they never get removed. Both COAS and PIDS will need to use this 
>>
>>deactivate code.
>>
>>Joncheng
>>
>>    
>>
>>>Thanks,
>>>
>>>Dave
>>>
>>>
>>>
>>>
>>>
>>> 
>>>
>>>      
>>>
>>// PersistentObservationAccess.java
>>
>>/**
>> * ***********************************
>> * Copyright Notice
>> * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of 
>>California. All rights reserved.
>> *
>> * DISCLAIMER
>> * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' 
>>AND ANY EXPRESS
>> * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
>>WARRANTIES OF
>> * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 
>>IN NO EVENT
>> * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
>>INDIRECT, INCIDENTAL,
>> * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
>>LIMITED TO,
>> * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
>>PROFITS; OR
>> * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
>>LIABILITY, WHETHER IN
>> * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR 
>>OTHERWISE) ARISING IN
>> * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
>>POSSIBILITY OF SUCH
>> * DAMAGE.
>> * ************************************
>> */
>>package gov.lanl.COAS;
>>
>>import org.omg.CORBA.Any;
>>import org.omg.DsObservationAccess.*;
>>import org.omg.PersonIdService.QualifiedPersonId;
>>
>>import java.util.ArrayList;
>>
>>/**
>> * This interface specifies the methods for accessing the persistent 
>>storage
>> * of observations. It provides an interface that is indepedant from 
>>actual
>> * database schema for storing observations.
>> */
>>public interface PersistentObservationAccess
>>{
>>    /**
>>     * Initialize this observation access object.
>>     */
>>    public void init(
>>        gov.lanl.Database.DatabaseMgr dbMgr,
>>        gov.lanl.Database.PersistentObjectFactory persObjFact,
>>        gov.lanl.Database.CodeMapper codeMapper,
>>        gov.lanl.COAS.PolicyMgr policyMgr);
>>
>>    /**
>>     * Retrieve one observation with its observation ID.
>>     * @param observation_id   the observation ID
>>     * @return the observation that matches the given observation ID.
>>     * @exception InvalidOids  if the observation cannot be found.
>>     */
>>    public PersistentCOAS retrieveObservation(
>>        ObservationId observation_id
>>    ) throws
>>        InvalidOids;
>>
>>    /**
>>     * Count observations based on the specified policy.
>>     *
>>     * @param who
>>     * @param what
>>     * @param when
>>     * @param qualifiers
>>     * @param policy
>>     *
>>     * @return the number of observations satisfying the specified 
>>policy
>>     */
>>    public int countObservationsWithPolicy(
>>        QualifiedPersonId[] who, String[] what,
>>        TimeSpan when, Any[] qualifiers,
>>        NameValuePair[] policy
>>    ) throws
>>        InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,
>>        InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,
>>        InvalidPolicies, DuplicatePolicies;
>>
>>    /**
>>     * Retrieve observations based on the specified policy.
>>     *
>>     * @param who
>>     * @param what
>>     * @param when
>>     * @param qualifiers
>>     * @param policy
>>     *
>>     * @return a vector of objects implementing the {@link 
>>PersistentCOAS}
>>     *         interface.
>>     */
>>    public ArrayList retrieveObservationsWithPolicy(
>>        QualifiedPersonId[] who, String[] what,
>>        TimeSpan when, Any[] qualifiers,
>>        NameValuePair[] policy);
>>
>>}
>>
>>
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by OSTG. Have you noticed the changes on
>Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
>one more big change to announce. We are now OSTG- Open Source Technology
>Group. Come see the changes on the new OSTG site. www.ostg.com
>_______________________________________________
>OpenMed-developer mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>
>
>
>  
>

Re: [OpenEMed-developer] Re: Your contributions

[David F. <dw...@la...>]

These all sound pretty reasonable.  It sounds like you want the interface t=
o help combine
some common code that might exist between QueryAccess and ObservationRemote=
.    Is that
correct?  One thing to think about, is the ability to use a POJO (Plain Old=
 Java Object) call
for the case (which seems to be coming up) of using COAS (and PIDS) with We=
b Services.

Thanks,

Dave

> ------------Original Message------------
> From: Joncheng Kuo <ck...@sy...>
> To: "David Forslund" <dw...@la...>
> Cc: ope...@li...
> Date: Wed, Aug-4-2004 9:29 PM
> Subject: [OpenEMed-developer] Re: Your contributions
>
> David Forslund wrote:
> =

> >it might be a good idea if you pass by me the structure that you are =

> going to submit, so I can make sure that it fits it with the overall =

> design (that might not be that clear).
> >
> I will. I've been thinking about the design and changes needed for a =

> few =

> days. Here are some thoughts that I'm considering.
> =

> 1. Create an interface called "PersistentObservationAccess" (see the =

> attached file).
> This interface is neutral to specific database schema. It is basically =

> the replacement for the retrieveObservations() method in =

> QueryAccessImpl. In this way, QueryAccessImpl will be independent from =

> any particular database schema. We can configure the actual class =

> implementing this interface depending on any specific database =

> schema/structure.
> =

> 2. Create a "remote" package under gov.lanl.COAS and implement =

> interfaces related to ObservationRemote such as ObservedSubject, =

> ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl =

> class will be still under gov.lanl.COAS, but it'll use classes =

> implemented in this "remote" package.
> =

> Besides, I found that the done() method is not adequately implemented. =

> We have to deactivate objects like ObservationDataIterator from their =

> POA or they never get removed. Both COAS and PIDS will need to use this =

> =

> deactivate code.
> =

> Joncheng
> =

> >
> >Thanks,
> >
> >Dave
> >
> >
> >
> >
> >
> >  =

> >
> =

> // PersistentObservationAccess.java
> =

> /**
>  * ***********************************
>  * Copyright Notice
>  * Copyright (c) 1999, 2000, 2001, 2002 Regents of the University of =

> California. All rights reserved.
>  *
>  * DISCLAIMER
>  * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' =

> AND ANY EXPRESS
>  * OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED =

> WARRANTIES OF
>  * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. =

> IN NO EVENT
>  * SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, =

> INDIRECT, INCIDENTAL,
>  * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT =

> LIMITED TO,
>  * PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR =

> PROFITS; OR
>  * BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF =

> LIABILITY, WHETHER IN
>  * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR =

> OTHERWISE) ARISING IN
>  * ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE =

> POSSIBILITY OF SUCH
>  * DAMAGE.
>  * ************************************
>  */
> package gov.lanl.COAS;
> =

> import org.omg.CORBA.Any;
> import org.omg.DsObservationAccess.*;
> import org.omg.PersonIdService.QualifiedPersonId;
> =

> import java.util.ArrayList;
> =

> /**
>  * This interface specifies the methods for accessing the persistent =

> storage
>  * of observations. It provides an interface that is indepedant from =

> actual
>  * database schema for storing observations.
>  */
> public interface PersistentObservationAccess
> {
>     /**
>      * Initialize this observation access object.
>      */
>     public void init(
>         gov.lanl.Database.DatabaseMgr dbMgr,
>         gov.lanl.Database.PersistentObjectFactory persObjFact,
>         gov.lanl.Database.CodeMapper codeMapper,
>         gov.lanl.COAS.PolicyMgr policyMgr);
> =

>     /**
>      * Retrieve one observation with its observation ID.
>      * @param observation_id   the observation ID
>      * @return the observation that matches the given observation ID.
>      * @exception InvalidOids  if the observation cannot be found.
>      */
>     public PersistentCOAS retrieveObservation(
>         ObservationId observation_id
>     ) throws
>         InvalidOids;
> =

>     /**
>      * Count observations based on the specified policy.
>      *
>      * @param who
>      * @param what
>      * @param when
>      * @param qualifiers
>      * @param policy
>      *
>      * @return the number of observations satisfying the specified =

> policy
>      */
>     public int countObservationsWithPolicy(
>         QualifiedPersonId[] who, String[] what,
>         TimeSpan when, Any[] qualifiers,
>         NameValuePair[] policy
>     ) throws
>         InvalidIds, DuplicateIds, InvalidCodes, DuplicateCodes,
>         InvalidTimeSpan, InvalidQualifiers, DuplicateQualifiers,
>         InvalidPolicies, DuplicatePolicies;
> =

>     /**
>      * Retrieve observations based on the specified policy.
>      *
>      * @param who
>      * @param what
>      * @param when
>      * @param qualifiers
>      * @param policy
>      *
>      * @return a vector of objects implementing the {@link =

> PersistentCOAS}
>      *         interface.
>      */
>     public ArrayList retrieveObservationsWithPolicy(
>         QualifiedPersonId[] who, String[] what,
>         TimeSpan when, Any[] qualifiers,
>         NameValuePair[] policy);
> =

> }
> =

> =

[OpenEMed-developer] Re: Your contributions

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

>it might be a good idea if you pass by me the structure that you are going to submit, so I can make sure that it fits it with the overall design (that might not be that clear).
>
I will. I've been thinking about the design and changes needed for a few 
days. Here are some thoughts that I'm considering.

1. Create an interface called "PersistentObservationAccess" (see the 
attached file).
This interface is neutral to specific database schema. It is basically 
the replacement for the retrieveObservations() method in 
QueryAccessImpl. In this way, QueryAccessImpl will be independent from 
any particular database schema. We can configure the actual class 
implementing this interface depending on any specific database 
schema/structure.

2. Create a "remote" package under gov.lanl.COAS and implement 
interfaces related to ObservationRemote such as ObservedSubject, 
ObservationRemoteIterator, etc. in this package. The BrowseAccessImpl 
class will be still under gov.lanl.COAS, but it'll use classes 
implemented in this "remote" package.

Besides, I found that the done() method is not adequately implemented. 
We have to deactivate objects like ObservationDataIterator from their 
POA or they never get removed. Both COAS and PIDS will need to use this 
deactivate code.

Joncheng

>
>Thanks,
>
>Dave
>
>
>
>
>
>  
>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

Hmm.=C2=A0=C2=A0 This is what I see. It used to work.=C2=A0 I'll try to upg=
rade to the new OpenORB soon and see if this fixes the problem.=C2=A0 I'm a=
ctually using
some intermediate version from CVS.=C2=A0=C2=A0 I thought it was working wh=
en I tested it.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li..., "Polar Humenn" <po...@sy...>
Date: Tue, Aug-3-2004 10:02 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I'm having some problem at the moment getting using the Trader with PIDS, b=
ut I think this is an unrelated issue.
=E2=80=A8I have a problem too. Every time before I restart the PIDS server,=
 I have to restart the Trader as well. If not, my PIDS client will not acce=
ss the Trader. I suspect it's a Trader implementation problem because the T=
rader throws an UNKNOWN exception, meaning that the Trader servant throws a=
 non-CORBA exception that is caught by the ORB.=E2=80=A8=E2=80=A8I don't ha=
ve time for this problem now. I may try OpenORB 1.4.0 BETA2 later.=E2=80=
=A8=E2=80=A8Joncheng=E2=80=A8
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:05 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I should say that these are parameterized with variables specified in setho=
me.bat and sethome.sh
=E2=80=A8You're right. These settings should be defined in sethome.[bat,sh]=
.=E2=80=A8
=C2=A0
Dave
=C2=A0
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 6:08 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
The standard CORBA way to specify services through command line is to use t=
he following arguments:=E2=80=A8=E2=80=A8-ORBInitRef NameService=3Dcorbaloc=
::localhost:5002/NameService=E2=80=A8-ORBInitRef TradingService=3Dcorbaloc:=
:localhost:5003/TradingService=E2=80=A8=E2=80=A8Because these arguments are=
 very long, I usually divide them into several lines in *.sh files. E.g.,=
=E2=80=A8
${JAVACMD} ${JVM_ARGS} -classpath "..." \=E2=80=A8    gov.lanl.COAS.Observa=
tionComponentImpl \=E2=80=A8    -file "$app_home/config/coas.cfg" \=E2=80=
=A8    -ORBInitRef NameService=3Dcorbaloc::localhost:5002/NameService \=E2=
=80=A8    -ORBInitRef TradingService=3Dcorbaloc::localhost:5003/TradingServ=
ice \=E2=80=A8    $*
Joncheng=E2=80=A8=E2=80=A8=E2=80=A8David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I've updated the .bat and .sh files in the coas and pids directories to rem=
ove the ORBconfig parameters.=C2=A0=C2=A0 They all seem to work on windows =
and Linux.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> I'm having some problem at the moment getting using the Trader with 
> PIDS, but I think this is an unrelated issue.


I have a problem too. Every time before I restart the PIDS server, I 
have to restart the Trader as well. If not, my PIDS client will not 
access the Trader. I suspect it's a Trader implementation problem 
because the Trader throws an UNKNOWN exception, meaning that the Trader 
servant throws a non-CORBA exception that is caught by the ORB.

I don't have time for this problem now. I may try OpenORB 1.4.0 BETA2 later.

Joncheng

>  
> Dave
>  
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Tue, Aug-3-2004 9:05 PM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     David Forslund wrote:
>
>>     I should say that these are parameterized with variables
>>     specified in sethome.bat and sethome.sh
>
>
>     You're right. These settings should be defined in sethome.[bat,sh].
>
>>      
>>     Dave
>>      
>>      
>>
>>         ------------Original Message------------
>>         From: Joncheng Kuo <ck...@sy...>
>>         To: "David Forslund" <dw...@la...>
>>         Cc: ope...@li...
>>         Date: Tue, Aug-3-2004 6:08 PM
>>         Subject: Re: [OpenEMed-developer] Re: Specify search criteria
>>         with PIDS idviewer
>>         The standard CORBA way to specify services through command
>>         line is to use the following arguments:
>>
>>         -ORBInitRef NameService=corbaloc::localhost:5002/NameService
>>         -ORBInitRef
>>         TradingService=corbaloc::localhost:5003/TradingService
>>
>>         Because these arguments are very long, I usually divide them
>>         into several lines in *.sh files. E.g.,
>>
>>${JAVACMD} ${JVM_ARGS} -classpath "..." \
>>    gov.lanl.COAS.ObservationComponentImpl \
>>    -file "$app_home/config/coas.cfg" \
>>    -ORBInitRef NameService=corbaloc::localhost:5002/NameService \
>>    -ORBInitRef TradingService=corbaloc::localhost:5003/TradingService \
>>    $*
>>
>>         Joncheng
>>
>>
>>         David Forslund wrote:
>>
>>>         I've updated the .bat and .sh files in the coas and pids
>>>         directories to remove the ORBconfig parameters.   They all
>>>         seem to work on windows and Linux.
>>>          
>>>         Dave
>>>          
>>>
>>>             ------------Original Message------------
>>>             From: Joncheng Kuo <ck...@sy...>
>>>             To: "David Forslund" <dw...@la...>
>>>             Cc: ope...@li...
>>>             Date: Tue, Aug-3-2004 3:54 PM
>>>             Subject: Re: [OpenEMed-developer] Re: Specify search
>>>             criteria with PIDS idviewer
>>>             David Forslund wrote:
>>>
>>>>             The naming service and trader service work from the
>>>>             build.xml files without much problem.   The Orbacus
>>>>             specific .bat and .sh files
>>>>             should be deprecated (and potentially removed).
>>>
>>>             Still, the targets in dist/servers/build.xml uses
>>>             ORBacus specific -ORBconfig argument. I like to use
>>>             *.bat or *.sh for deployment because I don't have to use
>>>             Ant every time I run them. I personally prefer not to
>>>             remove *.bat and *.sh files.
>>>
>>>             Joncheng
>>>
>>>>
>>>>              
>>>>             Dave
>>>>
>>>>                 ------------Original Message------------
>>>>                 From: Joncheng Kuo <ck...@sy...>
>>>>                 To: "David Forslund" <dw...@la...>
>>>>                 Cc: ope...@li...
>>>>                 Date: Tue, Aug-3-2004 10:38 AM
>>>>                 Subject: Re: [OpenEMed-developer] Re: Specify
>>>>                 search criteria with PIDS idviewer
>>>>                 David Forslund wrote:
>>>>
>>>>>                 This would be wonderful!  I'll add you to the
>>>>>                 developer list.   I only ask that you try to test
>>>>>                 your additions with some of the sample
>>>>>                 apps to ensure that they work ok.
>>>>
>>>>
>>>>                 Do I just use the scripts in dist/servers and
>>>>                 dist/clients to test?
>>>>
>>>>>                   If you can test on both Linux and Windows, it
>>>>>                 would be helpful,
>>>>
>>>>
>>>>                 I observed that *.sh scripts are not as updated as
>>>>                 *.bat. Besides, *.sh scripts are a little tricky
>>>>                 when they are used under Windows with Cygwin. I use
>>>>                 *.sh most of the time.
>>>>
>>>>                 All scripts use ORBacus-specific "-ORBconfig
>>>>                 orb.properties" arguments to specify Naming and
>>>>                 Trading services. I think they should be replaced
>>>>                 with the standard -ORBInit. OpenORB works now
>>>>                 because it puts IOR files on local file system.
>>>>
>>>>                 Cheers,
>>>>                 Joncheng
>>>>
>>>>>                 as we run into to some case problems
>>>>>                 with windows that can mess things up in Linux.  
>>>>>                 Also, we need help with more unit tests.
>>>>>                  
>>>>>                 Dave
>>>>>                  
>>>>>
>>>>>                     ------------Original Message------------
>>>>>                     From: Joncheng Kuo <ck...@sy...>
>>>>>                     To: "David Forslund" <dw...@la...>
>>>>>                     Cc: ope...@li...
>>>>>                     Date: Tue, Aug-3-2004 9:18 AM
>>>>>                     Subject: Re: [OpenEMed-developer] Re: Specify
>>>>>                     search criteria with PIDS idviewer
>>>>>                     Hi, Dave,
>>>>>
>>>>>                     We're implementing the BrowseAccess interface
>>>>>                     and interfaces related to ObservationRemote.
>>>>>                     If this effort is useful to you, we would like
>>>>>                     to contribute what we have to the OpenEMed
>>>>>                     project. My userid at SourceForge is "joncheng".
>>>>>
>>>>>                     Besides, thank you for your help on IDViewer.
>>>>>                     I know how to use it now.
>>>>>
>>>>>                     Joncheng
>>>>>
>>>>>                     David Forslund wrote:
>>>>>
>>>>>>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>>>>>>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>>>>>>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>>>>>>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>>>>>>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>>>>>>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>>>>>>
>>>>>><?xml version="1.0"?>
>>>>>><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
>>>>>><PIDS>
>>>>>><Trait name="HL7/PatientName"  T="XPN" sep="^">
>>>>>>	<item DISPLAY="1" T="ST">Family Name</item>
>>>>>>	<item DISPLAY="1" T="ST">Given Name</item>
>>>>>>	<item DISPLAY="1" T="ST">Middle Name </item>
>>>>>>	<item DISPLAY="0" T="ST">Suffix </item>
>>>>>>	<item DISPLAY="1" T="ST">Prefix</item>
>>>>>>	<item DISPLAY="0" T="ST">Degree</item>
>>>>>><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>>>>>>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>>>>>>-->
>>>>>></Trait>
>>>>>>
>>>>>>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>>>>>>
>>>>>>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>>>>>>
>>>>>>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>>>>>>
>>>>>>I need to get some more documentation on IDViewer into the repository.
>>>>>>
>>>>>>
>>>>>>I hope this helps,
>>>>>>
>>>>>>Dave
>>>>>>
>>>>>>  
>>>>>>
>>>>>>>------------Original Message------------
>>>>>>>From: Joncheng Kuo <ck...@sy...>
>>>>>>>To: ope...@li...
>>>>>>>Cc: "David Forslund" <dw...@la...>
>>>>>>>Date: Wed, Jun-23-2004 10:45 AM
>>>>>>>Subject: Specify search criteria with PIDS idviewer
>>>>>>>
>>>>>>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>>>>>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>>>>>>help me with that? Thank you.
>>>>>>>
>>>>>>>Joncheng
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>    
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>-------------------------------------------------------
>>>>>>This SF.Net email sponsored by Black Hat Briefings & Training.
>>>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>>>>>>digital self defense, top technical experts, no vendor pitches, 
>>>>>>unmatched networking opportunities. Visit www.blackhat.com
>>>>>>_______________________________________________
>>>>>>OpenMed-developer mailing list
>>>>>>Ope...@li...
>>>>>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>>>>>
>>>>>>
>>>>>>
>>>>>>  
>>>>>>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

I've paramertized them as IIOP_HOSTNAME, IIOP_NAME, and IIOP_TRADER with eq=
uivalent definitions as the corresponding variables in local.properties.=
=C2=A0=C2=A0=C2=A0 I'm fixing the .bat and .sh files in the various directo=
ries accordingly.
=C2=A0
I'm having some problem at the moment getting using the Trader with PIDS, b=
ut I think this is an unrelated issue.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:05 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I should say that these are parameterized with variables specified in setho=
me.bat and sethome.sh
=E2=80=A8You're right. These settings should be defined in sethome.[bat,sh]=
.=E2=80=A8
=C2=A0
Dave
=C2=A0
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 6:08 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
The standard CORBA way to specify services through command line is to use t=
he following arguments:=E2=80=A8=E2=80=A8-ORBInitRef NameService=3Dcorbaloc=
::localhost:5002/NameService=E2=80=A8-ORBInitRef TradingService=3Dcorbaloc:=
:localhost:5003/TradingService=E2=80=A8=E2=80=A8Because these arguments are=
 very long, I usually divide them into several lines in *.sh files. E.g.,=
=E2=80=A8
${JAVACMD} ${JVM_ARGS} -classpath "..." \=E2=80=A8    gov.lanl.COAS.Observa=
tionComponentImpl \=E2=80=A8    -file "$app_home/config/coas.cfg" \=E2=80=
=A8    -ORBInitRef NameService=3Dcorbaloc::localhost:5002/NameService \=E2=
=80=A8    -ORBInitRef TradingService=3Dcorbaloc::localhost:5003/TradingServ=
ice \=E2=80=A8    $*
Joncheng=E2=80=A8=E2=80=A8=E2=80=A8David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I've updated the .bat and .sh files in the coas and pids directories to rem=
ove the ORBconfig parameters.=C2=A0=C2=A0 They all seem to work on windows =
and Linux.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> I should say that these are parameterized with variables specified in 
> sethome.bat and sethome.sh


You're right. These settings should be defined in sethome.[bat,sh].

>  
> Dave
>  
>  
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Tue, Aug-3-2004 6:08 PM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     The standard CORBA way to specify services through command line is
>     to use the following arguments:
>
>     -ORBInitRef NameService=corbaloc::localhost:5002/NameService
>     -ORBInitRef TradingService=corbaloc::localhost:5003/TradingService
>
>     Because these arguments are very long, I usually divide them into
>     several lines in *.sh files. E.g.,
>
>${JAVACMD} ${JVM_ARGS} -classpath "..." \
>    gov.lanl.COAS.ObservationComponentImpl \
>    -file "$app_home/config/coas.cfg" \
>    -ORBInitRef NameService=corbaloc::localhost:5002/NameService \
>    -ORBInitRef TradingService=corbaloc::localhost:5003/TradingService \
>    $*
>
>     Joncheng
>
>
>     David Forslund wrote:
>
>>     I've updated the .bat and .sh files in the coas and pids
>>     directories to remove the ORBconfig parameters.   They all seem
>>     to work on windows and Linux.
>>      
>>     Dave
>>      
>>
>>         ------------Original Message------------
>>         From: Joncheng Kuo <ck...@sy...>
>>         To: "David Forslund" <dw...@la...>
>>         Cc: ope...@li...
>>         Date: Tue, Aug-3-2004 3:54 PM
>>         Subject: Re: [OpenEMed-developer] Re: Specify search criteria
>>         with PIDS idviewer
>>         David Forslund wrote:
>>
>>>         The naming service and trader service work from the
>>>         build.xml files without much problem.   The Orbacus specific
>>>         .bat and .sh files
>>>         should be deprecated (and potentially removed).
>>
>>         Still, the targets in dist/servers/build.xml uses ORBacus
>>         specific -ORBconfig argument. I like to use *.bat or *.sh for
>>         deployment because I don't have to use Ant every time I run
>>         them. I personally prefer not to remove *.bat and *.sh files.
>>
>>         Joncheng
>>
>>>
>>>          
>>>         Dave
>>>
>>>             ------------Original Message------------
>>>             From: Joncheng Kuo <ck...@sy...>
>>>             To: "David Forslund" <dw...@la...>
>>>             Cc: ope...@li...
>>>             Date: Tue, Aug-3-2004 10:38 AM
>>>             Subject: Re: [OpenEMed-developer] Re: Specify search
>>>             criteria with PIDS idviewer
>>>             David Forslund wrote:
>>>
>>>>             This would be wonderful!  I'll add you to the developer
>>>>             list.   I only ask that you try to test your additions
>>>>             with some of the sample
>>>>             apps to ensure that they work ok.
>>>
>>>
>>>             Do I just use the scripts in dist/servers and
>>>             dist/clients to test?
>>>
>>>>               If you can test on both Linux and Windows, it would
>>>>             be helpful,
>>>
>>>
>>>             I observed that *.sh scripts are not as updated as
>>>             *.bat. Besides, *.sh scripts are a little tricky when
>>>             they are used under Windows with Cygwin. I use *.sh most
>>>             of the time.
>>>
>>>             All scripts use ORBacus-specific "-ORBconfig
>>>             orb.properties" arguments to specify Naming and Trading
>>>             services. I think they should be replaced with the
>>>             standard -ORBInit. OpenORB works now because it puts IOR
>>>             files on local file system.
>>>
>>>             Cheers,
>>>             Joncheng
>>>
>>>>             as we run into to some case problems
>>>>             with windows that can mess things up in Linux.   Also,
>>>>             we need help with more unit tests.
>>>>              
>>>>             Dave
>>>>              
>>>>
>>>>                 ------------Original Message------------
>>>>                 From: Joncheng Kuo <ck...@sy...>
>>>>                 To: "David Forslund" <dw...@la...>
>>>>                 Cc: ope...@li...
>>>>                 Date: Tue, Aug-3-2004 9:18 AM
>>>>                 Subject: Re: [OpenEMed-developer] Re: Specify
>>>>                 search criteria with PIDS idviewer
>>>>                 Hi, Dave,
>>>>
>>>>                 We're implementing the BrowseAccess interface and
>>>>                 interfaces related to ObservationRemote. If this
>>>>                 effort is useful to you, we would like to
>>>>                 contribute what we have to the OpenEMed project. My
>>>>                 userid at SourceForge is "joncheng".
>>>>
>>>>                 Besides, thank you for your help on IDViewer. I
>>>>                 know how to use it now.
>>>>
>>>>                 Joncheng
>>>>
>>>>                 David Forslund wrote:
>>>>
>>>>>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>>>>>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>>>>>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>>>>>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>>>>>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>>>>>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>>>>>
>>>>><?xml version="1.0"?>
>>>>><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
>>>>><PIDS>
>>>>><Trait name="HL7/PatientName"  T="XPN" sep="^">
>>>>>	<item DISPLAY="1" T="ST">Family Name</item>
>>>>>	<item DISPLAY="1" T="ST">Given Name</item>
>>>>>	<item DISPLAY="1" T="ST">Middle Name </item>
>>>>>	<item DISPLAY="0" T="ST">Suffix </item>
>>>>>	<item DISPLAY="1" T="ST">Prefix</item>
>>>>>	<item DISPLAY="0" T="ST">Degree</item>
>>>>><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>>>>>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>>>>>-->
>>>>></Trait>
>>>>>
>>>>>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>>>>>
>>>>>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>>>>>
>>>>>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>>>>>
>>>>>I need to get some more documentation on IDViewer into the repository.
>>>>>
>>>>>
>>>>>I hope this helps,
>>>>>
>>>>>Dave
>>>>>
>>>>>  
>>>>>
>>>>>>------------Original Message------------
>>>>>>From: Joncheng Kuo <ck...@sy...>
>>>>>>To: ope...@li...
>>>>>>Cc: "David Forslund" <dw...@la...>
>>>>>>Date: Wed, Jun-23-2004 10:45 AM
>>>>>>Subject: Specify search criteria with PIDS idviewer
>>>>>>
>>>>>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>>>>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>>>>>help me with that? Thank you.
>>>>>>
>>>>>>Joncheng
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>    
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>-------------------------------------------------------
>>>>>This SF.Net email sponsored by Black Hat Briefings & Training.
>>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>>>>>digital self defense, top technical experts, no vendor pitches, 
>>>>>unmatched networking opportunities. Visit www.blackhat.com
>>>>>_______________________________________________
>>>>>OpenMed-developer mailing list
>>>>>Ope...@li...
>>>>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>>>>
>>>>>
>>>>>
>>>>>  
>>>>>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

These are now added to the various scripts (.bat and .sh) in pids/coas/RAD/=
passthru=C2=A0 server examples.=C2=A0 I'll get the others shortly.
I think this should work better now with ApacheORB and not depend on OpenOR=
B's xml configuration.
=C2=A0
This has also been added to the build.xml file in dist/servers.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 6:08 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
The standard CORBA way to specify services through command line is to use t=
he following arguments:=E2=80=A8=E2=80=A8-ORBInitRef NameService=3Dcorbaloc=
::localhost:5002/NameService=E2=80=A8-ORBInitRef TradingService=3Dcorbaloc:=
:localhost:5003/TradingService=E2=80=A8=E2=80=A8Because these arguments are=
 very long, I usually divide them into several lines in *.sh files. E.g.,=
=E2=80=A8
${JAVACMD} ${JVM_ARGS} -classpath "..." \=E2=80=A8    gov.lanl.COAS.Observa=
tionComponentImpl \=E2=80=A8    -file "$app_home/config/coas.cfg" \=E2=80=
=A8    -ORBInitRef NameService=3Dcorbaloc::localhost:5002/NameService \=E2=
=80=A8    -ORBInitRef TradingService=3Dcorbaloc::localhost:5003/TradingServ=
ice \=E2=80=A8    $*
Joncheng=E2=80=A8=E2=80=A8=E2=80=A8David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I've updated the .bat and .sh files in the coas and pids directories to rem=
ove the ORBconfig parameters.=C2=A0=C2=A0 They all seem to work on windows =
and Linux.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

I should say that these are parameterized with variables specified in setho=
me.bat and sethome.sh
=C2=A0
Dave
=C2=A0
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 6:08 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
The standard CORBA way to specify services through command line is to use t=
he following arguments:=E2=80=A8=E2=80=A8-ORBInitRef NameService=3Dcorbaloc=
::localhost:5002/NameService=E2=80=A8-ORBInitRef TradingService=3Dcorbaloc:=
:localhost:5003/TradingService=E2=80=A8=E2=80=A8Because these arguments are=
 very long, I usually divide them into several lines in *.sh files. E.g.,=
=E2=80=A8
${JAVACMD} ${JVM_ARGS} -classpath "..." \=E2=80=A8    gov.lanl.COAS.Observa=
tionComponentImpl \=E2=80=A8    -file "$app_home/config/coas.cfg" \=E2=80=
=A8    -ORBInitRef NameService=3Dcorbaloc::localhost:5002/NameService \=E2=
=80=A8    -ORBInitRef TradingService=3Dcorbaloc::localhost:5003/TradingServ=
ice \=E2=80=A8    $*
Joncheng=E2=80=A8=E2=80=A8=E2=80=A8David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

I've updated the .bat and .sh files in the coas and pids directories to rem=
ove the ORBconfig parameters.=C2=A0=C2=A0 They all seem to work on windows =
and Linux.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

The standard CORBA way to specify services through command line is to 
use the following arguments:

-ORBInitRef NameService=corbaloc::localhost:5002/NameService
-ORBInitRef TradingService=corbaloc::localhost:5003/TradingService

Because these arguments are very long, I usually divide them into 
several lines in *.sh files. E.g.,

${JAVACMD} ${JVM_ARGS} -classpath "..." \
    gov.lanl.COAS.ObservationComponentImpl \
    -file "$app_home/config/coas.cfg" \
    -ORBInitRef NameService=corbaloc::localhost:5002/NameService \
    -ORBInitRef TradingService=corbaloc::localhost:5003/TradingService \
    $*

Joncheng


David Forslund wrote:

> I've updated the .bat and .sh files in the coas and pids directories 
> to remove the ORBconfig parameters.   They all seem to work on windows 
> and Linux.
>  
> Dave
>  
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Tue, Aug-3-2004 3:54 PM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     David Forslund wrote:
>
>>     The naming service and trader service work from the build.xml
>>     files without much problem.   The Orbacus specific .bat and .sh files
>>     should be deprecated (and potentially removed).
>
>     Still, the targets in dist/servers/build.xml uses ORBacus specific
>     -ORBconfig argument. I like to use *.bat or *.sh for deployment
>     because I don't have to use Ant every time I run them. I
>     personally prefer not to remove *.bat and *.sh files.
>
>     Joncheng
>
>>
>>      
>>     Dave
>>
>>         ------------Original Message------------
>>         From: Joncheng Kuo <ck...@sy...>
>>         To: "David Forslund" <dw...@la...>
>>         Cc: ope...@li...
>>         Date: Tue, Aug-3-2004 10:38 AM
>>         Subject: Re: [OpenEMed-developer] Re: Specify search criteria
>>         with PIDS idviewer
>>         David Forslund wrote:
>>
>>>         This would be wonderful!  I'll add you to the developer
>>>         list.   I only ask that you try to test your additions with
>>>         some of the sample
>>>         apps to ensure that they work ok.
>>
>>
>>         Do I just use the scripts in dist/servers and dist/clients to
>>         test?
>>
>>>           If you can test on both Linux and Windows, it would be
>>>         helpful,
>>
>>
>>         I observed that *.sh scripts are not as updated as *.bat.
>>         Besides, *.sh scripts are a little tricky when they are used
>>         under Windows with Cygwin. I use *.sh most of the time.
>>
>>         All scripts use ORBacus-specific "-ORBconfig orb.properties"
>>         arguments to specify Naming and Trading services. I think
>>         they should be replaced with the standard -ORBInit. OpenORB
>>         works now because it puts IOR files on local file system.
>>
>>         Cheers,
>>         Joncheng
>>
>>>         as we run into to some case problems
>>>         with windows that can mess things up in Linux.   Also, we
>>>         need help with more unit tests.
>>>          
>>>         Dave
>>>          
>>>
>>>             ------------Original Message------------
>>>             From: Joncheng Kuo <ck...@sy...>
>>>             To: "David Forslund" <dw...@la...>
>>>             Cc: ope...@li...
>>>             Date: Tue, Aug-3-2004 9:18 AM
>>>             Subject: Re: [OpenEMed-developer] Re: Specify search
>>>             criteria with PIDS idviewer
>>>             Hi, Dave,
>>>
>>>             We're implementing the BrowseAccess interface and
>>>             interfaces related to ObservationRemote. If this effort
>>>             is useful to you, we would like to contribute what we
>>>             have to the OpenEMed project. My userid at SourceForge
>>>             is "joncheng".
>>>
>>>             Besides, thank you for your help on IDViewer. I know how
>>>             to use it now.
>>>
>>>             Joncheng
>>>
>>>             David Forslund wrote:
>>>
>>>>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>>>>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>>>>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>>>>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>>>>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>>>>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>>>>
>>>><?xml version="1.0"?>
>>>><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
>>>><PIDS>
>>>><Trait name="HL7/PatientName"  T="XPN" sep="^">
>>>>	<item DISPLAY="1" T="ST">Family Name</item>
>>>>	<item DISPLAY="1" T="ST">Given Name</item>
>>>>	<item DISPLAY="1" T="ST">Middle Name </item>
>>>>	<item DISPLAY="0" T="ST">Suffix </item>
>>>>	<item DISPLAY="1" T="ST">Prefix</item>
>>>>	<item DISPLAY="0" T="ST">Degree</item>
>>>><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>>>>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>>>>-->
>>>></Trait>
>>>>
>>>>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>>>>
>>>>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>>>>
>>>>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>>>>
>>>>I need to get some more documentation on IDViewer into the repository.
>>>>
>>>>
>>>>I hope this helps,
>>>>
>>>>Dave
>>>>
>>>>  
>>>>
>>>>>------------Original Message------------
>>>>>From: Joncheng Kuo <ck...@sy...>
>>>>>To: ope...@li...
>>>>>Cc: "David Forslund" <dw...@la...>
>>>>>Date: Wed, Jun-23-2004 10:45 AM
>>>>>Subject: Specify search criteria with PIDS idviewer
>>>>>
>>>>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>>>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>>>>help me with that? Thank you.
>>>>>
>>>>>Joncheng
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>    
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email sponsored by Black Hat Briefings & Training.
>>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>>>>digital self defense, top technical experts, no vendor pitches, 
>>>>unmatched networking opportunities. Visit www.blackhat.com
>>>>_______________________________________________
>>>>OpenMed-developer mailing list
>>>>Ope...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>>>
>>>>
>>>>
>>>>  
>>>>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

I've updated the .bat and .sh files in the coas and pids directories to rem=
ove the ORBconfig parameters.=C2=A0=C2=A0 They all seem to work on windows =
and Linux.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

I'll see if I can't correct the bat files as you suggest.=C2=A0 I do have s=
ome OpenORB specific stuff in there that I'm sure you dont need for ApacheO=
RB, too.
=C2=A0
thanks,
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 3:54 PM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).
Still, the targets in dist/servers/build.xml uses ORBacus specific -ORBconf=
ig argument. I like to use *.bat or *.sh for deployment because I don't hav=
e to use Ant every time I run them. I personally prefer not to remove *.bat=
 and *.sh files.=E2=80=A8=E2=80=A8Joncheng
=E2=80=A8=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> The naming service and trader service work from the build.xml files 
> without much problem.   The Orbacus specific .bat and .sh files
> should be deprecated (and potentially removed).

Still, the targets in dist/servers/build.xml uses ORBacus specific 
-ORBconfig argument. I like to use *.bat or *.sh for deployment because 
I don't have to use Ant every time I run them. I personally prefer not 
to remove *.bat and *.sh files.

Joncheng

>
>  
> Dave
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Tue, Aug-3-2004 10:38 AM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     David Forslund wrote:
>
>>     This would be wonderful!  I'll add you to the developer list.   I
>>     only ask that you try to test your additions with some of the sample
>>     apps to ensure that they work ok.
>
>
>     Do I just use the scripts in dist/servers and dist/clients to test?
>
>>       If you can test on both Linux and Windows, it would be helpful,
>
>
>     I observed that *.sh scripts are not as updated as *.bat. Besides,
>     *.sh scripts are a little tricky when they are used under Windows
>     with Cygwin. I use *.sh most of the time.
>
>     All scripts use ORBacus-specific "-ORBconfig orb.properties"
>     arguments to specify Naming and Trading services. I think they
>     should be replaced with the standard -ORBInit. OpenORB works now
>     because it puts IOR files on local file system.
>
>     Cheers,
>     Joncheng
>
>>     as we run into to some case problems
>>     with windows that can mess things up in Linux.   Also, we need
>>     help with more unit tests.
>>      
>>     Dave
>>      
>>
>>         ------------Original Message------------
>>         From: Joncheng Kuo <ck...@sy...>
>>         To: "David Forslund" <dw...@la...>
>>         Cc: ope...@li...
>>         Date: Tue, Aug-3-2004 9:18 AM
>>         Subject: Re: [OpenEMed-developer] Re: Specify search criteria
>>         with PIDS idviewer
>>         Hi, Dave,
>>
>>         We're implementing the BrowseAccess interface and interfaces
>>         related to ObservationRemote. If this effort is useful to
>>         you, we would like to contribute what we have to the OpenEMed
>>         project. My userid at SourceForge is "joncheng".
>>
>>         Besides, thank you for your help on IDViewer. I know how to
>>         use it now.
>>
>>         Joncheng
>>
>>         David Forslund wrote:
>>
>>>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>>>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>>>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>>>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>>>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>>>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>>>
>>><?xml version="1.0"?>
>>><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
>>><PIDS>
>>><Trait name="HL7/PatientName"  T="XPN" sep="^">
>>>	<item DISPLAY="1" T="ST">Family Name</item>
>>>	<item DISPLAY="1" T="ST">Given Name</item>
>>>	<item DISPLAY="1" T="ST">Middle Name </item>
>>>	<item DISPLAY="0" T="ST">Suffix </item>
>>>	<item DISPLAY="1" T="ST">Prefix</item>
>>>	<item DISPLAY="0" T="ST">Degree</item>
>>><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>>>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>>>-->
>>></Trait>
>>>
>>>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>>>
>>>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>>>
>>>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>>>
>>>I need to get some more documentation on IDViewer into the repository.
>>>
>>>
>>>I hope this helps,
>>>
>>>Dave
>>>
>>>  
>>>
>>>>------------Original Message------------
>>>>From: Joncheng Kuo <ck...@sy...>
>>>>To: ope...@li...
>>>>Cc: "David Forslund" <dw...@la...>
>>>>Date: Wed, Jun-23-2004 10:45 AM
>>>>Subject: Specify search criteria with PIDS idviewer
>>>>
>>>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>>>help me with that? Thank you.
>>>>
>>>>Joncheng
>>>>
>>>>
>>>>
>>>>
>>>>    
>>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email sponsored by Black Hat Briefings & Training.
>>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>>>digital self defense, top technical experts, no vendor pitches, 
>>>unmatched networking opportunities. Visit www.blackhat.com
>>>_______________________________________________
>>>OpenMed-developer mailing list
>>>Ope...@li...
>>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>>
>>>
>>>
>>>  
>>>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

=C2=A0
There are some scripts there, but I've also added some of the tests to the =
build.xml file to reduce the platform specifics.=C2=A0 =

I've not been using the .sh files with cygwin, as they frequently don't wor=
k correct.=C2=A0 Check out the build.xml files.=C2=A0 This is
where I would like to have most of the changes handled.=C2=A0=C2=A0 We spec=
ify the ORB in local.properties in the root directory of OpenEMed.
The naming service and trader service work from the build.xml files without=
 much problem.=C2=A0=C2=A0 The Orbacus specific .bat and .sh files
should be deprecated (and potentially removed).=C2=A0=C2=A0 =

=C2=A0
Dave
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 10:38 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
David Forslund wrote:
body { margin: 5px; font-size:10pt; font-family:"Arial"; color: black; scro=
llbar-base-color: #d4d4d4; scrollbar-arrow-color: #020202; scrollbar-darksh=
adow-color: #4f4f4f; scrollbar-face-color: #c2c2c2; scrollbar-highlight-col=
or: #ececec; scrollbar-shadow-color: #878787; scrollbar-track-color: #d4d4d=
4;} ol { margin-top: 5px; margin-bottom: 5px;} ul { margin-top: 5px; margin=
-bottom: 5px;} blockquote { margin-top: 5px; margin-bottom: 5px;} =

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.
=E2=80=A8Do I just use the scripts in dist/servers and dist/clients to test=
?=E2=80=A8
=C2=A0 If you can test on both Linux and Windows, it would be helpful,
=E2=80=A8I observed that *.sh scripts are not as updated as *.bat. Besides,=
 *.sh scripts are a little tricky when they are used under Windows with Cyg=
win. I use *.sh most of the time.=E2=80=A8=E2=80=A8All scripts use ORBacus-=
specific "-ORBconfig orb.properties" arguments to specify Naming and Tradin=
g services. I think they should be replaced with the standard -ORBInit. Ope=
nORB works now because it puts IOR files on local file system.=E2=80=A8=E2=
=80=A8Cheers,=E2=80=A8Joncheng=E2=80=A8
as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

David Forslund wrote:

> This would be wonderful!  I'll add you to the developer list.   I only 
> ask that you try to test your additions with some of the sample
> apps to ensure that they work ok.


Do I just use the scripts in dist/servers and dist/clients to test?

>   If you can test on both Linux and Windows, it would be helpful,


I observed that *.sh scripts are not as updated as *.bat. Besides, *.sh 
scripts are a little tricky when they are used under Windows with 
Cygwin. I use *.sh most of the time.

All scripts use ORBacus-specific "-ORBconfig orb.properties" arguments 
to specify Naming and Trading services. I think they should be replaced 
with the standard -ORBInit. OpenORB works now because it puts IOR files 
on local file system.

Cheers,
Joncheng

> as we run into to some case problems
> with windows that can mess things up in Linux.   Also, we need help 
> with more unit tests.
>  
> Dave
>  
>
>     ------------Original Message------------
>     From: Joncheng Kuo <ck...@sy...>
>     To: "David Forslund" <dw...@la...>
>     Cc: ope...@li...
>     Date: Tue, Aug-3-2004 9:18 AM
>     Subject: Re: [OpenEMed-developer] Re: Specify search criteria with
>     PIDS idviewer
>     Hi, Dave,
>
>     We're implementing the BrowseAccess interface and interfaces
>     related to ObservationRemote. If this effort is useful to you, we
>     would like to contribute what we have to the OpenEMed project. My
>     userid at SourceForge is "joncheng".
>
>     Besides, thank you for your help on IDViewer. I know how to use it
>     now.
>
>     Joncheng
>
>     David Forslund wrote:
>
>>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>>
>><?xml version="1.0"?>
>><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
>><PIDS>
>><Trait name="HL7/PatientName"  T="XPN" sep="^">
>>	<item DISPLAY="1" T="ST">Family Name</item>
>>	<item DISPLAY="1" T="ST">Given Name</item>
>>	<item DISPLAY="1" T="ST">Middle Name </item>
>>	<item DISPLAY="0" T="ST">Suffix </item>
>>	<item DISPLAY="1" T="ST">Prefix</item>
>>	<item DISPLAY="0" T="ST">Degree</item>
>><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>>-->
>></Trait>
>>
>>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>>
>>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>>
>>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>>
>>I need to get some more documentation on IDViewer into the repository.
>>
>>
>>I hope this helps,
>>
>>Dave
>>
>>  
>>
>>>------------Original Message------------
>>>From: Joncheng Kuo <ck...@sy...>
>>>To: ope...@li...
>>>Cc: "David Forslund" <dw...@la...>
>>>Date: Wed, Jun-23-2004 10:45 AM
>>>Subject: Specify search criteria with PIDS idviewer
>>>
>>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>>help me with that? Thank you.
>>>
>>>Joncheng
>>>
>>>
>>>
>>>
>>>    
>>>
>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email sponsored by Black Hat Briefings & Training.
>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>>digital self defense, top technical experts, no vendor pitches, 
>>unmatched networking opportunities. Visit www.blackhat.com
>>_______________________________________________
>>OpenMed-developer mailing list
>>Ope...@li...
>>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>>
>>
>>
>>  
>>

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

This would be wonderful!=C2=A0 I'll add you to the developer list.=C2=A0=
=C2=A0 I only ask that you try to test your additions with some of the samp=
le
apps to ensure that they work ok.=C2=A0 If you can test on both Linux and W=
indows, it would be helpful, as we run into to some case problems
with windows that can mess things up in Linux.=C2=A0=C2=A0 Also, we need he=
lp with more unit tests.
=C2=A0
Dave
=C2=A0
------------Original Message------------
From: Joncheng Kuo <ck...@sy...>
To: "David Forslund" <dw...@la...>
Cc: ope...@li...
Date: Tue, Aug-3-2004 9:18 AM
Subject: Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idv=
iewer
Hi, Dave,=E2=80=A8=E2=80=A8We're implementing the BrowseAccess interface an=
d interfaces related to ObservationRemote. If this effort is useful to you,=
 we would like to contribute what we have to the OpenEMed project. My useri=
d at SourceForge is "joncheng".=E2=80=A8=E2=80=A8Besides, thank you for you=
r help on IDViewer. I know how to use it now.=E2=80=A8=E2=80=A8Joncheng=E2=
=80=A8=E2=80=A8David Forslund wrote:
When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and=E2=80=A8select as in the other PIDS client), you s=
hould see a list of supported Traits in the right top panel=E2=80=A8and a l=
ist of sources in the upper left panel.   You can have multiple PIDS server=
s with IDViewer.  =E2=80=A8Open one of the sources and you should see a lis=
t of traits that you can specify.  Thus if you see=E2=80=A8HL7/PatientName,=
 you should see the various components of this trait below it, such as Fami=
ly Name,=E2=80=A8Given Name, Middle Name, Suffix and Prefix.  Click on the =
folder below the Family Name, say and you can type in a value.   Enter the =
family name you are looking for (or any portion thereof) and click on find.=
  You then should see search results in the panel below in a tree structure=
.  The upper right panel is to select which traits you want to be filled in=
.  The idea for IDViewer is to enable one to see much more complex traits t=
hat PIDS supports by displaying them in an tree structure.   How it handles=
 some of these traits is constrained by some XML files in the client direct=
ory.  For example HL7Types.xml has the following:=E2=80=A8=E2=80=A8<?xml ve=
rsion=3D"1.0"?>=E2=80=A8<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>=E2=80=A8<PIDS=
>=E2=80=A8<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">=E2=80=A8   =
     <item DISPLAY=3D"1" T=3D"ST">Family Name</item>=E2=80=A8        <item =
DISPLAY=3D"1" T=3D"ST">Given Name</item>=E2=80=A8        <item DISPLAY=3D"1=
" T=3D"ST">Middle Name </item>=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST"=
>Suffix </item>=E2=80=A8        <item DISPLAY=3D"1" T=3D"ST">Prefix</item>=
=E2=80=A8        <item DISPLAY=3D"0" T=3D"ST">Degree</item>=E2=80=A8<!--   =
 <item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>=E2=80=A8        <item D=
ISPLAY=3D"0" T=3D"ST">Name Representation Code</item>=E2=80=A8-->=E2=80=A8<=
/Trait>=E2=80=A8=E2=80=A8The DISPLAY attribute says to display the trait, t=
he T attribute is the HL7 data type, the value of the item is the string to=
 display for the type.   The commented out field is the difference between =
HL72.3 and HL72.4, I believe.=E2=80=A8=E2=80=A8The display of the data is c=
onstrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. =
=E2=80=A8=E2=80=A8This client was worked on several years ago to demonstrat=
e how one could handle arbitrary traits rather than the constrained ones in=
 the simple PIDS demo client.   It could use a little more work to improve =
its flexibility and streamline the code considerably.    But it should get =
the point across of the flexibility and power of PIDS.=E2=80=A8=E2=80=A8I n=
eed to get some more documentation on IDViewer into the repository.=E2=80=
=A8=E2=80=A8=E2=80=A8I hope this helps,=E2=80=A8=E2=80=A8Dave=E2=80=A8=E2=
=80=A8  =

------------Original Message------------=E2=80=A8From: Joncheng Kuo <ckuo01=
@syr.edu>=E2=80=A8To: ope...@li...=E2=80=A8Cc: "=
David Forslund" <dw...@la...>=E2=80=A8Date: Wed, Jun-23-2004 10:45 AM=E2=
=80=A8Subject: Specify search criteria with PIDS idviewer=E2=80=A8=E2=80=
=A8I'm trying out the PIDS examples. The idviewer asked me to specify a =
=E2=80=A8search criteria, but I couldn't figure out how to do that. Can any=
one =E2=80=A8help me with that? Thank you.=E2=80=A8=E2=80=A8Joncheng=E2=80=
=A8=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8    =

-------------------------------------------------------=E2=80=A8This SF.Net=
 email sponsored by Black Hat Briefings & Training.=E2=80=A8Attend Black Ha=
t Briefings & Training, Las Vegas July 24-29 - =E2=80=A8digital self defens=
e, top technical experts, no vendor pitches, =E2=80=A8unmatched networking =
opportunities. Visit www.blackhat.com=E2=80=A8_____________________________=
__________________=E2=80=A8OpenMed-developer mailing list=E2=80=A8OpenMed-d=
eve...@li...=E2=80=A8https://lists.sourceforge.net/lists/=
listinfo/openmed-developer=E2=80=A8=E2=80=A8=E2=80=A8=E2=80=A8  =

Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[Joncheng K. <ck...@sy...>]

Hi, Dave,

We're implementing the BrowseAccess interface and interfaces related to 
ObservationRemote. If this effort is useful to you, we would like to 
contribute what we have to the OpenEMed project. My userid at 
SourceForge is "joncheng".

Besides, thank you for your help on IDViewer. I know how to use it now.

Joncheng

David Forslund wrote:

>When you successfully connect to a PIDS server with the IDViewer (click on select source button and
>select as in the other PIDS client), you should see a list of supported Traits in the right top panel
>and a list of sources in the upper left panel.   You can have multiple PIDS servers with IDViewer.  
>Open one of the sources and you should see a list of traits that you can specify.  Thus if you see
>HL7/PatientName, you should see the various components of this trait below it, such as Family Name,
>Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the Family Name, say and you can type in a value.   Enter the family name you are looking for (or any portion thereof) and click on find.  You then should see search results in the panel below in a tree structure.  The upper right panel is to select which traits you want to be filled in.  The idea for IDViewer is to enable one to see much more complex traits that PIDS supports by displaying them in an tree structure.   How it handles some of these traits is constrained by some XML files in the client directory.  For example HL7Types.xml has the following:
>
><?xml version="1.0"?>
><!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
><PIDS>
><Trait name="HL7/PatientName"  T="XPN" sep="^">
>	<item DISPLAY="1" T="ST">Family Name</item>
>	<item DISPLAY="1" T="ST">Given Name</item>
>	<item DISPLAY="1" T="ST">Middle Name </item>
>	<item DISPLAY="0" T="ST">Suffix </item>
>	<item DISPLAY="1" T="ST">Prefix</item>
>	<item DISPLAY="0" T="ST">Degree</item>
><!--	<item DISPLAY="0" T="ST">Name Type Code</item>
>	<item DISPLAY="0" T="ST">Name Representation Code</item>
>-->
></Trait>
>
>The DISPLAY attribute says to display the trait, the T attribute is the HL7 data type, the value of the item is the string to display for the type.   The commented out field is the difference between HL72.3 and HL72.4, I believe.
>
>The display of the data is constrolled by the idviewer.xsl stylesheet that is applied to the DOM tree. 
>
>This client was worked on several years ago to demonstrate how one could handle arbitrary traits rather than the constrained ones in the simple PIDS demo client.   It could use a little more work to improve its flexibility and streamline the code considerably.    But it should get the point across of the flexibility and power of PIDS.
>
>I need to get some more documentation on IDViewer into the repository.
>
>
>I hope this helps,
>
>Dave
>
>  
>
>>------------Original Message------------
>>From: Joncheng Kuo <ck...@sy...>
>>To: ope...@li...
>>Cc: "David Forslund" <dw...@la...>
>>Date: Wed, Jun-23-2004 10:45 AM
>>Subject: Specify search criteria with PIDS idviewer
>>
>>I'm trying out the PIDS examples. The idviewer asked me to specify a 
>>search criteria, but I couldn't figure out how to do that. Can anyone 
>>help me with that? Thank you.
>>
>>Joncheng
>>
>>
>>
>>
>>    
>>
>
>
>
>
>-------------------------------------------------------
>This SF.Net email sponsored by Black Hat Briefings & Training.
>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
>digital self defense, top technical experts, no vendor pitches, 
>unmatched networking opportunities. Visit www.blackhat.com
>_______________________________________________
>OpenMed-developer mailing list
>Ope...@li...
>https://lists.sourceforge.net/lists/listinfo/openmed-developer
>
>
>
>  
>

[OpenEMed-developer] Re: Specify search criteria with PIDS idviewer

[David F. <dw...@la...>]

When you successfully connect to a PIDS server with the IDViewer (click on =
select source button and
select as in the other PIDS client), you should see a list of supported Tra=
its in the right top panel
and a list of sources in the upper left panel.   You can have multiple PIDS=
 servers with IDViewer.  =

Open one of the sources and you should see a list of traits that you can sp=
ecify.  Thus if you see
HL7/PatientName, you should see the various components of this trait below =
it, such as Family Name,
Given Name, Middle Name, Suffix and Prefix.  Click on the folder below the =
Family Name, say and you can type in a value.   Enter the family name you a=
re looking for (or any portion thereof) and click on find.  You then should=
 see search results in the panel below in a tree structure.  The upper righ=
t panel is to select which traits you want to be filled in.  The idea for I=
DViewer is to enable one to see much more complex traits that PIDS supports=
 by displaying them in an tree structure.   How it handles some of these tr=
aits is constrained by some XML files in the client directory.  For example=
 HL7Types.xml has the following:

<?xml version=3D"1.0"?>
<!DOCTYPE PIDS SYSTEM 'XMLtypes.dtd'>
<PIDS>
<Trait name=3D"HL7/PatientName"  T=3D"XPN" sep=3D"^">
	<item DISPLAY=3D"1" T=3D"ST">Family Name</item>
	<item DISPLAY=3D"1" T=3D"ST">Given Name</item>
	<item DISPLAY=3D"1" T=3D"ST">Middle Name </item>
	<item DISPLAY=3D"0" T=3D"ST">Suffix </item>
	<item DISPLAY=3D"1" T=3D"ST">Prefix</item>
	<item DISPLAY=3D"0" T=3D"ST">Degree</item>
<!--	<item DISPLAY=3D"0" T=3D"ST">Name Type Code</item>
	<item DISPLAY=3D"0" T=3D"ST">Name Representation Code</item>
-->
</Trait>

The DISPLAY attribute says to display the trait, the T attribute is the HL7=
 data type, the value of the item is the string to display for the type.   =
The commented out field is the difference between HL72.3 and HL72.4, I beli=
eve.

The display of the data is constrolled by the idviewer.xsl stylesheet that =
is applied to the DOM tree. =


This client was worked on several years ago to demonstrate how one could ha=
ndle arbitrary traits rather than the constrained ones in the simple PIDS d=
emo client.   It could use a little more work to improve its flexibility an=
d streamline the code considerably.    But it should get the point across o=
f the flexibility and power of PIDS.

I need to get some more documentation on IDViewer into the repository.


I hope this helps,

Dave

> ------------Original Message------------
> From: Joncheng Kuo <ck...@sy...>
> To: ope...@li...
> Cc: "David Forslund" <dw...@la...>
> Date: Wed, Jun-23-2004 10:45 AM
> Subject: Specify search criteria with PIDS idviewer
> =

> I'm trying out the PIDS examples. The idviewer asked me to specify a =

> search criteria, but I couldn't figure out how to do that. Can anyone =

> help me with that? Thank you.
> =

> Joncheng
> =

> =

> =

> =