Search by property

Jump to navigation Jump to search

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.

Search by property

A list of all pages that have property "DiscussQuestion" with value "This is a legacy field we could probably get rid of. Not sure when we stopped using it.". Since there have been only a few results, also nearby values are displayed.

⧼showingresults⧽

View (previous 1,000 | next 1,000) (20 | 50 | 100 | 250 | 500)


    

List of results

     (This is a legacy field we could probably get rid of. Not sure when we stopped using it.)
    • Service/Location field  + ( * Hey T, this page is for the Service loc</br>* Hey T, this page is for the Service location field in the demographics Tab correct? not sure why we have this as a legacy field? Or am I misunderstanding this?[[User:Lkaita|Lisa Kaita]] 15:11, 2024 March 6 (CST) </br>** I think that was written when we first changed and decided to only have <site>_<program>, ie before we split the CC program back up. In a way it is still legacy as that meaning, because now the meaningful info should live in Service and Unit entries in tmp. Between this and your question below about where that info should live, we may want to make an overarching page for the three concepts. I was wondering if we already have one, but the closest thing is [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] and that's not quite it. The cleanest way to to it might be to make a new page of the current [[Collection instructions for Service/Location vs Boarding Loc vs Service]] page, interlink it with the change page, and then keep only the current state/collector instruction in the "collection instructions..." page and the history in the "Change..." page. This is one of those things that are difficult to document because we need both the current state for collection and the complete history for interpretation. Having two pages like that should do it. [[User:Ttenbergen|Ttenbergen]] 16:30, 2024 March 6 (CST)</br>** I am not entirely clear on your instructions, or how to go about doing some of this, maybe when you have time we can chat about it, no rush [[User:Lkaita|Lisa Kaita]] 12:25, 2024 March 12 (CDT)</br>*** Are you in today to chat? [[User:Ttenbergen|Ttenbergen]] 11:22, 2024 March 21 (CDT)</br>[[User:Ttenbergen|Ttenbergen]] 11:22, 2024 March 21 (CDT) )
    • "cannot open any more tables" in Access  + ( *After 24 rows, open and closed assigning</br>*After 24 rows, open and closed assigning Pseudo Phin an error message pop up then I cannot assign Phin anymore. I closed CFE then open then I am good to go again. The second time the error message pop up not 24 rows it less than 24 like 15 rows then it will show again the error message. [[User:PTorres|PTorres]] 16:09, 2022 June 14 (CDT)</br>** Is it the "cannot open..." error or the "enter parameter..." error you get at this point? Emailed Pagasa... [[User:Ttenbergen|Ttenbergen]] 10:49, 2022 November 16 (CST) </br>*** Still shows "cannot open "so I clicked ok then it says run time error 3014 cannot open any more tables. Closed the CFE then log back in.</br>*** After I continue assigning Pseudo Phin after 25 rows "cannot open" showed up again I clicked ok then error message shows again. Closed CFE then log back in.[[User:PTorres|PTorres]] 14:42, 2022 November 30 (CST)</br></br>**** Are you following the steps in [[Generating PseudoPHINs]] when this goes wrong? Which step in those instructions are you at when it stops responding and you need to restart the program? [[User:Ttenbergen|Ttenbergen]] 13:48, 2022 November 29 (CST)</br>*** Yes, I am. I am clicking and assigning the new Pseudo Phin and not moving. [[User:PTorres|PTorres]] 14:47, 2022 November 30 (CST)</br>[[User:PTorres|PTorres]] 14:47, 2022 November 30 (CST) )
    • Change of remaining location names from "our" names to EPR/Cognos names  + (JALT - Is there anything here we want to dJALT - 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))