Facilitated Management of Serial numbers: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
(→‎Question - Serial series per laptop or per Service/Location: re-grouped into one vs more pools per laptop; moved details about what is collected on H4, H5, S5 to Laptop identifiers)
Line 11: Line 11:
Please put something like "per laptop" or "per unit", or narrative if it's more complicated than that:
Please put something like "per laptop" or "per unit", or narrative if it's more complicated than that:
* G8 - [[GRA_N3]], [[GRA_N5]] (N3a, N5a) - '''no response yet '''
* G8 - [[GRA_N3]], [[GRA_N5]] (N3a, N5a) - '''no response yet '''
* H9 - old HSC_ICUa - service locations are pooled (need to check what that means)
* H8 - old HSC_ICUb - service locations are pooled
* H7 - old HSC_ICUd - service locations are pooled
* S9 - old [[STB_ACCU]] - '''no response yet '''
* S9 - old [[STB_ACCU]] - '''no response yet '''
* S8 - old [[STB_CICU]] - '''no response yet '''
* S8 - old [[STB_CICU]] - '''no response yet '''
Line 23: Line 20:
* G7 - [[GRA_N5]]/[[GRA_S3]] - using 1 pool of numbers for both
* G7 - [[GRA_N5]]/[[GRA_S3]] - using 1 pool of numbers for both
* S6 - old STB_MedB ([[STB_B5]]/[[STB_IMCU]]) - Unit locations share same serial number pool
* S6 - old STB_MedB ([[STB_B5]]/[[STB_IMCU]]) - Unit locations share same serial number pool
* H9 - old HSC_ICUa - service locations are pooled
* H8 - old HSC_ICUb - service locations are pooled
* H7 - old HSC_ICUd - service locations are pooled





Revision as of 10:43, 2020 June 5

Collection instruction

The "Add Patient with Serial Helper" button on the Patient List launches a form that lets the collector pick a Service/Location. The form then proposes the next sequential Serial number based on the location chosen and any current or recently deleted records (we keep track since EPR Reports Integrator) on the laptop.

If no previous entry of that location is found, the number used for a new location as per Serial_number#Special-Use_Serial_Numbers will be used.

Question - Serial series per laptop or per Service/Location

  • As people are testing Cognos Admitter and "Add Patient with Serial Helper" button, I am hearing that there are two ways to generate the next Serial number. Some use a serial pool per Service/Location, and some use one serial pool for everything on their laptop. There might be a third option where some service locations are pooled but there also is a second pool for another service location. This makes automation or vacation coverage problematic. Could you please fill in what you do on your laptop?
  • SMW


  • Cargo


  • Categories

Still unclear: Please put something like "per laptop" or "per unit", or narrative if it's more complicated than that:


One pool per laptop:

  • G9 - GRA_MICU - one serial pool for laptop G9 & unit GRA MICUGens 12:45, 2020 June 3 (CDT)
  • G7 - GRA_N5/GRA_S3 - using 1 pool of numbers for both
  • S6 - old STB_MedB (STB_B5/STB_IMCU) - Unit locations share same serial number pool
  • H9 - old HSC_ICUa - service locations are pooled
  • H8 - old HSC_ICUb - service locations are pooled
  • H7 - old HSC_ICUd - service locations are pooled


More than one pool per laptop:

  • H6 - HSC_A4 - one set of serial numbers for A4 and contingency patients, one set of serial numbers for B2, one set of serial numbers for EMIP
  • H5 - HSC_B3 (& HSC_WRS3)
    • serial numbers for B3, WRS3 and contingency units (H6 & WRS2) are all from the same number pool.
    • Serial numbers for B2 (High Obs)are from a different pool.
    • Serial numbers for EMIPs are also from a different pool.
  • H4 - HSC_D5 and HSC_D4_COVID -
    • The serial numbers for D4 and it's boarding locations of H6 and WRS2 are all from the same number pool.
    • The serial numbers from B2 (which is currently the High Obs unit), are a different pool of serial numbers.
    • The EMIP's also have their own unique number pool.
  • H3 - HSC_H4 - one set of serial numbers for A4 and contingency patients, one set of serial numbers for B2, one set of serial numbers for EMIP
  • S5 - old STB_MedA (STB_E6_B) - Patients transferred to E5 (A service) continue to be followed-all using same serial number pool. In addition overs are tracked 1-15th inclusive every month and assigned/entered according to service. EMIPs 1-15th every month regardless of service and entered using a separate serial number pool.
  • S4 - old STB_MedD (STB_E5) - E5 uses one set of serial numbers, and the emip's that I collect are a completely different set of serial numbers DPageNewton 07:26, 2020 June 4 (CDT)



  • Would anyone see a problem if we standardized this to using one serial number pool per laptop? What would be the problems? Ttenbergen 19:55, 2020 June 2 (CDT)
    • if you follow the higher number sequence per laptop (discontinue the lower one). There will be no problem for unique record. However, those outstanding (incompletes) wards with lower number sequence will become orphans in the master database which Pagasa has to delete. I think the deletion will be easy and Pagasa need not crosscheck at all or confirm with the DC - simply delete the ones with lower serial number. The drawback for following the higher sequence order (currently 5 digits) is the growing number of digits over time which consequently has an effect on D_ID.
      • Another option, have a fresh start with a new lower number (2 or 3 digits) or continue the lower number sequence for all laptops. This would mean changing something to all profiles having laptop identifier (say, make the serial # negative or change the laptop identifier ,e.g. H9 to HS9). Any change for the incompletes will result to orphans and more orphans if this is the option. --JMojica 08:48, 2020 June 3 (CDT)
  • SMW


  • Cargo


  • Categories

Negative and presumably decreasing serials

  • Looks like HSC_WRS3 uses negative and possibly decreasing serial numbers. That would throw a wrench into automatic number suggestion. Is this a usual thing or just something to solve problems generated by the COVID moves?
    • this is not the usual thing, this was done initially to solve the duplicate records (i.e. before and after covid) but after changing the process, the positive serial number sequence has been followed. --JMojica 08:46, 2020 June 3 (CDT)
  • SMW


  • Cargo


  • Categories

Background

Data collectors currently collect one or more locations from one or more pools of serial number pools. Details of the serial number system are located in Serial number. This has been flagged as one reason why people find paper printouts of the most recent patients sent useful.

Serial numbers have to be unique for a collection location, so if a ward like HSC_H4H is collected on by multiple collectors then a serial number must never be re-used. This is currently achieved by assigning blocks of numbers for each 100 possible serial numbers to a given collector (again, see Serial number for details).

A serial number must be entered before any other data since access uses it to set the relationships for the data. To accomplish that, function new_pat_id() opens a window requesting the serial number pops up when "add new patient" is clicked on the patient list.

The need to keep track of this is one reason given by collectors to keep using the Data collection log form. We would like to eliminate reasons for this additional paperwork.

Related articles

Related articles: