Menu
▾
▴
Re: [OpenEMed-developer] Re: Specify search criteria with PIDS idviewer
|
From: Joncheng K. <ck...@sy...> - 2004-08-03 21:53:19
|
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 >>> >>> >>> >>> >>> |
