Centralized data front end.accdb Change Request
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.
|
|
New change request
|
|
|
Postal code table and PCH Pre Acte Living situation
|
|
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?
- 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
|
|
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.
- 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?