Centralized data front end.accdb Change Request: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 3: Line 3:
This article contains requested changes for [[Centralized data front end.accdb]]. See [[Centralized data front end.accdb Change Log]] for it's change log.
This article contains requested changes for [[Centralized data front end.accdb]]. See [[Centralized data front end.accdb Change Log]] for it's change log.


{{DT |  
{{DT | dev_CFE
* clean up the form (whatever that meant)
* clean up the form (whatever that meant)
* add button for link suspect queries to patient list
* add button for link suspect queries to patient list
Line 9: Line 9:


==New change request==
==New change request==
{{DT |  
{{DT | dev_CFE
* 2019 March 01 - move ''priority number'' column for ICD10 to be after the primary type column. This would make it the same as CCMDB.  
* 2019 March 01 - move ''priority number'' column for ICD10 to be after the primary type column. This would make it the same as CCMDB.  
* add TDI column to query L_CCI_Combined
* add TDI column to query L_CCI_Combined
Line 17: Line 17:


===Postal code table and PCH Pre Acte Living situation===
===Postal code table and PCH Pre Acte Living situation===
{{DT | Postal Code vs Pre-acute }}
{{DT | dev_CFE
Postal Code vs Pre-acute }}
The listed  postal codes are correlated to the items ‘PCH’  and ‘Chronic Health facility’  of the Pre-Acute Living Situation.  Since the data collectors are collecting the postal code from the patient’s address, will it be possible to automatically fill up the  Pre-Acute Living Situation as PCH or Chronic Health facility if the PCH postal codes are entered  or  ‘other ways’  to link the two fields and make them  consistent.    Info about PCH is now getting  more attention/request. Tina, Will this be hard to do?  Any suggestions?
The listed  postal codes are correlated to the items ‘PCH’  and ‘Chronic Health facility’  of the Pre-Acute Living Situation.  Since the data collectors are collecting the postal code from the patient’s address, will it be possible to automatically fill up the  Pre-Acute Living Situation as PCH or Chronic Health facility if the PCH postal codes are entered  or  ‘other ways’  to link the two fields and make them  consistent.    Info about PCH is now getting  more attention/request. Tina, Will this be hard to do?  Any suggestions?
*I have changed my mind to add the PCH postal code to the Postal_Code_Master due to the possible effect on its size  (when adding a new column containing text where most of the records will only be blanks).  It is better to have it in separate table since this pertains to Winnipeg area only.  I have added the exact address of these PCH facilities  -  link to table in email sent on Jan 12.18 at 1224 hrs from [[p:Julie Mojica]]
*I have changed my mind to add the PCH postal code to the Postal_Code_Master due to the possible effect on its size  (when adding a new column containing text where most of the records will only be blanks).  It is better to have it in separate table since this pertains to Winnipeg area only.  I have added the exact address of these PCH facilities  -  link to table in email sent on Jan 12.18 at 1224 hrs from [[p:Julie Mojica]]


=== Move Linked Pairs ===
=== Move Linked Pairs ===
{{DT | Linked pairs, better storage }}
{{DT | dev_CFE
Linked pairs, better storage }}
As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses.  
As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses.  
* need to change the query and process from one that re-does all, every time, to one that only updates new.  
* need to change the query and process from one that re-does all, every time, to one that only updates new.  

Revision as of 14:31, 2019 July 4

see the Development Documentation Category for other development logs

This article contains requested changes for Centralized data front end.accdb. See Centralized data front end.accdb Change Log for it's change log.


dev_CFE

  • clean up the form (whatever that meant)
  • add button for link suspect queries to patient list
  • update Correcting suspect links
  • SMW


  • Cargo


  • Categories

New change request

dev_CFE

  • 2019 March 01 - move priority number column for ICD10 to be after the primary type column. This would make it the same as CCMDB.
  • add TDI column to query L_CCI_Combined
  • fix dc treatment box that isn't showing up in form Ttenbergen 15:52, 2018 April 11 (CDT)
  • fix table reconnector to not look for L_Labs_DSM any longer, since it's now elsewhere. Ttenbergen 15:52, 2018 April 11 (CDT)
  • CCI and ICD10 make button for Pagasa
  • SMW


  • Cargo


  • Categories

Postal code table and PCH Pre Acte Living situation

dev_CFE Postal Code vs Pre-acute

  • SMW


  • Cargo


  • Categories

The listed postal codes are correlated to the items ‘PCH’ and ‘Chronic Health facility’ of the Pre-Acute Living Situation. Since the data collectors are collecting the postal code from the patient’s address, will it be possible to automatically fill up the Pre-Acute Living Situation as PCH or Chronic Health facility if the PCH postal codes are entered or ‘other ways’ to link the two fields and make them consistent. Info about PCH is now getting more attention/request. Tina, Will this be hard to do? Any suggestions?

  • I have changed my mind to add the PCH postal code to the Postal_Code_Master due to the possible effect on its size (when adding a new column containing text where most of the records will only be blanks). It is better to have it in separate table since this pertains to Winnipeg area only. I have added the exact address of these PCH facilities - link to table in email sent on Jan 12.18 at 1224 hrs from p:Julie Mojica

Move Linked Pairs

dev_CFE Linked pairs, better storage

  • SMW


  • Cargo


  • Categories

As discussed with Julie to prevent her having to rerun it and to insure that what Pagasa queries against is same as what Julie uses.

  • need to change the query and process from one that re-does all, every time, to one that only updates new.
    • How will that work for individual older records that were edited?

Related articles

Related articles: