Data Processor

From CCMDB Wiki
Jump to navigationJump to search

p:Pagasa Torres is the data processor for the Critical Care and Medicine Database.

The data processor is the main user of the Data Processor PC.

Her tasks include

Questions for Pagasa

21

 QuestionModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.Last editor is"Last editor is" is a predefined property that contains the page name of the user who created the last revision and is provided by Semantic MediaWiki.
Scanning to network
  • Discussed with Pagasa to test scanning larger volume to make this smudge problem show up, but then giving the scanner ~15 minutes to cool down without cleaning it to test if this is really an overheating issue. Waiting to hear back. PTorres 09:49, 2019 February 11 (CST)
11 February 2019 15:49:58Pagasa Torres
Correcting Person IDs
Cleaning up a failed send 7 February 2019 05:16:32Ttenbergen
Serial number duplication
  • Is any of this still an issue or have orphans and CFE taken care of it? Ttenbergen 16:07, 2015 May 27 (CDT) Ttenbergen 11:00, 2015 June 25 (CDT) Ttenbergen 17:07, 2016 March 21 (CDT) Ttenbergen 17:51, 2016 June 16 (CDT)
10 March 2019 04:46:34Ttenbergen
Data Processing Priority
  • Is this still accurate? How about other days? Why those days? This page needs to be set up so that whoever covers would know how to determine the priority.
7 February 2019 05:25:05Ttenbergen
Processing errors in patient data


Automate the populating of notes so button just does it.

  • raise an input box for a summary, if gets content put data and content into Notes, else put nothing.
7 February 2019 16:43:11Pagasa Torres
Changing PHINs
PL missing L Tables content
  • Pagasa, could you please log here when this query lists errors, and what was found to be the problem (ie whether there was data in CCMDB.mdb that didn't make it, or no data in first place.
  • 7 January 2019 03:24:29Ttenbergen
    Link suspect mismatch to ours incomplete query
    • There is a query Link suspect mismatch to ours incomplete2 (with a 2 at the end) in CFE. What is the story, and which one do you actually use?
    31 October 2018 23:36:26Ttenbergen
    Changing D IDs
    • Which program do you do this in? This may actually need to be different instructions for different scenarios.


    • what queries would get you to change a D_ID? We would want to cross-link them so they point to these instructions, and so these instructions can list them as cause.


    • what queries would get you to change a D_ID for medicine? We would want to cross-link them so they point to these instructions, and so these instructions can list them as cause.

    How about L TISS Form table, L TISS Item table and L Labs DSM table? Are there others I am not thinking about ? Ttenbergen 22:20, 2019 February 6 (CST)
    7 February 2019 05:35:20Ttenbergen
    PL Chart 9 Digit 7 February 2019 14:34:25Ttenbergen
    Crash TISS MDB 11 February 2019 17:02:28Ttenbergen
    Encounter processing
    • says inactive, but do you actually do this? Is there anything else to it? Do we have, and do you run any multi-encounter checks yet? I guess a lot of the PLs kind of are those...
    7 February 2019 05:38:55Ttenbergen
    Scheduled TasksDo we still schedule Backup Checker?10 March 2019 04:43:46Ttenbergen
    TISS28 backup and start.vbsDo you still use this? It is not linked, so as part of what process?7 February 2019 03:31:50Ttenbergen
    Fixing a D ID in TISS28.mdbPagasa will test the quicker way, and if satisfied, will clean out the two old methods.11 February 2019 22:30:49Pagasa Torres
    Pre-linking checksnot working right now due to PL_SamePHIN_Site_Diff_chart size limit
    This automatic list includes an PL missing L Tables content - where does it fit in into the order in which you run these above? It is likely a very first thing, right?
    20 March 2019 21:48:48Ttenbergen
    Linking in centralized data front end.mdbWhy are these not the same as below? What are we doing now? Do these need to be done in a specific order?30 January 2019 19:26:22Ttenbergen
    Procedure when there are differences between L Log and L PHIWhy, what does that tell you? The only way I can imagine this would happen is if the record was deleted in centralized L_Log. In that case, if you are lucky and there is still a ccmdb_data with the completed/sent record, you can follow the Re-sending data process. If not, find it in a previous version of Centralized data.mdb, print or write down all data for the record, and manually re-enter it in a CCMDB.mdb and follow the Re-sending data process. Or what do you do? Ttenbergen 21:38, 2019 February 6 (CST)7 February 2019 03:44:39Ttenbergen
    FirstName fieldunder #Legacy info it said we stopped messing with names so cross checks with old data would work. If we no longer do that we should fix the reasoning there.
    please confirm what we actually do now:
    9 March 2019 22:11:23Ttenbergen
    LastName fieldplease confirm what we actually do now:
  • in case of a typo
  • in case of a change
  • do you use the Alias ID collection for this?
  • 9 March 2019 22:11:46Ttenbergen

    Questions in category:Data processing

    Swiss Army Knife.svg leave these for now, Tina will go over these and take those that are not really data processing out of the category before we try to address the rest.
     QuestionModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.Last editor is"Last editor is" is a predefined property that contains the page name of the user who created the last revision and is provided by Semantic MediaWiki.
    Panelling or Discharge PlanningThat link no longer goes anywhere, the heading is not on that page. Can the reference be deleted from here, or do we need to review? And, how will this affect the use of the Category:Awaiting/delayed transfer codes? Ttenbergen 14:51, 2018 September 6 (CDT)
    28 November 2018 04:53:25Ttenbergen
    Check pre acute consistentwhat exactly do we want to check for? Please also have a look at the stuff below that doesn't specifically have your name. This requested check ties into a bunch of things and if we want the check we need to be sure that instructions stay consistent and lose ends are tied up.
    There was a previous attempt to address some of this in Care levels in the community; this page and it need to be consistent, and consistently linked from the relevant field definitions. If we can get it short enough we might make a template to apply the instructions to each of the field pages.
    How does Chronic Health Facility fit into this?
    There was talk about comparing Postal Codes to known PCH Postal Codes. Since these might Include other buildings at the same site that are not PCHs, this check can at best be a soft check. Please add the list of these postal codes here.
    • from a data perspective, what do you mean by "admitted directly"? If I were to build a check, where would I find that? OR maybe I don't need to know, but then I need to have a definition of what combination of data would be an error.

    Integrity check


    • ... unless they are discharged somewhere else entirely, like another ward. So what do we really mean with this? That they can't come from one PCH and go to another or maybe "home" after all?
      • I realize this maybe hard to do. what I mean here is that if one is already a PCH resident, when leaving the hospital, the dispo location must be a PCH location too. or is a patient is already in CHF, the destination when leaving the hospital must either be a CHF or another PCH.


    • Need to look at the PCH Postal code data.

    It may be relevant to this check that we have ICD10 Imprisonment/incarceration and other info in Prison / Jail / Correctional Institution.
    21 December 2018 16:09:26Ttenbergen
    Scanning to network
    • Discussed with Pagasa to test scanning larger volume to make this smudge problem show up, but then giving the scanner ~15 minutes to cool down without cleaning it to test if this is really an overheating issue. Waiting to hear back. PTorres 09:49, 2019 February 11 (CST)
    11 February 2019 15:49:58Pagasa Torres
    Correcting Person IDs
    Cleaning up a failed send 7 February 2019 05:16:32Ttenbergen
    TISS28 Form Scanning
    • Put the queries in a drop down list or accessible through a button in TISS.mdb, similar to way queries are set up in CFE. Trish Ostryzniuk 11:21, 2019 February 7 (CST)


    • If a frozen version is kept available during TISS scanning anyways then there is no reason to not do these checks in CFE, is there? Or rather, collectors sending would not be the reason. Pagasa, let's talk about this. Maybe we can make this more convenient for you. Or write down the actual reason why it can't be done. Ttenbergen 00:34, 2017 November 12 (CST)
      • Discussed this with Pagasa. It would mean doing scanning during send time, and likely doing all fixes during pull time, so all checks could actually be done form CFE. Discussed also w Pagasaa that we would delete the error checks from TISS so there is no duplicates getting out of sync
    10 March 2019 01:41:00Ttenbergen
    Data Processing Priority
    • Is this still accurate? How about other days? Why those days? This page needs to be set up so that whoever covers would know how to determine the priority.
    7 February 2019 05:25:05Ttenbergen
    Processing errors in patient data


    Automate the populating of notes so button just does it.

    • raise an input box for a summary, if gets content put data and content into Notes, else put nothing.
    7 February 2019 16:43:11Pagasa Torres
    Comfort Care
  • We may be able to stop this when ICD10 comes; but continued collection wont break anything.

    • Julie, can you add here why this can stop when ICD10 comes? Is it because we will start collecting Palliative care? Because that is not really the same definition...

    We will need to update a the reference to this in Palliative_care#This_code_vs_Comfort_Care once decided.

    1 February 2019 17:50:15Ttenbergen
    Changing PHINs
    Link suspect mismatch to ours incomplete query
    • There is a query Link suspect mismatch to ours incomplete2 (with a 2 at the end) in CFE. What is the story, and which one do you actually use?
    31 October 2018 23:36:26Ttenbergen
    List of Factor affecting data quality
    • These points about improving APACHE were made a long time ago. Since then we added a listing for default values and ranges, and the BP Helper button, and the reference values and ranges on the Patient viewer tab APACHE. Would you say that these issues are addressed or is this still a problem?

    These comments were made a long time ago, before we used EPR, and before we split the admit time into Accept DtTm and Arrive DtTm. Are any of these still relevant? If not I would like to clean them out.
    We certainly have more guidelines now than we did in 2011... is this still a concern?
    10 March 2019 04:20:22Ttenbergen
    Changing D IDs
    • Which program do you do this in? This may actually need to be different instructions for different scenarios.


    • what queries would get you to change a D_ID? We would want to cross-link them so they point to these instructions, and so these instructions can list them as cause.


    • what queries would get you to change a D_ID for medicine? We would want to cross-link them so they point to these instructions, and so these instructions can list them as cause.

    How about L TISS Form table, L TISS Item table and L Labs DSM table? Are there others I am not thinking about ? Ttenbergen 22:20, 2019 February 6 (CST)
    7 February 2019 05:35:20Ttenbergen
    PL Chart 9 Digit 7 February 2019 14:34:25Ttenbergen
    Bed Census Data Processing Instructions
    • is this the current process, or is Bed_census.mdb? I think the process is better off here than in the .mdb article.


    • probably incomplete... Ttenbergen 18:17, 2016 April 14 (CDT) emailed Trish/PAgasa Ttenbergen 16:46, 2018 October 30 (CDT)
    9 November 2018 01:05:32Trish Ostryzniuk
    Encounter processing
    • says inactive, but do you actually do this? Is there anything else to it? Do we have, and do you run any multi-encounter checks yet? I guess a lot of the PLs kind of are those...
    7 February 2019 05:38:55Ttenbergen
    Completeness of TISS records
    • we will track the TISS outstanding status in the L_PHI.notes field
    • that field will be made available in CFE underneath notes field
    • email button will be changed to store in L_PHI.notes
    • Pagasa will clear notes field when done
    • update definition for "vetted" to reflect it does not include TISS
    • move all TISS queries into CFE
    11 March 2019 20:18:39Ttenbergen
    Project ABO TEE
    • If there is no TEE done pre-CPB (cardiopulmonary bypass), then can you use a pre-op standard Echo-cardiogram for this?--LKolesar 13:19, 2015 September 16 (CDT)
      • Could you ask the cardiologists who wanted this data this question? Ttenbergen 22:28, 2019 March 9 (CST)
    10 March 2019 04:28:49Ttenbergen
    List of diagnoses affecting Overstay Project (pre-ICD10)
    • in reconciling these, a lot are based on Charlson Comorbidities in ICD10 codes, so whatever we use there should be consistent with here.
      • Allan was OK with these at list meet today Ttenbergen 14:58, 2019 February 25 (CST)
    25 February 2019 20:58:13Ttenbergen
    PL SamePHIN Site Diff chart1 this query has reached the 2GB limit, must see if I can lean it out or otherwise reduce the size7 February 2019 16:16:51Pagasa Torres
    TISS28 backup and start.vbsDo you still use this? It is not linked, so as part of what process?7 February 2019 03:31:50Ttenbergen
    Query NDC VAP no TISSFYI Maybe 7 February 2019 14:08:04Ttenbergen
    Reconnect CFE and initial error checksre-name these so not PL any more
    Fix why it gives this error as part of fixing DSM process.
    Tina will fix Query check CCI must have entry so those are caught going forward.
    7 February 2019 16:00:02Pagasa Torres
    Query NDC CLI AcqDX but NoCLI DateinTMPV2ICD/CCI remove once old pt gone7 February 2019 14:05:59Ttenbergen
    Query NDC CLI No AcqDX but CLI DateinTMPV2ICD/CCI remove once old pt gone7 February 2019 14:06:07Ttenbergen
    QA Septic ShockIs "Every entry for project QA Septic must have either a date or a time." a request for a cross check? or does that check exist already?3 January 2019 05:41:09Ttenbergen
    Critical Care Vital Signs MonitoringIt says that CCVSM is in Quarterly report. If CCVSM is no longer, is it still in quarterly?21 January 2019 18:46:58Ttenbergen
    Fixing a D ID in TISS28.mdbPagasa will test the quicker way, and if satisfied, will clean out the two old methods.11 February 2019 22:30:49Pagasa Torres
    Pre-linking checksnot working right now due to PL_SamePHIN_Site_Diff_chart size limit
    This automatic list includes an PL missing L Tables content - where does it fit in into the order in which you run these above? It is likely a very first thing, right?
    20 March 2019 21:48:48Ttenbergen
    Validation against Patient Registry DataThis page was started long ago to keep track of our attempt to get access to the registry. I think it would be good to re-convene on it so we have a central point where past efforts and current efforts can be tracked. That would also make it easier to take it to task or steering and have consistent info. Do you have a log of this somewhere? We can rename it if you want.3 January 2019 21:26:12Ttenbergen
    Query TISS Errors NrTISSDays NE LOSTina to break out this standard check information to a different page to link to... and clean up duplication11 February 2019 22:15:54Pagasa Torres
    Generate Person IDs20 March 2019 22:12:17Ttenbergen
    Linking in centralized data front end.mdbWhy are these not the same as below? What are we doing now? Do these need to be done in a specific order?30 January 2019 19:26:22Ttenbergen
    Procedure when there are differences between L Log and L PHIWhy, what does that tell you? The only way I can imagine this would happen is if the record was deleted in centralized L_Log. In that case, if you are lucky and there is still a ccmdb_data with the completed/sent record, you can follow the Re-sending data process. If not, find it in a previous version of Centralized data.mdb, print or write down all data for the record, and manually re-enter it in a CCMDB.mdb and follow the Re-sending data process. Or what do you do? Ttenbergen 21:38, 2019 February 6 (CST)7 February 2019 03:44:39Ttenbergen
    CRRTWould it make sense (e.g. are the stickers of a size where this is possible) to give the nephrologists stickers so they can attach them as needed? Ttenbergen 15:14, 2018 September 21 (CDT)3 January 2019 05:09:07Ttenbergen
    Project Borrow arrivedid they ever get back to us?23 January 2019 00:15:12Ttenbergen
    Data Processorleave these for now, Tina will go over these and take those that are not really data processing out of the category before we try to address the rest.10 March 2019 02:16:39Ttenbergen
    LastName fieldplease confirm what we actually do now:
  • in case of a typo
  • in case of a change
  • do you use the Alias ID collection for this?
  • 9 March 2019 22:11:46Ttenbergen
    H1N1seems odd that we would have done a flu study only for 1 month in a summer...3 January 2019 05:14:23Ttenbergen
    Correcting suspect linksupdate when the button has been added: When done, click the ... button to confirm all link_suspects queries are clean.7 February 2019 17:38:11Pagasa Torres
    Query TISS Errors missing dayswhich report/s are these actually included in?11 February 2019 22:14:57Pagasa Torres
    QA Infection VAPwill we still need to collect this in ICD10, since I think all the data now lives in the dx codes as well. I am holding off on implementing Query s tmp QAInf tmp no dx until resolved. same reply as in QA CLI. --JMojica 12:04, 2018 December 27 (CST)3 January 2019 05:08:29Ttenbergen
    Questioning data back to collectorsz
    • Possible future scenario: The data processor puts the concern into the Notes field and sets the RecordStatus field to "questioned". Next time the collector sends, the record is returned to the laptop by a series of queries. The collector updates the record, sets it to "complete" and sends it in with the next round of sends, at which time it will be processed like any other record.

    This process is more automated and would need to be validated before we could implement. It would be the least work for all involved, though, I think.

    We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)
    10 March 2019 04:32:26Ttenbergen

    IT Access used

    Related Articles

    Related articles: