Update of D ID to include a laptop identifier

From CCMDB Wiki
Jump to navigation Jump to search

This page documents our move to a D_ID that contains a Laptop identifier.

Why do we need to do this?

Our D_IDs consist of the site and location and the Pat ID/Serial number, e.g. HSC_A4-123. They must be unique. If two collectors wanted to enter for the same ward on two different laptops, we would need to make sure that there are no duplicate D_IDs used. Right now we use two methods for this.

If/when we move to PatientFollow Project, the first solution would become completely impractical, and we would have to add dozens of fake entries to S dispo table to use the second solution, so we should fix it right instead. Also, with current understaffing, it would be nice to be able to do this as necessary to help others out. Finally, the situation of "unknown location" patients at HSC leads us to a situation where we may not know for much of a pt's stay which laptop they should go on, so it would be best to collect as we go and be able to edit location to what it needs to be later.

This also needs to be addressed to better collect HSC Unknown Service.

What do we need to do?

We need to add the Laptop identifier to the beginning of the D_ID.

  • Can anyone else think of additional things that would be affected by this?
  • SMW


  • Cargo


  • Categories

local changes to laptops

Batches and scripts that would need updating

deal w orphans

When we do, there will be Orphans in Centralized data.mdb, so we need an easy way to tell "real" orphans from ones that should just be cleaned up after this. In other words a query for Pagasa to help make that determination.

update sending

We will need to update the send functionality for this. Sending_Patients#What_happens_when_patients_are_sent This requires a change to a lot of queries, so we would want to proof this before rolling it. Probably best to make a test patient on Tina's laptop send before and send after, and then test that Pagasa Query to see if pt us successfully excluded from orphans.

Any concern for Julie? Confirm no parsing of D_ID for meaning will break because of this

Julie has confirmed that we do not parse or otherwise draw meaning from D_ID in ways that would be broken by this change.

TISS Scanning

Background:

  • Currently the Unit and Serial on the TISS forms uniquely map each form to a patient / D_ID. To move to the new definition of the identifier we need to find a way to connect TISS to D_ID. One way would be to re-do the form and the TISS28 Form Scanning process to accommodate the new data natively. We rarely change things in Teleform, so it would be preferable to not mess with that working system.

Proposed solution:

  • There is a legacy field "Page" on the forms. It is still being scanned and verified, but we are no longer capturing the data because testing for continuous dates is sufficient. We will re-label and re-use this field to capture the laptop ID instead.
  • Pagasa has tested a re-labelled form and the Teleform scanning, verifying, committing and importing worked.
  • Julie has been consulted about this and thinks this should cause no problems at her end
  • Question has been put to collectors at TISS28 Collection Guide, waiting for feedback. Ttenbergen 08:03, 2020 February 12 (CST)
  • SMW


  • Cargo


  • Categories

Required changes:

First week in March Julie is away and Vac planning is done, so that would be the time to go live.

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Update_of_D_ID_to_include_a_laptop_identifier&oldid=142033"