- This Software License covers downloads from the i2b2 project ("i2b2") maintained by the Brigham and Women's Hospital, Inc. ("BWH").
-
- Your downloading, copying, modifying, displaying, distributing or use of any software and/or data from i2b2 (collectively, the "Software") constitutes acceptance of all of the terms and conditions of this Software License. If you do not agree to such terms and conditions, you have no right to download, copy, modify, display, distribute or use the Software.
-
-
-1. As used in this Software License, "you" means the individual downloading and/or using, reproducing, modifying, displaying and/or distributing the Software and the institution or entity which employs or is otherwise affiliated with such individual in connection therewith. The BWH hereby grants you, with right to sublicense, with respect to BWH's rights in the software, and related technical data, if any, which is the subject of this Software License, a royalty-free, non-exclusive license to use, reproduce, make derivative works of, display and distribute the Software, provided that:
-
-(a) You accept and adhere to all of the terms and conditions of this Software License;
-
-(b) In connection with any copy of or sublicense of all or any portion of the Software, all of the terms and conditions in this Software License shall appear in and shall apply to such copy and such sublicensee, including without limitation all source and executable forms and on any user documentation, prefaced with the following words: "All or portions of this licensed product (such portions are the "Software") have been obtained under license from The Brigham and Women's Hospital, Inc. and are subject to the following terms and conditions:"
-
-(c) You preserve and maintain all applicable attributions, copyright notices and licenses included in or applicable to the Software.
-
-
-
-2. Modifications to the Software shall mean any addition to or deletion from the substance or structure of either the Software or any previous Modifications. When Software is released as a series of files, a Modification is: (i) any addition to or deletion from the contents of a file containing the Software or previous Modifications; or (ii) any new file that contains any part of the Software or previous Modifications.
-
-(a) You agree that you will deliver, and you will cause all sublicensees to deliver, to BWH copies of all Modifications that are made to the Software, on or before the date on which the Modifications are distributed to any third party, and you hereby grant to BWH, and will cause all of your sublicensees to grant to BWH, a non-exclusive, royalty-free, irrevocable, non-terminable license to use, reproduce, make derivative works of, display, perform, and distribute any and all Modifications in source code and binary code form for any purpose and to sublicense such rights to others.
-
-(b) You agree that all Modifications of the Software must be clearly identified and marked as such, and must not be misrepresented as being the original Software.
-
-(c) You agree to consider making, but are under no obligation to make, the source code of any of your Modifications to the Software freely available to others on an open source basis.
-
-
-
-3. The license granted under this Software License includes without limitation the right to (i) incorporate the Software into proprietary programs (subject to any restrictions applicable to such programs), (ii) add your own copyright statement to your Modifications of the Software, and (iii) provide additional or different license terms and conditions in your sublicenses of Modifications of the Software; provided that in each case your use, reproduction or distribution of such modifications otherwise complies with the conditions stated in this Software License.
-
-
-4. This Software License does not grant any rights with respect to third party software, except those rights that BWH has been authorized by a third party to grant to you, and accordingly you are solely responsible for (i) obtaining any permissions from third parties that you need to use, reproduce, make derivative works of, display and distribute the Software, and (ii) informing your sublicensees, including without limitation your end-users, of their obligations to secure any such required permissions.
-
-
-5. The Software has been designed for research purposes only and has not been reviewed or approved by the Food and Drug Administration or by any other agency. YOU ACKNOWLEDGE AND AGREE THAT CLINICAL APPLICATIONS ARE NEITHER RECOMMENDED NOR ADVISED. Any commercialization of the Software is at the sole risk of the party or parties engaged in such commercialization. You further agree to use, reproduce, make derivative works of, display and distribute the Software in compliance with all applicable governmental laws, regulations and orders, including without limitation those relating to export and import control.
-
-
-6. The Software is provided "AS IS" and neither BWH nor any contributor to the software (each a "Contributor") shall have any obligation to provide maintenance, support, updates, enhancements or modifications thereto. You acknowledge and agree that you are responsible for your selection, testing, modification, use and distribution of the Software, in any form, and that you hereby expressly waive any claim for any loss, damage, or injury that may occur as a result of your use or distribution of the Software. You agree that you are responsible for obtaining and will maintain insurance providing coverage (including but not limited to general liability and product liability insurance) that is appropriate in light of the waivers and assumptions of liability set forth in this Software License. You furthermore waive any right of recovery against BWH or any Contributor (including any right of subrogation against BWH or any Contributor or any insurer of BWH or any Contributor) for loss or damage arising out of or incident to your use or distribution of the Software.
-
-7. BWH AND ALL CONTRIBUTORS SPECIFICALLY DISCLAIM ALL EXPRESS AND IMPLIED WARRANTIES OF ANY KIND INCLUDING, BUT NOT LIMITED TO, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL BWH OR ANY CONTRIBUTOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY ARISING IN ANY WAY RELATED TO THE SOFTWARE, EVEN IF BWH OR ANY CONTRIBUTOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE MAXIMUM EXTENT NOT PROHIBITED BY LAW OR REGULATION, YOU FURTHER ASSUME ALL LIABILITY FOR YOUR USE, REPRODUCTION, MAKING OF DERIVATIVE WORKS, DISPLAY, LICENSE OR DISTRIBUTION OF THE SOFTWARE AND AGREE TO INDEMNIFY AND HOLD HARMLESS BWH AND ALL CONTRIBUTORS (AND ALL RELATED INDIVIDUALS AND ENTITIES) FROM AND AGAINST ANY AND ALL CLAIMS, SUITS, ACTIONS, DEMANDS AND JUDGMENTS ARISING THEREFROM OR FROM ANY MODIFICATIONS OF THE SOFTWARE DELIVERED TO BWH HEREUNDER.
-
-
-8. None of the names, logos or trademarks of BWH or any of BWH's affiliates or any of the Contributors, or any funding agency, may be used to endorse or promote products produced in whole or in part by operation of the Software or derived from or based on the Software without specific prior written permission from the applicable party.
-
-
-9. Any use, reproduction or distribution of the Software which is not in accordance with this Software License shall automatically revoke all rights granted to you under this Software License and render Paragraphs 1 and 2 of this Software License null and void.
-
-
-10. This Software License does not grant any rights in or to any intellectual property owned by BWH or any Contributor except those rights expressly granted hereunder.
-
-
-Version 2.1 - 1/15/08
-
-
+
+i2b2 Software License ("Software License")
+Version 2.1 - 1/15/2009
+
+
+ This Software License covers downloads from the i2b2 project ("i2b2") maintained by the Brigham and Women's Hospital, Inc. ("BWH").
+
+ Your downloading, copying, modifying, displaying, distributing or use of any software and/or data from i2b2 (collectively, the "Software") constitutes acceptance of all of the terms and conditions of this Software License. If you do not agree to such terms and conditions, you have no right to download, copy, modify, display, distribute or use the Software.
+
+
+1. As used in this Software License, "you" means the individual downloading and/or using, reproducing, modifying, displaying and/or distributing the Software and the institution or entity which employs or is otherwise affiliated with such individual in connection therewith. The BWH hereby grants you, with right to sublicense, with respect to BWH's rights in the software, and related technical data, if any, which is the subject of this Software License, a royalty-free, non-exclusive license to use, reproduce, make derivative works of, display and distribute the Software, provided that:
+
+(a) You accept and adhere to all of the terms and conditions of this Software License;
+
+(b) In connection with any copy of or sublicense of all or any portion of the Software, all of the terms and conditions in this Software License shall appear in and shall apply to such copy and such sublicensee, including without limitation all source and executable forms and on any user documentation, prefaced with the following words: "All or portions of this licensed product (such portions are the "Software") have been obtained under license from The Brigham and Women's Hospital, Inc. and are subject to the following terms and conditions:"
+
+(c) You preserve and maintain all applicable attributions, copyright notices and licenses included in or applicable to the Software.
+
+
+
+2. Modifications to the Software shall mean any addition to or deletion from the substance or structure of either the Software or any previous Modifications. When Software is released as a series of files, a Modification is: (i) any addition to or deletion from the contents of a file containing the Software or previous Modifications; or (ii) any new file that contains any part of the Software or previous Modifications.
+
+(a) You agree that you will deliver, and you will cause all sublicensees to deliver, to BWH copies of all Modifications that are made to the Software, on or before the date on which the Modifications are distributed to any third party, and you hereby grant to BWH, and will cause all of your sublicensees to grant to BWH, a non-exclusive, royalty-free, irrevocable, non-terminable license to use, reproduce, make derivative works of, display, perform, and distribute any and all Modifications in source code and binary code form for any purpose and to sublicense such rights to others.
+
+(b) You agree that all Modifications of the Software must be clearly identified and marked as such, and must not be misrepresented as being the original Software.
+
+(c) You agree to consider making, but are under no obligation to make, the source code of any of your Modifications to the Software freely available to others on an open source basis.
+
+
+
+3. The license granted under this Software License includes without limitation the right to (i) incorporate the Software into proprietary programs (subject to any restrictions applicable to such programs), (ii) add your own copyright statement to your Modifications of the Software, and (iii) provide additional or different license terms and conditions in your sublicenses of Modifications of the Software; provided that in each case your use, reproduction or distribution of such modifications otherwise complies with the conditions stated in this Software License.
+
+
+4. This Software License does not grant any rights with respect to third party software, except those rights that BWH has been authorized by a third party to grant to you, and accordingly you are solely responsible for (i) obtaining any permissions from third parties that you need to use, reproduce, make derivative works of, display and distribute the Software, and (ii) informing your sublicensees, including without limitation your end-users, of their obligations to secure any such required permissions.
+
+
+5. The Software has been designed for research purposes only and has not been reviewed or approved by the Food and Drug Administration or by any other agency. YOU ACKNOWLEDGE AND AGREE THAT CLINICAL APPLICATIONS ARE NEITHER RECOMMENDED NOR ADVISED. Any commercialization of the Software is at the sole risk of the party or parties engaged in such commercialization. You further agree to use, reproduce, make derivative works of, display and distribute the Software in compliance with all applicable governmental laws, regulations and orders, including without limitation those relating to export and import control.
+
+
+6. The Software is provided "AS IS" and neither BWH nor any contributor to the software (each a "Contributor") shall have any obligation to provide maintenance, support, updates, enhancements or modifications thereto. You acknowledge and agree that you are responsible for your selection, testing, modification, use and distribution of the Software, in any form, and that you hereby expressly waive any claim for any loss, damage, or injury that may occur as a result of your use or distribution of the Software. You agree that you are responsible for obtaining and will maintain insurance providing coverage (including but not limited to general liability and product liability insurance) that is appropriate in light of the waivers and assumptions of liability set forth in this Software License. You furthermore waive any right of recovery against BWH or any Contributor (including any right of subrogation against BWH or any Contributor or any insurer of BWH or any Contributor) for loss or damage arising out of or incident to your use or distribution of the Software.
+
+7. BWH AND ALL CONTRIBUTORS SPECIFICALLY DISCLAIM ALL EXPRESS AND IMPLIED WARRANTIES OF ANY KIND INCLUDING, BUT NOT LIMITED TO, ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL BWH OR ANY CONTRIBUTOR BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY ARISING IN ANY WAY RELATED TO THE SOFTWARE, EVEN IF BWH OR ANY CONTRIBUTOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TO THE MAXIMUM EXTENT NOT PROHIBITED BY LAW OR REGULATION, YOU FURTHER ASSUME ALL LIABILITY FOR YOUR USE, REPRODUCTION, MAKING OF DERIVATIVE WORKS, DISPLAY, LICENSE OR DISTRIBUTION OF THE SOFTWARE AND AGREE TO INDEMNIFY AND HOLD HARMLESS BWH AND ALL CONTRIBUTORS (AND ALL RELATED INDIVIDUALS AND ENTITIES) FROM AND AGAINST ANY AND ALL CLAIMS, SUITS, ACTIONS, DEMANDS AND JUDGMENTS ARISING THEREFROM OR FROM ANY MODIFICATIONS OF THE SOFTWARE DELIVERED TO BWH HEREUNDER.
+
+
+8. None of the names, logos or trademarks of BWH or any of BWH's affiliates or any of the Contributors, or any funding agency, may be used to endorse or promote products produced in whole or in part by operation of the Software or derived from or based on the Software without specific prior written permission from the applicable party.
+
+
+9. Any use, reproduction or distribution of the Software which is not in accordance with this Software License shall automatically revoke all rights granted to you under this Software License and render Paragraphs 1 and 2 of this Software License null and void.
+
+
+10. This Software License does not grant any rights in or to any intellectual property owned by BWH or any Contributor except those rights expressly granted hereunder.
<div class="qryButtonDate" style="float:left"><a id="queryPanelDatesB1" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.dateConstraint.showDates(0)" title="Select the date range for this group's criterion to have occured within...">Dates</a></div>
<div class="qryButtonOccurs" style="float:left"><a id="queryPanelOccursB1" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[0].showOccurs()" title="Select the minimum number of times this group's criterion has occured...">Occurs > <span id="QP1Occurs">0</span>x</a></div>
<div class="qryButtonExclude" style="float:left"><a id="queryPanelExcludeB1" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[0].doExclude()" title="Exclude records matching this group's criteria...">Exclude</a></div>
<option value="SAMEVISIT">Occurs in Same Encounter</option>
</select>
</div>
<div class="qryButtonLimitB1" id="qryButtonLimitB1" style="display:none; float:right;"><a id="queryPanelLimitB1" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[0].showLimit()" title="Select the minimum number of times this group's criterion has occured...">Limit</a></div>
<div class="qryButtonDate" style="float:left"><a id="queryPanelDatesB2" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.dateConstraint.showDates(1)" title="Select the date range for this group's criterion to have occured within...">Dates</a></div>
<div class="qryButtonOccurs" style="float:left"><a id="queryPanelOccursB2" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[1].showOccurs()" title="Select the minimum number of times this group's criterion has occured...">Occurs > <span id="QP2Occurs">0</span>x</a></div>
<div class="qryButtonExclude" style="float:left"><a id="queryPanelExcludeB2" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[1].doExclude()" title="Exclude records matching this group's criteria...">Exclude</a></div>
<div class="qryButtonDate" style="float:left"><a id="queryPanelDatesB3" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.dateConstraint.showDates(2)" title="Select the date range for this group's criterion to have occured within...">Dates</a></div>
<div class="qryButtonOccurs" style="float:left"><a id="queryPanelOccursB3" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[2].showOccurs()" title="Select the minimum number of times this group's criterion has occured...">Occurs > <span id="QP3Occurs">0</span>x</a></div>
<div class="qryButtonExclude" style="float:left"><a id="queryPanelExcludeB3" class="queryPanelButton" href="JavaScript:i2b2.CRC.ctrlr.QT.panelControllers[2].doExclude()" title="Exclude records matching this group's criteria...">Exclude</a></div>
<div class="Descript">Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.</div>
<div class="hd" style="background:#6677AA;">Options for Navigating Terms</div>
<div class="bd">
<br />
<div style="font-size:12px; margin-left:50px" >Maximum Number of Children to Display: <input id="ONTNAVMaxQryDisp" style="width:35px" value="200" /></div>
<div style="margin-left:50px"><input type="checkbox" id="ONTNAVshowHiddens" /> Show Hidden Terms</div>
<div style="margin-left:50px"><input type="checkbox" id="ONTNAVshowSynonyms" /> Show Synonymous Terms</div>
<div class="hd" style="background:#6677AA;">Options for Finding Terms</div>
<div class="bd">
<br />
<div style="font-size:12px; margin-left:50px" >Maximum Number of Children to Display: <input id="ONTFINDMaxQryDisp" style="width:35px" value="200" /></div>
<div style="margin-left:50px"><input type="checkbox" id="ONTFINDshowHiddens" /> Show Hidden Terms</div>
<div style="margin-left:50px"><input type="checkbox" checked id="ONTFINDshowSynonyms" /> Show Synonymous Terms</div>
<input type="checkbox" id="constraintEncounterFirst" name="constraintEncounterBefore">Only use FIRST financial encounter in which the event(s) occur.<br/>
<input type="checkbox" id="constraintEncounterLast" name="constraintEncounterLast">Only use LAST financial encounter in which the event(s) occur.
<div style="font-size:12px; margin-left:10px" >Your session will automatically time out in 5 minutes due to inactivity. Please click "OK" to continue your session, or click cancel to log out.</div>
+ value = new Array(n = (group = this[0]).length);
+ while (++i < n) {
+ if (node = group[i]) {
+ value[i] = node.__data__;
+ }
+ }
+ return value;
+ }
+ function bind(group, groupData) {
+ var i, n = group.length, m = groupData.length, n0 = Math.min(n, m), updateNodes = new Array(m), enterNodes = new Array(m), exitNodes = new Array(n), node, nodeData;
+ if (key) {
+ var nodeByKeyValue = new d3_Map(), keyValues = new Array(n), keyValue;
+ for (i = -1; ++i < n; ) {
+ if (nodeByKeyValue.has(keyValue = key.call(node = group[i], node.__data__, i))) {
+ var min = Math.min(r /= 255, g /= 255, b /= 255), max = Math.max(r, g, b), d = max - min, h, s, l = (max + min) / 2;
+ if (d) {
+ s = l < .5 ? d / (max + min) : d / (2 - max - min);
+ if (r == max) h = (g - b) / d + (g < b ? 6 : 0); else if (g == max) h = (b - r) / d + 2; else h = (r - g) / d + 4;
+ h *= 60;
+ } else {
+ h = NaN;
+ s = l > 0 && l < 1 ? 0 : h;
+ }
+ return new d3_hsl(h, s, l);
+ }
+ function d3_rgb_lab(r, g, b) {
+ r = d3_rgb_xyz(r);
+ g = d3_rgb_xyz(g);
+ b = d3_rgb_xyz(b);
+ var x = d3_xyz_lab((.4124564 * r + .3575761 * g + .1804375 * b) / d3_lab_X), y = d3_xyz_lab((.2126729 * r + .7151522 * g + .072175 * b) / d3_lab_Y), z = d3_xyz_lab((.0193339 * r + .119192 * g + .9503041 * b) / d3_lab_Z);
+ d3_geo_centroidZ0 += (z - d3_geo_centroidZ0) / d3_geo_centroidW0;
+ }
+ function d3_geo_centroidLineStart() {
+ var x0, y0, z0;
+ d3_geo_centroid.point = function(λ, Ï) {
+ λ *= d3_radians;
+ var cosÏ = Math.cos(Ï *= d3_radians);
+ x0 = cosÏ * Math.cos(λ);
+ y0 = cosÏ * Math.sin(λ);
+ z0 = Math.sin(Ï);
+ d3_geo_centroid.point = nextPoint;
+ d3_geo_centroidPointXYZ(x0, y0, z0);
+ };
+ function nextPoint(λ, Ï) {
+ λ *= d3_radians;
+ var cosÏ = Math.cos(Ï *= d3_radians), x = cosÏ * Math.cos(λ), y = cosÏ * Math.sin(λ), z = Math.sin(Ï), w = Math.atan2(Math.sqrt((w = y0 * z - z0 * y) * w + (w = z0 * x - x0 * z) * w + (w = x0 * y - y0 * x) * w), x0 * x + y0 * y + z0 * z);
+ var k = lower48.scale(), t = lower48.translate(), x = (coordinates[0] - t[0]) / k, y = (coordinates[1] - t[1]) / k;
+ return (y >= .12 && y < .234 && x >= -.425 && x < -.214 ? alaska : y >= .166 && y < .234 && x >= -.214 && x < -.115 ? hawaii : lower48).invert(coordinates);
+ if (!arguments.length) return lower48.translate();
+ var k = lower48.scale(), x = +_[0], y = +_[1];
+ lower48Point = lower48.translate(_).clipExtent([ [ x - .455 * k, y - .238 * k ], [ x + .455 * k, y + .238 * k ] ]).stream(pointStream).point;
+ alaskaPoint = alaska.translate([ x - .307 * k, y + .201 * k ]).clipExtent([ [ x - .425 * k + ε, y + .12 * k + ε ], [ x - .214 * k - ε, y + .234 * k - ε ] ]).stream(pointStream).point;
+ hawaiiPoint = hawaii.translate([ x - .205 * k, y + .212 * k ]).clipExtent([ [ x - .214 * k + ε, y + .166 * k + ε ], [ x - .115 * k - ε, y + .234 * k - ε ] ]).stream(pointStream).point;
+ return albersUsa;
+ };
+ return albersUsa.scale(1070);
+ };
+ var d3_geo_pathAreaSum, d3_geo_pathAreaPolygon, d3_geo_pathArea = {
+ var s = [], q = [], n, A = d3.transform(a), B = d3.transform(b), ta = A.translate, tb = B.translate, ra = A.rotate, rb = B.rotate, wa = A.skew, wb = B.skew, ka = A.scale, kb = B.scale;
+ if (ta[0] != tb[0] || ta[1] != tb[1]) {
+ s.push("translate(", null, ",", null, ")");
+ q.push({
+ i: 1,
+ x: d3_interpolateNumber(ta[0], tb[0])
+ }, {
+ i: 3,
+ x: d3_interpolateNumber(ta[1], tb[1])
+ });
+ } else if (tb[0] || tb[1]) {
+ s.push("translate(" + tb + ")");
+ } else {
+ s.push("");
+ }
+ if (ra != rb) {
+ if (ra - rb > 180) rb += 360; else if (rb - ra > 180) ra += 360;
+ q.push({
+ i: s.push(s.pop() + "rotate(", null, ")") - 2,
+ x: d3_interpolateNumber(ra, rb)
+ });
+ } else if (rb) {
+ s.push(s.pop() + "rotate(" + rb + ")");
+ }
+ if (wa != wb) {
+ q.push({
+ i: s.push(s.pop() + "skewX(", null, ")") - 2,
+ x: d3_interpolateNumber(wa, wb)
+ });
+ } else if (wb) {
+ s.push(s.pop() + "skewX(" + wb + ")");
+ }
+ if (ka[0] != kb[0] || ka[1] != kb[1]) {
+ n = s.push(s.pop() + "scale(", null, ",", null, ")");
+ q.push({
+ i: n - 4,
+ x: d3_interpolateNumber(ka[0], kb[0])
+ }, {
+ i: n - 2,
+ x: d3_interpolateNumber(ka[1], kb[1])
+ });
+ } else if (kb[0] != 1 || kb[1] != 1) {
+ s.push(s.pop() + "scale(" + kb + ")");
+ }
+ n = q.length;
+ return function(t) {
+ var i = -1, o;
+ while (++i < n) s[(o = q[i]).i] = o.x(t);
+ return s.join("");
+ };
+ }
+ function d3_uninterpolateNumber(a, b) {
+ b = (b -= a = +a) || 1 / b;
+ return function(x) {
+ return (x - a) / b;
+ };
+ }
+ function d3_uninterpolateClamp(a, b) {
+ b = (b -= a = +a) || 1 / b;
+ return function(x) {
+ return Math.max(0, Math.min(1, (x - a) / b));
+ };
+ }
+ d3.layout = {};
+ d3.layout.bundle = function() {
+ return function(links) {
+ var paths = [], i = -1, n = links.length;
+ while (++i < n) paths.push(d3_layout_bundlePath(links[i]));
+ return paths;
+ };
+ };
+ function d3_layout_bundlePath(link) {
+ var start = link.source, end = link.target, lca = d3_layout_bundleLeastCommonAncestor(start, end), points = [ start ];
+ while (start !== lca) {
+ start = start.parent;
+ points.push(start);
+ }
+ var k = points.length;
+ while (end !== lca) {
+ points.splice(k, 0, end);
+ end = end.parent;
+ }
+ return points;
+ }
+ function d3_layout_bundleAncestors(node) {
+ var ancestors = [], parent = node.parent;
+ while (parent != null) {
+ ancestors.push(node);
+ node = parent;
+ parent = parent.parent;
+ }
+ ancestors.push(node);
+ return ancestors;
+ }
+ function d3_layout_bundleLeastCommonAncestor(a, b) {
+ linkDistance = typeof x === "function" ? x : +x;
+ return force;
+ };
+ force.distance = force.linkDistance;
+ force.linkStrength = function(x) {
+ if (!arguments.length) return linkStrength;
+ linkStrength = typeof x === "function" ? x : +x;
+ return force;
+ };
+ force.friction = function(x) {
+ if (!arguments.length) return friction;
+ friction = +x;
+ return force;
+ };
+ force.charge = function(x) {
+ if (!arguments.length) return charge;
+ charge = typeof x === "function" ? x : +x;
+ return force;
+ };
+ force.chargeDistance = function(x) {
+ if (!arguments.length) return Math.sqrt(chargeDistance2);
+ chargeDistance2 = x * x;
+ return force;
+ };
+ force.gravity = function(x) {
+ if (!arguments.length) return gravity;
+ gravity = +x;
+ return force;
+ };
+ force.theta = function(x) {
+ if (!arguments.length) return Math.sqrt(theta2);
+ theta2 = x * x;
+ return force;
+ };
+ force.alpha = function(x) {
+ if (!arguments.length) return alpha;
+ x = +x;
+ if (alpha) {
+ if (x > 0) alpha = x; else alpha = 0;
+ } else if (x > 0) {
+ event.start({
+ type: "start",
+ alpha: alpha = x
+ });
+ d3.timer(force.tick);
+ }
+ return force;
+ };
+ force.start = function() {
+ var i, n = nodes.length, m = links.length, w = size[0], h = size[1], neighbors, o;
+ for (i = 0; i < n; ++i) {
+ (o = nodes[i]).index = i;
+ o.weight = 0;
+ }
+ for (i = 0; i < m; ++i) {
+ o = links[i];
+ if (typeof o.source == "number") o.source = nodes[o.source];
+ if (typeof o.target == "number") o.target = nodes[o.target];
+ ++o.source.weight;
+ ++o.target.weight;
+ }
+ for (i = 0; i < n; ++i) {
+ o = nodes[i];
+ if (isNaN(o.x)) o.x = position("x", w);
+ if (isNaN(o.y)) o.y = position("y", h);
+ if (isNaN(o.px)) o.px = o.x;
+ if (isNaN(o.py)) o.py = o.y;
+ }
+ distances = [];
+ if (typeof linkDistance === "function") for (i = 0; i < m; ++i) distances[i] = +linkDistance.call(this, links[i], i); else for (i = 0; i < m; ++i) distances[i] = linkDistance;
+ strengths = [];
+ if (typeof linkStrength === "function") for (i = 0; i < m; ++i) strengths[i] = +linkStrength.call(this, links[i], i); else for (i = 0; i < m; ++i) strengths[i] = linkStrength;
+ charges = [];
+ if (typeof charge === "function") for (i = 0; i < n; ++i) charges[i] = +charge.call(this, nodes[i], i); else for (i = 0; i < n; ++i) charges[i] = charge;
+ function position(dimension, size) {
+ if (!neighbors) {
+ neighbors = new Array(n);
+ for (j = 0; j < n; ++j) {
+ neighbors[j] = [];
+ }
+ for (j = 0; j < m; ++j) {
+ var o = links[j];
+ neighbors[o.source.index].push(o.target);
+ neighbors[o.target.index].push(o.source);
+ }
+ }
+ var candidates = neighbors[i], j = -1, l = candidates.length, x;
+ while (++j < l) if (!isNaN(x = candidates[j][dimension])) return x;
+ return Math.random() * size;
+ }
+ return force.resume();
+ };
+ force.resume = function() {
+ return force.alpha(.1);
+ };
+ force.stop = function() {
+ return force.alpha(0);
+ };
+ force.drag = function() {
+ if (!drag) drag = d3.behavior.drag().origin(d3_identity).on("dragstart.force", d3_layout_forceDragstart).on("drag.force", dragmove).on("dragend.force", d3_layout_forceDragend);
+ var values = d3_identity, order = d3_layout_stackOrderDefault, offset = d3_layout_stackOffsetZero, out = d3_layout_stackOut, x = d3_layout_stackX, y = d3_layout_stackY;
+ var offsets = offset.call(stack, points, index);
+ var m = series[0].length, n, i, j, o;
+ for (j = 0; j < m; ++j) {
+ out.call(stack, series[0][j], o = offsets[j], points[0][j][1]);
+ for (i = 1; i < n; ++i) {
+ out.call(stack, series[i][j], o += points[i - 1][j][1], points[i][j][1]);
+ }
+ }
+ return data;
+ }
+ stack.values = function(x) {
+ if (!arguments.length) return values;
+ values = x;
+ return stack;
+ };
+ stack.order = function(x) {
+ if (!arguments.length) return order;
+ order = typeof x === "function" ? x : d3_layout_stackOrders.get(x) || d3_layout_stackOrderDefault;
+ return stack;
+ };
+ stack.offset = function(x) {
+ if (!arguments.length) return offset;
+ offset = typeof x === "function" ? x : d3_layout_stackOffsets.get(x) || d3_layout_stackOffsetZero;
+ return stack;
+ };
+ stack.x = function(z) {
+ if (!arguments.length) return x;
+ x = z;
+ return stack;
+ };
+ stack.y = function(z) {
+ if (!arguments.length) return y;
+ y = z;
+ return stack;
+ };
+ stack.out = function(z) {
+ if (!arguments.length) return out;
+ out = z;
+ return stack;
+ };
+ return stack;
+ };
+ function d3_layout_stackX(d) {
+ return d.x;
+ }
+ function d3_layout_stackY(d) {
+ return d.y;
+ }
+ function d3_layout_stackOut(d, y0, y) {
+ d.y0 = y0;
+ d.y = y;
+ }
+ var d3_layout_stackOrders = d3.map({
+ "inside-out": function(data) {
+ var n = data.length, i, j, max = data.map(d3_layout_stackMaxIndex), sums = data.map(d3_layout_stackReduceSum), index = d3.range(n).sort(function(a, b) {
+ var niced = d3_scale_nice(domain.map(log), positive ? Math : d3_scale_logNiceNegative);
+ linear.domain(niced);
+ domain = niced.map(pow);
+ return scale;
+ };
+ scale.ticks = function() {
+ var extent = d3_scaleExtent(domain), ticks = [], u = extent[0], v = extent[1], i = Math.floor(log(u)), j = Math.ceil(log(v)), n = base % 1 ? 2 : base;
+ if (isFinite(j - i)) {
+ if (positive) {
+ for (;i < j; i++) for (var k = 1; k < n; k++) ticks.push(pow(i) * k);
+ ticks.push(pow(i));
+ } else {
+ ticks.push(pow(i));
+ for (;i++ < j; ) for (var k = n - 1; k > 0; k--) ticks.push(pow(i) * k);
+ var g = d3.select(this).style("pointer-events", "all").style("-webkit-tap-highlight-color", "rgba(0,0,0,0)").on("mousedown.brush", brushstart).on("touchstart.brush", brushstart);
+ var background = g.selectAll(".background").data([ 0 ]);
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
-
-"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
-
-"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
-
-"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
-
-"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
-
-"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
-
-"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
-
-"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
-
-"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
-
-"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
-
- 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
-
- 2. You must cause any modified files to carry prominent notices stating that You changed the files; and
-
- 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
-
- 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
-
-You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
-
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
+
+ 1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
+
+ 2. You must cause any modified files to carry prominent notices stating that You changed the files; and
+
+ 3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
+
+ 4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
+
9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
-env.extConsole=null;}}},init:function(_css){var iconTitle="Click here or press F12, (CTRL|CMD)+SHIFT+L or SHIFT+ENTER to show Firebug Lite. CTRL|CMD click this icon to hide it.";with(firebug){if(document.getElementsByTagName('html')[0].attributes.getNamedItem('debug')){env.debug=document.getElementsByTagName('html')[0].attributes.getNamedItem('debug').nodeValue!=="false";}
-values+='height:'+(parseInt(targetWindow.firebug.el.main.element.style.height.replace(/px/,''),10)-38);exdate=new Date();exdate.setDate(exdate.getDate()+365);targetWindow.document.cookie='FBLiteSettings='+values+';expires='+exdate.toGMTString();}},refreshForm:function(){var fe=firebug.env,elSet=firebug.el.settings;elSet.cbxDebug.element.checked=fe.debug;elSet.cbxDetectFirebug.element.checked=fe.detectFirebug;elSet.cbxHideDOMFunctions.element.checked=fe.hideDOMFunctions;elSet.cbxOverride.element.checked=fe.override;elSet.cbxShowIcon.element.checked=fe.showIconWhenHidden;elSet.cbxOpenInPopup.element.checked=fe.openInPopup;}},win:{hide:function(){with(firebug){el.main.environment.addStyle({"display":"none"});el.mainiframe.environment.addStyle({"display":"none"});if(env.showIconWhenHidden){el.firebugIcon.environment.addStyle({"display":"block"});}}},show:function(){with(firebug){el.main.environment.addStyle({"display":"block"});el.mainiframe.environment.addStyle({"display":"block"});if(env.showIconWhenHidden){el.firebugIcon.environment.addStyle({"display":"none"});}}},iconClicked:function(_event){with(firebug){if(_event.ctrlKey==true||_event.metaKey==true){el.firebugIcon.environment.addStyle({"display":"none"});env.showIconWhenHidden=false;}else{win.show();}}},minimize:function(){with(firebug){env.minimized=true;el.main.environment.addStyle({"height":"35px"});el.mainiframe.environment.addStyle({"height":"35px"});el.button.maximize.environment.addStyle({"display":"block"});el.button.minimize.environment.addStyle({"display":"none"});win.refreshSize();}},maximize:function(){with(firebug){env.minimized=false;el.button.minimize.environment.addStyle({"display":"block"});el.button.maximize.environment.addStyle({"display":"none"});win.setHeight(env.height);}},newWindow:function(){var interval,scripts,script,scriptPath,fe=firebug.env;if(!fe.popupWin){scripts=document.getElementsByTagName('script');fe.popupWin=window.open("","_firebug","status=0,menubar=0,resizable=1,top="+fe.popupTop+",left="+fe.popupLeft+",width="+fe.popupWidth+",height="+fe.popupHeight+",scrollbars=0,addressbar=0,outerWidth="+fe.popupWidth+",outerHeight="+fe.popupHeight+"toolbar=0,location=0,directories=0,dialog=0");if(!fe.popupWin){alert("Firebug Lite could not open a pop-up window, most likely because of a popup blocker.\nPlease enable popups for this domain");}else{firebug.settings.hide();for(i=0,len=scripts.length;i<len;i++){if(scripts[i].src.indexOf(fe.liteFilename)>-1){scriptPath=scripts[i].src;break;}}
-if(scriptPath){script=fe.popupWin.document.createElement('script'),done=false;script.type='text/javascript';script.src=scriptPath;script[firebug.lib.env.ie?"onreadystatechange":"onload"]=function(){if(!done&&(!firebug.lib.env.ie||this.readyState=="complete"||this.readyState=="loaded")){done=true;if(fe.popupWin.firebug){with(fe.popupWin.firebug){env.isPopup=true;env.css=fe.css;init();el.button.dock.environment.addStyle({"display":"block"});el.button.newWindow.environment.addStyle({"display":"none"});}}}};if(!done&&firebug.lib.env.webkit){fe.popupWin.document.write('<html><head></head><body></body></html>');interval=setInterval(function(){if(fe.popupWin.firebug){clearInterval(interval);done=true;with(fe.popupWin.firebug){env.isPopup=true;env.css=fe.css;init();el.button.dock.environment.addStyle({"display":"block"});el.button.newWindow.environment.addStyle({"display":"none"});}}},10);};if(!done){fe.popupWin.document.getElementsByTagName('head')[0].appendChild(script);firebug.el.main.environment.addStyle({"display":"none"});firebug.el.mainiframe.environment.addStyle({"display":"none"});}}else{alert("Unable to detect the following script \""+fe.liteFilename+"\" ... if the script has been renamed then please set the value of firebug.env.liteFilename to reflect this change");fe.popupWin.close();fe.popupWin=null;}}}},dock:function(){with(opener.firebug){env.popupWin=null;el.main.environment.addStyle({"display":"block"});el.mainiframe.environment.addStyle({"display":"block"});settings.readCookie();window.close();};},unload:function(){with(firebug){if(env.isPopup){win.dock();}else if(env.popupWin){env.popupWin.close();}}},fitToPopup:function(){with(firebug){var viewport=lib.util.GetViewport(window);win.setHeight((window.innerHeight||viewport.height)-38);el.main.environment.addStyle({"width":(viewport.width)+"px"});el.mainiframe.environment.addStyle({"width":(viewport.width)+"px"});}},resizer:{y:[],enabled:false,start:function(_event){with(firebug){if(env.minimized)return;win.resizer.y=[el.main.element.offsetHeight,_event.clientY];if(lib.env.ie6){win.resizer.y[3]=parseInt(el.main.environment.getPosition().top);}
-d.console.countMap[_name]=0;d.console.countMap[_name]++;d.console.cmd.log.apply(window,[_name,d.console.countMap[_name]]);}},group:function(){with(firebug){d.console.cmd.log.apply(this,["console.group is not supported"]);}},groupEnd:function(){with(firebug){d.console.cmd.log.apply(this,["console.groupEnd is not supported"]);}},profile:function(){with(firebug){d.console.cmd.log.apply(this,["console.profile is not supported"]);}},profileEnd:function(){with(firebug){d.console.cmd.log.apply(this,["console.profileEnd is not supported"]);}}}},css:{index:-1,open:function(_index){with(firebug){var item=env.targetWindow.document.styleSheets[_index],uri=item.href;try{var rules=item[lib.env.ie?"rules":"cssRules"],str="";for(var i=0;i<rules.length;i++){var item=rules[i];var selector=item.selectorText;var cssText=lib.env.ie?item.style.cssText:item.cssText.match(/\{(.*)\}/)[1];str+=d.css.printRule(selector,cssText.split(";"),el.left.css.container);}}catch(e){str="<em>Access to restricted URI denied</em>";}
-_branch[name]={};this.createAccessors(_p[name],_branch[name]);}};};this.movePrivateMembers=function(_object,_branch){for(var name in _object){var isPrivate=name.substring(0,1)=="_";if(isPrivate){_branch[name]=_object[name];delete _object[name];}
+env.extConsole=null;}}},init:function(_css){var iconTitle="Click here or press F12, (CTRL|CMD)+SHIFT+L or SHIFT+ENTER to show Firebug Lite. CTRL|CMD click this icon to hide it.";with(firebug){if(document.getElementsByTagName('html')[0].attributes.getNamedItem('debug')){env.debug=document.getElementsByTagName('html')[0].attributes.getNamedItem('debug').nodeValue!=="false";}
+values+='height:'+(parseInt(targetWindow.firebug.el.main.element.style.height.replace(/px/,''),10)-38);exdate=new Date();exdate.setDate(exdate.getDate()+365);targetWindow.document.cookie='FBLiteSettings='+values+';expires='+exdate.toGMTString();}},refreshForm:function(){var fe=firebug.env,elSet=firebug.el.settings;elSet.cbxDebug.element.checked=fe.debug;elSet.cbxDetectFirebug.element.checked=fe.detectFirebug;elSet.cbxHideDOMFunctions.element.checked=fe.hideDOMFunctions;elSet.cbxOverride.element.checked=fe.override;elSet.cbxShowIcon.element.checked=fe.showIconWhenHidden;elSet.cbxOpenInPopup.element.checked=fe.openInPopup;}},win:{hide:function(){with(firebug){el.main.environment.addStyle({"display":"none"});el.mainiframe.environment.addStyle({"display":"none"});if(env.showIconWhenHidden){el.firebugIcon.environment.addStyle({"display":"block"});}}},show:function(){with(firebug){el.main.environment.addStyle({"display":"block"});el.mainiframe.environment.addStyle({"display":"block"});if(env.showIconWhenHidden){el.firebugIcon.environment.addStyle({"display":"none"});}}},iconClicked:function(_event){with(firebug){if(_event.ctrlKey==true||_event.metaKey==true){el.firebugIcon.environment.addStyle({"display":"none"});env.showIconWhenHidden=false;}else{win.show();}}},minimize:function(){with(firebug){env.minimized=true;el.main.environment.addStyle({"height":"35px"});el.mainiframe.environment.addStyle({"height":"35px"});el.button.maximize.environment.addStyle({"display":"block"});el.button.minimize.environment.addStyle({"display":"none"});win.refreshSize();}},maximize:function(){with(firebug){env.minimized=false;el.button.minimize.environment.addStyle({"display":"block"});el.button.maximize.environment.addStyle({"display":"none"});win.setHeight(env.height);}},newWindow:function(){var interval,scripts,script,scriptPath,fe=firebug.env;if(!fe.popupWin){scripts=document.getElementsByTagName('script');fe.popupWin=window.open("","_firebug","status=0,menubar=0,resizable=1,top="+fe.popupTop+",left="+fe.popupLeft+",width="+fe.popupWidth+",height="+fe.popupHeight+",scrollbars=0,addressbar=0,outerWidth="+fe.popupWidth+",outerHeight="+fe.popupHeight+"toolbar=0,location=0,directories=0,dialog=0");if(!fe.popupWin){alert("Firebug Lite could not open a pop-up window, most likely because of a popup blocker.\nPlease enable popups for this domain");}else{firebug.settings.hide();for(i=0,len=scripts.length;i<len;i++){if(scripts[i].src.indexOf(fe.liteFilename)>-1){scriptPath=scripts[i].src;break;}}
+if(scriptPath){script=fe.popupWin.document.createElement('script'),done=false;script.type='text/javascript';script.src=scriptPath;script[firebug.lib.env.ie?"onreadystatechange":"onload"]=function(){if(!done&&(!firebug.lib.env.ie||this.readyState=="complete"||this.readyState=="loaded")){done=true;if(fe.popupWin.firebug){with(fe.popupWin.firebug){env.isPopup=true;env.css=fe.css;init();el.button.dock.environment.addStyle({"display":"block"});el.button.newWindow.environment.addStyle({"display":"none"});}}}};if(!done&&firebug.lib.env.webkit){fe.popupWin.document.write('<html><head></head><body></body></html>');interval=setInterval(function(){if(fe.popupWin.firebug){clearInterval(interval);done=true;with(fe.popupWin.firebug){env.isPopup=true;env.css=fe.css;init();el.button.dock.environment.addStyle({"display":"block"});el.button.newWindow.environment.addStyle({"display":"none"});}}},10);};if(!done){fe.popupWin.document.getElementsByTagName('head')[0].appendChild(script);firebug.el.main.environment.addStyle({"display":"none"});firebug.el.mainiframe.environment.addStyle({"display":"none"});}}else{alert("Unable to detect the following script \""+fe.liteFilename+"\" ... if the script has been renamed then please set the value of firebug.env.liteFilename to reflect this change");fe.popupWin.close();fe.popupWin=null;}}}},dock:function(){with(opener.firebug){env.popupWin=null;el.main.environment.addStyle({"display":"block"});el.mainiframe.environment.addStyle({"display":"block"});settings.readCookie();window.close();};},unload:function(){with(firebug){if(env.isPopup){win.dock();}else if(env.popupWin){env.popupWin.close();}}},fitToPopup:function(){with(firebug){var viewport=lib.util.GetViewport(window);win.setHeight((window.innerHeight||viewport.height)-38);el.main.environment.addStyle({"width":(viewport.width)+"px"});el.mainiframe.environment.addStyle({"width":(viewport.width)+"px"});}},resizer:{y:[],enabled:false,start:function(_event){with(firebug){if(env.minimized)return;win.resizer.y=[el.main.element.offsetHeight,_event.clientY];if(lib.env.ie6){win.resizer.y[3]=parseInt(el.main.environment.getPosition().top);}
+d.console.countMap[_name]=0;d.console.countMap[_name]++;d.console.cmd.log.apply(window,[_name,d.console.countMap[_name]]);}},group:function(){with(firebug){d.console.cmd.log.apply(this,["console.group is not supported"]);}},groupEnd:function(){with(firebug){d.console.cmd.log.apply(this,["console.groupEnd is not supported"]);}},profile:function(){with(firebug){d.console.cmd.log.apply(this,["console.profile is not supported"]);}},profileEnd:function(){with(firebug){d.console.cmd.log.apply(this,["console.profileEnd is not supported"]);}}}},css:{index:-1,open:function(_index){with(firebug){var item=env.targetWindow.document.styleSheets[_index],uri=item.href;try{var rules=item[lib.env.ie?"rules":"cssRules"],str="";for(var i=0;i<rules.length;i++){var item=rules[i];var selector=item.selectorText;var cssText=lib.env.ie?item.style.cssText:item.cssText.match(/\{(.*)\}/)[1];str+=d.css.printRule(selector,cssText.split(";"),el.left.css.container);}}catch(e){str="<em>Access to restricted URI denied</em>";}
+_branch[name]={};this.createAccessors(_p[name],_branch[name]);}};};this.movePrivateMembers=function(_object,_branch){for(var name in _object){var isPrivate=name.substring(0,1)=="_";if(isPrivate){_branch[name]=_object[name];delete _object[name];}
- new lib.element("link").attribute.set("rel","stylesheet").attribute.set("type","text/css").attribute.set("href",env.css).element
- );
-
- if(env.override){
- overrideConsole();
- }
-
- /*
- * Firebug Icon
- */
- el.firebugIcon = new lib.element("div").attribute.set("id","firebugIconDiv").attribute.set("title",iconTitle).attribute.set("alt",iconTitle).event.addListener("mousedown",win.iconClicked).insert(document.body);
-
- /*
- * main interface
- */
- el.content = {};
- el.mainiframe = new lib.element("IFRAME").attribute.set("id","FirebugIFrame").environment.addStyle({ "display":"none", "width":lib.util.GetViewport().width+"px" }).insert(document.body);
- el.main = new lib.element("DIV").attribute.set("id","Firebug").environment.addStyle({ "display":"none", "width":lib.util.GetViewport().width+"px" }).insert(document.body);
- if(!env.isPopup){
- el.resizer = new lib.element("DIV").attribute.addClass("Resizer").event.addListener("mousedown",win.resizer.start).insert(el.main);
- }
- el.header = new lib.element("DIV").attribute.addClass("Header").insert(el.main);
- el.left = {};
- el.left.container = new lib.element("DIV").attribute.addClass("Left").insert(el.main);
- el.right = {};
- el.right.container = new lib.element("DIV").attribute.addClass("Right").insert(el.main);
- el.button.container = new lib.element("DIV").attribute.addClass("ButtonContainer").insert(el.header);
- el.button.logo = new lib.element("A").attribute.set("title","Firebug Lite").attribute.set("target","_blank").attribute.set("href","http://getfirebug.com/lite.html").update(" ").attribute.addClass("Button Logo").insert(el.button.container);
- el.button.inspect = new lib.element("A").attribute.addClass("Button").event.addListener("click",env.targetWindow.firebug.d.inspector.toggle).update("Inspect").insert(el.button.container);
- el.button.dock = new lib.element("A").attribute.addClass("Button Dock").event.addListener("click", win.dock).insert(el.button.container);
- el.button.newWindow = new lib.element("A").attribute.addClass("Button NewWindow").event.addListener("click", win.newWindow).insert(el.button.container);
-
- if(!env.isPopup){
- el.button.maximize = new lib.element("A").attribute.addClass("Button Maximize").event.addListener("click",win.maximize).insert(el.button.container);
- el.button.minimize = new lib.element("A").attribute.addClass("Button Minimize").event.addListener("click",win.minimize).insert(el.button.container);
- el.button.close = new lib.element("A").attribute.addClass("Button Close").event.addListener("click",win.hide).insert(el.button.container);
- el.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.left.container);
- el.nav.console = new lib.element("A").attribute.addClass("Tab Selected").event.addListener("click",lib.util.Curry(d.navigate,window,"console")).update("Console").insert(el.nav.container);
- el.nav.html = new lib.element("A").attribute.addClass("Tab").update("HTML").event.addListener("click",lib.util.Curry(d.navigate,window,"html")).insert(el.nav.container);
- el.nav.css = new lib.element("A").attribute.addClass("Tab").update("CSS").event.addListener("click",lib.util.Curry(d.navigate,window,"css")).insert(el.nav.container);
- if(!env.isPopup){
- el.nav.scripts = new lib.element("A").attribute.addClass("Tab").update("Script").event.addListener("click",lib.util.Curry(d.navigate,window,"scripts")).insert(el.nav.container);
- }
- el.nav.dom = new lib.element("A").attribute.addClass("Tab").update("DOM").event.addListener("click",lib.util.Curry(d.navigate,env.targetWindow,"dom")).insert(el.nav.container);
- el.nav.xhr = new lib.element("A").attribute.addClass("Tab").update("XHR").event.addListener("click",lib.util.Curry(d.navigate,window,"xhr")).insert(el.nav.container);
- el.nav.optionsdiv = new lib.element("DIV").attribute.addClass("Settings").insert(el.nav.container);
- el.nav.options = new lib.element("A").attribute.addClass("Tab").update("Options ∨").event.addListener("click", settings.toggle).insert(el.nav.optionsdiv);
-
- /*
- * inspector
- */
- el.borderInspector = new lib.element("DIV").attribute.set("id","FirebugBorderInspector").event.addListener("click",listen.inspector).insert(document.body);
- el.bgInspector = new lib.element("DIV").attribute.set("id","FirebugBGInspector").insert(document.body);
-
- /*
- * console
- */
- el.left.console = {};
- el.left.console.container = new lib.element("DIV").attribute.addClass("Console").insert(el.left.container);
- el.left.console.mlButton = new lib.element("A").attribute.addClass("MLButton").event.addListener("click",d.console.toggleML).insert(el.left.console.container);
- el.left.console.monitor = new lib.element("DIV").insert(
- new lib.element("DIV").attribute.addClass("Monitor").insert(el.left.console.container)
- );
- el.left.console.container.child.add(
- new lib.element("DIV").attribute.addClass("InputArrow").update(">>>")
- );
- el.left.console.input = new lib.element("INPUT").attribute.set("type","text").attribute.addClass("Input").event.addListener("keydown",listen.consoleTextbox).insert(
- new lib.element("DIV").attribute.addClass("InputContainer").insert(el.left.console.container)
- );
-
- el.right.console = {};
- el.right.console.container = new lib.element("DIV").attribute.addClass("Console Container").insert(el.right.container);
- el.right.console.mlButton = new lib.element("A").attribute.addClass("MLButton CloseML").event.addListener("click",d.console.toggleML).insert(el.right.console.container);
- el.right.console.input = new lib.element("TEXTAREA").attribute.addClass("Input").insert(el.right.console.container);
- el.right.console.run = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.runMultiline).update("Run").insert(el.right.console.container);
- el.right.console.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.clean,window,el.right.console.input)).update("Clear").insert(el.right.console.container);
-
- el.button.console = {};
- el.button.console.container = new lib.element("DIV").attribute.addClass("ButtonSet").insert(el.button.container);
- el.button.console.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",d.console.clear).update("Clear").insert(el.button.console.container);
-
- /*
- * html
- */
-
- el.left.html = {};
- el.left.html.container = new lib.element("DIV").attribute.addClass("HTML").insert(el.left.container);
-
- el.right.html = {};
- el.right.html.container = new lib.element("DIV").attribute.addClass("HTML Container").insert(el.right.container);
-
- el.right.html.nav = {};
- el.right.html.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.right.html.container);
- el.right.html.nav.computedStyle = new lib.element("A").attribute.addClass("Tab Selected").event.addListener("click",lib.util.Curry(d.html.navigate,firebug,"computedStyle")).update("Computed Style").insert(el.right.html.nav.container);
- el.right.html.nav.dom = new lib.element("A").attribute.addClass("Tab").event.addListener("click",lib.util.Curry(d.html.navigate,firebug,"dom")).update("DOM").insert(el.right.html.nav.container);
-
- el.right.html.content = new lib.element("DIV").attribute.addClass("Content").insert(el.right.html.container);
-
- el.button.html = {};
- el.button.html.container = new lib.element("DIV").attribute.addClass("ButtonSet HTML").insert(el.button.container);
-
- /*
- * css
- */
-
- el.left.css = {};
- el.left.css.container = new lib.element("DIV").attribute.addClass("CSS").insert(el.left.container);
-
- el.right.css = {};
- el.right.css.container = new lib.element("DIV").attribute.addClass("CSS Container").insert(el.right.container);
-
- el.right.css.nav = {};
- el.right.css.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.right.css.container);
- el.right.css.nav.runCSS = new lib.element("A").attribute.addClass("Tab Selected").update("Run CSS").insert(el.right.css.nav.container);
-
- el.right.css.mlButton = new lib.element("A").attribute.addClass("MLButton CloseML").event.addListener("click",d.console.toggleML).insert(el.right.css.container);
- el.right.css.input = new lib.element("TEXTAREA").attribute.addClass("Input").insert(el.right.css.container);
- el.right.css.run = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.runCSS).update("Run").insert(el.right.css.container);
- el.right.css.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.clean,window,el.right.css.input)).update("Clear").insert(el.right.css.container);
-
- el.button.css = {};
- el.button.css.container = new lib.element("DIV").attribute.addClass("ButtonSet CSS").insert(el.button.container);
- el.button.css.selectbox = new lib.element("SELECT").event.addListener("change",listen.cssSelectbox).insert(el.button.css.container);
-
- /*
- * scripts
- */
-
- el.left.scripts = {};
- el.left.scripts.container = new lib.element("DIV").attribute.addClass("Scripts").insert(el.left.container);
-
- el.right.scripts = {};
- el.right.scripts.container = new lib.element("DIV").attribute.addClass("Scripts Container").insert(el.right.container);
-
- el.button.scripts = {};
- el.button.scripts.container = new lib.element("DIV").attribute.addClass("ButtonSet Scripts").insert(el.button.container);
- el.button.scripts.selectbox = new lib.element("SELECT").event.addListener("change",listen.scriptsSelectbox).insert(el.button.scripts.container);
- el.button.scripts.lineNumbers = new lib.element("A").attribute.addClass("Button").event.addListener("click",d.scripts.toggleLineNumbers).update("Show Line Numbers").insert(el.button.scripts.container);
-
- /*
- * dom
- */
-
- el.left.dom = {};
- el.left.dom.container = new lib.element("DIV").attribute.addClass("DOM").insert(el.left.container);
-
- el.right.dom = {};
- el.right.dom.container = new lib.element("DIV").attribute.addClass("DOM Container").insert(el.right.container);
-
- el.button.dom = {};
- el.button.dom.container = new lib.element("DIV").attribute.addClass("ButtonSet DOM").insert(el.button.container);
- el.button.dom.label = new lib.element("LABEL").update("Object Path:").insert(el.button.dom.container);
- el.button.dom.textbox = new lib.element("INPUT").event.addListener("keydown",listen.domTextbox).update(env.isPopup?"window.opener":"window").insert(el.button.dom.container);
-
- /*
- * str
- */
- el.left.str = {};
- el.left.str.container = new lib.element("DIV").attribute.addClass("STR").insert(el.left.container);
-
- el.right.str = {};
- el.right.str.container = new lib.element("DIV").attribute.addClass("STR").insert(el.left.container);
-
- el.button.str = {};
- el.button.str.container = new lib.element("DIV").attribute.addClass("ButtonSet XHR").insert(el.button.container);
- el.button.str.watch = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.navigate,window,"xhr")).update("Back").insert(el.button.str.container);
-
- /*
- * xhr
- */
- el.left.xhr = {};
- el.left.xhr.container = new lib.element("DIV").attribute.addClass("XHR").insert(el.left.container);
-
- el.right.xhr = {};
- el.right.xhr.container = new lib.element("DIV").attribute.addClass("XHR").insert(el.left.container);
-
-
- el.button.xhr = {};
- el.button.xhr.container = new lib.element("DIV").attribute.addClass("ButtonSet XHR").insert(el.button.container);
- el.button.xhr.label = new lib.element("LABEL").update("XHR Path:").insert(el.button.xhr.container);
- el.button.xhr.textbox = new lib.element("INPUT").event.addListener("keydown",listen.xhrTextbox).insert(el.button.xhr.container);
- el.button.xhr.watch = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.addXhrObject).update("Watch").insert(el.button.xhr.container);
-
- /*
- * settings
- */
- el.settings = {};
- el.settings.container = new lib.element("DIV").child.add(
- new lib.element("DIV").attribute.addClass("Header").child.add(
- new lib.element().attribute.addClass("Title").update('Firebug Lite Settings')
- new lib.element("BR").insert(el.settings.content);
- el.settings.cbxDetectFirebug = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
- el.settings.content.child.add(document.createTextNode("Hide when Firebug active"));
- new lib.element("BR").insert(el.settings.content);
- el.settings.cbxHideDOMFunctions = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
- el.settings.content.child.add(document.createTextNode("Hide DOM functions"));
- new lib.element("BR").insert(el.settings.content);
- el.settings.cbxOverride = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
- new lib.element("BR").insert(el.settings.content);
- el.settings.cbxShowIcon = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
- el.settings.content.child.add(document.createTextNode("Show icon when hidden"));
- new lib.element("BR").insert(el.settings.content);
- el.settings.cbxOpenInPopup = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
- el.settings.content.child.add(document.createTextNode("Open in popup"));
- el.settings.buttonDiv = new lib.element("DIV").insert(el.settings.content);
- el.settings.buttonLeftDiv = new lib.element("DIV").attribute.addClass("ButtonsLeft").insert(el.settings.buttonDiv);
- el.settings.resetButton = new lib.element("INPUT").attribute.set("type","button").update("Reset").event.addListener("click",settings.reset).insert(el.settings.buttonLeftDiv);
- el.settings.buttonRightDiv = new lib.element("DIV").attribute.addClass("ButtonsRight").insert(el.settings.buttonDiv);
- el.settings.cancelButton = new lib.element("INPUT").attribute.set("type","button").update("Cancel").event.addListener("click",settings.hide).insert(el.settings.buttonRightDiv);
- el.settings.saveButton = new lib.element("INPUT").attribute.set("type","button").update("Save").event.addListener("click",settings.saveClicked).insert(el.settings.buttonRightDiv);
- if (env.hideDOMFunctions && typeof(obj[key]) == "function") continue;
- var value = obj[key], property = key, container = new lib.element("DIV").attribute.addClass("DOMRow").insert(parentElement),
- left = new lib.element("DIV").attribute.addClass("DOMRowLeft").insert(container), right = new lib.element("DIV").attribute.addClass("DOMRowRight").insert(container);
-
- container.child.add(
- new lib.element("DIV").attribute.addClass('Clear')
- );
-
- var link = new lib.element("A").attribute.addClass(
- new lib.element("A").attribute.addClass("Block").update("<span class='DarkBlue'><<span class='Blue'>html</span>>").insert(parent);
- };
-
- for(var i=0; i<=len; i++){
- if(i==len){
- new lib.element("A").attribute.addClass("Block").update("<span class='DarkBlue'></<span class='Blue'>"+element.nodeName.toLowerCase()+"</span>>").insert(container);
- break;
- }
- var item = element.childNodes[i];
-
- if (item.nodeType != 3){
- var container = new lib.element().attribute.addClass("Block").insert(parent),
- link = new lib.element("A").attribute.addClass("Link").insert(container),
- spacer = new lib.element("SPAN").attribute.addClass("Spacer").update(" ").insert(link),
- html = new lib.element("SPAN").attribute.addClass("Content").update(d.highlight(item)).insert(link),
- subContainer = new lib.element("DIV").attribute.addClass("SubContainer").insert(container),
- var property = ["opacity","filter","azimuth","background","backgroundAttachment","backgroundColor","backgroundImage","backgroundPosition","backgroundRepeat","border","borderCollapse","borderColor","borderSpacing","borderStyle","borderTop","borderRight","borderBottom","borderLeft","borderTopColor","borderRightColor","borderBottomColor","borderLeftColor","borderTopStyle","borderRightStyle","borderBottomStyle","borderLeftStyle","borderTopWidth","borderRightWidth","borderBottomWidth","borderLeftWidth","borderWidth","bottom","captionSide","clear","clip","color","content","counterIncrement","counterReset","cue","cueAfter","cueBefore","cursor","direction","display","elevation","emptyCells","cssFloat","font","fontFamily","fontSize","fontSizeAdjust","fontStretch","fontStyle","fontVariant","fontWeight","height","left","letterSpacing","lineHeight","listStyle","listStyleImage","listStylePosition","listStyleType","margin","marginTop","marginRight","marginBottom","marginLeft","markerOffset","marks","maxHeight","maxWidth","minHeight","minWidth","orphans","outline","outlineColor","outlineStyle","outlineWidth","overflow","padding","paddingTop","paddingRight","paddingBottom","paddingLeft","page","pageBreakAfter","pageBreakBefore","pageBreakInside","pause","pauseAfter","pauseBefore","pitch","pitchRange","playDuring","position","quotes","richness","right","size","speak","speakHeader","speakNumeral","speakPunctuation","speechRate","stress","tableLayout","textAlign","textDecoration","textIndent","textShadow","textTransform","top","unicodeBidi","verticalAlign","visibility","voiceFamily","volume","whiteSpace","widows","width","wordSpacing","zIndex"].sort();
- var view = document.defaultView?document.defaultView.getComputedStyle(node,null):node.currentStyle;
+ new lib.element("link").attribute.set("rel","stylesheet").attribute.set("type","text/css").attribute.set("href",env.css).element
+ );
+
+ if(env.override){
+ overrideConsole();
+ }
+
+ /*
+ * Firebug Icon
+ */
+ el.firebugIcon = new lib.element("div").attribute.set("id","firebugIconDiv").attribute.set("title",iconTitle).attribute.set("alt",iconTitle).event.addListener("mousedown",win.iconClicked).insert(document.body);
+
+ /*
+ * main interface
+ */
+ el.content = {};
+ el.mainiframe = new lib.element("IFRAME").attribute.set("id","FirebugIFrame").environment.addStyle({ "display":"none", "width":lib.util.GetViewport().width+"px" }).insert(document.body);
+ el.main = new lib.element("DIV").attribute.set("id","Firebug").environment.addStyle({ "display":"none", "width":lib.util.GetViewport().width+"px" }).insert(document.body);
+ if(!env.isPopup){
+ el.resizer = new lib.element("DIV").attribute.addClass("Resizer").event.addListener("mousedown",win.resizer.start).insert(el.main);
+ }
+ el.header = new lib.element("DIV").attribute.addClass("Header").insert(el.main);
+ el.left = {};
+ el.left.container = new lib.element("DIV").attribute.addClass("Left").insert(el.main);
+ el.right = {};
+ el.right.container = new lib.element("DIV").attribute.addClass("Right").insert(el.main);
+ el.button.container = new lib.element("DIV").attribute.addClass("ButtonContainer").insert(el.header);
+ el.button.logo = new lib.element("A").attribute.set("title","Firebug Lite").attribute.set("target","_blank").attribute.set("href","http://getfirebug.com/lite.html").update(" ").attribute.addClass("Button Logo").insert(el.button.container);
+ el.button.inspect = new lib.element("A").attribute.addClass("Button").event.addListener("click",env.targetWindow.firebug.d.inspector.toggle).update("Inspect").insert(el.button.container);
+ el.button.dock = new lib.element("A").attribute.addClass("Button Dock").event.addListener("click", win.dock).insert(el.button.container);
+ el.button.newWindow = new lib.element("A").attribute.addClass("Button NewWindow").event.addListener("click", win.newWindow).insert(el.button.container);
+
+ if(!env.isPopup){
+ el.button.maximize = new lib.element("A").attribute.addClass("Button Maximize").event.addListener("click",win.maximize).insert(el.button.container);
+ el.button.minimize = new lib.element("A").attribute.addClass("Button Minimize").event.addListener("click",win.minimize).insert(el.button.container);
+ el.button.close = new lib.element("A").attribute.addClass("Button Close").event.addListener("click",win.hide).insert(el.button.container);
+ el.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.left.container);
+ el.nav.console = new lib.element("A").attribute.addClass("Tab Selected").event.addListener("click",lib.util.Curry(d.navigate,window,"console")).update("Console").insert(el.nav.container);
+ el.nav.html = new lib.element("A").attribute.addClass("Tab").update("HTML").event.addListener("click",lib.util.Curry(d.navigate,window,"html")).insert(el.nav.container);
+ el.nav.css = new lib.element("A").attribute.addClass("Tab").update("CSS").event.addListener("click",lib.util.Curry(d.navigate,window,"css")).insert(el.nav.container);
+ if(!env.isPopup){
+ el.nav.scripts = new lib.element("A").attribute.addClass("Tab").update("Script").event.addListener("click",lib.util.Curry(d.navigate,window,"scripts")).insert(el.nav.container);
+ }
+ el.nav.dom = new lib.element("A").attribute.addClass("Tab").update("DOM").event.addListener("click",lib.util.Curry(d.navigate,env.targetWindow,"dom")).insert(el.nav.container);
+ el.nav.xhr = new lib.element("A").attribute.addClass("Tab").update("XHR").event.addListener("click",lib.util.Curry(d.navigate,window,"xhr")).insert(el.nav.container);
+ el.nav.optionsdiv = new lib.element("DIV").attribute.addClass("Settings").insert(el.nav.container);
+ el.nav.options = new lib.element("A").attribute.addClass("Tab").update("Options ∨").event.addListener("click", settings.toggle).insert(el.nav.optionsdiv);
+
+ /*
+ * inspector
+ */
+ el.borderInspector = new lib.element("DIV").attribute.set("id","FirebugBorderInspector").event.addListener("click",listen.inspector).insert(document.body);
+ el.bgInspector = new lib.element("DIV").attribute.set("id","FirebugBGInspector").insert(document.body);
+
+ /*
+ * console
+ */
+ el.left.console = {};
+ el.left.console.container = new lib.element("DIV").attribute.addClass("Console").insert(el.left.container);
+ el.left.console.mlButton = new lib.element("A").attribute.addClass("MLButton").event.addListener("click",d.console.toggleML).insert(el.left.console.container);
+ el.left.console.monitor = new lib.element("DIV").insert(
+ new lib.element("DIV").attribute.addClass("Monitor").insert(el.left.console.container)
+ );
+ el.left.console.container.child.add(
+ new lib.element("DIV").attribute.addClass("InputArrow").update(">>>")
+ );
+ el.left.console.input = new lib.element("INPUT").attribute.set("type","text").attribute.addClass("Input").event.addListener("keydown",listen.consoleTextbox).insert(
+ new lib.element("DIV").attribute.addClass("InputContainer").insert(el.left.console.container)
+ );
+
+ el.right.console = {};
+ el.right.console.container = new lib.element("DIV").attribute.addClass("Console Container").insert(el.right.container);
+ el.right.console.mlButton = new lib.element("A").attribute.addClass("MLButton CloseML").event.addListener("click",d.console.toggleML).insert(el.right.console.container);
+ el.right.console.input = new lib.element("TEXTAREA").attribute.addClass("Input").insert(el.right.console.container);
+ el.right.console.run = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.runMultiline).update("Run").insert(el.right.console.container);
+ el.right.console.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.clean,window,el.right.console.input)).update("Clear").insert(el.right.console.container);
+
+ el.button.console = {};
+ el.button.console.container = new lib.element("DIV").attribute.addClass("ButtonSet").insert(el.button.container);
+ el.button.console.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",d.console.clear).update("Clear").insert(el.button.console.container);
+
+ /*
+ * html
+ */
+
+ el.left.html = {};
+ el.left.html.container = new lib.element("DIV").attribute.addClass("HTML").insert(el.left.container);
+
+ el.right.html = {};
+ el.right.html.container = new lib.element("DIV").attribute.addClass("HTML Container").insert(el.right.container);
+
+ el.right.html.nav = {};
+ el.right.html.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.right.html.container);
+ el.right.html.nav.computedStyle = new lib.element("A").attribute.addClass("Tab Selected").event.addListener("click",lib.util.Curry(d.html.navigate,firebug,"computedStyle")).update("Computed Style").insert(el.right.html.nav.container);
+ el.right.html.nav.dom = new lib.element("A").attribute.addClass("Tab").event.addListener("click",lib.util.Curry(d.html.navigate,firebug,"dom")).update("DOM").insert(el.right.html.nav.container);
+
+ el.right.html.content = new lib.element("DIV").attribute.addClass("Content").insert(el.right.html.container);
+
+ el.button.html = {};
+ el.button.html.container = new lib.element("DIV").attribute.addClass("ButtonSet HTML").insert(el.button.container);
+
+ /*
+ * css
+ */
+
+ el.left.css = {};
+ el.left.css.container = new lib.element("DIV").attribute.addClass("CSS").insert(el.left.container);
+
+ el.right.css = {};
+ el.right.css.container = new lib.element("DIV").attribute.addClass("CSS Container").insert(el.right.container);
+
+ el.right.css.nav = {};
+ el.right.css.nav.container = new lib.element("DIV").attribute.addClass("Nav").insert(el.right.css.container);
+ el.right.css.nav.runCSS = new lib.element("A").attribute.addClass("Tab Selected").update("Run CSS").insert(el.right.css.nav.container);
+
+ el.right.css.mlButton = new lib.element("A").attribute.addClass("MLButton CloseML").event.addListener("click",d.console.toggleML).insert(el.right.css.container);
+ el.right.css.input = new lib.element("TEXTAREA").attribute.addClass("Input").insert(el.right.css.container);
+ el.right.css.run = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.runCSS).update("Run").insert(el.right.css.container);
+ el.right.css.clear = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.clean,window,el.right.css.input)).update("Clear").insert(el.right.css.container);
+
+ el.button.css = {};
+ el.button.css.container = new lib.element("DIV").attribute.addClass("ButtonSet CSS").insert(el.button.container);
+ el.button.css.selectbox = new lib.element("SELECT").event.addListener("change",listen.cssSelectbox).insert(el.button.css.container);
+
+ /*
+ * scripts
+ */
+
+ el.left.scripts = {};
+ el.left.scripts.container = new lib.element("DIV").attribute.addClass("Scripts").insert(el.left.container);
+
+ el.right.scripts = {};
+ el.right.scripts.container = new lib.element("DIV").attribute.addClass("Scripts Container").insert(el.right.container);
+
+ el.button.scripts = {};
+ el.button.scripts.container = new lib.element("DIV").attribute.addClass("ButtonSet Scripts").insert(el.button.container);
+ el.button.scripts.selectbox = new lib.element("SELECT").event.addListener("change",listen.scriptsSelectbox).insert(el.button.scripts.container);
+ el.button.scripts.lineNumbers = new lib.element("A").attribute.addClass("Button").event.addListener("click",d.scripts.toggleLineNumbers).update("Show Line Numbers").insert(el.button.scripts.container);
+
+ /*
+ * dom
+ */
+
+ el.left.dom = {};
+ el.left.dom.container = new lib.element("DIV").attribute.addClass("DOM").insert(el.left.container);
+
+ el.right.dom = {};
+ el.right.dom.container = new lib.element("DIV").attribute.addClass("DOM Container").insert(el.right.container);
+
+ el.button.dom = {};
+ el.button.dom.container = new lib.element("DIV").attribute.addClass("ButtonSet DOM").insert(el.button.container);
+ el.button.dom.label = new lib.element("LABEL").update("Object Path:").insert(el.button.dom.container);
+ el.button.dom.textbox = new lib.element("INPUT").event.addListener("keydown",listen.domTextbox).update(env.isPopup?"window.opener":"window").insert(el.button.dom.container);
+
+ /*
+ * str
+ */
+ el.left.str = {};
+ el.left.str.container = new lib.element("DIV").attribute.addClass("STR").insert(el.left.container);
+
+ el.right.str = {};
+ el.right.str.container = new lib.element("DIV").attribute.addClass("STR").insert(el.left.container);
+
+ el.button.str = {};
+ el.button.str.container = new lib.element("DIV").attribute.addClass("ButtonSet XHR").insert(el.button.container);
+ el.button.str.watch = new lib.element("A").attribute.addClass("Button").event.addListener("click",lib.util.Curry(d.navigate,window,"xhr")).update("Back").insert(el.button.str.container);
+
+ /*
+ * xhr
+ */
+ el.left.xhr = {};
+ el.left.xhr.container = new lib.element("DIV").attribute.addClass("XHR").insert(el.left.container);
+
+ el.right.xhr = {};
+ el.right.xhr.container = new lib.element("DIV").attribute.addClass("XHR").insert(el.left.container);
+
+
+ el.button.xhr = {};
+ el.button.xhr.container = new lib.element("DIV").attribute.addClass("ButtonSet XHR").insert(el.button.container);
+ el.button.xhr.label = new lib.element("LABEL").update("XHR Path:").insert(el.button.xhr.container);
+ el.button.xhr.textbox = new lib.element("INPUT").event.addListener("keydown",listen.xhrTextbox).insert(el.button.xhr.container);
+ el.button.xhr.watch = new lib.element("A").attribute.addClass("Button").event.addListener("click",listen.addXhrObject).update("Watch").insert(el.button.xhr.container);
+
+ /*
+ * settings
+ */
+ el.settings = {};
+ el.settings.container = new lib.element("DIV").child.add(
+ new lib.element("DIV").attribute.addClass("Header").child.add(
+ new lib.element().attribute.addClass("Title").update('Firebug Lite Settings')
+ new lib.element("BR").insert(el.settings.content);
+ el.settings.cbxDetectFirebug = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
+ el.settings.content.child.add(document.createTextNode("Hide when Firebug active"));
+ new lib.element("BR").insert(el.settings.content);
+ el.settings.cbxHideDOMFunctions = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
+ el.settings.content.child.add(document.createTextNode("Hide DOM functions"));
+ new lib.element("BR").insert(el.settings.content);
+ el.settings.cbxOverride = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
+ new lib.element("BR").insert(el.settings.content);
+ el.settings.cbxShowIcon = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
+ el.settings.content.child.add(document.createTextNode("Show icon when hidden"));
+ new lib.element("BR").insert(el.settings.content);
+ el.settings.cbxOpenInPopup = new lib.element("INPUT").attribute.set("type","checkbox").attribute.addClass("SettingsCBX").insert(el.settings.content);
+ el.settings.content.child.add(document.createTextNode("Open in popup"));
+ el.settings.buttonDiv = new lib.element("DIV").insert(el.settings.content);
+ el.settings.buttonLeftDiv = new lib.element("DIV").attribute.addClass("ButtonsLeft").insert(el.settings.buttonDiv);
+ el.settings.resetButton = new lib.element("INPUT").attribute.set("type","button").update("Reset").event.addListener("click",settings.reset).insert(el.settings.buttonLeftDiv);
+ el.settings.buttonRightDiv = new lib.element("DIV").attribute.addClass("ButtonsRight").insert(el.settings.buttonDiv);
+ el.settings.cancelButton = new lib.element("INPUT").attribute.set("type","button").update("Cancel").event.addListener("click",settings.hide).insert(el.settings.buttonRightDiv);
+ el.settings.saveButton = new lib.element("INPUT").attribute.set("type","button").update("Save").event.addListener("click",settings.saveClicked).insert(el.settings.buttonRightDiv);
+ if (env.hideDOMFunctions && typeof(obj[key]) == "function") continue;
+ var value = obj[key], property = key, container = new lib.element("DIV").attribute.addClass("DOMRow").insert(parentElement),
+ left = new lib.element("DIV").attribute.addClass("DOMRowLeft").insert(container), right = new lib.element("DIV").attribute.addClass("DOMRowRight").insert(container);
+
+ container.child.add(
+ new lib.element("DIV").attribute.addClass('Clear')
+ );
+
+ var link = new lib.element("A").attribute.addClass(
+ new lib.element("A").attribute.addClass("Block").update("<span class='DarkBlue'><<span class='Blue'>html</span>>").insert(parent);
+ };
+
+ for(var i=0; i<=len; i++){
+ if(i==len){
+ new lib.element("A").attribute.addClass("Block").update("<span class='DarkBlue'></<span class='Blue'>"+element.nodeName.toLowerCase()+"</span>>").insert(container);
+ break;
+ }
+ var item = element.childNodes[i];
+
+ if (item.nodeType != 3){
+ var container = new lib.element().attribute.addClass("Block").insert(parent),
+ link = new lib.element("A").attribute.addClass("Link").insert(container),
+ spacer = new lib.element("SPAN").attribute.addClass("Spacer").update(" ").insert(link),
+ html = new lib.element("SPAN").attribute.addClass("Content").update(d.highlight(item)).insert(link),
+ subContainer = new lib.element("DIV").attribute.addClass("SubContainer").insert(container),
+ var property = ["opacity","filter","azimuth","background","backgroundAttachment","backgroundColor","backgroundImage","backgroundPosition","backgroundRepeat","border","borderCollapse","borderColor","borderSpacing","borderStyle","borderTop","borderRight","borderBottom","borderLeft","borderTopColor","borderRightColor","borderBottomColor","borderLeftColor","borderTopStyle","borderRightStyle","borderBottomStyle","borderLeftStyle","borderTopWidth","borderRightWidth","borderBottomWidth","borderLeftWidth","borderWidth","bottom","captionSide","clear","clip","color","content","counterIncrement","counterReset","cue","cueAfter","cueBefore","cursor","direction","display","elevation","emptyCells","cssFloat","font","fontFamily","fontSize","fontSizeAdjust","fontStretch","fontStyle","fontVariant","fontWeight","height","left","letterSpacing","lineHeight","listStyle","listStyleImage","listStylePosition","listStyleType","margin","marginTop","marginRight","marginBottom","marginLeft","markerOffset","marks","maxHeight","maxWidth","minHeight","minWidth","orphans","outline","outlineColor","outlineStyle","outlineWidth","overflow","padding","paddingTop","paddingRight","paddingBottom","paddingLeft","page","pageBreakAfter","pageBreakBefore","pageBreakInside","pause","pauseAfter","pauseBefore","pitch","pitchRange","playDuring","position","quotes","richness","right","size","speak","speakHeader","speakNumeral","speakPunctuation","speechRate","stress","tableLayout","textAlign","textDecoration","textIndent","textShadow","textTransform","top","unicodeBidi","verticalAlign","visibility","voiceFamily","volume","whiteSpace","widows","width","wordSpacing","zIndex"].sort();
+ var view = document.defaultView?document.defaultView.getComputedStyle(node,null):node.currentStyle;
+<body class="api jquery single single-post postid-363 single-format-standard single-author singular">
+
+<!--[if lt IE 7]>
+<p class="chromeframe">You are using an outdated browser. <a href="http://browsehappy.com/">Upgrade your browser today</a> or <a href="http://www.google.com/chromeframe/?redirect=true">install Google Chrome Frame</a> to better experience this site.</p>
+<div>A Boolean indicating whether to remove all jQuery variables from the global scope (including jQuery itself).</div>
+</li></ul>
+</li></ul>
+<div class="longdesc" id="entry-longdesc">
+ <p>Many JavaScript libraries use <code>$</code> as a function or variable name, just as jQuery does. In jQuery's case, <code>$</code> is just an alias for <code>jQuery</code>, so all functionality is available without using <code>$</code>. If you need to use another JavaScript library alongside jQuery, return control of <code>$</code> back to the other library with a call to <code>$.noConflict()</code>. Old references of <code>$</code> are saved during jQuery initialization; <code>noConflict()</code> simply restores them.</p>
+ <p>If for some reason two versions of jQuery are loaded (which is not recommended), calling <code>$.noConflict( true )</code> from the second version will return the globally scoped jQuery variables to those of the first version.</p>
+ <p>This technique is especially effective in conjunction with the <code>.ready()</code> method's ability to alias the jQuery object, as within callback passed to <code>.ready()</code> you can use <code>$</code> if you wish without fear of conflicts later:</p>
+<h4>Example: <span class="desc">Map the original object that was referenced by $ back to $.</span>
+</h4>
+<div class="syntaxhighlighter javascript ">
+ <table>
+ <tbody>
+ <tr>
+ <td class="gutter">
+
+ <div class="line n1">1</div>
+
+ <div class="line n2">2</div>
+
+ <div class="line n3">3</div>
+
+ <div class="line n4">4</div>
+
+ <div class="line n5">5</div>
+
+ </td>
+ <td class="code">
+ <pre><div class="container"><div class="line"><code>jQuery.noConflict();</code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with jQuery</span></code></div></div><div class="container"><div class="line"><code>jQuery( <span class="string">"div p"</span> ).hide();</code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with another library's $()</span></code></div></div><div class="container"><div class="line"><code>$( <span class="string">"content"</span> ).style.display = <span class="string">"none"</span>;</code></div></div></pre>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+</div>
+<div class="entry-example" id="example-1">
+<h4>Example: <span class="desc">Revert the $ alias and then create and
+execute a function to provide the $ as a jQuery alias inside the
+function's scope. Inside the function the original $ object is not
+available. This works well for most plugins that don't rely on any other
+ library.
+ </span>
+</h4>
+<div class="syntaxhighlighter javascript ">
+ <table>
+ <tbody>
+ <tr>
+ <td class="gutter">
+
+ <div class="line n1">1</div>
+
+ <div class="line n2">2</div>
+
+ <div class="line n3">3</div>
+
+ <div class="line n4">4</div>
+
+ <div class="line n5">5</div>
+
+ <div class="line n6">6</div>
+
+ <div class="line n7">7</div>
+
+ <div class="line n8">8</div>
+
+ </td>
+ <td class="code">
+ <pre><div class="container"><div class="line"><code>jQuery.noConflict();</code></div></div><div class="container"><div class="line"><code>(<span class="keyword">function</span>( $ ) {</code></div></div><div class="container"><div class="line"><code> $(<span class="keyword">function</span>() {</code></div></div><div class="container"><div class="line"><code> <span class="comment">// More code using $ as alias to jQuery</span></code></div></div><div class="container"><div class="line"><code> });</code></div></div><div class="container"><div class="line"><code>})(jQuery);</code></div></div><div class="container"><div class="line"><code> </code></div></div><div class="container"><div class="line"><code><span class="comment">// Other code using $ as an alias to the other library</span></code></div></div></pre>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+</div>
+<div class="entry-example" id="example-2">
+<h4>Example: <span class="desc">Create a different alias instead of jQuery to use in the rest of the script.</span>
+</h4>
+<div class="syntaxhighlighter javascript ">
+ <table>
+ <tbody>
+ <tr>
+ <td class="gutter">
+
+ <div class="line n1">1</div>
+
+ <div class="line n2">2</div>
+
+ <div class="line n3">3</div>
+
+ <div class="line n4">4</div>
+
+ <div class="line n5">5</div>
+
+ <div class="line n6">6</div>
+
+ <div class="line n7">7</div>
+
+ </td>
+ <td class="code">
+ <pre><div class="container"><div class="line"><code><span class="keyword">var</span> j = jQuery.noConflict();</code></div></div><div class="container"><div class="line"><code> </code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with jQuery</span></code></div></div><div class="container"><div class="line"><code>j( <span class="string">"div p"</span> ).hide();</code></div></div><div class="container"><div class="line"><code> </code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with another library's $()</span></code></div></div><div class="container"><div class="line"><code>$( <span class="string">"content"</span> ).style.display = <span class="string">"none"</span>;</code></div></div></pre>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+</div>
+<div class="entry-example" id="example-3">
+<h4>Example: <span class="desc">Completely move jQuery to a new namespace in another object.</span>
+ <pre><div class="container"><div class="line"><code><span class="comment">// Do something with the new jQuery</span></code></div></div><div class="container"><div class="line"><code>dom.query( <span class="string">"div p"</span> ).hide();</code></div></div><div class="container"><div class="line"><code> </code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with another library's $()</span></code></div></div><div class="container"><div class="line"><code>$( <span class="string">"content"</span> ).style.display = <span class="string">"none"</span>;</code></div></div><div class="container"><div class="line"><code> </code></div></div><div class="container"><div class="line"><code><span class="comment">// Do something with another version of jQuery</span></code></div></div><div class="container"><div class="line"><code>jQuery( <span class="string">"div > p"</span> ).hide();</code></div></div></pre>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+</div>
+<div class="entry-example" id="example-4">
+<h4>Example: <span class="desc">Load two versions of jQuery (not recommended). Then, restore jQuery's globally scoped variables to the first loaded jQuery.</span>
+ <li class="cat-item cat-item-1"><a href="http://api.jquery.com/category/ajax/" title="View all posts filed under Ajax">Ajax</a>
+<ul class="children">
+ <li class="cat-item cat-item-2"><a href="http://api.jquery.com/category/ajax/global-ajax-event-handlers/" title="View all posts filed under Global Ajax Event Handlers">Global Ajax Event Handlers</a>
+</li>
+ <li class="cat-item cat-item-3"><a href="http://api.jquery.com/category/ajax/helper-functions/" title="View all posts filed under Helper Functions">Helper Functions</a>
+</li>
+ <li class="cat-item cat-item-4"><a href="http://api.jquery.com/category/ajax/low-level-interface/" title="View all posts filed under Low-Level Interface">Low-Level Interface</a>
+</li>
+ <li class="cat-item cat-item-5"><a href="http://api.jquery.com/category/ajax/shorthand-methods/" title="View all posts filed under Shorthand Methods">Shorthand Methods</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-6"><a href="http://api.jquery.com/category/attributes/" title="View all posts filed under Attributes">Attributes</a>
+</li>
+ <li class="cat-item cat-item-7"><a href="http://api.jquery.com/category/callbacks-object/" title="View all posts filed under Callbacks Object">Callbacks Object</a>
+</li>
+ <li class="cat-item cat-item-8 current-cat"><a href="http://api.jquery.com/category/core/" title="View all posts filed under Core">Core</a>
+</li>
+ <li class="cat-item cat-item-9"><a href="http://api.jquery.com/category/css/" title="View all posts filed under CSS">CSS</a>
+</li>
+ <li class="cat-item cat-item-10"><a href="http://api.jquery.com/category/data/" title="View all posts filed under Data">Data</a>
+</li>
+ <li class="cat-item cat-item-11"><a href="http://api.jquery.com/category/deferred-object/" title="View all posts filed under Deferred Object">Deferred Object</a>
+</li>
+ <li class="cat-item cat-item-87"><a href="http://api.jquery.com/category/deprecated/" title="View all posts filed under Deprecated">Deprecated</a>
+<ul class="children">
+ <li class="cat-item cat-item-90"><a href="http://api.jquery.com/category/deprecated/deprecated-1.3/" title="View all posts filed under Deprecated 1.3">Deprecated 1.3</a>
+</li>
+ <li class="cat-item cat-item-88"><a href="http://api.jquery.com/category/deprecated/deprecated-1.7/" title="View all posts filed under Deprecated 1.7">Deprecated 1.7</a>
+</li>
+ <li class="cat-item cat-item-89"><a href="http://api.jquery.com/category/deprecated/deprecated-1.8/" title="View all posts filed under Deprecated 1.8">Deprecated 1.8</a>
+</li>
+ <li class="cat-item cat-item-93"><a href="http://api.jquery.com/category/deprecated/deprecated-1.10/" title="View all posts filed under Deprecated 1.10">Deprecated 1.10</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-12"><a href="http://api.jquery.com/category/dimensions/" title="View all posts filed under Dimensions">Dimensions</a>
+</li>
+ <li class="cat-item cat-item-13"><a href="http://api.jquery.com/category/effects/" title="View all posts filed under Effects">Effects</a>
+<ul class="children">
+ <li class="cat-item cat-item-14"><a href="http://api.jquery.com/category/effects/basics/" title="View all posts filed under Basics">Basics</a>
+</li>
+ <li class="cat-item cat-item-15"><a href="http://api.jquery.com/category/effects/custom-effects/" title="View all posts filed under Custom">Custom</a>
+</li>
+ <li class="cat-item cat-item-16"><a href="http://api.jquery.com/category/effects/fading/" title="View all posts filed under Fading">Fading</a>
+</li>
+ <li class="cat-item cat-item-17"><a href="http://api.jquery.com/category/effects/sliding/" title="View all posts filed under Sliding">Sliding</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-18"><a href="http://api.jquery.com/category/events/" title="View all posts filed under Events">Events</a>
+<ul class="children">
+ <li class="cat-item cat-item-19"><a href="http://api.jquery.com/category/events/browser-events/" title="View all posts filed under Browser Events">Browser Events</a>
+</li>
+ <li class="cat-item cat-item-20"><a href="http://api.jquery.com/category/events/document-loading/" title="View all posts filed under Document Loading">Document Loading</a>
+</li>
+ <li class="cat-item cat-item-21"><a href="http://api.jquery.com/category/events/event-handler-attachment/" title="View all posts filed under Event Handler Attachment">Event Handler Attachment</a>
+</li>
+ <li class="cat-item cat-item-22"><a href="http://api.jquery.com/category/events/event-object/" title="View all posts filed under Event Object">Event Object</a>
+</li>
+ <li class="cat-item cat-item-23"><a href="http://api.jquery.com/category/events/form-events/" title="View all posts filed under Form Events">Form Events</a>
+</li>
+ <li class="cat-item cat-item-24"><a href="http://api.jquery.com/category/events/keyboard-events/" title="View all posts filed under Keyboard Events">Keyboard Events</a>
+</li>
+ <li class="cat-item cat-item-25"><a href="http://api.jquery.com/category/events/mouse-events/" title="View all posts filed under Mouse Events">Mouse Events</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-26"><a href="http://api.jquery.com/category/forms/" title="View all posts filed under Forms">Forms</a>
+</li>
+ <li class="cat-item cat-item-27"><a href="http://api.jquery.com/category/internals/" title="View all posts filed under Internals">Internals</a>
+</li>
+ <li class="cat-item cat-item-28"><a href="http://api.jquery.com/category/manipulation/" title="View all posts filed under Manipulation">Manipulation</a>
+<ul class="children">
+ <li class="cat-item cat-item-29"><a href="http://api.jquery.com/category/manipulation/class-attribute/" title="View all posts filed under Class Attribute">Class Attribute</a>
+</li>
+ <li class="cat-item cat-item-30"><a href="http://api.jquery.com/category/manipulation/copying/" title="View all posts filed under Copying">Copying</a>
+</li>
+ <li class="cat-item cat-item-32"><a href="http://api.jquery.com/category/manipulation/dom-insertion-around/" title="View all posts filed under DOM Insertion, Around">DOM Insertion, Around</a>
+</li>
+ <li class="cat-item cat-item-33"><a href="http://api.jquery.com/category/manipulation/dom-insertion-inside/" title="View all posts filed under DOM Insertion, Inside">DOM Insertion, Inside</a>
+</li>
+ <li class="cat-item cat-item-34"><a href="http://api.jquery.com/category/manipulation/dom-insertion-outside/" title="View all posts filed under DOM Insertion, Outside">DOM Insertion, Outside</a>
+</li>
+ <li class="cat-item cat-item-35"><a href="http://api.jquery.com/category/manipulation/dom-removal/" title="View all posts filed under DOM Removal">DOM Removal</a>
+</li>
+ <li class="cat-item cat-item-36"><a href="http://api.jquery.com/category/manipulation/dom-replacement/" title="View all posts filed under DOM Replacement">DOM Replacement</a>
+</li>
+ <li class="cat-item cat-item-37"><a href="http://api.jquery.com/category/manipulation/general-attributes/" title="View all posts filed under General Attributes">General Attributes</a>
+</li>
+ <li class="cat-item cat-item-38"><a href="http://api.jquery.com/category/manipulation/style-properties/" title="View all posts filed under Style Properties">Style Properties</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-39"><a href="http://api.jquery.com/category/miscellaneous/" title="View all posts filed under Miscellaneous">Miscellaneous</a>
+<ul class="children">
+ <li class="cat-item cat-item-40"><a href="http://api.jquery.com/category/miscellaneous/collection-manipulation/" title="View all posts filed under Collection Manipulation">Collection Manipulation</a>
+</li>
+ <li class="cat-item cat-item-41"><a href="http://api.jquery.com/category/miscellaneous/data-storage/" title="View all posts filed under Data Storage">Data Storage</a>
+</li>
+ <li class="cat-item cat-item-42"><a href="http://api.jquery.com/category/miscellaneous/dom-element-methods/" title="View all posts filed under DOM Element Methods">DOM Element Methods</a>
+</li>
+ <li class="cat-item cat-item-43"><a href="http://api.jquery.com/category/miscellaneous/setup-methods/" title="View all posts filed under Setup Methods">Setup Methods</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-44"><a href="http://api.jquery.com/category/offset/" title="View all posts filed under Offset">Offset</a>
+</li>
+ <li class="cat-item cat-item-45"><a href="http://api.jquery.com/category/properties/" title="View all posts filed under Properties">Properties</a>
+<ul class="children">
+ <li class="cat-item cat-item-46"><a href="http://api.jquery.com/category/properties/jquery-object-instance-properties/" title="View all posts filed under Properties of jQuery Object Instances">Properties of jQuery Object Instances</a>
+</li>
+ <li class="cat-item cat-item-47"><a href="http://api.jquery.com/category/properties/global-jquery-object-properties/" title="View all posts filed under Properties of the Global jQuery Object">Properties of the Global jQuery Object</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-92"><a href="http://api.jquery.com/category/removed/" title="View all posts filed under Removed">Removed</a>
+</li>
+ <li class="cat-item cat-item-48"><a href="http://api.jquery.com/category/selectors/" title="View all posts filed under Selectors">Selectors</a>
+<ul class="children">
+ <li class="cat-item cat-item-49"><a href="http://api.jquery.com/category/selectors/attribute-selectors/" title="View all posts filed under Attribute">Attribute</a>
+</li>
+ <li class="cat-item cat-item-50"><a href="http://api.jquery.com/category/selectors/basic-css-selectors/" title="View all posts filed under Basic">Basic</a>
+</li>
+ <li class="cat-item cat-item-51"><a href="http://api.jquery.com/category/selectors/basic-filter-selectors/" title="View all posts filed under Basic Filter">Basic Filter</a>
+</li>
+ <li class="cat-item cat-item-52"><a href="http://api.jquery.com/category/selectors/child-filter-selectors/" title="View all posts filed under Child Filter">Child Filter</a>
+</li>
+ <li class="cat-item cat-item-53"><a href="http://api.jquery.com/category/selectors/content-filter-selector/" title="View all posts filed under Content Filter">Content Filter</a>
+</li>
+ <li class="cat-item cat-item-54"><a href="http://api.jquery.com/category/selectors/form-selectors/" title="View all posts filed under Form">Form</a>
+</li>
+ <li class="cat-item cat-item-55"><a href="http://api.jquery.com/category/selectors/hierarchy-selectors/" title="View all posts filed under Hierarchy">Hierarchy</a>
+</li>
+ <li class="cat-item cat-item-56"><a href="http://api.jquery.com/category/selectors/jquery-selector-extensions/" title="View all posts filed under jQuery Extensions">jQuery Extensions</a>
+</li>
+ <li class="cat-item cat-item-57"><a href="http://api.jquery.com/category/selectors/visibility-filter-selectors/" title="View all posts filed under Visibility Filter">Visibility Filter</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-58"><a href="http://api.jquery.com/category/traversing/" title="View all posts filed under Traversing">Traversing</a>
+<ul class="children">
+ <li class="cat-item cat-item-59"><a href="http://api.jquery.com/category/traversing/filtering/" title="View all posts filed under Filtering">Filtering</a>
+</li>
+ <li class="cat-item cat-item-60"><a href="http://api.jquery.com/category/traversing/miscellaneous-traversal/" title="View all posts filed under Miscellaneous Traversing">Miscellaneous Traversing</a>
+</li>
+ <li class="cat-item cat-item-61"><a href="http://api.jquery.com/category/traversing/tree-traversal/" title="View all posts filed under Tree Traversal">Tree Traversal</a>
+</li>
+</ul>
+</li>
+ <li class="cat-item cat-item-63"><a href="http://api.jquery.com/category/utilities/" title="View all posts filed under Utilities">Utilities</a>
+</li>
+ <li class="cat-item cat-item-64"><a href="http://api.jquery.com/category/version/" title="View all posts filed under Version">Version</a>
+<ul class="children">
+ <li class="cat-item cat-item-65"><a href="http://api.jquery.com/category/version/1.0/" title="View all posts filed under Version 1.0">Version 1.0</a>
+</li>
+ <li class="cat-item cat-item-66"><a href="http://api.jquery.com/category/version/1.0.4/" title="View all posts filed under Version 1.0.4">Version 1.0.4</a>
+</li>
+ <li class="cat-item cat-item-67"><a href="http://api.jquery.com/category/version/1.1/" title="View all posts filed under Version 1.1">Version 1.1</a>
+</li>
+ <li class="cat-item cat-item-68"><a href="http://api.jquery.com/category/version/1.1.2/" title="View all posts filed under Version 1.1.2">Version 1.1.2</a>
+</li>
+ <li class="cat-item cat-item-69"><a href="http://api.jquery.com/category/version/1.1.3/" title="View all posts filed under Version 1.1.3">Version 1.1.3</a>
+</li>
+ <li class="cat-item cat-item-70"><a href="http://api.jquery.com/category/version/1.1.4/" title="View all posts filed under Version 1.1.4">Version 1.1.4</a>
+</li>
+ <li class="cat-item cat-item-71"><a href="http://api.jquery.com/category/version/1.2/" title="View all posts filed under Version 1.2">Version 1.2</a>
+</li>
+ <li class="cat-item cat-item-72"><a href="http://api.jquery.com/category/version/1.2.3/" title="View all posts filed under Version 1.2.3">Version 1.2.3</a>
+</li>
+ <li class="cat-item cat-item-73"><a href="http://api.jquery.com/category/version/1.2.6/" title="View all posts filed under Version 1.2.6">Version 1.2.6</a>
+</li>
+ <li class="cat-item cat-item-74"><a href="http://api.jquery.com/category/version/1.3/" title="View all posts filed under Version 1.3">Version 1.3</a>
+</li>
+ <li class="cat-item cat-item-75"><a href="http://api.jquery.com/category/version/1.4/" title="View all posts filed under Version 1.4">Version 1.4</a>
+</li>
+ <li class="cat-item cat-item-76"><a href="http://api.jquery.com/category/version/1.4.1/" title="View all posts filed under Version 1.4.1">Version 1.4.1</a>
+</li>
+ <li class="cat-item cat-item-77"><a href="http://api.jquery.com/category/version/1.4.2/" title="View all posts filed under Version 1.4.2">Version 1.4.2</a>
+</li>
+ <li class="cat-item cat-item-78"><a href="http://api.jquery.com/category/version/1.4.3/" title="View all posts filed under Version 1.4.3">Version 1.4.3</a>
+</li>
+ <li class="cat-item cat-item-79"><a href="http://api.jquery.com/category/version/1.4.4/" title="View all posts filed under Version 1.4.4">Version 1.4.4</a>
+</li>
+ <li class="cat-item cat-item-80"><a href="http://api.jquery.com/category/version/1.5/" title="View all posts filed under Version 1.5">Version 1.5</a>
+</li>
+ <li class="cat-item cat-item-81"><a href="http://api.jquery.com/category/version/1.5.1/" title="View all posts filed under Version 1.5.1">Version 1.5.1</a>
+</li>
+ <li class="cat-item cat-item-82"><a href="http://api.jquery.com/category/version/1.6/" title="View all posts filed under Version 1.6">Version 1.6</a>
+</li>
+ <li class="cat-item cat-item-83"><a href="http://api.jquery.com/category/version/1.7/" title="View all posts filed under Version 1.7">Version 1.7</a>
+</li>
+ <li class="cat-item cat-item-84"><a href="http://api.jquery.com/category/version/1.8/" title="View all posts filed under Version 1.8">Version 1.8</a>
+</li>
+ <li class="cat-item cat-item-86"><a href="http://api.jquery.com/category/version/1.9/" title="View all posts filed under Version 1.9">Version 1.9</a>
+ <img src="jQuery.noConflict%28%29%20_%20jQuery%20API%20Documentation_files/learning-jquery-4th-ed.jpg" alt="Learning jQuery 4th Edition by Karl Swedberg and Jonathan Chaffer" height="114" width="92">
+ <img src="jQuery.noConflict%28%29%20_%20jQuery%20API%20Documentation_files/jquery-in-action.jpg" alt="jQuery in Action by Bear Bibeault, Yehuda Katz, and Aurelio De Rosa" height="114" width="92">
+ jQuery in Action
+ <cite>Bear Bibeault, Yehuda Katz, and Aurelio De Rosa</cite>
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/252d1bca0e21492bbb0d390e8685097e.png b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/252d1bca0e21492bbb0d390e8685097e.png
new file mode 100644
index 000000000..aa556b0f1
Binary files /dev/null and b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/252d1bca0e21492bbb0d390e8685097e.png differ
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/ados b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/ados
new file mode 100644
index 000000000..7d17fb9e9
--- /dev/null
+++ b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/ados
+E.xa=function(a,b){if(a)if(Ca(a))this.set(a,b);else if("object"==typeof a)for(var c in a)a.hasOwnProperty(c)&&this.set(c,a[c])};E.addEventListener=function(a,b){var c=this.get(Nc)[a];c&&c[n](b)};E.removeEventListener=function(a,b){for(var c=this.get(Nc)[a],d=0;c&&d<c[w];d++)if(c[d]==b){c.splice(d,1);break}};E.qa=function(){return"5.5.7"};E.B=function(a){this.get(hb);a="auto"==a?Ka(J.domain):a&&"-"!=a&&"none"!=a?a[D]():"";this.set(bb,a)};E.va=function(a){this.set(hb,!!a)};
+E.sa=function(a,b){return this.m().getKey(a,b)};E.ta=function(a,b){return this.m().N(a,b)};E.fa=function(a){this.m().L(a)};E.ga=function(a){this.m().M(a)};E.ja=function(){return new yd};E.W=function(a){a&&this.get(Ab)[n](a[D]())};E.ba=function(){this.set(Ab,[])};E.X=function(a){a&&this.get(Bb)[n](a[D]())};E.ca=function(){this.set(Bb,[])};E.Z=function(a,b,c,d,e){if(a&&b){a=[a,b[D]()][C](":");if(d||e)a=[a,d,e][C](":");d=this.get(zb);d.splice(c?0:d[w],0,a)}};E.da=function(){this.set(zb,[])};
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/i.gif b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/i.gif
new file mode 100644
index 000000000..3c51d740c
Binary files /dev/null and b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/i.gif differ
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-in-action.jpg b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-in-action.jpg
new file mode 100644
index 000000000..b40181129
Binary files /dev/null and b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-in-action.jpg differ
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-succinctly.jpg b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-succinctly.jpg
new file mode 100644
index 000000000..463e09f82
Binary files /dev/null and b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery-succinctly.jpg differ
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery.js b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery.js
new file mode 100644
index 000000000..006e95310
--- /dev/null
+++ b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/jquery.js
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/learning-jquery-4th-ed.jpg b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/learning-jquery-4th-ed.jpg
new file mode 100644
index 000000000..1d228d9e2
Binary files /dev/null and b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/learning-jquery-4th-ed.jpg differ
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/main.js b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/main.js
new file mode 100644
index 000000000..312d371b8
--- /dev/null
+++ b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/main.js
@@ -0,0 +1,391 @@
+/*
+ * All sites
+ */
+$(function() {
+ // copyable auto-select-all
+ $( ".copyable" ).on( "click", function() {
+ if ( typeof this.select === "function" ) {
+ this.select();
+ }
+ });
+
+ /*
+ * Change navigation elements for smaller screens
+ */
+ (function() {
+
+ // Move the global nav to the footer and collapse to a select menu
+;window.Modernizr=function(a,b,c){function A(a){j.cssText=a}function B(a,b){return A(m.join(a+";")+(b||""))}function C(a,b){return typeof a===b}function D(a,b){return!!~(""+a).indexOf(b)}function E(a,b){for(var d in a){var e=a[d];if(!D(e,"-")&&j[e]!==c)return b=="pfx"?e:!0}return!1}function F(a,b,d){for(var e in a){var f=b[a[e]];if(f!==c)return d===!1?a[e]:C(f,"function")?f.bind(d||b):f}return!1}function G(a,b,c){var d=a.charAt(0).toUpperCase()+a.slice(1),e=(a+" "+o.join(d+" ")+d).split(" ");return C(b,"string")||C(b,"undefined")?E(e,b):(e=(a+" "+p.join(d+" ")+d).split(" "),F(e,b,c))}var d="2.6.2",e={},f=!0,g=b.documentElement,h="modernizr",i=b.createElement(h),j=i.style,k,l={}.toString,m=" -webkit- -moz- -o- -ms- ".split(" "),n="Webkit Moz O ms",o=n.split(" "),p=n.toLowerCase().split(" "),q={},r={},s={},t=[],u=t.slice,v,w=function(a,c,d,e){var f,i,j,k,l=b.createElement("div"),m=b.body,n=m||b.createElement("body");if(parseInt(d,10))while(d--)j=b.createElement("div"),j.id=e?e[d]:h+(d+1),l.appendChild(j);return f=["­",'<style id="s',h,'">',a,"</style>"].join(""),l.id=h,(m?l:n).innerHTML+=f,n.appendChild(l),m||(n.style.background="",n.style.overflow="hidden",k=g.style.overflow,g.style.overflow="hidden",g.appendChild(n)),i=c(l,a),m?l.parentNode.removeChild(l):(n.parentNode.removeChild(n),g.style.overflow=k),!!i},x=function(b){var c=a.matchMedia||a.msMatchMedia;if(c)return c(b).matches;var d;return w("@media "+b+" { #"+h+" { position: absolute; } }",function(b){d=(a.getComputedStyle?getComputedStyle(b,null):b.currentStyle)["position"]=="absolute"}),d},y={}.hasOwnProperty,z;!C(y,"undefined")&&!C(y.call,"undefined")?z=function(a,b){return y.call(a,b)}:z=function(a,b){return b in a&&C(a.constructor.prototype[b],"undefined")},Function.prototype.bind||(Function.prototype.bind=function(b){var c=this;if(typeof c!="function")throw new TypeError;var d=u.call(arguments,1),e=function(){if(this instanceof e){var a=function(){};a.prototype=c.prototype;var f=new a,g=c.apply(f,d.concat(u.call(arguments)));return Object(g)===g?g:f}return c.apply(b,d.concat(u.call(arguments)))};return e}),q.multiplebgs=function(){return A("background:url(https://),url(https://),red url(https://)"),/(url\s*\(.*?){3}/.test(j.background)},q.boxshadow=function(){return G("boxShadow")},q.cssgradients=function(){var a="background-image:",b="gradient(linear,left top,right bottom,from(#9f9),to(white));",c="linear-gradient(left top,#9f9, white);";return A((a+"-webkit- ".split(" ").join(b+a)+m.join(c+a)).slice(0,-a.length)),D(j.backgroundImage,"gradient")};for(var H in q)z(q,H)&&(v=H.toLowerCase(),e[v]=q[H](),t.push((e[v]?"":"no-")+v));return e.addTest=function(a,b){if(typeof a=="object")for(var d in a)z(a,d)&&e.addTest(d,a[d]);else{a=a.toLowerCase();if(e[a]!==c)return e;b=typeof b=="function"?b():b,typeof f!="undefined"&&f&&(g.className+=" "+(b?"":"no-")+a),e[a]=b}return e},A(""),i=k=null,function(a,b){function k(a,b){var c=a.createElement("p"),d=a.getElementsByTagName("head")[0]||a.documentElement;return c.innerHTML="x<style>"+b+"</style>",d.insertBefore(c.lastChild,d.firstChild)}function l(){var a=r.elements;return typeof a=="string"?a.split(" "):a}function m(a){var b=i[a[g]];return b||(b={},h++,a[g]=h,i[h]=b),b}function n(a,c,f){c||(c=b);if(j)return c.createElement(a);f||(f=m(c));var g;return f.cache[a]?g=f.cache[a].cloneNode():e.test(a)?g=(f.cache[a]=f.createElem(a)).cloneNode():g=f.createElem(a),g.canHaveChildren&&!d.test(a)?f.frag.appendChild(g):g}function o(a,c){a||(a=b);if(j)return a.createDocumentFragment();c=c||m(a);var d=c.frag.cloneNode(),e=0,f=l(),g=f.length;for(;e<g;e++)d.createElement(f[e]);return d}function p(a,b){b.cache||(b.cache={},b.createElem=a.createElement,b.createFrag=a.createDocumentFragment,b.frag=b.createFrag()),a.createElement=function(c){return r.shivMethods?n(c,a,b):b.createElem(c)},a.createDocumentFragment=Function("h,f","return function(){var n=f.cloneNode(),c=n.createElement;h.shivMethods&&("+l().join().replace(/\w+/g,function(a){return b.createElem(a),b.frag.createElement(a),'c("'+a+'")'})+");return n}")(r,b.frag)}function q(a){a||(a=b);var c=m(a);return r.shivCSS&&!f&&!c.hasCSS&&(c.hasCSS=!!k(a,"article,aside,figcaption,figure,footer,header,hgroup,nav,section{display:block}mark{background:#FF0;color:#000}")),j||p(a,c),a}var c=a.html5||{},d=/^<|^(?:button|map|select|textarea|object|iframe|option|optgroup)$/i,e=/^(?:a|b|code|div|fieldset|h1|h2|h3|h4|h5|h6|i|label|li|ol|p|q|span|strong|style|table|tbody|td|th|tr|ul)$/i,f,g="_html5shiv",h=0,i={},j;(function(){try{var a=b.createElement("a");a.innerHTML="<xyz></xyz>",f="hidden"in a,j=a.childNodes.length==1||function(){b.createElement("a");var a=b.createDocumentFragment();return typeof a.cloneNode=="undefined"||typeof a.createDocumentFragment=="undefined"||typeof a.createElement=="undefined"}()}catch(c){f=!0,j=!0}})();var r={elements:c.elements||"abbr article aside audio bdi canvas data datalist details figcaption figure footer header hgroup mark meter nav output progress section summary time video",shivCSS:c.shivCSS!==!1,supportsUnknownElements:j,shivMethods:c.shivMethods!==!1,type:"default",shivDocument:q,createElement:n,createDocumentFragment:o};a.html5=r,q(b)}(this,b),e._version=d,e._prefixes=m,e._domPrefixes=p,e._cssomPrefixes=o,e.mq=x,e.testProp=function(a){return E([a])},e.testAllProps=G,e.testStyles=w,g.className=g.className.replace(/(^|\s)no-js(\s|$)/,"$1$2")+(f?" js "+t.join(" "):""),e}(this,this.document);
\ No newline at end of file
diff --git a/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/plugins.js b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/plugins.js
new file mode 100644
index 000000000..7560541f3
--- /dev/null
+++ b/shrine-webclient/src/main/html/js-ext/jquerycode/jQuery.noConflict() _ jQuery API Documentation_files/plugins.js
@@ -0,0 +1,59 @@
+
+/*! matchMedia() polyfill - Test a CSS media type/query in JS. Authors & copyright (c) 2012: Scott Jehl, Paul Irish, Nicholas Zakas. Dual MIT/BSD license */
+/*! NOTE: If you're already including a window.matchMedia polyfill via Modernizr or otherwise, you don't need this part */
+/*! Respond.js v1.1.0: min/max-width media query polyfill. (c) Scott Jehl. MIT/GPLv2 Lic. j.mp/respondjs */
+(function(e){e.respond={};respond.update=function(){};respond.mediaQueriesSupported=e.matchMedia&&e.matchMedia("only all").matches;if(respond.mediaQueriesSupported){return}var w=e.document,s=w.documentElement,i=[],k=[],q=[],o={},h=30,f=w.getElementsByTagName("head")[0]||s,g=w.getElementsByTagName("base")[0],b=f.getElementsByTagName("link"),d=[],a=function(){var D=b,y=D.length,B=0,A,z,C,x;for(;B<y;B++){A=D[B],z=A.href,C=A.media,x=A.rel&&A.rel.toLowerCase()==="stylesheet";if(!!z&&x&&!o[z]){if(A.styleSheet&&A.styleSheet.rawCssText){m(A.styleSheet.rawCssText,z,C);o[z]=true}else{if((!/^([a-zA-Z:]*\/\/)/.test(z)&&!g)||z.replace(RegExp.$1,"").split("/")[0]===e.location.host){d.push({href:z,media:C})}}}}u()},u=function(){if(d.length){var x=d.shift();n(x.href,function(y){m(y,x.href,x.media);o[x.href]=true;u()})}},m=function(I,x,z){var G=I.match(/@media[^\{]+\{([^\{\}]*\{[^\}\{]*\})+/gi),J=G&&G.length||0,x=x.substring(0,x.lastIndexOf("/")),y=function(K){return K.replace(/(url\()['"]?([^\/\)'"][^:\)'"]+)['"]?(\))/g,"$1"+x+"$2$3")},A=!J&&z,D=0,C,E,F,B,H;if(x.length){x+="/"}if(A){J=1}for(;D<J;D++){C=0;if(A){E=z;k.push(y(I))}else{E=G[D].match(/@media *([^\{]+)\{([\S\s]+?)$/)&&RegExp.$1;k.push(RegExp.$2&&y(RegExp.$2))}B=E.split(",");H=B.length;for(;C<H;C++){F=B[C];i.push({media:F.split("(")[0].match(/(only\s+)?([a-zA-Z]+)\s?/)&&RegExp.$2||"all",rules:k.length-1,hasquery:F.indexOf("(")>-1,minw:F.match(/\(min\-width:[\s]*([\s]*[0-9\.]+)(px|em)[\s]*\)/)&&parseFloat(RegExp.$1)+(RegExp.$2||""),maxw:F.match(/\(max\-width:[\s]*([\s]*[0-9\.]+)(px|em)[\s]*\)/)&&parseFloat(RegExp.$1)+(RegExp.$2||"")})}}j()},l,r,v=function(){var z,A=w.createElement("div"),x=w.body,y=false;A.style.cssText="position:absolute;font-size:1em;width:1em";if(!x){x=y=w.createElement("body");x.style.background="none"}x.appendChild(A);s.insertBefore(x,s.firstChild);z=A.offsetWidth;if(y){s.removeChild(x)}else{x.removeChild(A)}z=p=parseFloat(z);return z},p,j=function(I){var x="clientWidth",B=s[x],H=w.compatMode==="CSS1Compat"&&B||w.body[x]||B,D={},G=b[b.length-1],z=(new Date()).getTime();if(I&&l&&z-l<h){clearTimeout(r);r=setTimeout(j,h);return}else{l=z}for(var E in i){var K=i[E],C=K.minw,J=K.maxw,A=C===null,L=J===null,y="em";if(!!C){C=parseFloat(C)*(C.indexOf(y)>-1?(p||v()):1)}if(!!J){J=parseFloat(J)*(J.indexOf(y)>-1?(p||v()):1)}if(!K.hasquery||(!A||!L)&&(A||H>=C)&&(L||H<=J)){if(!D[K.media]){D[K.media]=[]}D[K.media].push(k[K.rules])}}for(var E in q){if(q[E]&&q[E].parentNode===f){f.removeChild(q[E])}}for(var E in D){var M=w.createElement("style"),F=D[E].join("\n");M.type="text/css";M.media=E;f.insertBefore(M,G.nextSibling);if(M.styleSheet){M.styleSheet.cssText=F}else{M.appendChild(w.createTextNode(F))}q.push(M)}},n=function(x,z){var y=c();if(!y){return}y.open("GET",x,true);y.onreadystatechange=function(){if(y.readyState!=4||y.status!=200&&y.status!=304){return}z(y.responseText)};if(y.readyState==4){return}y.send(null)},c=(function(){var x=false;try{x=new XMLHttpRequest()}catch(y){x=new ActiveXObject("Microsoft.XMLHTTP")}return function(){return x}})();a();respond.update=a;function t(){j(true)}if(e.addEventListener){e.addEventListener("resize",t,false)}else{if(e.attachEvent){e.attachEvent("onresize",t)}}})(this);
+ e+'direction-nav"><li><a class="'+e+'prev" href="#">'+c.prevText+'</a></li><li><a class="'+e+'next" href="#">'+c.nextText+"</a></li></ul>");a.controlsContainer?(d(a.controlsContainer).append(b),a.directionNav=d("."+e+"direction-nav li a",a.controlsContainer)):(a.append(b),a.directionNav=d("."+e+"direction-nav li a",a));f.directionNav.update();a.directionNav.bind(t,function(b){b.preventDefault();b=d(this).hasClass(e+"next")?a.getTarget("next"):a.getTarget("prev");a.flexAnimate(b,c.pauseOnAction)});
+q.prototype.createElement=function(a,c,b){a=this.j.createElement(a);if(c)for(var d in c)c.hasOwnProperty(d)&&("style"==d?this.ya(a,c[d]):a.setAttribute(d,c[d]));b&&a.appendChild(this.j.createTextNode(b));return a};function r(a,c,b){a=a.j.getElementsByTagName(c)[0];a||(a=document.documentElement);a&&a.lastChild&&a.insertBefore(b,a.lastChild)}function s(a){function c(){document.body?a():setTimeout(c,0)}c()}function t(a){a.parentNode&&a.parentNode.removeChild(a)}
+Oa.prototype.h=function(a,c){var b=this.j.createElement("img");b.setAttribute("width",62);b.setAttribute("height",25);b.setAttribute("src",this.La.h(J(c)));b.setAttribute("class","typekit-badge");b.setAttribute("alt","Fonts by Typekit");b.setAttribute("title","Information about the fonts used on this site");b.style.position="fixed";b.style.zIndex=2E9;b.style.right=0;b.style.bottom=0;b.style.cursor="pointer";b.style.border=0;"Opera"!=a.getName()&&(b.style.content="none");b.style.display="inline";b.style["float"]=
+hh:"%d hours",d:"a day",dd:"%d days",M:"a month",MM:"%d months",y:"a year",yy:"%d years"},Qd=r.prototype;Qd._calendar=Kd,Qd.calendar=Yb,Qd._longDateFormat=Ld,Qd.longDateFormat=Zb,Qd._invalidDate=Md,Qd.invalidDate=$b,Qd._ordinal=Nd,Qd.ordinal=_b,Qd._ordinalParse=Od,Qd.preparse=ac,Qd.postformat=ac,Qd._relativeTime=Pd,Qd.relativeTime=bc,Qd.pastFuture=cc,Qd.set=dc,Qd.months=S,Qd._months=id,Qd.monthsShort=T,Qd._monthsShort=jd,Qd.monthsParse=U,Qd.week=ia,Qd._week=qd,Qd.firstDayOfYear=ka,Qd.firstDayOfWeek=ja,Qd.weekdays=Ib,Qd._weekdays=Ad,Qd.weekdaysMin=Kb,Qd._weekdaysMin=Cd,Qd.weekdaysShort=Jb,Qd._weekdaysShort=Bd,Qd.weekdaysParse=Lb,Qd.isPM=Rb,Qd._meridiemParse=Dd,Qd.meridiem=Sb,v("en",{ordinalParse:/\d{1,2}(th|st|nd|rd)/,ordinal:function(a){var b=a%10,c=1===p(a%100/10)?"th":1===b?"st":2===b?"nd":3===b?"rd":"th";return a+c}}),a.lang=$("moment.lang is deprecated. Use moment.locale instead.",v),a.langData=$("moment.langData is deprecated. Use moment.localeData instead.",x);var Rd=Math.abs,Sd=uc("ms"),Td=uc("s"),Ud=uc("m"),Vd=uc("h"),Wd=uc("d"),Xd=uc("w"),Yd=uc("M"),Zd=uc("y"),$d=wc("milliseconds"),_d=wc("seconds"),ae=wc("minutes"),be=wc("hours"),ce=wc("days"),de=wc("months"),ee=wc("years"),fe=Math.round,ge={s:45,m:45,h:22,d:26,M:11},he=Math.abs,ie=Ea.prototype;ie.abs=lc,ie.add=nc,ie.subtract=oc,ie.as=sc,ie.asMilliseconds=Sd,ie.asSeconds=Td,ie.asMinutes=Ud,ie.asHours=Vd,ie.asDays=Wd,ie.asWeeks=Xd,ie.asMonths=Yd,ie.asYears=Zd,ie.valueOf=tc,ie._bubble=pc,ie.get=vc,ie.milliseconds=$d,ie.seconds=_d,ie.minutes=ae,ie.hours=be,ie.days=ce,ie.weeks=xc,ie.months=de,ie.years=ee,ie.humanize=Bc,ie.toISOString=Cc,ie.toString=Cc,ie.toJSON=Cc,ie.locale=pb,ie.localeData=qb,ie.toIsoString=$("toIsoString() is deprecated. Please use toISOString() instead (notice the capitals)",Cc),ie.lang=yd,G("X",0,0,"unix"),G("x",0,0,"valueOf"),L("x",Xc),L("X",Zc),O("X",function(a,b,c){c._d=new Date(1e3*parseFloat(a,10))}),O("x",function(a,b,c){c._d=new Date(p(a))}),a.version="2.10.3",b(Aa),a.fn=Jd,a.min=Ca,a.max=Da,a.utc=h,a.unix=Wb,a.months=gc,a.isDate=d,a.locale=v,a.invalid=l,a.duration=Va,a.isMoment=o,a.weekdays=ic,a.parseZone=Xb,a.localeData=x,a.isDuration=Fa,a.monthsShort=hc,a.weekdaysMin=kc,a.defineLocale=w,a.weekdaysShort=jc,a.normalizeUnits=z,a.relativeTimeThreshold=Ac;var je=a;return je});
+ jQuery('<span title="This item is being excluded" class="itemExclude"> NOT </span>').prependTo(jQuery('#QPD'+(this.panelCurrentIndex+1)+' [class^="sdxDefault"]')[i]);
- if (results.errorMsg.substring(0,9) == "LOCKEDOUT")
- {
- results.errorMsg = 'As an "obfuscated user" you have exceeded the allowed query repeat and are now LOCKED OUT, please notify your system administrator.';
- }
- }
- alert(results.errorMsg);
- private_cancelQuery();
- return;
- }
-
- //query was successful so update global settings.
- clearInterval(private_refreshInterrupt);
- private_refreshInterrupt = false;
- private_singleton_isRunning = false;
-
- //update the ui
- var self = i2b2.CRC.ctrlr.currentQueryStatus;
-
- // this private function refreshes the display DIV
- var d = new Date();
- var t = Math.floor((d.getTime() - private_startTime)/100)/10;
+ if (results.errorMsg.substring(0,9) == "LOCKEDOUT")
+ {
+ results.errorMsg = 'As an "obfuscated user" you have exceeded the allowed query repeat and are now LOCKED OUT, please notify your system administrator.';
s += '<query_timing>SAMEINSTANCENUM</query_timing>\n';
s += '<specificity_scale>0</specificity_scale>\n';
}
for (var p = 0; p < panel_cnt; p++) {
s += '\t<panel>\n';
s += '\t\t<panel_number>' + (p+1) + '</panel_number>\n';
// date range constraints
if (panel_list[p].dateFrom) {
s += '\t\t<panel_date_from>'+panel_list[p].dateFrom.Year+'-'+padNumber(panel_list[p].dateFrom.Month,2)+'-'+padNumber(panel_list[p].dateFrom.Day,2)+'T00:00:00.000-05:00</panel_date_from>\n';
}
if (panel_list[p].dateTo) {
s += '\t\t<panel_date_to>'+panel_list[p].dateTo.Year+'-'+padNumber(panel_list[p].dateTo.Month,2)+'-'+padNumber(panel_list[p].dateTo.Day,2)+'T00:00:00.000-05:00</panel_date_to>\n';
}
s += "\t\t<panel_accuracy_scale>" + panel_list[p].relevance + "</panel_accuracy_scale>\n";
// Exclude constraint (invert flag)
if (panel_list[p].exclude) {
s += '\t\t<invert>1</invert>\n';
} else {
s += '\t\t<invert>0</invert>\n';
}
// Panel Timing
s += '\t\t<panel_timing>' + panel_list[p].timing + '</panel_timing>\n';
// Occurs constraint
s += '\t\t<total_item_occurrences>'+((panel_list[p].occurs*1)+1)+'</total_item_occurrences>\n';
// Concepts
for (i=0; i < panel_list[p].items.length; i++) {
var sdxData = panel_list[p].items[i];
s += '\t\t<item>\n';
switch(sdxData.sdxInfo.sdxType) {
case "QM":
s += '\t\t\t<item_key>masterid:' + sdxData.origData.id + '</item_key>\n';
s += '\t\t\t<item_name>' + sdxData.origData.title + '</item_name>\n';
s += '\t\t\t<tooltip>' + sdxData.origData.name + '</tooltip>\n';
s += '\t\t\t<item_is_synonym>false</item_is_synonym>\n';
s += '\t\t\t<hlevel>0</hlevel>\n';
break;
case "PRS":
s += '\t\t\t<item_key>patient_set_coll_id:' + sdxData.sdxInfo.sdxKeyValue + '</item_key>\n';
s += '\t\t\t<item_name>' + sdxData.sdxInfo.sdxDisplayName + '</item_name>\n';
s += '\t\t\t<tooltip>' + sdxData.sdxInfo.sdxDisplayName + '</tooltip>\n';
s += '\t\t\t<item_is_synonym>false</item_is_synonym>\n';
s += '\t\t\t<hlevel>0</hlevel>\n';
break;
case "ENS":
s += '\t\t\t<item_key>patient_set_enc_id:' + sdxData.sdxInfo.sdxKeyValue + '</item_key>\n';
s += '\t\t\t<item_name>' + sdxData.sdxInfo.sdxDisplayName + '</item_name>\n';
s += '\t\t\t<tooltip>' + sdxData.sdxInfo.sdxDisplayName + '</tooltip>\n';
s += '\t\t\t<item_is_synonym>false</item_is_synonym>\n';
s += '\t\t\t<hlevel>0</hlevel>\n';
break;
default:
if (sdxData.origData.isModifier) {
var modParent = sdxData.origData.parent;
var level = sdxData.origData.level;
var key = sdxData.origData.parent.key;
var name = (sdxData.origData.parent.name != null ? i2b2.h.Escape(sdxData.origData.parent.name) : i2b2.h.Escape(sdxData.origData.name)) ;
var tooltip = sdxData.origData.tooltip;
var itemicon = sdxData.origData.hasChildren;
while (modParent != null)
{
if (modParent.isModifier)
{
modParent = modParent.parent;
} else {
level = modParent.level;
key = modParent.key;
name = modParent.name;
tooltip = modParent.tooltip;
itemicon = modParent.hasChildren;
break;
}
}
s += '\t\t\t<hlevel>' + level + '</hlevel>\n';
s += '\t\t\t<item_key>' + key + '</item_key>\n';
s += '\t\t\t<item_name>' + name + '</item_name>\n';
s += '\t\t\t<item_key>' + sdxData.origData.key + '</item_key>\n';
s += '\t\t\t<tooltip>' + sdxData.origData.tooltip + '</tooltip>\n';
s += '\t\t\t<class>ENC</class>\n';
s += '\t\t\t<item_icon>' + sdxData.origData.hasChildren + '</item_icon>\n';
}
try {
var t = i2b2.h.XPath(sdxData.origData.xmlOrig,'descendant::synonym_cd/text()');
t = (t[0].nodeValue=="Y");
} catch(e) {
var t = "false";
}
s += '\t\t\t<item_is_synonym>'+t+'</item_is_synonym>\n';
if (sdxData.LabValues) {
//s += '\t\t\t<constrain_by_value>\n';
s += this.getValues( sdxData.LabValues);
}
break;
}
//TODO add contraint to the item in the future
/*
s += '\t\t\t<constrain_by_date>\n';
if (panel_list[p].dateFrom) {
s += '\t\t\t\t<date_from>'+panel_list[p].dateFrom.Year+'-'+padNumber(panel_list[p].dateFrom.Month,2)+'-'+padNumber(panel_list[p].dateFrom.Day,2)+'Z</date_from>\n';
}
if (panel_list[p].dateTo) {
s += '\t\t\t\t<date_to>'+panel_list[p].dateTo.Year+'-'+padNumber(panel_list[p].dateTo.Month,2)+'-'+padNumber(panel_list[p].dateTo.Day,2)+'Z</date_to>\n';
+ "<span class='no-print' style='font-family:Arial;font-size:11px;'><img src=\"js-i2b2/cells/CRC/assets/print.png\"/><a href='javascript:window.print()' title='Click here to print the report.'> Print Report</a></span>"+
+ "<span class='no-print' style='font-family:Arial;font-size:11px;'><img src=\"js-i2b2/cells/CRC/assets/print.png\"/><a href='javascript:window.print()' title='Click here to print the report.'> Print Report</a></span>"+
+ output = "<div style=\"padding:15px;text-align:center;font-size:16px;\"><img src=\"js-i2b2/cells/plugins/biobankportal/BiobankDatafile/assets/csv_icon.png\" align=\"absmiddle\"/> You can download the de-identified data for this query as an Excel/CSV file. ";
+ output += "<input onclick=\"loadDownloadData();i2b2.BiobankDatafile.queryAutoDropped(i2b2.CRC.view.downloadData.active_qm_id);\" type=\"button\" class=\"BiobankDatafile-button\" value=\"Proceed to the Download\">";
+errorsHash = $H(); //This hastable keeps {facility name, error message} pairs for all sites that returns error
+
+finalResultsArray = new Array([]); // This is a 2-D array. Keeps data in tabular format where the columns are the sites and rows are the category of results.This array wiil be used to create the CSV table easily.
+
+breakdownHash = $H(); //This hashtable will keep al breakdown categories in lowercase letters. This will help resolve case sensitivity issues for same categories
+ '<td style="color: darkblue; text-align: center; vertical-align: middle; font-size: 20px">Graph Results is not supported for this version</td>' +
+ '</tr>' +
+ '<tr style="background-color: white">' +
+ '<td style="color: darkblue; text-align: center; vertical-align: middle; font-size: 20px">of Internet Explorer. In order to display the graphs in </td>' +
+ '</tr>' +
+ '<tr style="background-color: white">' +
+ '<td style="color: darkblue; text-align: center; vertical-align: middle; font-size: 20px">Internet Explorer you will need to use version 11 or higher.</td>' +
description: "The SHRINE software is not running at the queried" +
" site. This error must be corrected at the queried site.Check network status or contact your local SHRINE administrator. For faster assistance, expand this window and provide all text below this line to your local SHRINE administrator.",
details: "There is a fatal syntax error in the remote site's" +
" shrine.conf or another .conf file. The remote site admin should check to make sure that there are no stray/missing quotes or brackets, and that URLs are entered correctly.",
- Beth Israel Deaconess Medical Center (BIDMC) medications are derived from the internal <a href="http://www.bidmc.org/MedicalEducation/Departments/Medicine/ResidencyinInternalMedicine/WhyBIDMC/WhatSetsUsApart.aspx" target="_blank">Provider Order Entry and Online Medical Record</a> systems.
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ Beth Israel Deaconess Medical Center (BIDMC) medications are derived from the internal <a href="http://www.bidmc.org/MedicalEducation/Departments/Medicine/ResidencyinInternalMedicine/WhyBIDMC/WhatSetsUsApart.aspx" target="_blank">Provider Order Entry and Online Medical Record</a> systems.
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h3>
- <a name="ChbMedSemantics">CHB Medications</a>
- </h3>
- <p>
- Children's Hospital Boston (CHB) medications are derived from ordered medications data for inpatient encounters, including clinic visits. This data is derived from an internal <em>Provider Order Entry</em> system.
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h3>
+ <a name="ChbMedSemantics">CHB Medications</a>
+ </h3>
+ <p>
+ Children's Hospital Boston (CHB) medications are derived from ordered medications data for inpatient encounters, including clinic visits. This data is derived from an internal <em>Provider Order Entry</em> system.
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- All local institutionals use ICD-9 vocabulary for diagnoses data. In addition, individual institution's diagnoses are derived from specific internal systems as described in this section.
- </p>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ All local institutionals use ICD-9 vocabulary for diagnoses data. In addition, individual institution's diagnoses are derived from specific internal systems as described in this section.
+ </p>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h3>
- <a name="PartnersDiagSemantics">BWH and MGH Diagnoses</a>
- </h3>
- <p>
- Diagnoses are organized into 22 major categories generally by body system, such as Digestive System, or by disease type, such as Infectious and Parasitic Diseases. Diagnoses data are based on the following:
- </p>
-
-<ul><li>ICD-9-CM codes derived from TSI or IDX</li>
-<li>COSTAR codes derived from OnCall problems identified as <em>diagnoses</em></li>
-<li>LMR codes derived from LMR problems identified as <em>diagnoses</em></li></ul>
-
- <p>
- LMR and OnCall codes and descriptions are developed locally. A number of analytic processes are performed to make the data as consistent and reliable as possible. If a provider described a diagnostic condition in several different ways, such as, for example, Upper Respiratory Infection, the analytic processes attempt to collapse all of the synonyms under one consistent code and description. If the LMR code for this common ailment is LPA1960, but it is described as <em>Upper Respiratory Infection</em> 79% of the time, as <em>URI</em> 19% of the time, and as <em>Cold</em> 3% of the time, these are reviewed manually reviewed, determined to be synonymous, and altered to a single description--Upper Respiratory Infection.
- </p>
-
- <p>
- In general, diagnostic ICD-9-CM coding for inpatient encounters is more accurate
-than for outpatient encounters due to the strict requirements involved in DRG billing for both diagnoses and procedures associated with an inpatient stay. In addition,
-discharge diagnoses or principal diagnoses often are better defined by the time patients' records are reviewed for billing. In contrast, outpatient billing tends to be less accurate on diagnostic codes. In addition, illness visits often are coded for signs and symptoms rather than a well-defined diagnosis, especially in the early stage of an episode of care.
- </p>
-
- <p>
- These groups in the diagnoses Terms view are of special interest:
- </p>
-
-
-<ul><li>Sign or Symptoms - These codes, comprising 780.xx through 789.xx., include presenting conditions as being febrile, or having abdominal tenderness or edema. </li>
-<li>E-Codes - Required for public reporting of accident or traumatic situations or adverse events from medical care. </li>
-<li>V-Codes - A special category for patient or family history of illness.</li></ul>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h3>
+ <a name="PartnersDiagSemantics">BWH and MGH Diagnoses</a>
+ </h3>
+ <p>
+ Diagnoses are organized into 22 major categories generally by body system, such as Digestive System, or by disease type, such as Infectious and Parasitic Diseases. Diagnoses data are based on the following:
+ </p>
+
+<ul><li>ICD-9-CM codes derived from TSI or IDX</li>
+<li>COSTAR codes derived from OnCall problems identified as <em>diagnoses</em></li>
+<li>LMR codes derived from LMR problems identified as <em>diagnoses</em></li></ul>
+
+ <p>
+ LMR and OnCall codes and descriptions are developed locally. A number of analytic processes are performed to make the data as consistent and reliable as possible. If a provider described a diagnostic condition in several different ways, such as, for example, Upper Respiratory Infection, the analytic processes attempt to collapse all of the synonyms under one consistent code and description. If the LMR code for this common ailment is LPA1960, but it is described as <em>Upper Respiratory Infection</em> 79% of the time, as <em>URI</em> 19% of the time, and as <em>Cold</em> 3% of the time, these are reviewed manually reviewed, determined to be synonymous, and altered to a single description--Upper Respiratory Infection.
+ </p>
+
+ <p>
+ In general, diagnostic ICD-9-CM coding for inpatient encounters is more accurate
+than for outpatient encounters due to the strict requirements involved in DRG billing for both diagnoses and procedures associated with an inpatient stay. In addition,
+discharge diagnoses or principal diagnoses often are better defined by the time patients' records are reviewed for billing. In contrast, outpatient billing tends to be less accurate on diagnostic codes. In addition, illness visits often are coded for signs and symptoms rather than a well-defined diagnosis, especially in the early stage of an episode of care.
+ </p>
+
+ <p>
+ These groups in the diagnoses Terms view are of special interest:
+ </p>
+
+
+<ul><li>Sign or Symptoms - These codes, comprising 780.xx through 789.xx., include presenting conditions as being febrile, or having abdominal tenderness or edema. </li>
+<li>E-Codes - Required for public reporting of accident or traumatic situations or adverse events from medical care. </li>
+<li>V-Codes - A special category for patient or family history of illness.</li></ul>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h3>
- <a name="PartnersMedSemantics">BWH and MGH Medications</a>
- </h3>
- <p>
- Medications are derived from <i>TSI</i>, the <a href="http://www.partners.org/cird/StaffPrj.asp?cBox=CurrProj&prAb=LMR" target="_blank">Longitudinal Medical Record</a> (LMR), and <i>OnCall</i> systems.
- </p>
-
- <p>
- Medications from TSI are associated with hospital encounters only. These comprise mainly inpatient status patients, but also include emergency department, surgical day care (SDC), or observation status patients. Hospital-based patient medications for BWH include inpatients, emergency room, observation stays, and newborns. For MGH, medications include inpatients, dialysis, observation stays, surgical day care, newborns and some research patients.
- </p>
-
- <p>
- Medications from the LMR are associated with outpatient encounters, while the codes are defined locally. A number of analytic processes are performed to make the data as consistent and reliable as possible. If a provider describes a medication in several different ways, such as, for example, aspirin, the analytic processes applied attempt to collapse all of the synonyms under one consistent code and description. If the LMR code for this common medication is 3644, but it is described as <em>Aspirin</em> 79% of the time, as <em>ASA</em> 19% of the time, and as <em>Bayer</em> 3% of the time, these are reviewed manually, determined to be synonymous, and altered to a single descriptionâAspirin.
- </p>
-
- <p>
- Medications from the OnCall system are associated with outpatient encounters within MGH. The codes are in the <a href="http://www.clinfowiki.org/wiki/index.php/COmputer_STored_Ambulatory_Record_(COSTAR)" target="_blank">COSTAR</a> coding system.
- Hospital encounters (inpatient, emergency, observation, dialysis, newborns, research patients)
- </p>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- LMR
- </p>
- </td>
- <td>
- <p>
- BWH, MGH
- </p>
- </td>
- <td>
- <p>
- Outpatient encounters
- </p>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- COSTAR
- </p>
- </td>
- <td>
- <p>
- MGH
- </p>
- </td>
- <td>
- <p>
- Outpatient encounters
- </p>
- </td>
- </tr>
- </tbody>
- </table>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h3>
+ <a name="PartnersMedSemantics">BWH and MGH Medications</a>
+ </h3>
+ <p>
+ Medications are derived from <i>TSI</i>, the <a href="http://www.partners.org/cird/StaffPrj.asp?cBox=CurrProj&prAb=LMR" target="_blank">Longitudinal Medical Record</a> (LMR), and <i>OnCall</i> systems.
+ </p>
+
+ <p>
+ Medications from TSI are associated with hospital encounters only. These comprise mainly inpatient status patients, but also include emergency department, surgical day care (SDC), or observation status patients. Hospital-based patient medications for BWH include inpatients, emergency room, observation stays, and newborns. For MGH, medications include inpatients, dialysis, observation stays, surgical day care, newborns and some research patients.
+ </p>
+
+ <p>
+ Medications from the LMR are associated with outpatient encounters, while the codes are defined locally. A number of analytic processes are performed to make the data as consistent and reliable as possible. If a provider describes a medication in several different ways, such as, for example, aspirin, the analytic processes applied attempt to collapse all of the synonyms under one consistent code and description. If the LMR code for this common medication is 3644, but it is described as <em>Aspirin</em> 79% of the time, as <em>ASA</em> 19% of the time, and as <em>Bayer</em> 3% of the time, these are reviewed manually, determined to be synonymous, and altered to a single descriptionâAspirin.
+ </p>
+
+ <p>
+ Medications from the OnCall system are associated with outpatient encounters within MGH. The codes are in the <a href="http://www.clinfowiki.org/wiki/index.php/COmputer_STored_Ambulatory_Record_(COSTAR)" target="_blank">COSTAR</a> coding system.
+ Hospital encounters (inpatient, emergency, observation, dialysis, newborns, research patients)
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <p>
+ LMR
+ </p>
+ </td>
+ <td>
+ <p>
+ BWH, MGH
+ </p>
+ </td>
+ <td>
+ <p>
+ Outpatient encounters
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <p>
+ COSTAR
+ </p>
+ </td>
+ <td>
+ <p>
+ MGH
+ </p>
+ </td>
+ <td>
+ <p>
+ Outpatient encounters
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252797232">Basics</a>
- </h1>
- <p>
- SHRINE currently makes patient demographics, diagnoses, medications, and a sample of laboratory results data available to be searched. SHRINE Core
- ontology is a collection of terms that describe these data and can be used to construct queries. The terms are arranged into a hierarchy for easy
- navigation; the ontology can be searched for a particular terms as well.
- </p>
- <p>
- A standard terminology was selected where possible to represent each type of data accessible through use of the system. A terminology was modified as
- necessary to fit the requirements of SHRINE.
- </p>
- <h2>
- <a name="_Toc252797232">Terminology</a>
- </h2>
- <p>
- The following standard terminology provides the baseline for the Core ontology:
- </p>
- <ul><li>
- Demographics – Patient demographic data available at each participating SHRINE hospital include:
- <ul>
- <li>
- Age
- </li>
- <li>
- Gender – Health Level Seven International (HL7) <a href="http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/AdministrativeGender.htm" title="HL7 Administrative Gender" target="_blank">Administrative Gender</a>
- </li>
- <li>
- Language – International Organization for Standardization (ISO) <a href="http://www.iso.org/iso/catalogue_detail?csnumber=22109" title="ISO 639-1" target="_blank">ISO 639-1</a>
- Race and Ethnicity – Centers for Disease Control and Prevention (CDC) <a href="http://www.cdc.gov/nedss/DataModels/index.html" title="CDC Race and Ethnicity" target="_blank">Race and Ethnicity Code Sets</a>
- </li></ul></li>
- <li>
- Diagnoses – Diagnoses are identified by National Center for Health Statistics (NCHS) <a href="http://www.cdc.gov/nchs/about/otheract/icd9/abticd9.htm" title="ICD-9-CM" target="_blank">ICD-9-CM</a> standards and Clinical Classification
- Medications – Medications are identified by the Unified Medical Language System (UMLS) <a href="http://www.nlm.nih.gov/research/umls/rxnorm/" title="RxNorm" target="_blank">RxNorm</a> (Ingredient) and the Veterans Administration
- (VA) National Drug File Reference Terminology (<a href="http://bioportal.nci.nih.gov/ncbo/faces/pages/ontology_details.xhtml?ontology_display_name=National%20Drug%20File%20-%20Reference%20Terminology" title="NDR-RT" target="_blank">NDF-RT</a>) hierarchy.
- </li>
- <li>
- Lab Tests – Data on lab tests is derived from the Clinical Data Repository (CDR). Data are identified by Logical Observation Identifiers
- Names and Codes (<a href="http://loinc.org/" title="LOINC" target="_blank">LOINC</a>) and Partners HealthCare System.
- </li></ul>
- <p>
- The Core ontology was constructed following recommendations of relevant government and private sector bodies using a pragmatic approach. It is a static snapshot of underlying standards. As they change (for example, there are regular updates of ICD-9-CM and RxNorm), we
- expect that the Core ontology will follow after a reasonable delay to accommodate the effort of introducing the changes, resolving issues and completing quality
- assurance processes.
- </p>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252797232">Basics</a>
+ </h1>
+ <p>
+ SHRINE currently makes patient demographics, diagnoses, medications, and a sample of laboratory results data available to be searched. SHRINE Core
+ ontology is a collection of terms that describe these data and can be used to construct queries. The terms are arranged into a hierarchy for easy
+ navigation; the ontology can be searched for a particular terms as well.
+ </p>
+ <p>
+ A standard terminology was selected where possible to represent each type of data accessible through use of the system. A terminology was modified as
+ necessary to fit the requirements of SHRINE.
+ </p>
+ <h2>
+ <a name="_Toc252797232">Terminology</a>
+ </h2>
+ <p>
+ The following standard terminology provides the baseline for the Core ontology:
+ </p>
+ <ul><li>
+ Demographics – Patient demographic data available at each participating SHRINE hospital include:
+ <ul>
+ <li>
+ Age
+ </li>
+ <li>
+ Gender – Health Level Seven International (HL7) <a href="http://www.hl7.org/v3ballot/html/infrastructure/vocabulary/AdministrativeGender.htm" title="HL7 Administrative Gender" target="_blank">Administrative Gender</a>
+ </li>
+ <li>
+ Language – International Organization for Standardization (ISO) <a href="http://www.iso.org/iso/catalogue_detail?csnumber=22109" title="ISO 639-1" target="_blank">ISO 639-1</a>
+ Race and Ethnicity – Centers for Disease Control and Prevention (CDC) <a href="http://www.cdc.gov/nedss/DataModels/index.html" title="CDC Race and Ethnicity" target="_blank">Race and Ethnicity Code Sets</a>
+ </li></ul></li>
+ <li>
+ Diagnoses – Diagnoses are identified by National Center for Health Statistics (NCHS) <a href="http://www.cdc.gov/nchs/about/otheract/icd9/abticd9.htm" title="ICD-9-CM" target="_blank">ICD-9-CM</a> standards and Clinical Classification
+ Medications – Medications are identified by the Unified Medical Language System (UMLS) <a href="http://www.nlm.nih.gov/research/umls/rxnorm/" title="RxNorm" target="_blank">RxNorm</a> (Ingredient) and the Veterans Administration
+ (VA) National Drug File Reference Terminology (<a href="http://bioportal.nci.nih.gov/ncbo/faces/pages/ontology_details.xhtml?ontology_display_name=National%20Drug%20File%20-%20Reference%20Terminology" title="NDR-RT" target="_blank">NDF-RT</a>) hierarchy.
+ </li>
+ <li>
+ Lab Tests – Data on lab tests is derived from the Clinical Data Repository (CDR). Data are identified by Logical Observation Identifiers
+ Names and Codes (<a href="http://loinc.org/" title="LOINC" target="_blank">LOINC</a>) and Partners HealthCare System.
+ </li></ul>
+ <p>
+ The Core ontology was constructed following recommendations of relevant government and private sector bodies using a pragmatic approach. It is a static snapshot of underlying standards. As they change (for example, there are regular updates of ICD-9-CM and RxNorm), we
+ expect that the Core ontology will follow after a reasonable delay to accommodate the effort of introducing the changes, resolving issues and completing quality
+ assurance processes.
+ </p>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252797233">Availability and Maintenance</a>
- </h2>
- <p>
- Data in the SHRINE system are available from January 1 and are refreshed regularly. Scheduled maintenance of the Core ontology
- is not defined at that time.
- </p>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252797233">Availability and Maintenance</a>
+ </h2>
+ <p>
+ Data in the SHRINE system are available from January 1 and are refreshed regularly. Scheduled maintenance of the Core ontology
+ is not defined at that time.
+ </p>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- Initial version uses Partners HealthCare System coding standard
- </p>
- </td>
- </tr>
- </tbody>
- </table>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ Initial version uses Partners HealthCare System coding standard
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- CDC <a href="http://www.cdc.gov/nedss/DataModels/index.html" target="_blank">Race & Ethnicity Code Sets</a>
- </p>
- </td>
- <td>
- <p>
- Yes
- </p>
- </td>
- <td>
- <p>
- - Other Race (R9)
- <br/>
- + R9: Unknown Race
- </p>
- </td>
- <td>
- <p>
- C1561446
- </p>
- </td>
- </tr>
- <tr>
- <td>
- <p>
- Ethnicity
- </p>
- </td>
- <td>
- <p>
- N/A
- </p>
- </td>
- <td>
- <p>
- Yes
- </p>
- </td>
- <td>
- <p>
- + E9: Unknown Ethnicity
- <br/>
- see Notes for E2=!E1
- </p>
- </td>
- <td>
- <p>
- C1553821
- </p>
- </td>
- </tr>
- </tbody>
- </table>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ CDC <a href="http://www.cdc.gov/nedss/DataModels/index.html" target="_blank">Race & Ethnicity Code Sets</a>
+ </p>
+ </td>
+ <td>
+ <p>
+ Yes
+ </p>
+ </td>
+ <td>
+ <p>
+ - Other Race (R9)
+ <br/>
+ + R9: Unknown Race
+ </p>
+ </td>
+ <td>
+ <p>
+ C1561446
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <p>
+ Ethnicity
+ </p>
+ </td>
+ <td>
+ <p>
+ N/A
+ </p>
+ </td>
+ <td>
+ <p>
+ Yes
+ </p>
+ </td>
+ <td>
+ <p>
+ + E9: Unknown Ethnicity
+ <br/>
+ see Notes for E2=!E1
+ </p>
+ </td>
+ <td>
+ <p>
+ C1553821
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252797237">Diagnoses Standards</a>
- </h2>
- <p>
- The <a href="http://www.hcup-us.ahrq.gov/toolssoftware/ccs/ccs.jsp" target="_blank">Clinical Classifications Software</a> for ICD-9-CM standard is used for diagnoses data.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252797237">Diagnoses Standards</a>
+ </h2>
+ <p>
+ The <a href="http://www.hcup-us.ahrq.gov/toolssoftware/ccs/ccs.jsp" target="_blank">Clinical Classifications Software</a> for ICD-9-CM standard is used for diagnoses data.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h3>
- <a name="_Toc252797239">Site to RxNorm Associations Type Mapping</a>
- </h3>
- <p>
- For the ingredient name (IN) and trade name (BN), the BN is derived from <a href="http://www.fda.gov/Drugs/InformationOnDrugs/ucm142438.htm" title="FDA Trade Name" target="_blank">FDA Trade Name</a>, and is the same as IN in most cases. In cases where they
- differ, such as extended release variants with something similar to <em>XL</em> in the trade name, that component of the IN is not in the BN.
- </p>
- <p>
- A diagram indicates the datatype relationships for medication data.
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h3>
+ <a name="_Toc252797239">Site to RxNorm Associations Type Mapping</a>
+ </h3>
+ <p>
+ For the ingredient name (IN) and trade name (BN), the BN is derived from <a href="http://www.fda.gov/Drugs/InformationOnDrugs/ucm142438.htm" title="FDA Trade Name" target="_blank">FDA Trade Name</a>, and is the same as IN in most cases. In cases where they
+ differ, such as extended release variants with something similar to <em>XL</em> in the trade name, that component of the IN is not in the BN.
+ </p>
+ <p>
+ A diagram indicates the datatype relationships for medication data.
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h3>
- <a name="_Toc252797240">Site to NDR-RT Mapping</a>
- </h3>
- <p>
- SHRINE uses the OWL version of <a href="http://bioportal.nci.nih.gov/ncbo/faces/pages/ontology_details.xhtml?ontology_display_name=National%20Drug%20File%20-%20Reference%20Terminology" title="NDR-RT" target="_blank">NDF-RT</a> VA Class and VA Product hierarchies for medications data, from the May 12, 2009 NDF-RF XML distribution.
- </p>
- <p>
- The Veterans Administration (VA) Product Component is classified consistently. Any drug or ingredient on the US market has a corresponding VA Product
- Component. Note that there are numerous ingredients that are not part of drugs on the market, such as reagents or preservatives, which result in occasional classification inconsistencies.
- </p>
- <p>
- For NDR-RT mapping of precise versus base ingredients in RxNorm, base ingredients comprise those without salt. NDF-RT links to base ingredient unless a
- salt makes a clinical difference, such as Mg Citrate compared with Mg Oxide.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h3>
+ <a name="_Toc252797240">Site to NDR-RT Mapping</a>
+ </h3>
+ <p>
+ SHRINE uses the OWL version of <a href="http://bioportal.nci.nih.gov/ncbo/faces/pages/ontology_details.xhtml?ontology_display_name=National%20Drug%20File%20-%20Reference%20Terminology" title="NDR-RT" target="_blank">NDF-RT</a> VA Class and VA Product hierarchies for medications data, from the May 12, 2009 NDF-RF XML distribution.
+ </p>
+ <p>
+ The Veterans Administration (VA) Product Component is classified consistently. Any drug or ingredient on the US market has a corresponding VA Product
+ Component. Note that there are numerous ingredients that are not part of drugs on the market, such as reagents or preservatives, which result in occasional classification inconsistencies.
+ </p>
+ <p>
+ For NDR-RT mapping of precise versus base ingredients in RxNorm, base ingredients comprise those without salt. NDF-RT links to base ingredient unless a
+ salt makes a clinical difference, such as Mg Citrate compared with Mg Oxide.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252797241">Labs Standards</a>
- </h2>
- <p>
- Lab data in the SHRINE Core ontology are encoded to Partners HealthCare System coding standard. Mapping of Labs to SHRINE data supports the following
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252797241">Labs Standards</a>
+ </h2>
+ <p>
+ Lab data in the SHRINE Core ontology are encoded to Partners HealthCare System coding standard. Mapping of Labs to SHRINE data supports the following
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- Each participating institution's data is loaded with native coding schemes used by local information technology solutions. To understand SHRINE queries
- issued using terms from the Core ontology, a mapping is created and maintained for each institution that enables a translation from SHRINE Core
- ontology term to a corresponding local term, enabling the capability to perform a query at that institution.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ Each participating institution's data is loaded with native coding schemes used by local information technology solutions. To understand SHRINE queries
+ issued using terms from the Core ontology, a mapping is created and maintained for each institution that enables a translation from SHRINE Core
+ ontology term to a corresponding local term, enabling the capability to perform a query at that institution.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
-<p>This guide describes the SHRINE Core ontology, including terminology, composition, source systems and maintenance schedules, and data descriptions.</p>
-
-<p>Harvard Catalyst provides a full set of guides to support use of SHRINE:</p>
-
- <ul>
- <li>
- <em><a href="../UG_Help_Files/index.htm" title="SHRINE User Guide">SHRINE User Guide</a></em>
- – Use the Query Tool to locate patient populations.
- – Construct optimum queries by using the Query Tool.
- </li>
- <li>
- <em><a href="index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
- – Understand the terms available for query.
- </li>
- </ul>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+<p>This guide describes the SHRINE Core ontology, including terminology, composition, source systems and maintenance schedules, and data descriptions.</p>
+
+<p>Harvard Catalyst provides a full set of guides to support use of SHRINE:</p>
+
+ <ul>
+ <li>
+ <em><a href="../UG_Help_Files/index.htm" title="SHRINE User Guide">SHRINE User Guide</a></em>
+ – Use the Query Tool to locate patient populations.
+ – Construct optimum queries by using the Query Tool.
+ </li>
+ <li>
+ <em><a href="index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
+ – Understand the terms available for query.
+ </li>
+ </ul>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
- <h1>
- <a name="_Toc252370633">Query Topics</a>
-
- </h1>
- <p>
- The Data Steward maintains Query Topic requests, which grant users access to the SHRINE query topics. You must have an approved topic to run a query.
- </p>
- <h2>
- <a name="_Toc252370633">Data Steward</a>
- </h2>
- <p>
- The Data Steward approves query topics and regularly reviews use of the Query Tool to ensure that no suspicious or unapproved examination of data is
- performed.
- </p>
- <p>
- You can access the Data Steward directly in a web browser at the following address, and log in by using your eCommons account credentials:
- Or, you can access the Data Steward from within the SHRINE Query Tool. Click Request New Topic in the tool view to open the Data Steward in a new window.
- </p>
-
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+ <h1>
+ <a name="_Toc252370633">Query Topics</a>
+
+ </h1>
+ <p>
+ The Data Steward maintains Query Topic requests, which grant users access to the SHRINE query topics. You must have an approved topic to run a query.
+ </p>
+ <h2>
+ <a name="_Toc252370633">Data Steward</a>
+ </h2>
+ <p>
+ The Data Steward approves query topics and regularly reviews use of the Query Tool to ensure that no suspicious or unapproved examination of data is
+ performed.
+ </p>
+ <p>
+ You can access the Data Steward directly in a web browser at the following address, and log in by using your eCommons account credentials:
+ Or, you can access the Data Steward from within the SHRINE Query Tool. Click Request New Topic in the tool view to open the Data Steward in a new window.
+ </p>
+
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370634">Guidelines for Query Topics</a>
- </h2>
- <p>
- Topics for which you might choose to use the Query Tool include:
- </p>
- <ul>
- <li>
- Generating new research hypotheses
- </li>
- <li>
- Conducting research requiring large sample sizes not easily available at any single institution
- </li>
- <li>
- Preparing grant applications that would benefit from characterization of a potential research cohort
- </li>
- <li>
- Identifying potential cohorts for clinical trials
- </li>
- </ul>
-
- <p>
- Individual queries are subject to review by the Data Steward for appropriate usage. Query histories are logged and audited on a regular
- basis to ensure that there are no violations of the Terms of Access Agreement. If the Data Steward suspects inappropriate use of the Query Tool to
- investigate patient data the steward will suspend the user account under which that use occurred.
- </p>
- <p>
- <strong>Note</strong>: Violation of the Terms of Access Agreement results in a misconduct review by your institution and, if appropriate, by Harvard Medical School.
- </p>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370634">Guidelines for Query Topics</a>
+ </h2>
+ <p>
+ Topics for which you might choose to use the Query Tool include:
+ </p>
+ <ul>
+ <li>
+ Generating new research hypotheses
+ </li>
+ <li>
+ Conducting research requiring large sample sizes not easily available at any single institution
+ </li>
+ <li>
+ Preparing grant applications that would benefit from characterization of a potential research cohort
+ </li>
+ <li>
+ Identifying potential cohorts for clinical trials
+ </li>
+ </ul>
+
+ <p>
+ Individual queries are subject to review by the Data Steward for appropriate usage. Query histories are logged and audited on a regular
+ basis to ensure that there are no violations of the Terms of Access Agreement. If the Data Steward suspects inappropriate use of the Query Tool to
+ investigate patient data the steward will suspend the user account under which that use occurred.
+ </p>
+ <p>
+ <strong>Note</strong>: Violation of the Terms of Access Agreement results in a misconduct review by your institution and, if appropriate, by Harvard Medical School.
+ </p>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370635">Sample Query Topic</a>
- </h2>
- <p>
- Following is a sample of how you might describe your query request to the Data Steward:
- </p>
- <blockquote>
- Query Topic: Formulating hypotheses
- <br />
- <br />
- Literature shows that patients diagnosed with inflammatory bowel disease are at higher risk for cancers of the colon. It is unclear why. I would like
- to use the SHRINE system to try to identify characteristics of IBD patients who have a co-morbid diagnosis of colon cancer:
- <br />
- <ul>
- <li>
- Quantify the number of patients in the Boston area with a diagnosis of Inflammatory Bowel Disease and Colon Cancer
- </li>
- <li>
- Identify how many patient were treated at each participating institution
- </li>
- <li>
- Obtain breakdown of patients (by gender) who are treated with 5-ASA’s, steroids and/or biologics
- </li>
- <li>
- Obtain breakdown of patients who are considered active or in remission for their IBD
- </li>
- </ul>
- </blockquote>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370635">Sample Query Topic</a>
+ </h2>
+ <p>
+ Following is a sample of how you might describe your query request to the Data Steward:
+ </p>
+ <blockquote>
+ Query Topic: Formulating hypotheses
+ <br />
+ <br />
+ Literature shows that patients diagnosed with inflammatory bowel disease are at higher risk for cancers of the colon. It is unclear why. I would like
+ to use the SHRINE system to try to identify characteristics of IBD patients who have a co-morbid diagnosis of colon cancer:
+ <br />
+ <ul>
+ <li>
+ Quantify the number of patients in the Boston area with a diagnosis of Inflammatory Bowel Disease and Colon Cancer
+ </li>
+ <li>
+ Identify how many patient were treated at each participating institution
+ </li>
+ <li>
+ Obtain breakdown of patients (by gender) who are treated with 5-ASA’s, steroids and/or biologics
+ </li>
+ <li>
+ Obtain breakdown of patients who are considered active or in remission for their IBD
+ </li>
+ </ul>
+ </blockquote>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252370637">Query Construction</a>
- </h1>
- <p>
- Two icons at the top-right corner of the Query Tool view provide the following options:
- </p>
- <ul>
- <li>
- Show Options icon – Click this icon at the top-right corner of the view to Select the Maximum Time to Wait for XML Response (in seconds). This value is the length of time that SHRINE will continue to process a query. <br />
-If a query does not process completely within period, only those results that completed processing within an institution are returned.
-
- </li>
- <li>
- Toggle Zoom icon – Click the Toggle Zoom icon at the top-right corner of the view to toggle between expanded and compressed view sizes.
- </li>
- </ul>
- <h2>
- <a name="_Toc252370637">Tool Logic</a>
- </h2>
- <p>
- You can add terms within a Group to apply OR logic, and use multiple Groups to define your selection by using AND logic. Tool options function as follows:
- </p>
- <ul>
- <li>
- Query Name – This field remains blank. You cannot edit this field.
- </li>
- <li>
- Group columns – Query groups represent a set of patients defined by the terms within the group and any constraints applied to that group.
- Drag terms into one or more Group fields to narrow the patient cohort for which you are querying.
- </li>
- <li>
- Constrain group options – Define criteria by which you can limit all terms within a group:
- <ul>
- <li>
- Dates – Set a date range within which the terms associated with patients must fall.
- </li>
- <li>
- Occurs > 0x – Set the number of occurrences for which patients within the query group must be associated with a term.
- </li>
- <li>
- Exclude – Exclude all patients that meet the criteria of the query group.
- </li>
- </ul>
- Click the constraint a second time to remove it.
- <br />
- <strong>Note</strong>: Not all terms accept all constraints.
- </li>
- <li>
- Term right-click menu – Right-click a term to set a specific value by which to query a term, or to delete the term from the query group.
- </li>
- <li>
- Select a Topic pull-down list – Select the query topic to which this query relates, as approved by the Data Steward.
- </li>
- <li>
- Info button – View the description of that topic as provided to the Data Steward.
- </li>
- <li>
- Request New Topic button – Access the Data Steward in a new window.
- </li>
- <li>
- Run Query button – Start the query process.
- </li>
- <li>
- New Query button – Clear the Query Tool fields and settings and start a new query.
- </li>
- <li>
- New Group button – Add additional terms and values to your query if needed.
- </li>
- <li>
- Group page controls – Navigate to additional groups if you add new groups.
- </li>
- </ul>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252370637">Query Construction</a>
+ </h1>
+ <p>
+ Two icons at the top-right corner of the Query Tool view provide the following options:
+ </p>
+ <ul>
+ <li>
+ Show Options icon – Click this icon at the top-right corner of the view to Select the Maximum Time to Wait for XML Response (in seconds). This value is the length of time that SHRINE will continue to process a query. <br />
+If a query does not process completely within period, only those results that completed processing within an institution are returned.
+
+ </li>
+ <li>
+ Toggle Zoom icon – Click the Toggle Zoom icon at the top-right corner of the view to toggle between expanded and compressed view sizes.
+ </li>
+ </ul>
+ <h2>
+ <a name="_Toc252370637">Tool Logic</a>
+ </h2>
+ <p>
+ You can add terms within a Group to apply OR logic, and use multiple Groups to define your selection by using AND logic. Tool options function as follows:
+ </p>
+ <ul>
+ <li>
+ Query Name – This field remains blank. You cannot edit this field.
+ </li>
+ <li>
+ Group columns – Query groups represent a set of patients defined by the terms within the group and any constraints applied to that group.
+ Drag terms into one or more Group fields to narrow the patient cohort for which you are querying.
+ </li>
+ <li>
+ Constrain group options – Define criteria by which you can limit all terms within a group:
+ <ul>
+ <li>
+ Dates – Set a date range within which the terms associated with patients must fall.
+ </li>
+ <li>
+ Occurs > 0x – Set the number of occurrences for which patients within the query group must be associated with a term.
+ </li>
+ <li>
+ Exclude – Exclude all patients that meet the criteria of the query group.
+ </li>
+ </ul>
+ Click the constraint a second time to remove it.
+ <br />
+ <strong>Note</strong>: Not all terms accept all constraints.
+ </li>
+ <li>
+ Term right-click menu – Right-click a term to set a specific value by which to query a term, or to delete the term from the query group.
+ </li>
+ <li>
+ Select a Topic pull-down list – Select the query topic to which this query relates, as approved by the Data Steward.
+ </li>
+ <li>
+ Info button – View the description of that topic as provided to the Data Steward.
+ </li>
+ <li>
+ Request New Topic button – Access the Data Steward in a new window.
+ </li>
+ <li>
+ Run Query button – Start the query process.
+ </li>
+ <li>
+ New Query button – Clear the Query Tool fields and settings and start a new query.
+ </li>
+ <li>
+ New Group button – Add additional terms and values to your query if needed.
+ </li>
+ <li>
+ Group page controls – Navigate to additional groups if you add new groups.
+ </li>
+ </ul>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370638">Constraints</a>
- </h2>
- <p>
- At the top of each group are three criteria by which you can limit all query terms within that group:
- </p>
- <ul>
- <li>
- Dates – Set a date range to query terms associated with patients for that period.
- <br/>
- For example, a constraint setting of <em>Diagnosis of Asthma for <date range></em> returns all patients diagnosed with asthma within the
- specified date range.
- </li>
- <li>
- Occurs > 0x – Set the number of times that patients must be associated with the query term.
- <br />
- For example, a constraint setting of <em>Diagnosis of Fracture of ankle Occurs > 2x</em> returns all patients diagnosed with a broken an ankle at
- least twice.
- </li>
- <li>
- Exclude – Exclude patients meeting the specified term or terms.
- <br />
- For example, <em>exclude all patients 35 years old</em> returns all patients who are not 35 years old.
- </li>
- </ul>
-
- <p>
- To remove a constraint, click the constraint again and remove the check box from the value that you set. For an exclusion constraint, simply click
- Exclude again to remove it.
- </p>
- <p>
- <strong>Note</strong>: Not all terms accept all constraints. For example, a demographic gender term of <em>Female</em> does not accept a date range constraint.
- </p>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370638">Constraints</a>
+ </h2>
+ <p>
+ At the top of each group are three criteria by which you can limit all query terms within that group:
+ </p>
+ <ul>
+ <li>
+ Dates – Set a date range to query terms associated with patients for that period.
+ <br/>
+ For example, a constraint setting of <em>Diagnosis of Asthma for <date range></em> returns all patients diagnosed with asthma within the
+ specified date range.
+ </li>
+ <li>
+ Occurs > 0x – Set the number of times that patients must be associated with the query term.
+ <br />
+ For example, a constraint setting of <em>Diagnosis of Fracture of ankle Occurs > 2x</em> returns all patients diagnosed with a broken an ankle at
+ least twice.
+ </li>
+ <li>
+ Exclude – Exclude patients meeting the specified term or terms.
+ <br />
+ For example, <em>exclude all patients 35 years old</em> returns all patients who are not 35 years old.
+ </li>
+ </ul>
+
+ <p>
+ To remove a constraint, click the constraint again and remove the check box from the value that you set. For an exclusion constraint, simply click
+ Exclude again to remove it.
+ </p>
+ <p>
+ <strong>Note</strong>: Not all terms accept all constraints. For example, a demographic gender term of <em>Female</em> does not accept a date range constraint.
+ </p>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370639">Term Values</a>
- </h2>
- <p>
- To set a specific value by which to query a term, right-click the term in the Query Tool group and select Set Value.
- </p>
- <p>
- The <em>Choose value of <term></em> dialog box appears. Use this dialog to set specific values by which to query. Value options vary depending on the term
- you selected. Click OK to set the query value, or click Cancel to accept the default value.
- </p>
- <p>
-If you change the units of a term when you set a value, note that SHRINE returns the results in the default units, not the units that you selected for your query value.
- </p>
- <p>
- <strong>Note</strong>: Not every term offers the option to set a value limiter.
- </p>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370639">Term Values</a>
+ </h2>
+ <p>
+ To set a specific value by which to query a term, right-click the term in the Query Tool group and select Set Value.
+ </p>
+ <p>
+ The <em>Choose value of <term></em> dialog box appears. Use this dialog to set specific values by which to query. Value options vary depending on the term
+ you selected. Click OK to set the query value, or click Cancel to accept the default value.
+ </p>
+ <p>
+If you change the units of a term when you set a value, note that SHRINE returns the results in the default units, not the units that you selected for your query value.
+ </p>
+ <p>
+ <strong>Note</strong>: Not every term offers the option to set a value limiter.
+ </p>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm">Results: Query Status View</a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370640">Query Optimization</a>
- </h2>
- <p>
- Tips for optimizing your query include the following:
- </p>
- <ul>
- <li>
- Select the most-limiting terms first.
- <br/>
- For example, demographic data is broader in scope than diagnoses or lab values. Therefore, if you select your diagnoses or lab value terms first
- and then select your demographic terms, SHRINE returns your query results more quickly.
- </li>
- <li>
- Queries that include lab values require a longer processing time that diagnoses or medications.
- <br />
- Consider including either diagnoses or medication
- terms in your first groups before adding a lab test term to your query.
- </li>
- <li>
-When a term category maps to more than 120 specific terms, there are too many values to process and you cannot use the full category in your query. This is an indication that broader terms and multiple terms process more slowly than narrow or fewer terms. You might consider running multiple queries with simpler criteria in place of one complex query.
- </li>
- </ul>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm">Results: Query Status View</a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370640">Query Optimization</a>
+ </h2>
+ <p>
+ Tips for optimizing your query include the following:
+ </p>
+ <ul>
+ <li>
+ Select the most-limiting terms first.
+ <br/>
+ For example, demographic data is broader in scope than diagnoses or lab values. Therefore, if you select your diagnoses or lab value terms first
+ and then select your demographic terms, SHRINE returns your query results more quickly.
+ </li>
+ <li>
+ Queries that include lab values require a longer processing time that diagnoses or medications.
+ <br />
+ Consider including either diagnoses or medication
+ terms in your first groups before adding a lab test term to your query.
+ </li>
+ <li>
+When a term category maps to more than 120 specific terms, there are too many values to process and you cannot use the full category in your query. This is an indication that broader terms and multiple terms process more slowly than narrow or fewer terms. You might consider running multiple queries with simpler criteria in place of one complex query.
+ </li>
+ </ul>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370641.htm"><strong><em>Results: Query Status View</em></strong></a>
- </p>
-
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
-
- <h1>
- <a name="_Toc252370641">Results: Query Status View</a>
- </h1>
- <p>
- The results of your query appear in the Query Status view. Information provided includes:
- </p>
- <ul>
- <li>
- Query Name
- </li>
- <li>
- Elapsed execution time
- </li>
- <li>
- Aggregated Query Results from participating hospitals
- </li>
- </ul>
- <p>
- If your query returned between zero (0) and 10 patients, your results display as <em>None</em>.
- </p>
- <p>
- The results are time and date stamped.
- </p>
- <p>
- <strong>Note</strong>: When you log out of SHRINE, your results are no longer available.
- </p>
-</td>
-</tr>
-</table>
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370641.htm"><strong><em>Results: Query Status View</em></strong></a>
+ </p>
+
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+
+ <h1>
+ <a name="_Toc252370641">Results: Query Status View</a>
+ </h1>
+ <p>
+ The results of your query appear in the Query Status view. Information provided includes:
+ </p>
+ <ul>
+ <li>
+ Query Name
+ </li>
+ <li>
+ Elapsed execution time
+ </li>
+ <li>
+ Aggregated Query Results from participating hospitals
+ </li>
+ </ul>
+ <p>
+ If your query returned between zero (0) and 10 patients, your results display as <em>None</em>.
+ </p>
+ <p>
+ The results are time and date stamped.
+ </p>
+ <p>
+ <strong>Note</strong>: When you log out of SHRINE, your results are no longer available.
+ </p>
+</td>
+</tr>
+</table>
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- – Construct optimum queries by using the Query Tool.
- </li>
- <li>
- <em><a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
- – Understand the terms available for query.
- </li>
- </ul>
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ – Construct optimum queries by using the Query Tool.
+ </li>
+ <li>
+ <em><a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
+ – Understand the terms available for query.
+ </li>
+ </ul>
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252370683">Basics</a>
- </h1>
- <p>
- This topic describes basic functions and requirements associated with the SHRINE system.
- </p>
- <h2>
- <a name="_Toc252370683">Requirements</a>
- </h2>
- <p>
- You need the following to use SHRINE:
- </p>
- <ul><li>
- Meet the criteria required to register for SHRINE use through your local institution – You must be a Harvard Medical School faculty member appointed at or above the level of
- Instructor and employed by one of the participating SHRINE hospitals:
- <ul>
- <li>Beth Israel Deaconess Medical Center (BIDMC)</li>
- <li>Brigham and Women's Hospital (BWH)</li>
- <li>Children's Hospital Boston (CHB)</li>
- <li>Massachusetts General Hospital (MGH)</li></ul>
- In this case, <em>employed by</em> means that your
- paycheck is generated by that institution.
- <br/>
- When you satisfy these criteria, your local institution gives you an account with access to the SHRINE system.
- <br />
- If you are an instructor or above at Harvard University who is <em>not</em> employed at a participating hospital but you collaborate with a SHRINE member who is, you may access the data indirectly through that relationship. Your
- collaborator must be in the medical specialty of your interest and only your collaborator may initiate a data query.
- </li>
- <li>
- Confirm your eCommons account – To log in to the Data Steward component of SHRINE and submit a <em>Query Topic</em> request, you use your eCommons account credentials.
- </li>
- <li>
- Submit a Query Topic for approval – Before you can query any data, you must describe how you intend to use the system to support your research. For
- example, you might use SHRINE to develop preliminary data for a grant proposal. IRB approval is <em>not</em> required to query data; the Data Steward approves Query
- Topic requests based on ethical validity, not scientific objectives.
- </li>
- <li>
- Verify browser support – The SHRINE web client is verified to function in the following browsers:
- <ul><li>
- Internet Explorer 6, 7, and 8
- </li>
- <li>
- Mozilla Firefox 3.5.5 and 3.5.6
- </li>
- <li>
- Safari 4
- </li></ul>
- <strong>Note</strong>: JavaScript must be enabled to use SHRINE.
- </li></ul>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252370683">Basics</a>
+ </h1>
+ <p>
+ This topic describes basic functions and requirements associated with the SHRINE system.
+ </p>
+ <h2>
+ <a name="_Toc252370683">Requirements</a>
+ </h2>
+ <p>
+ You need the following to use SHRINE:
+ </p>
+ <ul><li>
+ Meet the criteria required to register for SHRINE use through your local institution – You must be a Harvard Medical School faculty member appointed at or above the level of
+ Instructor and employed by one of the participating SHRINE hospitals:
+ <ul>
+ <li>Beth Israel Deaconess Medical Center (BIDMC)</li>
+ <li>Brigham and Women's Hospital (BWH)</li>
+ <li>Children's Hospital Boston (CHB)</li>
+ <li>Massachusetts General Hospital (MGH)</li></ul>
+ In this case, <em>employed by</em> means that your
+ paycheck is generated by that institution.
+ <br/>
+ When you satisfy these criteria, your local institution gives you an account with access to the SHRINE system.
+ <br />
+ If you are an instructor or above at Harvard University who is <em>not</em> employed at a participating hospital but you collaborate with a SHRINE member who is, you may access the data indirectly through that relationship. Your
+ collaborator must be in the medical specialty of your interest and only your collaborator may initiate a data query.
+ </li>
+ <li>
+ Confirm your eCommons account – To log in to the Data Steward component of SHRINE and submit a <em>Query Topic</em> request, you use your eCommons account credentials.
+ </li>
+ <li>
+ Submit a Query Topic for approval – Before you can query any data, you must describe how you intend to use the system to support your research. For
+ example, you might use SHRINE to develop preliminary data for a grant proposal. IRB approval is <em>not</em> required to query data; the Data Steward approves Query
+ Topic requests based on ethical validity, not scientific objectives.
+ </li>
+ <li>
+ Verify browser support – The SHRINE web client is verified to function in the following browsers:
+ <ul><li>
+ Internet Explorer 6, 7, and 8
+ </li>
+ <li>
+ Mozilla Firefox 3.5.5 and 3.5.6
+ </li>
+ <li>
+ Safari 4
+ </li></ul>
+ <strong>Note</strong>: JavaScript must be enabled to use SHRINE.
+ </li></ul>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370684">Data Steward</a>
- </h2>
- <p>
- The Data Steward must review and approve your Query Topic requests before you access SHRINE data. In addition, the Data Steward also regularly reviews your use of the
- <em>Query Tool</em> to ensure that no unapproved examination of data is performed. You submit a request that describes your intended use of the
- system. Log back in with the Data Steward to find out when your request is approved.
- </p>
- <p>
- You can access the Data Steward from within the SHRINE Query Tool. Click <em>Request New Topic</em> in the tool view to open the Data Steward in a new window, and log in by using your eCommons account credentials.
- </p>
- <p>Or, access the Data Steward directly in your browser at the following address:</p>
- Individual queries are subject to review by the Data Steward for compliance with approved topics. Query histories are logged and audited on a regular
- basis to ensure that there are no violations of the Terms of Access Agreement that you must accept when you log in to SHRINE. Any inappropriate use of the Query Tool to investigate
- patient data results in immediate suspension of your account, and Notification is sent to your institution regarding possible misconduct.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370684">Data Steward</a>
+ </h2>
+ <p>
+ The Data Steward must review and approve your Query Topic requests before you access SHRINE data. In addition, the Data Steward also regularly reviews your use of the
+ <em>Query Tool</em> to ensure that no unapproved examination of data is performed. You submit a request that describes your intended use of the
+ system. Log back in with the Data Steward to find out when your request is approved.
+ </p>
+ <p>
+ You can access the Data Steward from within the SHRINE Query Tool. Click <em>Request New Topic</em> in the tool view to open the Data Steward in a new window, and log in by using your eCommons account credentials.
+ </p>
+ <p>Or, access the Data Steward directly in your browser at the following address:</p>
+ Individual queries are subject to review by the Data Steward for compliance with approved topics. Query histories are logged and audited on a regular
+ basis to ensure that there are no violations of the Terms of Access Agreement that you must accept when you log in to SHRINE. Any inappropriate use of the Query Tool to investigate
+ patient data results in immediate suspension of your account, and Notification is sent to your institution regarding possible misconduct.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370685">SHRINE Data</a>
- </h2>
- <p>
- SHRINE currently has a complete set of data for demographics and diagnosis, and partial data sets for medications and laboratory values. The quality
- and completeness reflect what is available based on each institution's electronic medical record system. Queries return aggregate results only.
- </p>
- <p>
- Data begin in January 1, 2001 and are current to the present. SHRINE data are refreshed on a regular basis.
- </p>
- <p>
- <strong>Note</strong>: SHRINE does not provide access to patient records. There are plans to provide access to limited data sets in a future release. There are <em>no</em>
- plans to provide access to full datasets.
- </p>
- <p>
- Available data comprise the following:
- </p>
- <ul><li>
- Demographics – Patient demographic data available at each participating SHRINE hospital consists of:
- <ul><li>
- Age
- </li>
- <li>
- Gender – Health Level Seven International (HL7) Administrative Gender
- </li>
- <li>
- Language – ISO 639-1
- </li>
- <li>
- Marital status – HL7 Marital Status
- </li>
- <li>
- Race and Ethnicity – Centers for Disease Control and Prevention (CDC) Race and Ethnicity Code Sets
- </li>
- </ul></li>
- <li>
- Diagnoses – SHRINE contains inpatient and outpatient diagnosis information from BWH and MGH. Diagnoses are identified by National Center
- for Health Statistics (NCHS) ICD-9-CM standards and Clinical Classification Software (CCS) hierarchy.
- </li>
- <li>
- Lab Tests – Data on lab tests are identified by Logical Observation Identifiers Names and Codes (LOINC) and Partners HealthCare System's hierarchy.
- <br/>
- You can constrain test terms by high/low flags, or by specific values.
- </li>
- <li>
- Medications – SHRINE shows a subset of medication data for those practices that record this information. Outpatient medication information
- is limited to observation patients, surgical day patients, and ER patients. Medications are identified by the Unified Medical Language System
- (UMLS) RxNorm (Ingredient) and the Veterans Administration National Drug File Reference Terminology (NDF-RT) hierarchy.
- </li></ul>
- <p>
- Note the following qualifications to data availability:
- </p>
- <ul><li>
- Not all data points are available on all patients.
- </li>
- <li>
- Individual patient records are not available through SHRINE.
- </li>
- <li>
- Limited data sets, consisting of personal health information that excludes 16 HIPAA-defined attributes that could identify the patient, are planned for a future release.
- </li</ul>
- <p>
- See the <a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide"><em>Data Reference Guide</em></a> for a detailed description of the data available to query by using SHRINE.
- </p>
-
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370685">SHRINE Data</a>
+ </h2>
+ <p>
+ SHRINE currently has a complete set of data for demographics and diagnosis, and partial data sets for medications and laboratory values. The quality
+ and completeness reflect what is available based on each institution's electronic medical record system. Queries return aggregate results only.
+ </p>
+ <p>
+ Data begin in January 1, 2001 and are current to the present. SHRINE data are refreshed on a regular basis.
+ </p>
+ <p>
+ <strong>Note</strong>: SHRINE does not provide access to patient records. There are plans to provide access to limited data sets in a future release. There are <em>no</em>
+ plans to provide access to full datasets.
+ </p>
+ <p>
+ Available data comprise the following:
+ </p>
+ <ul><li>
+ Demographics – Patient demographic data available at each participating SHRINE hospital consists of:
+ <ul><li>
+ Age
+ </li>
+ <li>
+ Gender – Health Level Seven International (HL7) Administrative Gender
+ </li>
+ <li>
+ Language – ISO 639-1
+ </li>
+ <li>
+ Marital status – HL7 Marital Status
+ </li>
+ <li>
+ Race and Ethnicity – Centers for Disease Control and Prevention (CDC) Race and Ethnicity Code Sets
+ </li>
+ </ul></li>
+ <li>
+ Diagnoses – SHRINE contains inpatient and outpatient diagnosis information from BWH and MGH. Diagnoses are identified by National Center
+ for Health Statistics (NCHS) ICD-9-CM standards and Clinical Classification Software (CCS) hierarchy.
+ </li>
+ <li>
+ Lab Tests – Data on lab tests are identified by Logical Observation Identifiers Names and Codes (LOINC) and Partners HealthCare System's hierarchy.
+ <br/>
+ You can constrain test terms by high/low flags, or by specific values.
+ </li>
+ <li>
+ Medications – SHRINE shows a subset of medication data for those practices that record this information. Outpatient medication information
+ is limited to observation patients, surgical day patients, and ER patients. Medications are identified by the Unified Medical Language System
+ (UMLS) RxNorm (Ingredient) and the Veterans Administration National Drug File Reference Terminology (NDF-RT) hierarchy.
+ </li></ul>
+ <p>
+ Note the following qualifications to data availability:
+ </p>
+ <ul><li>
+ Not all data points are available on all patients.
+ </li>
+ <li>
+ Individual patient records are not available through SHRINE.
+ </li>
+ <li>
+ Limited data sets, consisting of personal health information that excludes 16 HIPAA-defined attributes that could identify the patient, are planned for a future release.
+ </li</ul>
+ <p>
+ See the <a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide"><em>Data Reference Guide</em></a> for a detailed description of the data available to query by using SHRINE.
+ </p>
+
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370686">Results</a>
- </h2>
- <p>
- To protect patient privacy, data are de-identified before incorporation into the Core ontology. In addition, we blur the aggregate patient counts
- returned as query results so that they are an estimate of the actual number. For information about the technology used to implement this additional obfuscation,
- refer to the following paper:
- </p>
- <blockquote>
- Murphy SN, Chueh HC. A Security Architecture for Query Tools used to Access Large Biomedical Databases. Proceedings of the 2002, AMIA Annual Symposium.
- 2002 Nov 9-13, San Antonio, TX p. 552-6.
- </blockquote>
- <p>
- If you run the same query more than one time, you receive slightly different results each time. SHRINE is designed to lock out users who receive the
- same query results seven times.
- </p>
- <p>
- When you log out of SHRINE, your results no longer are available.
- </p>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370686">Results</a>
+ </h2>
+ <p>
+ To protect patient privacy, data are de-identified before incorporation into the Core ontology. In addition, we blur the aggregate patient counts
+ returned as query results so that they are an estimate of the actual number. For information about the technology used to implement this additional obfuscation,
+ refer to the following paper:
+ </p>
+ <blockquote>
+ Murphy SN, Chueh HC. A Security Architecture for Query Tools used to Access Large Biomedical Databases. Proceedings of the 2002, AMIA Annual Symposium.
+ 2002 Nov 9-13, San Antonio, TX p. 552-6.
+ </blockquote>
+ <p>
+ If you run the same query more than one time, you receive slightly different results each time. SHRINE is designed to lock out users who receive the
+ same query results seven times.
+ </p>
+ <p>
+ When you log out of SHRINE, your results no longer are available.
+ </p>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252370688">Menus and Options</a>
- </h1>
- <p>
- SHRINE menus and options are described in this section.
- </p>
- <h2>
- <a name="_Toc252370688">Main Menu and Options</a>
- </h2>
- <p>
- The main SHRINE menu is located in the top-right corner of the web browser window. Options include:
- </p>
- <ul><li>
- Find Patients – The main page, on which you locate patient terms (characteristics), construct queries, and view query status.
- </li>
- <li>
- Message Log – A development tool used by technical staff to track system functions.
- </li>
- <li>
- Help – A link to the SHRINE Help home page, from which you can access all guides. Also use this
- option if you need to contact us.
- </li>
- <li>
- Logout – Exit SHRINE.
- </li>
- </ul>
- <p>
- In addition, two icons at the top-right corner of the Terms and Query Tool views offer options specific to those views:
- </p>
- <ul><li>
- Show Options icon – Click this icon at the top-right corner of the view to select from the following:
- <ul><li>
- Terms view options –
- <ul><li>
- Maximum Number of Children to Display – Default is 200
- </li>
- <li>
- Show Hidden Terms – Check box to include hidden terms
- </li>
- <li>
- Show Synonymous Terms – Check box to include terms that are synonymous
- </li></ul></li>
- <li>
- Query Tool view option – Select the Maximum Time to Wait for XML Response (in seconds). This is the length of time the system will wait for query results. <br />
-If your query does not process completely within this length of time, it returns only those results that completed processing within an institution. If no institutionâs data completed processing, the query does not return any results.
- </li></ul></li>
- <li>
- Toggle Zoom icon – Click the Toggle Zoom icon at the top-right corner of the view to toggle between expanded and compressed view sizes.
- </li></ul>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252370688">Menus and Options</a>
+ </h1>
+ <p>
+ SHRINE menus and options are described in this section.
+ </p>
+ <h2>
+ <a name="_Toc252370688">Main Menu and Options</a>
+ </h2>
+ <p>
+ The main SHRINE menu is located in the top-right corner of the web browser window. Options include:
+ </p>
+ <ul><li>
+ Find Patients – The main page, on which you locate patient terms (characteristics), construct queries, and view query status.
+ </li>
+ <li>
+ Message Log – A development tool used by technical staff to track system functions.
+ </li>
+ <li>
+ Help – A link to the SHRINE Help home page, from which you can access all guides. Also use this
+ option if you need to contact us.
+ </li>
+ <li>
+ Logout – Exit SHRINE.
+ </li>
+ </ul>
+ <p>
+ In addition, two icons at the top-right corner of the Terms and Query Tool views offer options specific to those views:
+ </p>
+ <ul><li>
+ Show Options icon – Click this icon at the top-right corner of the view to select from the following:
+ <ul><li>
+ Terms view options –
+ <ul><li>
+ Maximum Number of Children to Display – Default is 200
+ </li>
+ <li>
+ Show Hidden Terms – Check box to include hidden terms
+ </li>
+ <li>
+ Show Synonymous Terms – Check box to include terms that are synonymous
+ </li></ul></li>
+ <li>
+ Query Tool view option – Select the Maximum Time to Wait for XML Response (in seconds). This is the length of time the system will wait for query results. <br />
+If your query does not process completely within this length of time, it returns only those results that completed processing within an institution. If no institutionâs data completed processing, the query does not return any results.
+ </li></ul></li>
+ <li>
+ Toggle Zoom icon – Click the Toggle Zoom icon at the top-right corner of the view to toggle between expanded and compressed view sizes.
+ </li></ul>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370689">Terms View</a>
- </h2>
- <p>
- Use the patient Terms view, on the left side of the SHRINE window, to navigate (browse) or find (search) the medical terms on which you choose to
- query. The full range of terms available for you to query is listed in this view, grouped into four main criteria:
- </p>
- <ul>
- <li>
- Demographics
- </li>
- <li>
- Diagnoses
- </li>
- <li>
- Lab Tests
- </li>
- <li>
- Medications
- </li>
- </ul>
- <p>
- Each of the main criteria contains multiple categories that are displayed in subfolders, which contain more-specific terms by which you can refine your
- query. As you navigate through the subfolders and locate a term or category that you choose to include in your query, drag that entry to the Query Tool
- and drop it in a Group column to add it to your query criteria. You can select term folders, subfolders, or discrete terms to add to your query.
- </p>
-
- <p>
-If a term category maps to more than 120 specific terms, you cannot use that category in the Query Tool. You must expand it and select a more specific term to use. This is an indication that the query would take too long to process.
- </p>
- <p>
-
- Fields and functions in the Terms view include:
- </p>
- <ul><li>
- Navigate Terms tab – Default tab of the Terms view. Use the Expand (+) and Compress (-) buttons to browse through available
- characteristics on which to query.
- </li>
- <li>
- Find Terms tab – To search for specific characteristics on which to query, click the Find Terms tab on the Terms view. You can search by
- using the following criteria:
- <ul><li>
- Search by Name – This is the default tab of the Find Terms view.
- <br />
- To search by Name:
- <ol><li>
- Click the top pull-down list to select the logical search operator. Options include Contains, Exact, Left (starts with), or Right (ends with).
- </li>
- <li>
- Enter your search string in the text field beside the operator pull-down list.
- </li>
- <li>
- Click the Category pull-down list to select which category of data and select the SHRINE option.
- </li>
- <li>
- Click Find.
- </li></ol></li>
- <li>
- Search by Codes – Click this tab to search criteria for specific coding system terms.
- <br />
- To search by Code:
- <ol><li>
- Use the Select a Coding System pull-down list to select the specific code type for which you choose to search.
- </li>
- <li>
- Enter the term in the text field above the list.
- </li>
- <li>
- Click Find.
- </li></ol>
- Coding systems on which you can search include:
- <ul>
- <li>
- Demographics (Marital)
- </li>
- <li>
- Demographics (Sex)
- </li>
- <li>
- Demographics (Language)
- </li>
- <li>
- Demographics (Age)
- </li>
- <li>
- Demographics (Race)
- </li>
- <li>
- Lab Tests
- </li>
- <li>
- Diagnoses (ICD9)
- </li>
- <li>
- Medications (RxNorm)
- </li></ul>
- </li></ul>
- </li></ul>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370689">Terms View</a>
+ </h2>
+ <p>
+ Use the patient Terms view, on the left side of the SHRINE window, to navigate (browse) or find (search) the medical terms on which you choose to
+ query. The full range of terms available for you to query is listed in this view, grouped into four main criteria:
+ </p>
+ <ul>
+ <li>
+ Demographics
+ </li>
+ <li>
+ Diagnoses
+ </li>
+ <li>
+ Lab Tests
+ </li>
+ <li>
+ Medications
+ </li>
+ </ul>
+ <p>
+ Each of the main criteria contains multiple categories that are displayed in subfolders, which contain more-specific terms by which you can refine your
+ query. As you navigate through the subfolders and locate a term or category that you choose to include in your query, drag that entry to the Query Tool
+ and drop it in a Group column to add it to your query criteria. You can select term folders, subfolders, or discrete terms to add to your query.
+ </p>
+
+ <p>
+If a term category maps to more than 120 specific terms, you cannot use that category in the Query Tool. You must expand it and select a more specific term to use. This is an indication that the query would take too long to process.
+ </p>
+ <p>
+
+ Fields and functions in the Terms view include:
+ </p>
+ <ul><li>
+ Navigate Terms tab – Default tab of the Terms view. Use the Expand (+) and Compress (-) buttons to browse through available
+ characteristics on which to query.
+ </li>
+ <li>
+ Find Terms tab – To search for specific characteristics on which to query, click the Find Terms tab on the Terms view. You can search by
+ using the following criteria:
+ <ul><li>
+ Search by Name – This is the default tab of the Find Terms view.
+ <br />
+ To search by Name:
+ <ol><li>
+ Click the top pull-down list to select the logical search operator. Options include Contains, Exact, Left (starts with), or Right (ends with).
+ </li>
+ <li>
+ Enter your search string in the text field beside the operator pull-down list.
+ </li>
+ <li>
+ Click the Category pull-down list to select which category of data and select the SHRINE option.
+ </li>
+ <li>
+ Click Find.
+ </li></ol></li>
+ <li>
+ Search by Codes – Click this tab to search criteria for specific coding system terms.
+ <br />
+ To search by Code:
+ <ol><li>
+ Use the Select a Coding System pull-down list to select the specific code type for which you choose to search.
+ </li>
+ <li>
+ Enter the term in the text field above the list.
+ </li>
+ <li>
+ Click Find.
+ </li></ol>
+ Coding systems on which you can search include:
+ <ul>
+ <li>
+ Demographics (Marital)
+ </li>
+ <li>
+ Demographics (Sex)
+ </li>
+ <li>
+ Demographics (Language)
+ </li>
+ <li>
+ Demographics (Age)
+ </li>
+ <li>
+ Demographics (Race)
+ </li>
+ <li>
+ Lab Tests
+ </li>
+ <li>
+ Diagnoses (ICD9)
+ </li>
+ <li>
+ Medications (RxNorm)
+ </li></ul>
+ </li></ul>
+ </li></ul>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370690">Query Tool View</a>
- </h2>
- <p>
- The Query Tool enables you to create complicated queries by using a simple user interface.
- </p>
- <p>
- <strong>Note</strong>: You cannot run a query until you select a topic. If you do not have an approved Query Topic, you must request a new topic approval from the Data
- Steward.
- </p>
- <p>
- Construct your query by using these fields and functions:
- <ul>
- <li>
- Query Name – When you click Run Query, SHRINE prompts you to enter a name for that query instance before you can run the process. The
- default name is a string constructed from your term selections and the time at which you run the query.
- <br />
- You cannot type a query name directly into this field.
- </li>
- <li>
- Group columns – Query groups represent a set of patients defined by the terms within the group and any constraints applied to that group.
- <br />
- Terms within a group operate as <em>OR</em> logic, while terms between groups operate as <em>AND</em> logic. For example, from the Terms view drag
- demographic terms of <em>35 years old</em> and <em>36 years old</em> to one group to select patients either 35 or 36 years old. Or drag a diagnosis
- term of <em>Asthma</em> to one group, a demographic age term of <em>35 years old</em> to a second group, and a demographic gender term of <em>Male</em>
- to a third group to select patients diagnosed with asthma who are 35-year old males.
- <br />
- When a group contains multiple terms, the query first runs with a single term from each group, and then runs with any additional terms. For example, if
- you drag a diagnosis of <em>Asthma</em> to Group 1 and then drag demographic terms of <em>10-17 years old</em> and <em>0-9 years old</em> to Group 2,
- the query first processes diagnosis of asthma and demographics of 10-17 years old. Another query process runs diagnosis of asthma and demographics of
- 0-9 years old. The two results sets then are added together to return the final query results.
- </li>
- <li>
- Select a Topic pull-down list – Before you can run a query, you must select the Query Topic to which this query relates. The Topics list contains
- all your Data Steward-approved topics.
- <br />
- The Data Steward monitors query activities. If you select query terms that do not apply logically to your topic, the steward can suspend your access to
- SHRINE, and a review of your activities is required.
- </li>
- <li>
- Info button – When a Query Topic is selected, click Info to view the description of that topic as it was provided to the Data Steward.
- </li>
- <li>
- Request New Topic button – Access the Data Steward from the SHRINE system by clicking this button. The Data Steward opens in a new window.
- <br />
- <strong>Note</strong>: To run a query that does not conform to any of your approved Topics, you must request a new topic from the Data Steward and receive approval before
- you can perform the query.
- </li>
- <li>
- Run Query button – When you complete construction of your query using the terms, constraints, and options available, click Run Query to
- start the query process.
- <br />
- You can run additional queries by retaining the existing terms in the Query Tool fields, and then adding new criteria to the query. Be careful not to
- run the same query multiple times.
- </li>
- <li>
- New Query button – Click this button to clear all Query Tool fields and start a new query.
- </li>
- <li>
- New Group button – To add additional groups of terms to your query, click this button.
- </li>
- <li>
- Group page controls – If you add groups to the default of three, you can navigate to additional groups by using these page controls.
- </li></ul>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370690">Query Tool View</a>
+ </h2>
+ <p>
+ The Query Tool enables you to create complicated queries by using a simple user interface.
+ </p>
+ <p>
+ <strong>Note</strong>: You cannot run a query until you select a topic. If you do not have an approved Query Topic, you must request a new topic approval from the Data
+ Steward.
+ </p>
+ <p>
+ Construct your query by using these fields and functions:
+ <ul>
+ <li>
+ Query Name – When you click Run Query, SHRINE prompts you to enter a name for that query instance before you can run the process. The
+ default name is a string constructed from your term selections and the time at which you run the query.
+ <br />
+ You cannot type a query name directly into this field.
+ </li>
+ <li>
+ Group columns – Query groups represent a set of patients defined by the terms within the group and any constraints applied to that group.
+ <br />
+ Terms within a group operate as <em>OR</em> logic, while terms between groups operate as <em>AND</em> logic. For example, from the Terms view drag
+ demographic terms of <em>35 years old</em> and <em>36 years old</em> to one group to select patients either 35 or 36 years old. Or drag a diagnosis
+ term of <em>Asthma</em> to one group, a demographic age term of <em>35 years old</em> to a second group, and a demographic gender term of <em>Male</em>
+ to a third group to select patients diagnosed with asthma who are 35-year old males.
+ <br />
+ When a group contains multiple terms, the query first runs with a single term from each group, and then runs with any additional terms. For example, if
+ you drag a diagnosis of <em>Asthma</em> to Group 1 and then drag demographic terms of <em>10-17 years old</em> and <em>0-9 years old</em> to Group 2,
+ the query first processes diagnosis of asthma and demographics of 10-17 years old. Another query process runs diagnosis of asthma and demographics of
+ 0-9 years old. The two results sets then are added together to return the final query results.
+ </li>
+ <li>
+ Select a Topic pull-down list – Before you can run a query, you must select the Query Topic to which this query relates. The Topics list contains
+ all your Data Steward-approved topics.
+ <br />
+ The Data Steward monitors query activities. If you select query terms that do not apply logically to your topic, the steward can suspend your access to
+ SHRINE, and a review of your activities is required.
+ </li>
+ <li>
+ Info button – When a Query Topic is selected, click Info to view the description of that topic as it was provided to the Data Steward.
+ </li>
+ <li>
+ Request New Topic button – Access the Data Steward from the SHRINE system by clicking this button. The Data Steward opens in a new window.
+ <br />
+ <strong>Note</strong>: To run a query that does not conform to any of your approved Topics, you must request a new topic from the Data Steward and receive approval before
+ you can perform the query.
+ </li>
+ <li>
+ Run Query button – When you complete construction of your query using the terms, constraints, and options available, click Run Query to
+ start the query process.
+ <br />
+ You can run additional queries by retaining the existing terms in the Query Tool fields, and then adding new criteria to the query. Be careful not to
+ run the same query multiple times.
+ </li>
+ <li>
+ New Query button – Click this button to clear all Query Tool fields and start a new query.
+ </li>
+ <li>
+ New Group button – To add additional groups of terms to your query, click this button.
+ </li>
+ <li>
+ Group page controls – If you add groups to the default of three, you can navigate to additional groups by using these page controls.
+ </li></ul>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370691">Query Status View</a>
- </h2>
- <p>
- The results of your query appear in the Query Status view. Information provided includes:
- </p>
- <ul>
- <li>
- Query name
- </li>
- <li>
- Elapsed execution time
- </li>
- <li>
- Aggregated query results from participating hospitals
- </li>
- </ul>
- <p>
- The results are time and date stamped.
- </p>
- <p>
- <strong>Note</strong>: When you log out of SHRINE, your results no longer are available.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370691">Query Status View</a>
+ </h2>
+ <p>
+ The results of your query appear in the Query Status view. Information provided includes:
+ </p>
+ <ul>
+ <li>
+ Query name
+ </li>
+ <li>
+ Elapsed execution time
+ </li>
+ <li>
+ Aggregated query results from participating hospitals
+ </li>
+ </ul>
+ <p>
+ The results are time and date stamped.
+ </p>
+ <p>
+ <strong>Note</strong>: When you log out of SHRINE, your results no longer are available.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- This view is not functional in the initial release of SHRINE. This view is scheduled for implementation in the SHRINE 1.8 release.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ This view is not functional in the initial release of SHRINE. This view is scheduled for implementation in the SHRINE 1.8 release.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <li>BWH and MGH – Contact Shawn N. Murphy (snmurphy@partners.org) for more information.
- </li>
- </ul>
-
- <p>
- <strong>Note</strong>: You must be behind your hospital's firewall to access SHRINE.
- </p>
- <p>
- Complete the registration process as identified by your institution. This process might take a few minutes or a few days,
- depending on the specific verification process. After you are registered, you use the account credentials provided to access SHRINE.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <li>BWH and MGH – Contact Shawn N. Murphy (snmurphy@partners.org) for more information.
+ </li>
+ </ul>
+
+ <p>
+ <strong>Note</strong>: You must be behind your hospital's firewall to access SHRINE.
+ </p>
+ <p>
+ Complete the registration process as identified by your institution. This process might take a few minutes or a few days,
+ depending on the specific verification process. After you are registered, you use the account credentials provided to access SHRINE.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm"><strong><em>Logging In to SHRINE</em></strong></a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h2>
- <a name="_Toc252370695">Logging In to SHRINE</a>
- </h2>
- <p>
- After your registration status is approved at your local institution, access the SHRINE Query Tool using the address, username, and password provided to you.
- </p>
- <ol><li>
- Point your browser to the address identified when you registered for SHRINE.<br />
- <strong>Note</strong>: You must be behind your hospital's firewall to view the login page.
- </li>
- <li>
- Enter your username and password.
- </li>
- <li>
- Use the SHRINE Host pull-down list to select the version of SHRINE available at your institution.
- </li>
- <li>
- Click Login.
- <br />
- You see a Terms of Access Agreement that you must review and accept before you can use the Query Tool.
- </li>
- <li>
- To use the SHRINE system, click <em>Yes, I agree</em>.
- <br />
- You see the SHRINE system in your browser window.
- </li></ol>
- <p>
- Continue to <a href="Toc252370696.htm">Submitting a Query Topic Request</a> to find out how to access the SHRINE Query Tool.
- </p>
-
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm"><strong><em>Logging In to SHRINE</em></strong></a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h2>
+ <a name="_Toc252370695">Logging In to SHRINE</a>
+ </h2>
+ <p>
+ After your registration status is approved at your local institution, access the SHRINE Query Tool using the address, username, and password provided to you.
+ </p>
+ <ol><li>
+ Point your browser to the address identified when you registered for SHRINE.<br />
+ <strong>Note</strong>: You must be behind your hospital's firewall to view the login page.
+ </li>
+ <li>
+ Enter your username and password.
+ </li>
+ <li>
+ Use the SHRINE Host pull-down list to select the version of SHRINE available at your institution.
+ </li>
+ <li>
+ Click Login.
+ <br />
+ You see a Terms of Access Agreement that you must review and accept before you can use the Query Tool.
+ </li>
+ <li>
+ To use the SHRINE system, click <em>Yes, I agree</em>.
+ <br />
+ You see the SHRINE system in your browser window.
+ </li></ol>
+ <p>
+ Continue to <a href="Toc252370696.htm">Submitting a Query Topic Request</a> to find out how to access the SHRINE Query Tool.
+ </p>
+
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm"><strong><em>Submitting a Query Topic Request</em></strong></a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
-
- <h1>
- <a name="_Toc252370696">
- Submitting a Query Topic Request</a>
- </h1>
- <p>
- Before you can construct a query to determine patient populations, you must submit a request to the Data Steward and define a specific topic for which
- you choose to query patient data. The Data Steward approves all topics, and monitors query activities for all topics to ensure that no inappropriate
- use of patient data occurs.
- </p>
- <p>
- You can request multiple Query Topics to support different selection criteria of patient cohorts.
- </p>
- <p>
- To submit a Query Topic request:
- </p>
- <ol><li>
- In a browser window, go to the Data Steward home page:
- Note that you also can access the Data Steward from the SHRINE system. In the Query Tool pane, click Request New Topic at the bottom-left of the tool.
- </li>
- <li>
- In the Data Steward window, complete the following information:
- <ul>
- <li>
- Enter a Query Name for your topic.
- </li>
- <li>
- In the Query Intent field, describe the research topic for which you choose to explore potential cohorts.
- </li>
- <li>
- Use the Reason for Query pull-down list to select the reason for which you choose to explore this specific topic. If you select a Reason of
- Other, add an explanation for your reason in the text field below the pull-down.
- </li>
- <li>
- If you are collaborating with a non-SHRINE associate, use the associated pull-down list and select Yes. Then add an explanation in the text
- field below that pull-down.<br />
- <strong>Note</strong>: Collaborations with individuals or entities outside of the participating SHRINE institutions, including academia and industry, currently are prohibited.
- </li>
- </ul>
- </li>
- <li>
- Click Submit.
- <br/>
- The Data Steward will review your Query Topic to determine if it constitutes appropriate use of SHRINE data. If more information is needed, the Data
- Steward will contact you. We try to process all requests within 48 hours.
- <br/>
- You can check the Data Steward to view the status of your request as listed in the Active Requests field at the bottom of the window. When your request
- is approved, you now have access to SHRINE data.
- </li>
- <li>
- Click Logout to exit the Data Steward.
- </li></ol>
- <p>
- Continue to <a href="Toc252370697.htm">Constructing a Query</a>.
- </p>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm"><strong><em>Submitting a Query Topic Request</em></strong></a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+
+ <h1>
+ <a name="_Toc252370696">
+ Submitting a Query Topic Request</a>
+ </h1>
+ <p>
+ Before you can construct a query to determine patient populations, you must submit a request to the Data Steward and define a specific topic for which
+ you choose to query patient data. The Data Steward approves all topics, and monitors query activities for all topics to ensure that no inappropriate
+ use of patient data occurs.
+ </p>
+ <p>
+ You can request multiple Query Topics to support different selection criteria of patient cohorts.
+ </p>
+ <p>
+ To submit a Query Topic request:
+ </p>
+ <ol><li>
+ In a browser window, go to the Data Steward home page:
+ Note that you also can access the Data Steward from the SHRINE system. In the Query Tool pane, click Request New Topic at the bottom-left of the tool.
+ </li>
+ <li>
+ In the Data Steward window, complete the following information:
+ <ul>
+ <li>
+ Enter a Query Name for your topic.
+ </li>
+ <li>
+ In the Query Intent field, describe the research topic for which you choose to explore potential cohorts.
+ </li>
+ <li>
+ Use the Reason for Query pull-down list to select the reason for which you choose to explore this specific topic. If you select a Reason of
+ Other, add an explanation for your reason in the text field below the pull-down.
+ </li>
+ <li>
+ If you are collaborating with a non-SHRINE associate, use the associated pull-down list and select Yes. Then add an explanation in the text
+ field below that pull-down.<br />
+ <strong>Note</strong>: Collaborations with individuals or entities outside of the participating SHRINE institutions, including academia and industry, currently are prohibited.
+ </li>
+ </ul>
+ </li>
+ <li>
+ Click Submit.
+ <br/>
+ The Data Steward will review your Query Topic to determine if it constitutes appropriate use of SHRINE data. If more information is needed, the Data
+ Steward will contact you. We try to process all requests within 48 hours.
+ <br/>
+ You can check the Data Steward to view the status of your request as listed in the Active Requests field at the bottom of the window. When your request
+ is approved, you now have access to SHRINE data.
+ </li>
+ <li>
+ Click Logout to exit the Data Steward.
+ </li></ol>
+ <p>
+ Continue to <a href="Toc252370697.htm">Constructing a Query</a>.
+ </p>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm"><strong><em>Constructing a Query</em></strong></a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252370697">
- Constructing a Query</a>
- </h1>
- <p>
- SHRINE enables you to explore your topic in whatever depth is available currently, as long as your individual queries are related to your general Query
- Topic.
- </p>
- <p>
- To query SHRINE data:
- </p>
- <ol><li>
- Point your browser to the address identified when you registered for SHRINE, and log in by using your institution account credentials.<br />
- <strong>Note</strong>: You must be behind your hospital's firewall to view the login page.<br />
- When you are logged in to SHRINE, you see the SHRINE system in your browser.
- </li>
- <li>
- Select a Query Topic.
- <br/>
- In the Query Tool view, use the Select a Topic pull-down list in the middle-right side of the window and select the topic to which this query applies.
- <br />
- The first time that you use the Query Tool, you will not see any data listed in the Terms view until you select a Query Topic.
- </li>
- <li>
- Navigate (browse) or find (search) for medical terms from which you choose to query for a patient cohort.
- <br />
- In the Terms pane, click the Navigate Terms tab to browse for patient characteristics or medical terms that you would like to query. Click the Expand
- (+) button for a category to view criteria subcategories.
- <br />
- To locate a specific term quickly, use the Find Terms tab options.
- <br />
- Terms comprise the following characteristics:
- <ul>
- <li>
- Demographics
- </li>
- <li>
- Diagnoses
- </li>
- <li>
- Medications
- </li>
- <li>
- Laboratory values
- </li>
- </ul>
- See the <a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide"><em>Data Reference Guide</em></a> for detailed information about the types of data available for you to query.
- </li>
- <li>
- Drag your selected term to the Query Tool view, Group 1 field.
- <br />
- <strong>Tip</strong>: To optimize the rate at which your query executes, select the most-limiting terms first. For example, demographic data is broader in scope than
- diagnoses or lab values. In addition, lab test terms take longer to process than other terms. Therefore, if you select your diagnoses terms first and
- then select your lab or demographic terms, SHRINE returns your query results more quickly.
- <br />
- See the <a href="../QR_Help_Files/index.htm" title="SHRINE Query Quick Reference"><em>Query Quick Reference</em></a> for detailed information about how to optimize query formats and define query logic.
- </li>
- <li>
- Right-click your selected term in the Group field to select patients with specific values of that term.
- <br />
- Or, apply constraints to all terms in a group by using the Date, Occurs, and Exclude options at the top of the Group.
- </li>
- <li>
- Repeat steps 3—5 for additional terms to narrow your query.
- <br />
- You can add terms within a Group to apply OR logic, and use multiple Groups to define your selection by using AND logic.
- <br/>
- The following is a logical construction of a sample query:
- <ul type="none"><li>
- Query Topic – What is the overall incidence of myocardial infarction?
- <br />
- The description of this topic is to look for a subset of cardiac myopathies with possible genetic predisposition.
- </li>
- <li>
- Some individual queries that you might run for this topic –
- <ul><li>
- Diagnoses myocardial infarction AND NOT diagnoses diabetes (eliminate a common cause of CV disease)
- </li>
- <li>
- Diagnoses myocardial infarction AND NOT diagnoses diabetes AND (Age > 20 and Age < 40) (identify unusual heart attacks)
- </li>
- <li>
- Diagnoses myocardial infarction AND NOT diagnoses diabetes AND (Age > 20 and Age < 40) AND NOT diagnoses hypercholesterolemia (enrich for
- genetic myopathies)
- </li></ul></li></ul></li>
- <li>
- When your query terms are defined, click Run Query.
- <br />
- You are prompted to enter a name for this query. The default name is a string derived from the terms that you selected for the query and the time at
- which you run it.
- </li>
- <li>
- Enter a name for the query or accept the default, and then click OK to run your query.
- <br />
- When the query process completes, the aggregate number of potential patient cohorts is displayed in the Query Status view.
- <br />
- <strong>Note</strong>: You cannot access patient records through SHRINE.
- </li></ol>
-
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm"><strong><em>Constructing a Query</em></strong></a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252370697">
+ Constructing a Query</a>
+ </h1>
+ <p>
+ SHRINE enables you to explore your topic in whatever depth is available currently, as long as your individual queries are related to your general Query
+ Topic.
+ </p>
+ <p>
+ To query SHRINE data:
+ </p>
+ <ol><li>
+ Point your browser to the address identified when you registered for SHRINE, and log in by using your institution account credentials.<br />
+ <strong>Note</strong>: You must be behind your hospital's firewall to view the login page.<br />
+ When you are logged in to SHRINE, you see the SHRINE system in your browser.
+ </li>
+ <li>
+ Select a Query Topic.
+ <br/>
+ In the Query Tool view, use the Select a Topic pull-down list in the middle-right side of the window and select the topic to which this query applies.
+ <br />
+ The first time that you use the Query Tool, you will not see any data listed in the Terms view until you select a Query Topic.
+ </li>
+ <li>
+ Navigate (browse) or find (search) for medical terms from which you choose to query for a patient cohort.
+ <br />
+ In the Terms pane, click the Navigate Terms tab to browse for patient characteristics or medical terms that you would like to query. Click the Expand
+ (+) button for a category to view criteria subcategories.
+ <br />
+ To locate a specific term quickly, use the Find Terms tab options.
+ <br />
+ Terms comprise the following characteristics:
+ <ul>
+ <li>
+ Demographics
+ </li>
+ <li>
+ Diagnoses
+ </li>
+ <li>
+ Medications
+ </li>
+ <li>
+ Laboratory values
+ </li>
+ </ul>
+ See the <a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide"><em>Data Reference Guide</em></a> for detailed information about the types of data available for you to query.
+ </li>
+ <li>
+ Drag your selected term to the Query Tool view, Group 1 field.
+ <br />
+ <strong>Tip</strong>: To optimize the rate at which your query executes, select the most-limiting terms first. For example, demographic data is broader in scope than
+ diagnoses or lab values. In addition, lab test terms take longer to process than other terms. Therefore, if you select your diagnoses terms first and
+ then select your lab or demographic terms, SHRINE returns your query results more quickly.
+ <br />
+ See the <a href="../QR_Help_Files/index.htm" title="SHRINE Query Quick Reference"><em>Query Quick Reference</em></a> for detailed information about how to optimize query formats and define query logic.
+ </li>
+ <li>
+ Right-click your selected term in the Group field to select patients with specific values of that term.
+ <br />
+ Or, apply constraints to all terms in a group by using the Date, Occurs, and Exclude options at the top of the Group.
+ </li>
+ <li>
+ Repeat steps 3—5 for additional terms to narrow your query.
+ <br />
+ You can add terms within a Group to apply OR logic, and use multiple Groups to define your selection by using AND logic.
+ <br/>
+ The following is a logical construction of a sample query:
+ <ul type="none"><li>
+ Query Topic – What is the overall incidence of myocardial infarction?
+ <br />
+ The description of this topic is to look for a subset of cardiac myopathies with possible genetic predisposition.
+ </li>
+ <li>
+ Some individual queries that you might run for this topic –
+ <ul><li>
+ Diagnoses myocardial infarction AND NOT diagnoses diabetes (eliminate a common cause of CV disease)
+ </li>
+ <li>
+ Diagnoses myocardial infarction AND NOT diagnoses diabetes AND (Age > 20 and Age < 40) (identify unusual heart attacks)
+ </li>
+ <li>
+ Diagnoses myocardial infarction AND NOT diagnoses diabetes AND (Age > 20 and Age < 40) AND NOT diagnoses hypercholesterolemia (enrich for
+ genetic myopathies)
+ </li></ul></li></ul></li>
+ <li>
+ When your query terms are defined, click Run Query.
+ <br />
+ You are prompted to enter a name for this query. The default name is a string derived from the terms that you selected for the query and the time at
+ which you run it.
+ </li>
+ <li>
+ Enter a name for the query or accept the default, and then click OK to run your query.
+ <br />
+ When the query process completes, the aggregate number of potential patient cohorts is displayed in the Query Status view.
+ <br />
+ <strong>Note</strong>: You cannot access patient records through SHRINE.
+ </li></ol>
+
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm"><strong><em>Working with Query Results</em></strong></a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
- <h1>
- <a name="_Toc252370698">Working with Query Results</a>
- </h1>
- <p>
- When your query is complete, aggregated results for each institution appear in the Query Status view, with time and date stamp. When you log out of
- SHRINE, your results no longer are available.
- </p>
- <p>
-<strong>None</strong>: If your query returned between zero (0) and 10 patients, your results display as <em>None</em>.
- </p>
- <p>
- SHRINE does not provide direct access to information about individual patients at any of the participating hospitals. To follow up with a potential
- cohort of interest, you must identify a collaborator at the institution where you located patients. Your collaborator then must work with the IRB to seek approval of the proposed study.
- </p>
- <p>
- If you currently do not collaborate with an investigator at that institution and do not know who might be doing similar research, visit the Harvard
- Catalyst website to explore options and make connections. For example, visit the Profiles research social networking system to conduct keyword searches
- for collaborators at Harvard-affiliated institutions. Or visit Medvane to access a Harvard-specific view of PubMed that can help you to identify who at
- Harvard has published on your research of interest.
- </p>
- <p>
- You can search Profiles and Medvane simultaneously using the Search box in the top-right corner of every page on the Harvard Catalyst website.
- </p>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm"><strong><em>Working with Query Results</em></strong></a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+ <h1>
+ <a name="_Toc252370698">Working with Query Results</a>
+ </h1>
+ <p>
+ When your query is complete, aggregated results for each institution appear in the Query Status view, with time and date stamp. When you log out of
+ SHRINE, your results no longer are available.
+ </p>
+ <p>
+<strong>None</strong>: If your query returned between zero (0) and 10 patients, your results display as <em>None</em>.
+ </p>
+ <p>
+ SHRINE does not provide direct access to information about individual patients at any of the participating hospitals. To follow up with a potential
+ cohort of interest, you must identify a collaborator at the institution where you located patients. Your collaborator then must work with the IRB to seek approval of the proposed study.
+ </p>
+ <p>
+ If you currently do not collaborate with an investigator at that institution and do not know who might be doing similar research, visit the Harvard
+ Catalyst website to explore options and make connections. For example, visit the Profiles research social networking system to conduct keyword searches
+ for collaborators at Harvard-affiliated institutions. Or visit Medvane to access a Harvard-specific view of PubMed that can help you to identify who at
+ Harvard has published on your research of interest.
+ </p>
+ <p>
+ You can search Profiles and Medvane simultaneously using the Search box in the top-right corner of every page on the Harvard Catalyst website.
+ </p>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <a href="Toc252370695.htm">Logging In to SHRINE</a>
- </li></ul
- <p>
- <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
- </p>
- <p>
- <a href="Toc252370697.htm">Constructing a Query</a>
- </p>
- <p>
- <a href="Toc252370698.htm">Working with Query Results</a>
- </p>
- <p>
- [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
- </p>
-
-</td>
-<td valign="top">
-
-
-<!-- Content -->
-
-
-<p>Harvard Catalyst developed the Shared Health Research
-Information Network (SHRINE) to support researchers when planning and performing population-based research, such as compiling large groups of well-characterized
-patients or repeating study results. Qualified investigators can use the SHRINE
-web-based <em>Query Tool</em> to determine the aggregate total number of patients at participating
-hospitals who meet a given set of criteria using both inclusion and exclusion logic.
-Characteristics on which you can query include demographics, diagnoses,
-medications, and selected laboratory values. Because counts are aggregated,
-patient privacy is protected.</p>
-
-<p>This guide describes the SHRINE Query Tool, including how to
-register for use, log in to SHRINE, request a <em>Query Topic</em>, and construct a
-query. Harvard Catalyst provides a full set of guides to support use of SHRINE:</p>
-
- <ul>
- <li>
- <em><a href="index.htm" title="SHRINE User Guide">SHRINE User Guide</a></em>
- – Use the Query Tool to locate patient populations.
- – Construct optimum queries by using the Query Tool.
- </li>
- <li>
- <em><a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
- – Understand the terms available for query.
- </li>
- </ul>
-
-
-</td>
-</tr>
-</table>
-
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
-</body>
-
-</html>
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+ <a href="Toc252370695.htm">Logging In to SHRINE</a>
+ </li></ul
+ <p>
+ <a href="Toc252370696.htm">Submitting a Query Topic Request</a>
+ </p>
+ <p>
+ <a href="Toc252370697.htm">Constructing a Query</a>
+ </p>
+ <p>
+ <a href="Toc252370698.htm">Working with Query Results</a>
+ </p>
+ <p>
+ [ <a href="../index.htm">SHRINE Help Main Menu</a> ]
+ </p>
+
+</td>
+<td valign="top">
+
+
+<!-- Content -->
+
+
+<p>Harvard Catalyst developed the Shared Health Research
+Information Network (SHRINE) to support researchers when planning and performing population-based research, such as compiling large groups of well-characterized
+patients or repeating study results. Qualified investigators can use the SHRINE
+web-based <em>Query Tool</em> to determine the aggregate total number of patients at participating
+hospitals who meet a given set of criteria using both inclusion and exclusion logic.
+Characteristics on which you can query include demographics, diagnoses,
+medications, and selected laboratory values. Because counts are aggregated,
+patient privacy is protected.</p>
+
+<p>This guide describes the SHRINE Query Tool, including how to
+register for use, log in to SHRINE, request a <em>Query Topic</em>, and construct a
+query. Harvard Catalyst provides a full set of guides to support use of SHRINE:</p>
+
+ <ul>
+ <li>
+ <em><a href="index.htm" title="SHRINE User Guide">SHRINE User Guide</a></em>
+ – Use the Query Tool to locate patient populations.
+ – Construct optimum queries by using the Query Tool.
+ </li>
+ <li>
+ <em><a href="../DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></em>
+ – Understand the terms available for query.
+ </li>
+ </ul>
+
+
+</td>
+</tr>
+</table>
+
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
-<li><strong><a href="DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></strong></li></ul>
-</td>
-<td valign="top">
-
-<p>This is a Beta release of the Harvard Catalyst Shared Health Research
-Information Network (SHRINE). These guides describes the SHRINE Query Tool,
-query construction, and SHRINE data:</p>
-
- <ul>
- <li>
- <em>SHRINE User Guide</em>
- – Use the Query Tool to locate patient populations.
- </li>
- <li>
- <em>SHRINE Query Quick Reference<</em>
- – Construct optimum queries by using the Query Tool.
- </li>
- <li>
- <em>SHRINE Data Reference Guide</em>
- – Understand the terms available for query.
- </li>
- </ul>
-
-</td></tr>
-</table>
-
-</div>
-
- <div id="footer">
-
-<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- </div>
-
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<li><strong><a href="DR_Help_Files/index.htm" title="SHRINE Data Reference Guide">SHRINE Data Reference Guide</a></strong></li></ul>
+</td>
+<td valign="top">
+
+<p>This is a Beta release of the Harvard Catalyst Shared Health Research
+Information Network (SHRINE). These guides describes the SHRINE Query Tool,
+query construction, and SHRINE data:</p>
+
+ <ul>
+ <li>
+ <em>SHRINE User Guide</em>
+ – Use the Query Tool to locate patient populations.
+ </li>
+ <li>
+ <em>SHRINE Query Quick Reference<</em>
+ – Construct optimum queries by using the Query Tool.
+ </li>
+ <li>
+ <em>SHRINE Data Reference Guide</em>
+ – Understand the terms available for query.
+ </li>
+ </ul>
+
+</td></tr>
+</table>
+
+</div>
+
+ <div id="footer">
+
+<p>Please use our <a href="http://cbmi.catalyst.harvard.edu/formsJsf/shrine_feedback.jsf" target=_BLANK>Feedback</a> form to contact the SHRINE team or to request assistance.</p>
- <div>Select a communicator object and populate its input data below, and then click the "View Results" tab for the resulting XML messages sent and recieved.</div>
- This plugin demonstrates provides an interface to interact with Cell Communicator objects based on the web client's standardized i2b2 communicator objects.
- The this plugin will search all loaded plugins and core modules within the web client looking for a standard Cell Communicator object at the namespace <span style="font-family:monospace">i2b2.<i>PLUGINCODE</i>.ajax</span>.
- <h2>Instructions</h2>
- Navigate to the "Specify Data" tab. Then, drag and drop an i2b2 object such as a search term or previous query onto the input box. Finally, click the "View Results" tab for information about that object.
- <h2>About Us</h2>
- This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
- <h2>Terms of Use</h2>
- This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- </div>
- </div>
- </div>
- </div>
- </div>
-
-
- </div>
- </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+ <div>Select a communicator object and populate its input data below, and then click the "View Results" tab for the resulting XML messages sent and recieved.</div>
+ This plugin demonstrates provides an interface to interact with Cell Communicator objects based on the web client's standardized i2b2 communicator objects.
+ The this plugin will search all loaded plugins and core modules within the web client looking for a standard Cell Communicator object at the namespace <span style="font-family:monospace">i2b2.<i>PLUGINCODE</i>.ajax</span>.
+ <h2>Instructions</h2>
+ Navigate to the "Specify Data" tab. Then, drag and drop an i2b2 object such as a search term or previous query onto the input box. Finally, click the "View Results" tab for information about that object.
+ <h2>About Us</h2>
+ This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
+ <h2>Terms of Use</h2>
+ This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- <div>Drop a Patient Set and a Concept (Ontology Term) into the input boxes below, and then click the "View Results" tab to retrieve information about when that concept was observed in the selected patient set. In this example, the results are returned in the standard i2b2 PDO (Patient Data Object) XML format. You may select whether to return information about the patients, events, or observations.</div>
- <div class="droptrgtlbl">Patient Set:</div>
- <div class="droptrgt SDX-PRS" id="ExampPDO-PRSDROP">Drop a Patient Set here</DIV>
- <div class="droptrgtlbl">Concept:</div>
- <div class="droptrgt SDX-CONCPT" id="ExampPDO-CONCPTDROP">Drop a Concept here</DIV>
- This plugin demonstrates how to retrieve information using the Patient Data Object (PDO).
- The PDO is the standard way in which i2b2 encapsulates all patient data.
- All plugins that need to access patient data must construct PDO Requests and parse the returned PDO Response.
- The PDO Request takes several input options, including a list of patients, groups of concepts, the list of items to be returned.
- The PDO Response, dependeing on the input options, might return details about the patients, a list of observations corresponding to the selected concepts, or information about the events during which the observations occurred.
- <h2>Instructions</h2>
- Navigate to the "Specify Data" tab. Then, drag and drop a Patient Set and a Concept (Ontology Term) onto the input boxes. You may optionally select which types of information you want returned. Finally, click the "View Results" tab to view the PDO Response.
- <h2>About Us</h2>
- This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
- <h2>Terms of Use</h2>
- This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- </div>
- </div>
- </div>
- </div>
- </div>
-
-
- </div>
-
-
- </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+ <div>Drop a Patient Set and a Concept (Ontology Term) into the input boxes below, and then click the "View Results" tab to retrieve information about when that concept was observed in the selected patient set. In this example, the results are returned in the standard i2b2 PDO (Patient Data Object) XML format. You may select whether to return information about the patients, events, or observations.</div>
+ <div class="droptrgtlbl">Patient Set:</div>
+ <div class="droptrgt SDX-PRS" id="ExampPDO-PRSDROP">Drop a Patient Set here</DIV>
+ <div class="droptrgtlbl">Concept:</div>
+ <div class="droptrgt SDX-CONCPT" id="ExampPDO-CONCPTDROP">Drop a Concept here</DIV>
+ This plugin demonstrates how to retrieve information using the Patient Data Object (PDO).
+ The PDO is the standard way in which i2b2 encapsulates all patient data.
+ All plugins that need to access patient data must construct PDO Requests and parse the returned PDO Response.
+ The PDO Request takes several input options, including a list of patients, groups of concepts, the list of items to be returned.
+ The PDO Response, dependeing on the input options, might return details about the patients, a list of observations corresponding to the selected concepts, or information about the events during which the observations occurred.
+ <h2>Instructions</h2>
+ Navigate to the "Specify Data" tab. Then, drag and drop a Patient Set and a Concept (Ontology Term) onto the input boxes. You may optionally select which types of information you want returned. Finally, click the "View Results" tab to view the PDO Response.
+ <h2>About Us</h2>
+ This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
+ <h2>Terms of Use</h2>
+ This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- <div>Drop an i2b2 object such as a search term or previous query onto the input box below, and then click the "View Results" tab for information about that object.</div>
- <div class="droptrgtlbl">i2b2 Object:</div>
- <div class="droptrgt SDX-PRS" id="ExampTabs-PRSDROP" style="">Drop an object here</DIV>
- </div>
- </div>
- </div>
- <div>
- <div class="ExampTabs-MainContent">
- <div class="results-directions">You must first provide an i2b2 object. Please return to the "Specify Data" tab then drag and drop an i2b2 object onto the input box.</div>
- <tr><th>Original XML Data</th><td class="sdxOriginalXML"><div class="originalXML"></div></td></tr>
- </table>
- </div>
- </div>
- </div>
- </div>
- <div>
- <div class="ExampTabs-MainContent">
- <div class="ExampTabs-MainContentPad">
- <h1>Example #2 - Tabs and DragDrop</h1>
- <hr size="1" noshade>
- <h2>Introduction</h2>
- This plugin demonstrates how to use tabs and interact with i2b2 objects by accepting DragDrop messages (SDX Objects).
- The three tab layout, which separates plugin input (specify data), plugin output (view results), and help content is a model that can be used by many plugins.
- SDX stands for Standard Data Exchange, which is the i2b2 web client framework's mechanism for handling drag and drop objects. The SDX, AJAX, and other utility functions provided by the framework greatly simplify the process of creating new plugins.
- <h2>Instructions</h2>
- Navigate to the "Specify Data" tab. Then, drag and drop an i2b2 object such as a search term or previous query onto the input box. Finally, click the "View Results" tab for information about that object.
- <h2>About Us</h2>
- This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
- <h2>Terms of Use</h2>
- This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- </div>
- </div>
- </div>
- </div>
- </div>
-
-
- </div>
-
-
- </body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+ <div>Drop an i2b2 object such as a search term or previous query onto the input box below, and then click the "View Results" tab for information about that object.</div>
+ <div class="droptrgtlbl">i2b2 Object:</div>
+ <div class="droptrgt SDX-PRS" id="ExampTabs-PRSDROP" style="">Drop an object here</DIV>
+ </div>
+ </div>
+ </div>
+ <div>
+ <div class="ExampTabs-MainContent">
+ <div class="results-directions">You must first provide an i2b2 object. Please return to the "Specify Data" tab then drag and drop an i2b2 object onto the input box.</div>
+ <tr><th>Original XML Data</th><td class="sdxOriginalXML"><div class="originalXML"></div></td></tr>
+ </table>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div>
+ <div class="ExampTabs-MainContent">
+ <div class="ExampTabs-MainContentPad">
+ <h1>Example #2 - Tabs and DragDrop</h1>
+ <hr size="1" noshade>
+ <h2>Introduction</h2>
+ This plugin demonstrates how to use tabs and interact with i2b2 objects by accepting DragDrop messages (SDX Objects).
+ The three tab layout, which separates plugin input (specify data), plugin output (view results), and help content is a model that can be used by many plugins.
+ SDX stands for Standard Data Exchange, which is the i2b2 web client framework's mechanism for handling drag and drop objects. The SDX, AJAX, and other utility functions provided by the framework greatly simplify the process of creating new plugins.
+ <h2>Instructions</h2>
+ Navigate to the "Specify Data" tab. Then, drag and drop an i2b2 object such as a search term or previous query onto the input box. Finally, click the "View Results" tab for information about that object.
+ <h2>About Us</h2>
+ This plugin was created by Nick Benik and Griffin Weber, MD, PhD.
+ <h2>Terms of Use</h2>
+ This example plugin is distributed with the i2b2 web client framework and may be used free of charge.
- <div><center><h1>Creating a new project based upon the existing project</h1></center><br/>This form allows a request for a new project data mart to be created. Please make the notations on the form by choosing from the options available or dragging items from existing patient sets or concepts in the current project into the boxes below. If these items are not yet created, please exit from the form to create them and then return to this form.<br/></div>
-
-<table cellpadding="0" cellspacing="0"><tr valign="top"><td width="60%"><div class="droptrgtlbl">Enter Title:</div><br clear="all"/><div class="TextMessage">Please begin by giving this project a name. This will be the name that is used throughout the program to reference the project, so generally the name should be short, although can be up to 255 characters:</div></td>
- <tr valign="top" bgcolor="#F0F0F0"><td><div class="droptrgtlbl">Select approval:</div><br clear="all"/><div class="TextMessage">Please choose from one of your registered approvals below. If as approval does not appear, it will need to be registered by an administrator before you may proceed:</div></td>
- <tr id="ProjectRequest-part2a" style="display:none;" valign="top"><td width="60%"><div class="droptrgtlbl">Pick users:</div><br clear="all"/><div class="TextMessage">According to the data from the i2b2 project management cell, the following users are allowed to be registered for this project using the approval that was chosen. If a user is not found on the list below, an administrator will need to specifically add them to the approval before you can proceed. The newly created project will allow these users to access it with the roles you choose for each user below.</div></td>
- <tr id="ProjectRequest-part2b" style="display:none;" valign="top" bgcolor="#F0F0F0"><td width="60%"><div class="droptrgtlbl">Cases:</div><br clear="all"/><div class="TextMessage">The new project will be created to include the set of patients that was created in a patient set of a current project. It may also exclude patients from separate sets as desired. These sets are dragged from the previous queries or workplace areas to the boxes below:</div></td>
- <div class="excprsItem">Drop one or more Patient Set here</div>
- </DIV>
- <br clear="all"/><div class="SubInputMessage">Exclude these patients from the cases</div>
- <div id="ProjectRequest-DeleteMsgExcPRS"><br clear="all"/>Click a Patient Set to remove it from the list.</div><br /></td></tr>
-
- <tr id="ProjectRequest-part2c" style="display:none;" valign="top"><td width="60%"><div class="droptrgtlbl">Controls:</div><br clear="all"/><div class="TextMessage">The new project may include a set of matched controls. These are included from the current project and will be selected based upon age, gender, race, and co-morbidities. You may define a specific set of the controls to be matched from, or create a set of all patients in the current project and drag the set to the box below. Patients can also be excluded from this set in a similar way to that described above.</div></td>
- <div class="excicItem">Drop one or more Patient Set here</div>
- </DIV>
- <br clear="all"/><div class="SubInputMessage">Exclude these patients from the controls</div>
- <div id="ProjectRequest-DeleteMsgExcIC"><br clear="all"/>Click a Patient Set to remove it from the list.</div><br/></td></tr>
-
- <tr id="ProjectRequest-part2d" style="display:none;" valign="top" bgcolor="#F0F0F0"><td width="60%"><div class="droptrgtlbl">Concepts:</div><br clear="all"/><div class="TextMessage">The concepts that will be included in the new project are chosen by dragging items from the Ontology or Workplace views into the boxes below:</div></td>
- <div class="excconcptItem">Drop one or more Concepts here</div>
- </DIV>
- <br clear="all"/><div class="SubInputMessage">Exclude these concepts</div>
- <div id="ProjectRequest-DeleteMsgExcConcept"><br clear="all"/>Click a concept to remove it from the list.</div><br/></td></tr>
-
-
- <tr id="ProjectRequest-part2e" style="display:none;" valign="top"><td width="60%"><div class="TextMessage">When the above form is complete, you may request this project be created by clicking the "submit" button below. A reference number will be returned that can be used to track the project.</div></td>
- <div class="results-text">Your request for a new project to be created has been received and will be serviced by the administrators. The reference number for tracking this project is shown below:
- <UL>
- </UL>
- </div>
- <div id="ProjectRequest-InfoPDO">
- <table>
- <tr>
- <th>Project ID</th>
- <td class="InfoPDO-Response"></td>
- </tr>
- </table>
- </div>
- </div>
- </div>
- </div>
- <div>
- <div class="ProjectRequest-MainContent">
- <div class="ProjectRequest-MainContentPad">
- <h1>Project Request</h1>
- <hr size="1" noshade>
- <h2>Instructions</h2>
- Navigate to the "Specify Data" tab. Then, drag and drop a Patient Set and a Concept (Ontology Term) onto the input boxes. Finally, click the "View Results" tab to view the PDO Response.
- <h2>About Us</h2>
- This plugin was created by Mike Mendis
- <h2>Terms of Use</h2>
- This plugin is distributed with the i2b2 web client framework and may be used free of charge. </div>
- </div>
- </div>
- </div>
- </div>
-</div>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+ <div><center><h1>Creating a new project based upon the existing project</h1></center><br/>This form allows a request for a new project data mart to be created. Please make the notations on the form by choosing from the options available or dragging items from existing patient sets or concepts in the current project into the boxes below. If these items are not yet created, please exit from the form to create them and then return to this form.<br/></div>
+
+<table cellpadding="0" cellspacing="0"><tr valign="top"><td width="60%"><div class="droptrgtlbl">Enter Title:</div><br clear="all"/><div class="TextMessage">Please begin by giving this project a name. This will be the name that is used throughout the program to reference the project, so generally the name should be short, although can be up to 255 characters:</div></td>
+ <tr valign="top" bgcolor="#F0F0F0"><td><div class="droptrgtlbl">Select approval:</div><br clear="all"/><div class="TextMessage">Please choose from one of your registered approvals below. If as approval does not appear, it will need to be registered by an administrator before you may proceed:</div></td>
+ <tr id="ProjectRequest-part2a" style="display:none;" valign="top"><td width="60%"><div class="droptrgtlbl">Pick users:</div><br clear="all"/><div class="TextMessage">According to the data from the i2b2 project management cell, the following users are allowed to be registered for this project using the approval that was chosen. If a user is not found on the list below, an administrator will need to specifically add them to the approval before you can proceed. The newly created project will allow these users to access it with the roles you choose for each user below.</div></td>
+ <tr id="ProjectRequest-part2b" style="display:none;" valign="top" bgcolor="#F0F0F0"><td width="60%"><div class="droptrgtlbl">Cases:</div><br clear="all"/><div class="TextMessage">The new project will be created to include the set of patients that was created in a patient set of a current project. It may also exclude patients from separate sets as desired. These sets are dragged from the previous queries or workplace areas to the boxes below:</div></td>
+ <div class="excprsItem">Drop one or more Patient Set here</div>
+ </DIV>
+ <br clear="all"/><div class="SubInputMessage">Exclude these patients from the cases</div>
+ <div id="ProjectRequest-DeleteMsgExcPRS"><br clear="all"/>Click a Patient Set to remove it from the list.</div><br /></td></tr>
+
+ <tr id="ProjectRequest-part2c" style="display:none;" valign="top"><td width="60%"><div class="droptrgtlbl">Controls:</div><br clear="all"/><div class="TextMessage">The new project may include a set of matched controls. These are included from the current project and will be selected based upon age, gender, race, and co-morbidities. You may define a specific set of the controls to be matched from, or create a set of all patients in the current project and drag the set to the box below. Patients can also be excluded from this set in a similar way to that described above.</div></td>
+ <div class="excicItem">Drop one or more Patient Set here</div>
+ </DIV>
+ <br clear="all"/><div class="SubInputMessage">Exclude these patients from the controls</div>
+ <div id="ProjectRequest-DeleteMsgExcIC"><br clear="all"/>Click a Patient Set to remove it from the list.</div><br/></td></tr>
+
+ <tr id="ProjectRequest-part2d" style="display:none;" valign="top" bgcolor="#F0F0F0"><td width="60%"><div class="droptrgtlbl">Concepts:</div><br clear="all"/><div class="TextMessage">The concepts that will be included in the new project are chosen by dragging items from the Ontology or Workplace views into the boxes below:</div></td>
+ <div class="excconcptItem">Drop one or more Concepts here</div>
+ </DIV>
+ <br clear="all"/><div class="SubInputMessage">Exclude these concepts</div>
+ <div id="ProjectRequest-DeleteMsgExcConcept"><br clear="all"/>Click a concept to remove it from the list.</div><br/></td></tr>
+
+
+ <tr id="ProjectRequest-part2e" style="display:none;" valign="top"><td width="60%"><div class="TextMessage">When the above form is complete, you may request this project be created by clicking the "submit" button below. A reference number will be returned that can be used to track the project.</div></td>
+ <div class="results-text">Your request for a new project to be created has been received and will be serviced by the administrators. The reference number for tracking this project is shown below:
+ <UL>
+ </UL>
+ </div>
+ <div id="ProjectRequest-InfoPDO">
+ <table>
+ <tr>
+ <th>Project ID</th>
+ <td class="InfoPDO-Response"></td>
+ </tr>
+ </table>
+ </div>
+ </div>
+ </div>
+ </div>
+ <div>
+ <div class="ProjectRequest-MainContent">
+ <div class="ProjectRequest-MainContentPad">
+ <h1>Project Request</h1>
+ <hr size="1" noshade>
+ <h2>Instructions</h2>
+ Navigate to the "Specify Data" tab. Then, drag and drop a Patient Set and a Concept (Ontology Term) onto the input boxes. Finally, click the "View Results" tab to view the PDO Response.
+ <h2>About Us</h2>
+ This plugin was created by Mike Mendis
+ <h2>Terms of Use</h2>
+ This plugin is distributed with the i2b2 web client framework and may be used free of charge. </div>
- * @projectDescription Message Sniffer object - sniffs communication for objects which expose a _DebugMessaging event. Example: i2b2.CRC.ajax._DebugMessaging is a custom YUI event object.
- * @author Nick Benik, Griffin Weber MD PhD
- * @version 1.3
- * updated 9-15-08: RC4 launch [Nick Benik]
- */
-
-i2b2.hive.MsgSniffer = {
- yuiModalMsg: false,
- crtlDown: false,
- windowRef: null,
- sniffSources: [],
- signalOrigins: [],
- signalMessageDB: [],
- asyncStackFilter: false,
- initialize: function(doActivate) {},
- _showSingleMsgModal: function() {
- if (!i2b2.hive.MsgSniffer.yuiModalMsg) {
- // show non-modal dialog with help documentation
- var panel = new YAHOO.widget.Panel("commViewerSingleMsg-panel", {
- draggable: true,
- zindex:10000,
- width: "650px",
- height: "450px",
- autofillheight: "body",
- constraintoviewport: true,
- context: ["tl", "bl"],
- visible: false
- });
- $("commViewerSingleMsg-panel").show();
- panel.render(document.body);
- i2b2.hive.MsgSniffer.yuiModalMsg = panel;
-
- // resizer object and event handlers
- i2b2.hive.MsgSniffer.yuiSingleMsgResizer = new YAHOO.util.Resize("commViewerSingleMsg-panel", {
+ * @projectDescription Message Sniffer object - sniffs communication for objects which expose a _DebugMessaging event. Example: i2b2.CRC.ajax._DebugMessaging is a custom YUI event object.
+ * @author Nick Benik, Griffin Weber MD PhD
+ * @version 1.3
+ * updated 9-15-08: RC4 launch [Nick Benik]
+ */
+
+i2b2.hive.MsgSniffer = {
+ yuiModalMsg: false,
+ crtlDown: false,
+ windowRef: null,
+ sniffSources: [],
+ signalOrigins: [],
+ signalMessageDB: [],
+ asyncStackFilter: false,
+ initialize: function(doActivate) {},
+ _showSingleMsgModal: function() {
+ if (!i2b2.hive.MsgSniffer.yuiModalMsg) {
+ // show non-modal dialog with help documentation
+ var panel = new YAHOO.widget.Panel("commViewerSingleMsg-panel", {
+ draggable: true,
+ zindex:10000,
+ width: "650px",
+ height: "450px",
+ autofillheight: "body",
+ constraintoviewport: true,
+ context: ["tl", "bl"],
+ visible: false
+ });
+ $("commViewerSingleMsg-panel").show();
+ panel.render(document.body);
+ i2b2.hive.MsgSniffer.yuiModalMsg = panel;
+
+ // resizer object and event handlers
+ i2b2.hive.MsgSniffer.yuiSingleMsgResizer = new YAHOO.util.Resize("commViewerSingleMsg-panel", {