Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

• Sexually transmitted (venereal) infections, NOS  +
• Treponema pallidum (Syphilis)  +
• Neisseria gonorrhea (gonococcus)  +
• Chlamydia trachomatis (bug responsible for regular sexually transmitted chlamydia)  +
• Changing D IDs  +
• Pain, pleuritic chest pain  +
• Hemorrhage, NOS  +
• Hypercapnia (hypercarbia)  +
• Stridor  +
• Dyspnea  +
• Cough  +
• Hemorrhage, respiratory sites, NOS  +
• Epistaxis  +
• High blood pressure reading  +
• Polyphagia  +
• Polydipsia  +
• Fever or fever of unknown origin (FUO)  +
• Pain, chest NOS  +
• Hypoxemia (hypoxia)  +
• Pain, abdominal or pelvic  +
• Nausea or vomiting  +
• Jaundice  +
• Tremor  +
• Dysuria (pain with urination)  +
• Anuria or oliguria  +
• Prerenal uremia/state  +
• Amnesia  +
• Hyperkalemia, severe or symptomatic  +
• Agitation, restlessness  +
• Pain, chronic NOS  +
• Hepatomegaly  +
• Organ NOS, function test, abnormal  +
• Musculoskeletal system, diagnostic imaging, abnormal  +
• Lung, diagnostic imaging, abnormal  +
• Glycosuria  +
• Testing of specimens (fluid or biopsy) from organ or tissue, NOS, abnormal  +
• Toxicology, blood, cocaine, positive  +
• Lung, function test, abnormal (Pulmonary function test, PFT)  +
• Toxicology, blood, addictive drugs NOS, positive  +
• Central nervous system, diagnostic imaging, abnormal  +
• Cardiovascular system, function test, abnormal  +
• Atrial fibrillation and/or atrial flutter  +
• Ventricular fibrillation  +
• Ventricular tachycardia  +
• Supraventricular tachycardia, paroxysmal  +
• Tachycardia  +
• Sick sinus syndrome (SSS, tachy-brady syndrome)  +
• Hypoglycemia, in diabetes  +
• Violent behavior  +
• Pain NOS, not specified if acute or chronic  +
• Category:Testing  +
• Category:Symptom/Sign  +
• Hypocalcemia, severe or symptomatic  +
• SBGH Swing Beds  + ( * to be sure, if I remember right STB ICU … </br>* to be sure, if I remember right STB ICU does that for ALL [[Boarding Loc]] entries, not just swing beds, right? Just trying to confirm, because if that's true then it's not a swing bed instruction but instead a [[STB Critical Care Collection Guide]] instruction (or possibly a [[Boarding Loc]] one). [[User:Ttenbergen|Ttenbergen]] 11:33, 2022 January 27 (CST)</br>** Yes, the arrive time for all ICU patients is taken from the ICU flow sheets</br>*** Then we should remove this info from here and from [[STB CICU Collection Guide]] and put it into [[STB Critical Care Collection Guide]] instead. I can do that, any objections? [[User:Ttenbergen|Ttenbergen]] 15:57, 2023 May 24 (CDT)</br>** I have done this Tina can we delete this page? [[User:Lkaita|Lisa Kaita]] 11:36, 2024 March 12 (CDT) I haven't done anything with the background or related articles etc</br>with the background or related articles etc )
• Cardiac arrest  + (Could we please have some clarification ar … Could we please have some clarification around using this code and when to check as primary? </br>**example 1 patient arrests in ER, goes to OR and is admitted to ICU from the OR. Diagnosis, cardiac arrest (6-10 min downtime) abdominal compartment syndrome/obstruction/perforation/, acute liver failure from shock liver, shock, NOS</br>*when to carry it forward as an admit for subsequent profiles in the same episode of care?</br>**example 2 April 6, PEA arrest secondary to anaphylactic shock, April 19 melena, scope suspicious for ischemic gut, goes to the OR April 20 confirms gangrenous bowel/perforation, abscesses, to SICU post op (clinically in SS but doesn't have lactate high enough for our criteria) do we still include the cardiac arrest code? (In MICU no anoxic brain injury, A & O) [[User:Lkaita|Lisa Kaita]] 11:54, 2024 May 2 (CDT)[[User:Lkaita|Lisa Kaita]] 11:54, 2024 May 2 (CDT))
• Change of remaining location names from "our" names to EPR/Cognos names  + (JALT - Is there anything here we want to d … JALT - Is there anything here we want to do before SF? Or that still needs to be done at all? [[User:Ttenbergen|Ttenbergen]] 09:42, 2023 July 6 (CDT)</br>* What happens to the ICU [[Previous Location]], [[Pre-admit Inpatient Institution]], [[Dispo]] or even [[Service Location]] - should they be changed too by the new COGNOS ICU locations? Example current STB_ACCU is SBGH-CCUO in COGNOS, STB_CICU is SBGH_ICCS, STB_MICU is SBGH_ICMS. Should the old labels remain? We need to think hard for its implications to queries of linking and/or matching tables before implementing any change. --[[User:JMojica|JMojica]] 16:33, 2022 February 2 (CST) </br>** It would be nice to have this consistent, and yet you are correct that this would tie into a lot of things. I think the benefits of making it consistent win out, though especially when it comes to also thinking about this in terms of that metadata we discussed the other day. Even if we keep the (possibly identical) data in both s_tmp and s_dispo for now, we would then be able to use that metadata table for both. This would require thinking through the details. Julie, I think it only involves you and me, so maybe we should discuss at our wiki meetings? [[User:Ttenbergen|Ttenbergen]] 13:44, 2022 February 8 (CST)</br>*** Julie and Tina discussed: </br>:::* We use the 4 fields [[Previous Location]], [[Pre-admit Inpatient Institution]], [[Dispo]] and [[Service/Location]] also to map patient flow between laptops, and we very much don't use Cognos values for this (e.g. HSC_Med). We need to retain this ability to use the entries for linking but would also make them the same as Cognos where possible. So we need to keep our "own" values for this for locations where we collect. </br>:::* We decided to use manually split CC entries e.g. HSC_MICU vs HSC_SICU since Julie reports in those increments, ie it is hard to pull apart a stay in two ICU types if it is collected as one record. We don't want to lose that. </br>:::* We would still like to change these own values to the "modern" values where we use legacy terms, eg. STB ICMS vs STB MICU. As long as we make a clean transition between old and new, or change all old, that should not be a problem, but we need to account for it. </br>:::* We could use the Cognos values for all places where we don't collect, e.g. if a pt comes from Ward HSC_A1 and Cognos lists that as HSC-GA1, we could just enter that. However, for locations we don't collect we currently aggregate this to HSC_ward. Do we want the extra detail? It would be easier to enter but might be harder to interpret and possibly even harder to work with for collectors. </br>:::* If we want to keep our proprietary value for locations where we collect, and keep aggregate ones for locations where we don't collect, I am not sure which locations that then leaves where we would use the Cognos values? </br>*** Julie, do you agree to that summary? If so, there may be nothing to discuss with Lisa, since we will need to leave this as is. If I am missing something pls update and then pass on to Lisa for her take. [[User:Ttenbergen|Ttenbergen]] 16:56, 2022 March 23 (CDT) </br>**** agree. pass to lisa. --[[User:JMojica|JMojica]] 15:27, 2022 June 8 (CDT)</br>*I think this is no longer an issue, unless we are looking to change how we collect this, which I am not in favor of [[User:Lkaita|Lisa Kaita]] 12:23, 2022 August 24 (CDT)</br>** Even though this is no longer an issue, we should keep the above 5 summary issues here for future reference. --[[User:JMojica|JMojica]] 13:38, 2024 March 12 (CDT)[[User:JMojica|JMojica]] 13:38, 2024 March 12 (CDT))
• Query cardiac arrest throughout admission  + (JALT Review after 2023-09-15 * Lisa flagge … JALT Review after 2023-09-15</br>* Lisa flagged that, if we do this for Cardiac Arrest, we should really do it for other dxs as well. And if we did that, it could result in a lot of work since it would need to be mediated by Pagasa for now. So we decided to see where the SF implementation goes and review the definition of this check once we have a centralized tool where the data collector would not need to mediate this. [[User:Ttenbergen|Ttenbergen]] 15:43, 2023 July 13 (CDT)[[User:Ttenbergen|Ttenbergen]] 15:43, 2023 July 13 (CDT))