http://mircwiki.rsna.org/api.php?action=feedcontributions&user=Rboden&feedformat=atomMircWiki - User contributions [en]2024-03-28T14:09:00ZUser contributionsMediaWiki 1.35.5http://mircwiki.rsna.org/index.php?title=User_talk:Poggio&diff=7051User talk:Poggio2013-01-07T15:19:40Z<p>Rboden: Welcome!</p>
<hr />
<div>'''Welcome to ''MircWiki''!'''<br />
We hope you will contribute much and well.<br />
You will probably want to read the [[Help:Contents|help pages]].<br />
Again, welcome and have fun! [[User:Rboden|rboden]] 09:19, 7 January 2013 (CST)</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=User:Poggio&diff=7050User:Poggio2013-01-07T15:19:21Z<p>Rboden: Creating user page with biography of new user.</p>
<hr />
<div>Medical Director of Cimed and President of Fundami. Director of Residency Program of Cimed-Fundami. non profit teaching</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MIRC_Overview_-_CTP_and_TFS&diff=3402MIRC Overview - CTP and TFS2008-07-02T14:51:00Z<p>Rboden: Reverted edits by Philljf12345900 (Talk); changed back to last version by Johnperry</p>
<hr />
<div>The MIRC project was initiated by the RSNA Radiology Informatics Committee to construct a library of medical information, globally accessible to the imaging community through the Internet. The project has evolved to support communities of cooperating libraries, individually managed by healthcare and educational institutions, whose content can be accessed by a user as if it were a single library. The libraries can provide all kinds of digital information, including teaching files, clinical and technical documents, electronic presentations, and imaging datasets for research and clinical trials. <br />
<br />
The RSNA manages an open-source project that has produced software making it easy to install a system for teaching files and clinical trials at no cost. Numerous other developers have produced complete or partial MIRC implementations.<br />
<br />
=== The MIRC Community ===<br />
Many MIRC communities have arisen - some within institutions and some shared globally. The RSNA maintains a MIRC site that provides access to libraries around the world.<br />
<br />
Any MIRC site can function as an access point for users, called a query service, or an indexed information library, called a storage service, or both. A query service provides a point of access to a MIRC community. It provides a query form to the user, distributes the search criteria to all selected storage services, collates the responses, and presents them to the user. A storage service responds to the query received from the query service, searches its index for documents meeting the search criteria, and returns abstracts and locations of the matching documents to the query service.<br />
<br />
Authors on a storage service can use a MIRC-defined format to construct teaching files and other documents in a common structure that allows libraries to index the documents in medically meaningful ways. The indexing mechanism provides users great flexibility in searching the MIRC community. Users can perform free-text searches on the contents of documents as well as structured searches on patient criteria (e.g., sex, age), image criteria (e.g., modality, anatomical region, storage format, compression), diagnosis and other codes, through a standard web browser.<br />
<br />
There are several ways for an individual or an institution to establish a system that can participate in a MIRC community:<br />
*The RSNA MIRC software provides both a query service and a storage service as well as support for the MIRC-defined authoring format.<br />
*An existing teaching file system can be modified to use its internal database to provide an index of its documents, requiring only the construction of the software layer necessary to respond to a MIRC query.<br />
*Some commercial teaching file systems also support the MIRC query mechanism, allowing them to participate in a MIRC community.<br />
<br />
=== MIRC Hardware Considerations ===<br />
For guidance on choosing hardware for a MIRC site running the RSNA MIRC implementation, see [[MIRC Hardware Considerations]].<br />
<br />
=== Installation Instructions ===<br />
For help on installing a new MIRC site see [[New Installation Instructions]]<br />
<br />
=== User's Manual ===<br />
The RSNA MIRC implementation has numerous components for accessing, creating, and managing documents and files.<br />
Information on how to use the RSNA MIRC software is collected in the [[MIRC User%27s Manual]].<br />
<br />
=== Administrator's Manual ===<br />
The RSNA MIRC implementation is designed to minimize management effort. The [[MIRC Administrator's Manual]] describes how to set up a MIRC site using the software and how to configure it to meet the needs of its users.<br />
<br />
=== Clinical Trial Administrator's Manual ===<br />
The RSNA MIRC implementation includes a powerful suite of tools to support both single-site and multi-site clinical trials. The [[Clinical Trial Administrator's Manual]] provides details on configuring the software for a trial. Some of the information may also be useful for MIRC site administrators who want to enable DICOM communication with PACS or modalities and who need to configure the system to manage PHI in accordance with HIPAA regulations.<br />
<br />
=== Developer's Manual ===<br />
The RSNA MIRC implementation is an open source project. Developers are welcome to download the software, modify it for their own purposes, and to participate in the extension of the software for the entire community. The [[Developers Manual|Developer's Manual]] will assist developers wishing to build, modify, or extent the code base.<br />
<br />
=== Getting Help ===<br />
There are a couple of ways to get help, if you have questions.<br />
<br />
* You can post your question to the [http://forums.rsna.org/forumdisplay.php?forumid=9 MIRC Forums].<br />
* You can also subscribe to the [[MIRC Mailing List]], and post your question there.<br />
<br />
=== Tools ===<br />
The RSNA MIRC project has developed several tools which are not part of the MIRC site software but which are useful as stand-alone applications in MIRC-related projects. The source code for all the tools is part of [[the RSNA MIRC Source Code]]. The key tools are:<br />
*DicomEditor: a tool for examining DICOM objects and for testing anonymization scripts for clinical trials. This tool is also useful for correcting certain problems in DICOM objects.<br />
*FileSender: a tool for transmitting files of various types using the DICOM, HTTP, and HTTPS protocols. This tool includes a zip unpacking feature that is very useful when managing large groups of images in multi-center clinical trials.<br />
*HttpTest: a tool for testing HTTP connections. This tool is useful for testing the connection of a remote image acquisition site to a principal investigator site in a clinical trial, especially when the remote site is behind a proxy server.<br />
*DicomRouter: a general tool for routing DICOM transmissions to one or more destinations depending on their contents. (This tool is a separate module in CVS.)<br />
*ExportManager: an implementation of the IHE TCE integration profile, providing a very powerful coupling between PACS diagnostic workstations and MIRC.<br />
*[[MIRC Powerpoint Tool|PowerpointTool]]: a Powerpoint plug-in that saves presentations as MIRCdocuments on a MIRC server.<br />
*[[TCE Selector]]: a tool for integration of PACS and MIRC for semiautomated teaching file generation. Using RadLex for indexing and categorization</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MediaWiki:Sidebar&diff=3307MediaWiki:Sidebar2008-02-27T14:55:56Z<p>Rboden: </p>
<hr />
<div>* navigation<br />
** mainpage|mainpage<br />
** downloads|Downloads<br />
** http://mirc.rsna.org|RSNA MIRC Site<br />
** http://forums.rsna.org/forumdisplay.php?forumid=9|MIRC Forums<br />
** MIRC Mailing List | Mailing List<br />
** Give Feedback | Give Feedback<br />
** Special:Allpages | Article Index<br />
<br />
* manuals<br />
** New Installation Instructions|Installation<br />
** MIRC User's Manual|User's Manual<br />
** MIRC Administrator's Manual|Admin's Manual<br />
** Clinical Trial Administrator's Manual|Clinical Trials Manual<br />
** Developers Manual| Developer's Manual</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Give_Feedback&diff=3117Give Feedback2007-12-03T21:06:22Z<p>Rboden: </p>
<hr />
<div>To give feedback on MIRC, please use the following link: [mailto:mirc-feedback@rsna.org]</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Give_Feedback&diff=3116Give Feedback2007-12-03T21:05:36Z<p>Rboden: </p>
<hr />
<div>To give feedback on MIRC, please send an email to the following: [mailto:mirc-feedback@rsna.org]</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Give_Feedback&diff=3115Give Feedback2007-12-03T21:05:01Z<p>Rboden: </p>
<hr />
<div>To give feedback on MIRC, please send an email to [mailto:mirc-feedback@rsna.org]</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Give_Feedback&diff=3114Give Feedback2007-12-03T21:04:45Z<p>Rboden: </p>
<hr />
<div>To give feedback on MIRC, please send an email to [mirc-feedback@rsna.org]</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Give_Feedback&diff=3113Give Feedback2007-12-03T21:04:28Z<p>Rboden: New page: To give feedback on MIRC, please send an email to mirc-feedback@rsna.org</p>
<hr />
<div>To give feedback on MIRC, please send an email to mirc-feedback@rsna.org</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MediaWiki:Sidebar&diff=3112MediaWiki:Sidebar2007-12-03T21:03:47Z<p>Rboden: </p>
<hr />
<div>* navigation<br />
** mainpage|mainpage<br />
** downloads|Downloads<br />
** http://mirc.rsna.org|RSNA MIRC Site<br />
** http://forums.rsna.org/forumdisplay.php?forumid=9|MIRC Forums<br />
** MIRC Mailing List | Mailing List<br />
** http://bugzilla.mirc.rsna.org:8088/ | Report a Bug<br />
** Give Feedback | Give Feedback<br />
** Special:Allpages | Article Index<br />
<br />
* manuals<br />
** New Installation Instructions|Installation<br />
** MIRC User's Manual|User's Manual<br />
** MIRC Administrator's Manual|Admin's Manual<br />
** Clinical Trial Administrator's Manual|Clinical Trials Manual<br />
** Developers Manual| Developer's Manual</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Downloads&diff=3087Downloads2007-11-08T14:42:25Z<p>Rboden: /* Major Release */</p>
<hr />
<div>==Installation Documents==<br />
<br />
* '''[[New Installation Instructions]]''' - Installing a new MIRC site? These instructions should help you through the installation process.<br />
<br />
== Installation Files ==<br />
<br />
* '''[http://mirc.rsna.org/T32/MIRCsite-installer-full.jar T32 Full Installer] - Use this installer for any new installations, or upgrades from any version prior to T32'''<br />
<br />
== Other Components ==<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:Downloads&diff=3086Talk:Downloads2007-11-08T14:40:14Z<p>Rboden: </p>
<hr />
<div>What happend to exist.war? Has it been removed from the wiki or is it just a bug? Or is it now included in the installer? -christopher<br />
<br />
It's in the installer -bobby</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Downloads&diff=3085Downloads2007-11-08T14:39:42Z<p>Rboden: </p>
<hr />
<div>==Installation Documents==<br />
<br />
* '''[[New Installation Instructions]]''' - Installing a new MIRC site? These instructions should help you through the installation process.<br />
<br />
== Major Release ==<br />
''This is the current MIRC release. It is recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/T32/MIRCsite-installer.jar T32 Installer]'''<br />
<br />
<br />
== Other Components ==<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MIRC_User%27s_Manual&diff=3080MIRC User's Manual2007-10-25T13:54:08Z<p>Rboden: </p>
<hr />
<div>The User's manual has been broken up into three parts, as follows:<br />
<br />
* [[Viewing Teaching Files]] talks about viewing, and searching for teaching files.<br />
* [[Your Account]] talks about your login and what you can do with it.<br />
* [[The Author Service]] is intended for the author's of teaching files.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MIRC_User%27s_Manual&diff=3079MIRC User's Manual2007-10-25T13:53:55Z<p>Rboden: </p>
<hr />
<div>The User's manual has been broken up into three parts, as follows:<br />
<br />
* [[Viewing Teaching Files]] talks about viewing, and searching for teaching files.<br />
* [[Your Account]] talks about your login and what you can do with it.<br />
* [[The Authoring Service]] is intended for the author's of teaching files.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:New_Installation_Instructions&diff=3014Talk:New Installation Instructions2007-10-23T15:50:01Z<p>Rboden: </p>
<hr />
<div>New steps for exist installation:<br />
<br />
Before installing MIRC:<br />
<br />
-I put exist.war into webapps<br />
<br />
-I started tomcat (forcing it to extract the exist.war)<br />
<br />
-I stopped tomcat again</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MircWiki:About&diff=2865MircWiki:About2007-06-14T14:02:22Z<p>Rboden: Reverted edits by AgoVhv (Talk); changed back to last version by Rboden</p>
<hr />
<div>The MIRC Wiki is intended to be used for documentation about the RSNA's MIRC Project.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:KeyMaker1.JPG&diff=2864File:KeyMaker1.JPG2007-06-14T14:02:09Z<p>Rboden: Reverted edits by IxrPz7 (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:DicomConfig1.JPG&diff=2863File:DicomConfig1.JPG2007-06-14T14:01:59Z<p>Rboden: Reverted edits by IwaTja (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:SSConfigurator1.JPG&diff=2862File:SSConfigurator1.JPG2007-06-14T14:01:49Z<p>Rboden: Reverted edits by TunNbk (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:ZipService2.jpg&diff=2861File:ZipService2.jpg2007-06-14T14:01:37Z<p>Rboden: Reverted edits by CbsR5k (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:DicomConfig6.JPG&diff=2860File:DicomConfig6.JPG2007-06-14T14:01:26Z<p>Rboden: Reverted edits by MxfCnj (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:Service4.JPG&diff=2859File:Service4.JPG2007-06-14T14:01:14Z<p>Rboden: Reverted edits by TrpF8q (Talk); changed back to last version by Rboden</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:SubmitServiceZipWindow1.JPG&diff=2858File:SubmitServiceZipWindow1.JPG2007-06-14T14:01:00Z<p>Rboden: Reverted edits by Cc1Uaf (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:TCEConfigurator1.JPG&diff=2857File:TCEConfigurator1.JPG2007-06-14T14:00:48Z<p>Rboden: Reverted edits by FqxRzh (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:The_Storage_Service_List_Schema&diff=2856Talk:The Storage Service List Schema2007-06-14T14:00:37Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=The_Storage_Service_Index_File&diff=2855The Storage Service Index File2007-06-14T14:00:20Z<p>Rboden: Reverted edits by Bc0C3d (Talk); changed back to last version by Rboden</p>
<hr />
<div>This article describes the index file used by storage services in the RSNA MIRC implementation. The expected audience for this document is MIRC site administrators or software developers who are modifying the open source version of the RSNA software.<br />
==The Storage Service Index File==<br />
When a storage service starts, it looks in its root directory (for example, <b>/webapps/mircstorage</b>) for a file called <b>siteindex.xml</b> containing the names of the documents it should index. From this file, it builds an XML object in memory containing the searchable parts of all the documents. The XML object in memory is searched whenever a query is received, providing rapid responses.<br />
The index file is an XML file with the following format:<br />
<pre><br />
<MIRCindex><br />
<doc>case1folderpath/case1.xml</doc><br />
<doc>case2folderpath/case2.xml</doc><br />
<doc>case3folderpath/case3.xml</doc><br />
...<br />
</MIRCindex><br />
</pre><br />
There is one <b>doc</b> element for each document to be indexed. Each <b>doc</b> element contains the path from the servlet root directory (<b>/webapps/[storage service name]</b>) to the XML file to be indexed.<br />
<br />
The submit service servlet inserts new <b>doc</b> elements without parsing the XML file, and the algorithm requires exactly the form shown above, with the <b>MIRCindex</b> tag, each <b>doc</b> element, and the <b>MIRCindex</b> end tag all to be on separate lines in the file.<br />
<br />
The MIRC software contains no siteindex.xml file as a precaution against overwriting an existing file during an upgrade installation. The storage service servlet automatically creates an empty index file if necessary, containing only:<br />
<pre><br />
<MIRCindex><br />
</MIRCindex><br />
</pre><br />
<br />
The storage service index file and its corresponding XML index object are maintained automatically by the software as documents are submitted through the author service or the submit service or created automatically by the DICOM service. In unusual circumstances, such as when a document is inserted into a system manually by an administrator, administrators can manually initiate reloading of the memory-resident index object or rebuilding of the index file using buttons on the storage service admin page.<br />
<br />
The XML index object contains <b>MIRCdocument</b> elements in the order in which they occur in the index file. An administrator who wishes to give a document preferential treatment by causing it to appear earlier in query results lists can move the <b>doc</b> element for that document higher in the index file by editing the file with a text editor like TextPad.<br />
==Remote Site Indexing==<br />
Rarely, it may be desirable to index the contents of a remote web site on a storage service. Such indexes are usually created programmatically. To simplify the process, storage services can accept XML files containing index cards for groups of documents. A remote site index is an XML file with the following structure:<br />
<pre><br />
<MIRCsiteindex><br />
<MIRCdocument docref=”...”>...</MIRCdocument><br />
<MIRCdocument docref=”...”>...</MIRCdocument><br />
...<br />
</MIRCsiteindex><br />
</pre><br />
where each <b>MIRCdocument</b> element is a MIRCdocument index card with a <b>docref</b> attribute containing a fully qualified URL pointing to a document on another site. An index card is a MIRCdocument with at least a <b>title</b>, <b>author</b>, and <b>abstract</b> element and containing no local references.<br />
<br />
The remote site index is represented in the storage service index with an <b>index</b> element containing the path from the servlet root directory to the file containing the remote site index. <b>doc</b> elements and <b>index</b> elements can be mixed in the same storage service index file, as in this example:<br />
<pre><br />
<MIRCindex><br />
<doc>case1folderpath/case1.xml</doc><br />
<doc>case2folderpath/case2.xml</doc><br />
...<br />
<index>index1path/index1.xml</index><br />
<index>index2path/index2.xml</index><br />
...<br />
</MIRCindex><br />
</pre><br />
There is no support in the admin service or the submit service for managing remote site indexes, so they must be entered by hand.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:XML_Primer&diff=2854Talk:XML Primer2007-06-14T14:00:08Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:The_MIRCqueryresult_Schema&diff=2853Talk:The MIRCqueryresult Schema2007-06-14T13:59:04Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=RadLex_API&diff=2852RadLex API2007-06-14T13:58:44Z<p>Rboden: Reverted edits by TfpO1l (Talk); changed back to last version by Johnpaulett</p>
<hr />
<div>'''Warning: This documentation is currently being updated to reflect version 2 of the servlet.'''<br />
<br />
The RadLex API acts as a webservice, which allows developers to query the RadLex terminology and retrieve an XML response. For more information about the RadLexID's, see [[RadLex Term Browser#RadLex URI's]]. The servlets treat HTTP GET's and POST's the same, so while the examples use GET requests, you are free to use HTTP POST request (POST's are merely redirected to GET's by the servlet).<br />
<br />
As a convention for this API, elements preceded by a dollar sign ($) are variable content.<br />
<br />
__TOC__<br />
== API Methods ==<br />
=== getTermByID ===<br />
'''URL:''' [http://radlex.org/getTermByID http://radlex.org/getTermByID]<br />
<br />
'''Parameters:''' <br />
* ''radlexID'' - the RadLex ID to obtain in the form "^RID([0-9] )$"<br />
<br />
'''Return:'''<br />
[[#<term>]] structure. <br />
<br />
'''Notes:'''<br />
Obtains all information pertaining to the ''radlexID'' in the terminology.<br />
<br />
<br />
=== getTree ===<br />
'''URL:''' [http://radlex.org/getTree http://radlex.org/getTree]<br />
<br />
'''Parameters:''' <br />
<br />
* ''relationType'' - the type of relation the tree should show.<br />
* (''baseID'') - optional. The RadLex ID to start the tree at. Default: RID0<br />
* (''radlexID'') - optional. The RadLex ID to enumerate the tree to.<br />
<br />
'''Return:'''<br />
[[#<links>]] structure. <br />
<br />
'''Notes:'''<br />
Returns a tree structure that represents the terms and their relationships. It returns all links starting with the baseID as the root term related via the relationType. If no radlexID is present only a single layer of children below the baseID term will be returned. If radlexID is present, all nodes that will create the structure from the baseID term to the radlexID term are given—this is "filled" out with the children of the nodes above the radlexID level. That is, if baseID = A and radlexID = a1, and A has children a, b, c, d, and a has children a1, a2, a3. The links of all of A’s children will be given, followed by all of a’s children. If no baseID is given, the root term for the terminology ("RID0") is used.<br />
<br />
<br />
=== getChildren ===<br />
'''URL:''' [http://radlex.org/getChildren http://radlex.org/getChildren]<br />
<br />
'''Parameters:'''<br />
* ''radlexID'' - the RadLex term for which you which to find its children<br />
* (''relationType'') - optional. The relation that the children must have with the radlexID term. Default: all relationships<br />
<br />
'''Return:'''<br />
[[#<children>]] structure. All the children of the radlexID, based upon the relationType (if defined)<br />
<br />
'''Notes:'''<br />
Serves as an extension of the getTree method, by allowing the program to see one level farther down the tree. Calls to the [[#getTermByID]] method, automatically include any child information.<br />
<br />
<br />
=== search ===<br />
'''URL:''' [http://radlex.org/search http://radlex.org/search]<br />
<br />
'''Parameters:''' <br />
* ''query'' - string to search for in the database<br />
<br />
'''Return:'''<br />
See notes below. <terms> structure.<br />
<br />
'''Notes:'''<br />
Performs a search on the database for the ''query''' term or phrase. <br />
*If the query matches "^RID([0-9] )$", a search for that radlexID is performed, which should yield 0 or 1 results. If 1 result is found, the search exits and returns that one value. <br />
*If the query has fewer than 4 characters, the database is queried via several LIKE statements. The 4 character minimum is a result of MySQL's Fulltext Search default limit. The query will return all, if any, matches and exit the search. <br />
*If the search has not already been exited, a MySQL Fulltext Search will be initiated on the database. This is the preferred method, as it uses MySQL's native natural language search ([http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html MySQL Documentation]). <br />
<br />
<br />
=== getRelationTypes ===<br />
'''URL:''' [http://radlex.org/getRelationTypes http://radlex.org/getRelationTypes]<br />
<br />
'''Parameters:'''<br />
none<br />
<br />
'''Return:'''<br />
[[#<relationTypes>]] structure. <br />
<br />
'''Notes:'''<br />
Returns all the types of relationships that are currently used or supported in the terminology.<br />
<br />
<br />
=== getTotalNumberOfTerms ===<br />
'''URL:''' [http://radlex.org/getTotalNumberOfTerms http://radlex.org/getTotalNumberOfTerms]<br />
<br />
'''Parameters:'''<br />
none<br />
<br />
'''Return:'''<br />
A number, not enclosed in any xml, of the number of RadLex terms in the database. <br />
<br />
'''Notes:'''<br />
Returns the number of terms that are in the terminology.<br />
<br />
<br />
== Return Structures ==<br />
=== Notes ===<br />
==== Boolean values ====<br />
Boolean values are represented as 0 (=false) or 1 (=true)<br />
<br />
=== <term> ===<br />
<pre><nowiki><br />
<term id="$radlexID"><br />
<name>$termName</name><br />
<uri>$URItoTerm</uri><br />
<definition>$termDefinition</definition><br />
<comment>$termComment</comment><br />
<source>$sourceOfTerm</source><br />
<dateCreated>$dateTermCreated</dateCreated><br />
<termStatus>$statusOfTerm</termStatus><br />
<versionNumber>$termVersionNumber</versionNumber><br />
<acr id="$acrTermID">$acrTermName</acr><br />
<snomed id="$snomedTermID">$snomedTermName</snomed><br />
<umls id="$umlsTermID">$umlsTermName</umls><br />
<parents><br />
<parent id="$parentsRadlexID" relationType="$relationWithParent" preferred="$0_or_1">$parentName</parent><br />
...<br />
</parents><br />
<children><br />
<child id="$childRadlexID" relationType="$relationWithChild" preferred="$0_or_1" childIsParent="$0_or_1">$childName</child><br />
...<br />
</children><br />
</term><br />
</nowiki></pre><br />
See [[#<children>]] for information on ''childIsParent''<br />
<br />
=== <terms> ===<br />
<pre><nowiki><br />
<terms><br />
<term id="$termsID" preferredid="$preferredID">$termName</term><br />
...<br />
</terms><br />
</nowiki></pre><br />
* ''preferredid'' represents the term that is considered the 'main' term by RadLex. Cases where the ''id'' and ''preferredid'' differ are usually when the term is a synonym. Since a synonym is not considered a 'main' term by RadLex, the <terms> structure points the user in the direction of the term that is the 'main' term.<br />
<br />
=== <children> ===<br />
<pre><nowiki><br />
<children parent="$parentRID"><br />
<child id="$radlexID" relationType="$relationType" preferred="$0_or_1" childIsParent="$0_or_1"><br />
$termName<br />
</child><br />
...<br />
</children><br />
</nowiki></pre><br />
* ''childIsParent'' - indicates if the term is itself a parent. If childIsParent=1, there are children of the $radlexID given this $relationType<br />
<br />
=== <links> ===<br />
<pre><nowiki><br />
<links><br />
<link parent="$parentID" id="$radlexID" relationType="$relationType" preferred="$0_or_1" childIsParent="$0_or_1">$termName</link><br />
</links><br />
</nowiki></pre><br />
See [[#<children>]] for information on ''childIsParent''<br />
<br />
=== <relationTypes> ===<br />
<pre><nowiki><br />
<relationTypes><br />
<relationType>$nameOfType</relationType><br />
...<br />
</relationTypes><br />
</nowiki></pre><br />
<br />
=== <error> ===<br />
For a more detailed discussion of [[#Errors | error messages]], see below.<br />
<pre><nowiki><br />
<program><br />
<error id="$errorid">$errormessage</error><br />
</program><br />
</nowiki></pre><br />
<br />
<br />
== Errors ==<br />
When there has been an error processing an API request, the server will respond with a generic error message, explaining the problem. For the [[#<error>]] return format<br />
<br />
{| <br />
! error id !! meaning<br />
|-<br />
| 1<br />
| RadLex ID is not valid<br />
|- <br />
| 2<br />
| Radlex ID could not be found<br />
|- <br />
| 3<br />
| Relationship type is not valid<br />
|- <br />
| 4<br />
| Database connection error<br />
|- <br />
| 5<br />
| Insufficient http get parameters.<br />
|- <br />
| 6<br />
| No search results matching query<br />
|}<br />
<br />
<br />
== Current Relation Types ==<br />
* preferred - indicates that the parent-child relationship is preferred. The preferred status usually highlights that one of the other relations is preferred. There are cases where another relation has not yet been defined (but eventually should be).<br />
* isa<br />
* partof<br />
* branchof<br />
* segmentof<br />
* tributaryof<br />
* continuouswith<br />
* containedin<br />
* memberof<br />
* synonymof<br />
<br />
<br />
== Examples ==<br />
=== getTermByID Example ===<br />
I want to get all the details about [http://radlex.org/RID1243 Thorax]. So, I construct a GET request using RID1243, for [http://radlex.org/RID1243 Thorax]:<br />
<br />
<pre><nowiki><br />
http://radlex.org/getTermByID?radlexID=RID1243<br />
</nowiki></pre><br />
<br />
And the server responds with:<br />
<pre><nowiki><br />
<term id="RID1243"><br />
<name>thorax</name><br />
<uri>http://radlex.org/RID1243</uri><br />
<definition></definition><br />
<comment>child of anatomic location</comment><br />
<source/><br />
<dateCreated/><br />
<termStatus/><br />
<versionNumber/><br />
<acr id=""/><br />
<snomed id=""/><br />
<umls id=""/><br />
<parents><br />
<parent id="RID3" relationType="" preferred="1">anatomic location</parent><br />
</parents><br />
<children><br />
<child id="RID1245" relationType="continuouswith" preferred="1" childIsParent="1">airway</child><br />
<child id="RID1524" relationType="continuouswith" preferred="1" childIsParent="1">diaphragm</child><br />
<child id="RID1530" relationType="continuouswith" preferred="1" childIsParent="1">diaphragmatic sulcus</child><br />
<child id="RID1301" relationType="continuouswith" preferred="1" childIsParent="1">lung</child><br />
<child id="RID1384" relationType="continuouswith" preferred="1" childIsParent="1">mediastinum</child><br />
<child id="RID1362" relationType="continuouswith" preferred="1" childIsParent="1">pleura</child><br />
<child id="RID1463" relationType="continuouswith" preferred="1" childIsParent="1">thoracic lymph node</child><br />
<child id="RID1244" relationType="synonymof" preferred="0" childIsParent="0">chest</child><br />
</children><br />
</term><br />
</nowiki></pre><br />
<br />
<br />
=== getTree Example ===<br />
I want to find all the terms between the root of the terminology (RID0) and [http://radlex.org/RID3 anatomic location], so I construct a GET request using getTree:<br />
<pre><nowiki><br />
http://radlex.org/getTree?relationType=preferred<br />
</nowiki></pre></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:Controlled_Terminology_Extension&diff=2851Talk:Controlled Terminology Extension2007-06-14T13:57:52Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MIRC_TCE_Export_Manager&diff=2850MIRC TCE Export Manager2007-06-14T13:57:32Z<p>Rboden: Reverted edits by WzeRz2 (Talk); changed back to last version by Rboden</p>
<hr />
<div>ExportManager is an implementation of the [http://www.ihe.net IHE] Teaching Files and Clinical Trials (TCE) integration profile Export Manager actor. This article provides links to the ExportManager and ManifestGenerator programs. <br />
<br />
==ExportManager==<br />
<br />
The [http://mirc.rsna.org/ExportManager/ExportManager-installer.jar ExportManager installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. On a Windows platform, you can simply double-click the program. On other platforms, you can use the command: <b>java -jar ExportManager-installer.jar</b>. <br />
<br />
The installer will create a directory called <b>ExportManager</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ExportManager, run the <b>ExportManager.jar</b> file, using a command similar to the one you used to run the installer. <br />
<br />
When ExportManager first runs, its export function is disabled. The <b>Help</b> tab provides information for configuring the destination URL, all the other program parameters, and the anonymization scripts. <br />
<br />
In normal operation, the program runs unattended; however, for IHE Connectaton testing, it may be useful to monitor the Event Log and Queue Status, both of which can be viewed either by clicking the corresponding tab or by accessing the built-in HTTP server with a browser.<br />
<br />
If objects are received which cannot be anonymized or transmitted, they are moved to quarantine directories with corresponding names. For convenience, there is a DICOM file dump utility included in the Quarantine tab that displays the contents of any DICOM file. <br />
<br />
==ManifestGenerator==<br />
ManifestGenerator is a minimal test utility for constructing IHE TCE manifests referencing DICOM instances. ManifestGenerator does <b>not</b> create complete TCE manifests, however. It constructs manifests which contain only the necessary elements for an Export Manager that does not have to query for the instances. All the elements which are included are correct as defined by the TCE integration profile, but elements unnecessary for the purpose of testing the Export Manager are omitted. These manifests, therefore, will fail when tested by almost any validation program. <br />
<br />
The [http://mirc.rsna.org/ExportManager/ManifestGenerator-installer.jar ManifestGenerator installer] can be downloaded from the RSNA MIRC site. The program requires Java 1.5. <br />
<br />
To install the program, download the installer, save it on your disk and run it. The installer will create a directory called <b>ManifestGenerator</b> wherever you choose and then put all the required files in it. <br />
<br />
To run ManifestGenerator, run the <b>ManifestGenerator.jar</b> file. <br />
<br />
The program provides two tabs, one for selecting instances for inclusion in the manifest, and one for entering textual information. <br />
<br />
In the <b>Instance Selector</b> tab, click the <b>Open Directory</b> button to get a file chooser. Navigate to the directory containing the desired instances. Check or uncheck files to select or deselect instances for the manifest. All the instances must be in the same directory. As instances are selected, the right pane displays their DICOM elements. <br />
<br />
In the <b>Manifest Constructor</b> tab, enter whatever information you wish in the fields provided. The text pane at the bottom allows you to enter text data for the manifest. No testing of the entered information is done. Make certain that you insert a UID. No automatic UID generation is provided. <br />
<br />
When the <b>Save</b> button is clicked at the bottom of the <b>Manifest Constructor</b> tab, the program constructs a manifest and saves it in the same directory with the instances. Any selected instance files that do not parse are not included in the manifest. The manifest file is named <b>[UID].kos</b>. After the manifest is saved, the program then constructs a zip file containing the manifest and all the referenced instances. The zip file is named <b>[UID].kos.zip</b> and is stored in the same directory with the instances and the manifest. This zip file is a convenient way to package test sets, especially when combined with the use of the FileSender program.<br />
<br />
==FileSender==<br />
FileSender is a MIRC utility program that can transmit files using the DICOM, HTTP, and HTTPS protocols. For more information and access to the program, see [[FileSender]]. <br />
<br />
In the context of the ExportManager and ManifestGenerator programs, FileSender can transmit manifests and instances for testing. <br />
<br />
The program includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together all the zip files for individual manifests and their instances. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:The_Remapper_Encryption_Key&diff=2849Talk:The Remapper Encryption Key2007-06-14T13:57:20Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=FileSender&diff=2848FileSender2007-06-14T13:56:57Z<p>Rboden: Reverted edits by JlaD53 (Talk); changed back to last version by Rboden</p>
<hr />
<div>FileSender is a utility program for sending files via HTTP or DICOM. It is written in Java and requires Java 1.5 or better to be on the target computer. Its intended use is as a test program for MIRC development, but it can be used more generally to upload DICOM images to MIRC DICOM services or MIRCdocument zip files to MIRC storage services. It also uploads files to MIRC file services. <br />
<br />
==Instructions==<br />
To use the program, download the [http://mirc.rsna.org/FileSender/FileSender-installer.jar installer] and run it. It will create a folder called <b>FileSender</b> and put the required files inside it. To launch the program, double-click the <b>FileSender.jar</b> file. You can create a shortcut to that file and put it anyplace convenient. <br />
<br />
The left pane in FileSender is used to navigate to a file or a folder of interest. The pull-down menu in the header of the left pane lets you choose the root (drive) file system. The button in the footer bar lets you specify the extensions to accept. <br />
<br />
The right pane is used to specify the destination URL. There are four example URLs in the header bar: <br />
<br />
* a typical transfer to the HttpImportService of a clinical trial service using HTTP <br />
* a typical transfer to the HttpImportService of a clinical trial service using secure sockets layer (HTTPS) <br />
* a typical transfer to a DicomImportService of a clinical trial service <br />
* a typical transfer to a MIRC Submit Service using HTTP <br />
<br />
FileSender supports secure sockets layer as well as standard HTTP. To use secure sockets layer, enter <b>https:</b> for the protocol in the URL rather than <b>http:</b>. You must also specify the proper port. If you are sending to a MIRC site, SSL is typically enabled on port <b>8443</b>. If you run into certificate problems with a MIRC site, see [[Configuring Tomcat to Support SSL]]. <br />
<br />
Once a file or folder is selected in the left pane and you have entered or selected a URL in the right pane and clicked its radio button to select it, clicking the <b>Send</b> button in the footer bar of the right pane starts the transmission. <br />
* If you selected an individual file in the left pane, that is all that is sent. <br />
* If you selected a folder and the <b>Include subdirectories</b> checkbox in the footer bar is not checked, then it just sends the files in the folder. <br />
* If you selected a folder and also checked the checkbox, then it sends the files in the folder and the files in all the subfolders, walking the entire tree below the selected folder. When sending the contents of a folder, only files matching the specified extensions are sent. <br />
<br />
FileSender includes a special mode for automatically unpacking and transmitting the contents of zip files like those constructed by the ManifestGenerator program. This mode is enabled by checking the <b>Unpack zip files</b> checkbox at the bottom of the right pane. When unpacking a zip file, this mode will unpack any contained zip files as well, allowing large datasets to be constructed by zipping together multiple zip files. FileSender will then, with a single command, unpack the entire tree of zip files down to their individual non-zip constituents and send everything. All extracted files are written to the default temp directory and deleted after transmission. <br />
<br />
FileSender supports Content-Type setting based on the extension of the file being transmitted. This feature allows transmission of MIRCdocuments in the standard MIRC zip-file export format, defining the Content-Type as <b>application/x-zip-compressed</b> as required by MIRC Submit Services. <br />
* To allow FileSender to set the Content-Type from the extension, uncheck the <b>Force DICOM Content-Type</b> box in the footer of the right pane. <br />
* When using FileSender to transmit DICOM images via HTTP or HTTPS, however, be sure to check the <b>Force DICOM Content-Type</b> box. <br />
<br />
The program creates a preferences file and initializes itself to the last settings of the previous run. Each time you run it, it lists all the previous destination URLs and gives you another blank space to add a new one. You can edit, reuse, or erase any of the URLs. <br />
<br />
If you find any problems with the program, please post them on the RSNA Forum Site in the MIRC Forum's User Comments thread.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:MIRC_Overview_-_CTP_and_TFS&diff=2847Talk:MIRC Overview - CTP and TFS2007-06-14T13:56:43Z<p>Rboden: Reverted edits by JjcL4z (Talk); changed back to last version by Rboden</p>
<hr />
<div>This is future content for the main page, relevant to the up and coming "My Mirc" (name not finalized)<br />
<br />
== My Mirc ==<br />
My Mirc is an RSNA hosted MIRC site that allows you to author and store your teaching files on the RSNA servers. You will also be able to create groups, and share teaching files you have uploaded with those groups. My Mirc also allows you to search for teaching files on other Mirc sites that have been made publicly available (Want to make your MIRC Site publicly available? [[http://www2.rsna.org/mirc/request.cfm Click here]]).</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:New_Installation_Instructions&diff=2846Talk:New Installation Instructions2007-06-14T13:56:30Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Talk:The_MIRC_Protocol_for_Document_Exchange&diff=2845Talk:The MIRC Protocol for Document Exchange2007-06-14T13:56:11Z<p>Rboden: Removing all content from page</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:DicomAnonymizer2.JPG&diff=2844File:DicomAnonymizer2.JPG2007-06-14T13:55:44Z<p>Rboden: Reverted edits by En0Qla (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:FileServiceAdmin1.JPG&diff=2843File:FileServiceAdmin1.JPG2007-06-14T13:55:32Z<p>Rboden: Reverted edits by RddLn4 (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:ClinicalTrial1.JPG&diff=2842File:ClinicalTrial1.JPG2007-06-14T13:55:12Z<p>Rboden: Reverted edits by Fx1L49 (Talk); changed back to last version by Johnperry</p>
<hr />
<div></div>Rbodenhttp://mircwiki.rsna.org/index.php?title=File:RsnaMircBlockDiagram-1.GIF&diff=2841File:RsnaMircBlockDiagram-1.GIF2007-06-14T13:55:08Z<p>Rboden: Reverted edits by JytN5v (Talk); changed back to last version by Johnperry</p>
<hr />
<div>Block diagram of the RSNA MIRC implemmentation.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=The_MIRCquery_Schema&diff=2840The MIRCquery Schema2007-06-14T13:55:04Z<p>Rboden: Reverted edits by AavPqf (Talk); changed back to last version by Johnperry</p>
<hr />
<div>This article describes technical requirements for participation in the MIRC community as a storage service. <br />
Additional information is provided in [[The MIRCqueryresult Schema]] and [[The MIRCdocument Schema]].<br />
<br />
The intended audience for this article is the developer or system administrator of a teaching file system who is implementing a MIRC storage service to make the system’s teaching files available to the MIRC community.<br />
<br />
==Overview==<br />
MIRC may be defined as a collection of web sites that share a common query mechanism. <br />
<br />
The two key components involved in the query process are:<br />
*Query Service: a web site that is accessed by a MIRC user with a web browser. The query service provides web pages that allow a user to define search criteria and select sites in the MIRC community to be searched. It queries the selected sites, organizes the query results into a web page or pages, and sends the pages to the browser.<br />
*Storage Service: a web site that stores information of interest to MIRC users. In response to a query received from a query service, it identifies all the information it stores which meets the search criteria, constructs a query response containing an abstract of the information to allow a user to determine whether the information is of interest, and sends the response to the query service. It also serves the information directly to a MIRC user in response to a request from the user.<br />
<br />
The query service and storage service are independent. A MIRC site may include a query service or a storage service, or both.<br />
==MIRC Query==<br />
A MIRC query is an XML object in the form defined by the MIRCquery schema. It is passed from a query site to a storage service via an HTTP POST of content type <b>text/xml</b>. <br />
<br />
The following is an example of a MIRCquery:<br />
<pre><br />
<MIRCquery firstresult=”…” maxresults=”…” queryUID=”…” unknown=”…”><br />
<title> . . . </title><br />
<author> . . . </author><br />
<abstract> . . . </abstract><br />
<keywords> . . . </keywords><br />
<history> . . . </history><br />
<findings> . . . </findings><br />
<diagnosis> . . . </diagnosis><br />
<differential-diagnosis> . . . </differential-diagnosis><br />
<discussion> . . . </discussion><br />
<pathology> . . . </pathology><br />
<anatomy> . . . </anatomy><br />
<organ-system> . . . </organ-system><br />
<code coding-system=”…”> . . . </code><br />
<modality> . . . </modality><br />
<patient><br />
<pt-age><br />
<years> . . . </years><br />
<months> . . . </months><br />
<weeks> . . . </weeks><br />
<days> . . . </days><br />
</pt-age><br />
<pt-sex> . . . </pt-sex><br />
<pt-race> . . . </pt-race><br />
<pt-species> . . . </pt-species> <!—-veterinary--><br />
<pt-breed> . . . </pt-breed> <!--veterinary--><br />
</patient><br />
<image><br />
<format> . . . </format><br />
<compression> . . . </compression><br />
<modality> . . . </modality><br />
<anatomy> . . . </anatomy><br />
<pathology> . . . </pathology><br />
</image><br />
<document-type> . . . </document-type><br />
<category> . . . </category><br />
<level> . . . </level><br />
<access> . . . </access><br />
<peer-review/><br />
<language code=”…”> . . . </language><br />
… free text search field …<br />
</MIRCquery><br />
</pre><br />
<br />
===MIRCquery Attributes===<br />
The <b>firstresult</b> and <b>maxresults</b> attributes of the <b>MIRCquery</b> element are used to allow the query service to break the responses into groups. The <b>firstresult</b> attribute specifies the first result to be returned by the storage service. The value 0 corresponds to the first result in the list. If the attribute is missing, the default value 0 is to be used.<br />
<br />
The <b>maxresults</b> attribute specifies the maximum number of results to be returned by the storage service. For example, if the query service is grouping results into sets of 10 and is asking for the third group, <b>firstresult</b> would be set to 20 and <b>maxresults</b> would be set to 10. If the <b>maxresults</b> attribute is missing or 0, the storage service is to return 1 result.<br />
<br />
The <b>queryUID</b> attribute may be generated by query services to uniquely identify the query. If present, it can be used by the storage service to cache the results of the query. When provided, all page requests, (all <b>MIRCquery</b> elements with different <b>firstresult</b> attribute values but otherwise containing the same child elements) have the same <b>queryUID</b> attribute value.<br />
<br />
The <b>unknown</b> attribute is optionally provided by the query service to instruct the storage service to return the query results as a set of unknowns, providing an alternative title and abstract that conceal the diagnostic result from the student. The value of the attribute may be <b>yes</b> or <b>no</b>. If the attribute is missing, the default value of <b>no</b> is to be used.<br />
<br />
===MIRCquery Child Elements===<br />
All the child elements are optional in a MIRCquery. <br />
A storage service uses the value of any child element included in a MIRCquery as a query field and searches its index for documents containing the contents of the query field in data that is identified to be of the type defined by the name of the child element. Thus, if a MIRCquery contains an <br />
<pre><anatomy>chest</anatomy></pre><br />
child, the storage service searches its index for documents which containing the word <b>chest</b> in a field identified as <b>anatomy</b>. <br />
<br />
Certain elements have enumerated values:<br />
*<b>pt-sex</b><br />
*<b>format</b><br />
*<b>compression</b><br />
*<b>modality</b><br />
*<b>document-type</b><br />
*<b>level</b><br />
*<b>access</b><br />
*<b>language code="…"</b><br />
These values are defined in [[The MIRCdocument Schema]].<br />
<br />
The <b>author</b> element is a special case. Any text contained within the <b>author</b> element of a MIRCquery is intended to be used as a match against any information associated with an author. The RSNA storage service, for example, uses the contents of the <b>author</b> element of the MIRCquery to search all the child elements of the <b>author</b> element in a MIRCdocument (e.g., the <b>name</b>, <b>affiliation</b>, and <b>contact</b> elements).<br />
<br />
The <b>peer-review</b> element is another special case. If the element is present in the MIRCquery, all documents listed in search results are required to have been peer-reviewed. If it is missing from the MIRCquery, no constraints are placed on the peer-review status of documents listed in search results. Any text value of the peer-review element is ignored.<br />
<br />
==Query Rules==<br />
There may be at most one child element of each type in a MIRCquery. Complex searches within an element type are done using the boolean syntax described below.<br />
<br />
The RSNA query and storage services implement the following search rules:<br />
*If text appears in any MIRCquery child element or attribute, it is a required match for a corresponding element in a document to be listed in the search results.<br />
*All child elements appearing within a MIRCquery are required matches, e.g., a matching document is one that matches all query fields.<br />
*Child elements that are not included in a MIRCquery are not required matches. Thus, an empty MIRCquery (<MIRCquery/>) is a match to all documents in the storage service.<br />
*Text is not case-sensitive.<br />
*A free-text search, matching text anywhere in a document, is done by placing the search text in the text value of the <MIRCquery> element.<br />
*Search text containing separate words with no intervening operator characters results in a logical AND of all the words, but not necessarily in order.<br />
*Search text can be constructed with a logical OR using the “|” character. <br />
*Search text can be constrained to appear in order by placing it in quotes within the search string.<br />
*Complex combinations of logical AND and logical OR operations can be created using the parenthesis operator, ( … ).<br />
<br />
Note that the first bullet above implies that if text appears in a MIRCquery element or attribute that is not supported by a site’s software implementation, the site must return zero matches.<br />
<br />
==Examples==<br />
===Free-text Search===<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
alpha bravo charlie<br />
</MIRCquery><br />
</pre><br />
matches documents containing all the words <b>alpha</b>, <b>bravo</b>, and <b>charlie</b> in any order anywhere in the document, together or apart.<br />
<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
alpha | “bravo charlie” delta<br />
</MIRCquery><br />
</pre><br />
matches documents containing the word <b>alpha</b>. It also matches all documents containing the words <b>bravo</b>, and <b>charlie</b> together, in order, along with the word <b>delta</b> anywhere in the document, together or apart, whether <b>alpha</b> appears or not. This query is identical to:<br />
<pre><br />
<MIRCquery><br />
alpha | (“bravo charlie” delta)<br />
</MIRCquery><br />
</pre><br />
The following query:<br />
<pre><br />
<MIRCquery><br />
(alpha | “bravo charlie”) delta<br />
</MIRCquery><br />
</pre><br />
matches documents containing the word <b>delta</b> and either or both of <b>alpha</b> and <b>bravo charlie</b>, where <b>bravo charlie</b> appears as written. <br />
===Author Search===<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
author> john </author><br />
</MIRCquery><br />
</pre><br />
matches documents where at least one of the author’s names is <b>John</b>, so it matches author names <b>John Doe</b> and <b>Elton John</b>. It would also match a document authored by <b>Jane Doe</b> of <b>Johns Hopkins</b>.<br />
<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<author> john doe </author><br />
</MIRCquery><br />
</pre><br />
matches documents where an author’s name is “John Doe” or “Doe John”. It also matches documents with two authors named “John Smith” and “Jane Doe”, but it does not match a document with only one author named “Elton John”.<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<author> ”john doe” </author><br />
</MIRCquery><br />
</pre><br />
matches documents where an author’s name is <b>John Doe</b> or <b>Elton John Doe</b> but not <b>John Q. Doe</b>. It also does not match documents with two authors named <b>John Smith</b> and <b>Jane Doe</b>.<br />
<br />
===Patient Search===<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<patient><br />
<pt-age><br />
<months>0-2</months><br />
<pt-age><br />
</patient><br />
</MIRCquery><br />
</pre><br />
matches documents containing at least one reference to a patient from birth to 2 months old.<br />
===Image Search===<br />
The <b>image</b> element is used to search for documents containing images. The following query:<br />
<pre><br />
<MIRCquery><br />
<image><br />
<format>DICOM</format><br />
<modality>CT</modality><br />
<anatomy>brain</anatomy><br />
</image><br />
</MIRCquery><br />
</pre><br />
matches documents referencing at least one DICOM CT image of the brain. <br />
<br />
The <b>modality</b> and <b>anatomy</b> elements may also appear as children of the <b>MIRCquery</b> element, in which case they refer to the document as a whole rather than to images within the document. Thus, the following query:<br />
<pre><br />
<MIRCquery><br />
<modality>MR</modality><br />
<anatomy>chest</anatomy><br />
</MIRCquery><br />
</pre><br />
matches documents referencing the MR modality and chest anatomy, whether they contain images or not.<br />
<br />
===Code Search===<br />
The <b>code</b> element is used in documents stored in MIRCdocument format to identify medical codes, e.g. ACR, CPT, SNOMED, etc.<br />
<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<code coding-system=”ACR”>1.2</code><br />
</MIRCquery><br />
</pre><br />
matches documents containing an <b>ACR</b> code with the value 1.2.<br />
<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<code>1.2</code><br />
</MIRCquery><br />
</pre><br />
matches documents containing a code element with the value 1.2 in any coding-scheme.<br />
<br />
===Document Description Search===<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<document-description><br />
radiologic teaching file<br />
</document-description><br />
</MIRCquery><br />
</pre><br />
matches documents identified as teaching files.<br />
<br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<document-type><br />
radiologic teaching file<br />
</document-type><br />
<level><br />
advanced<br />
</level><br />
<peer-review/><br />
<access><br />
public<br />
</access><br />
</MIRCquery><br />
</pre><br />
matches advanced teaching files that have been peer-reviewed and that are defined as publicly accessible.<br />
<br />
===Combined Element and Free Text Search===<br />
When multiple elements occur in a query, the search criteria are treated as all being required. <br />
The following query:<br />
<pre><br />
<MIRCquery><br />
<access>public</access><br />
<author>john</author><br />
<modality>MR</modality><br />
<anatomy>chest</anatomy><br />
alpha bravo charlie<br />
</MIRCquery><br />
</pre><br />
matches public documents where at least one of the author’s names is <b>John</b>, at least one reference to an MR chest image is included, and the words <b>alpha</b>, <b>bravo</b>, and <b>charlie</b> all occur in any order anywhere in the document, together or apart.<br />
<br />
==Notes and Suggestions for Implementers==<br />
===Content Type===<br />
To provide the most efficient support for all languages, query services and storage services should transmit their MIRCquery and MIRCqueryresult contents in UTF-8. Some MIRC query service implementations, in order to convert to UTF-8, transmit a content type of:<br />
<pre><br />
text/xml; charset=utf-8<br />
</pre><br />
For that reason, storage services should not test the Content-Type using something like:<br />
<pre><br />
if (contentType.equals(“text/xml”)) { … }<br />
</pre><br />
but instead:<br />
<pre><br />
if (contentType.indexOf(“text/xml”) != -1) { … }<br />
</pre><br />
<br />
===The Abstract===<br />
The contents of the <b>abstract</b> element should be brief – less than 10 lines of text – in order to keep the complete set of query results short enough to allow the user to look through the results and select the desired document. The RSNA query service imposes a 1000-character limit on the length of the abstract. Abstracts that exceed the limit are truncated, and any embedded element tags (e.g. HTML) are suppressed to ensure that the result remains well-formed.<br />
<br />
If the document is not in HTML format, its format can be noted in the abstract to assist the user in deciding whether the document is of interest.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MediaWiki:Sidebar&diff=2838MediaWiki:Sidebar2007-06-13T15:22:08Z<p>Rboden: </p>
<hr />
<div>* navigation<br />
** mainpage|mainpage<br />
** downloads|Downloads<br />
** http://mirc.rsna.org|RSNA MIRC Site<br />
** http://forums.rsna.org/forumdisplay.php?forumid=9|MIRC Forums<br />
** MIRC Mailing List | Mailing List<br />
** http://bugzilla.mirc.rsna.org:8088/ | Report a Bug<br />
** Special:Allpages | Article Index<br />
<br />
* manuals<br />
** New Installation Instructions|Installation<br />
** MIRC User's Manual|User's Manual<br />
** MIRC Administrator's Manual|Admin's Manual<br />
** Clinical Trial Administrator's Manual|Clinical Trials Manual<br />
** Developers Manual| Developer's Manual</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=MediaWiki:Sidebar&diff=2665MediaWiki:Sidebar2007-02-20T16:07:12Z<p>Rboden: </p>
<hr />
<div>* navigation<br />
** mainpage|mainpage<br />
** downloads|Downloads<br />
** http://mirc.rsna.org|RSNA MIRC Site<br />
** http://forums.rsna.org/forumdisplay.php?forumid=9|MIRC Forums<br />
** MIRC Mailing List | Mailing List<br />
** http://bugzilla.mirc.rsna.org:8088/ | Report a Bug<br />
** Special:Allpages | Article Index<br />
<br />
* manuals<br />
** New Installation Instructions|Installation<br />
** MIRC User's Manual|User's Manual<br />
** MIRC Administrator's Manual|Admin's Manual<br />
** Clinical Trial Administrator's Manual|Clinical Trial's Manual<br />
** Developers Manual| Developer's Manual</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Contact&diff=2620Contact2007-01-23T14:56:41Z<p>Rboden: /* Using the Mailing List */</p>
<hr />
<div>The MIRC Mailing list was created as an alternate to the MIRC Forums. The mailing list is intended as a way of discussing things pertaining to MIRC, as well as a place for people to come, to find answers to their MIRC Questions.<br />
<br />
==Joining the Mailing List==<br />
The easiest way to join the mailing list, is to send an email to [mailto:rsnamirc-subscribe@yahoogroups.com rsnamirc-subscribe@yahoogroups.com] from the email address that you wish to use. There is a manual approval process, so you may need to wait a day or two for your request to be approved.<br />
<br />
==Who should join the mailing list?==<br />
This is a work in progress right now. We envision a mailing list that would benefit all MIRC users. It could be a place where people could come to ask an experienced group of MIRC users for answers to their questions. It couldalso be a place for experienced MIRC users to discuss new features. In the future we may consider breaking this off into more than one mailing list for the different interests (clinical trials, teaching files, etc.).<br />
<br />
==Using the Mailing List==<br />
To send a message to the mailing list, you can simply write an email to [mailto:rsnamirc@yahoogroups.com rsnamirc@yahoogroups.com]. You must be a member of the list first. (See Joining the Mailing list above.) There is also a web interface at http://groups.yahoo.com that allows you to view all of the previous topics in the list, as well as compose messages via the web. This feature however requires that you have a Yahoo account.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Contact&diff=2619Contact2007-01-23T14:56:13Z<p>Rboden: /* Joining the Mailing List */</p>
<hr />
<div>The MIRC Mailing list was created as an alternate to the MIRC Forums. The mailing list is intended as a way of discussing things pertaining to MIRC, as well as a place for people to come, to find answers to their MIRC Questions.<br />
<br />
==Joining the Mailing List==<br />
The easiest way to join the mailing list, is to send an email to [mailto:rsnamirc-subscribe@yahoogroups.com rsnamirc-subscribe@yahoogroups.com] from the email address that you wish to use. There is a manual approval process, so you may need to wait a day or two for your request to be approved.<br />
<br />
==Who should join the mailing list?==<br />
This is a work in progress right now. We envision a mailing list that would benefit all MIRC users. It could be a place where people could come to ask an experienced group of MIRC users for answers to their questions. It couldalso be a place for experienced MIRC users to discuss new features. In the future we may consider breaking this off into more than one mailing list for the different interests (clinical trials, teaching files, etc.).<br />
<br />
==Using the Mailing List==<br />
To send a message to the mailing list, you can simply write an email to rsnamirc@yahoogroups.com. You must be a member of the list first. (See Joining the Mailing list above.) There is also a web interface at http://groups.yahoo.com that allows you to view all of the previous topics in the list, as well as compose messages via the web. This feature however requires that you have a Yahoo account.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Contact&diff=2618Contact2007-01-23T14:54:01Z<p>Rboden: /* Using the Mailing List */</p>
<hr />
<div>The MIRC Mailing list was created as an alternate to the MIRC Forums. The mailing list is intended as a way of discussing things pertaining to MIRC, as well as a place for people to come, to find answers to their MIRC Questions.<br />
<br />
==Joining the Mailing List==<br />
The easiest way to join the mailing list, is to send an email to rsnamirc-subscribe@yahoogroups.com from the email address that you wish to use. There is a manual approval process, so you may need to wait a day or two for your request to be approved.<br />
<br />
==Who should join the mailing list?==<br />
This is a work in progress right now. We envision a mailing list that would benefit all MIRC users. It could be a place where people could come to ask an experienced group of MIRC users for answers to their questions. It couldalso be a place for experienced MIRC users to discuss new features. In the future we may consider breaking this off into more than one mailing list for the different interests (clinical trials, teaching files, etc.).<br />
<br />
==Using the Mailing List==<br />
To send a message to the mailing list, you can simply write an email to rsnamirc@yahoogroups.com. You must be a member of the list first. (See Joining the Mailing list above.) There is also a web interface at http://groups.yahoo.com that allows you to view all of the previous topics in the list, as well as compose messages via the web. This feature however requires that you have a Yahoo account.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Downloads&diff=2617Downloads2007-01-23T14:50:06Z<p>Rboden: /* Beta Release */</p>
<hr />
<div>==Installation Documents==<br />
<br />
* '''[[New Installation Instructions]]''' - Installing a new MIRC site? These instructions should help you through the installation process.<br />
<br />
== Major Release ==<br />
''This is the current MIRC release. It is recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/T30/MIRCsite-installer.jar T30 Installer]'''<br />
<br />
* '''[[New MIRC Features|Release Notes]]''' - List of new features added to the MIRC software.<br />
<br />
== Beta Release ==<br />
''This is the current version in development. It contains all the latest features, but it has not been tested as heavily. This release is recommended for beta-testers.''<br />
<br />
* '''[http://mirc.rsna.org/T31alpha/MIRCsite-installer.jar T31-alpha Installer]'''<br />
<br />
* '''[[New MIRC Features(Beta)|Beta Release Notes]]''' - List of new features added to the MIRC software.<br />
<br />
== Other Components ==<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Downloads&diff=2612Downloads2007-01-23T14:34:28Z<p>Rboden: </p>
<hr />
<div>==Installation Documents==<br />
<br />
* '''[[New Installation Instructions]]''' - Installing a new MIRC site? These instructions should help you through the installation process.<br />
<br />
== Major Release ==<br />
''This is the current MIRC release. It is recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/T30/MIRCsite-installer.jar T30 Installer]'''<br />
<br />
* '''[[New MIRC Features|Release Notes]]''' - List of new features added to the MIRC software.<br />
<br />
== Beta Release ==<br />
''This is the current version in development. It contains all the latest features, but it has not been tested as heavily. This release is recommended for beta-testers.''<br />
<br />
* '''[http://mirc.rsna.org/T31alpha/MIRCsite-installer.jar T31-alpha Installer]''' - This latest version incorporates some fixes in various web browsers.<br />
<br />
* '''[[New MIRC Features(Beta)|Beta Release Notes]]''' - List of new features added to the MIRC software.<br />
<br />
== Other Components ==<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>Rbodenhttp://mircwiki.rsna.org/index.php?title=Downloads&diff=2610Downloads2007-01-22T20:50:13Z<p>Rboden: </p>
<hr />
<div>==Installation Documents==<br />
<br />
* '''[[New MIRC Features|Release Notes]]''' - List of new features added to the MIRC software.<br />
<br />
* '''[[New Installation Instructions]]''' - Installing a new MIRC site? These instructions should help you through the installation process.<br />
<br />
== Major Release ==<br />
''This is the current MIRC release. It is recommended for most users.''<br />
<br />
* '''[http://mirc.rsna.org/T30/MIRCsite-installer.jar T30 Installer]'''<br />
<br />
== Beta Release ==<br />
''This is the current version in development. It contains all the latest features, but it has not been tested as heavily. This release is recommended for beta-testers.''<br />
<br />
* '''[http://mirc.rsna.org/T31alpha/MIRCsite-installer.jar T31-alpha Installer]''' - This latest version incorporates some fixes in various web browsers.<br />
<br />
== Other Components ==<br />
''These are client-side tools.''<br />
<br />
* '''[[MIRC Powerpoint Tool]]''' - A Powerpoint plug-in that enables saving Powerpoint presentations on a MIRC site.<br />
* '''[[MIRC TCE Export Manager]]''' - The MIRC implementation of the IHE Teaching Files and Clinical Trials Export integration profile Export Manager actor.<br />
* '''[[DicomEditor]]''' - A utility program for viewing, anonymizing and editing DICOM image files.<br />
* '''[[FileSender]]''' - A file transmission utility that supports DICOM, HTTP, and HTTPS.</div>Rboden