Centralized data front end.accdb Change Request: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m (u) |
Ttenbergen (talk | contribs) m (u) |
||
| Line 10: | Line 10: | ||
Can the early D-ID and Late D_ID columns be wider? | Can the early D-ID and Late D_ID columns be wider? | ||
* Links suspect Med from med (and med to med as well) - Not everyone from *W needs to come from a ward where we collect; need acceptable delay and var1/2 etc | |||
* The copy and paste in CFE is broken | * The copy and paste in CFE is broken | ||
Revision as of 15:34, 2014 November 27
see the Development Documentation Category for other development logs
This article contains requested changes for Centralized data front end.mdb. See Centralized data front end.mdb Change Log for it's change log.
Other change requests
- put back the sort buttons for the patient list
Linking pairs – OPEN suspect links Can the early D-ID and Late D_ID columns be wider?
- Links suspect Med from med (and med to med as well) - Not everyone from *W needs to come from a ward where we collect; need acceptable delay and var1/2 etc
- The copy and paste in CFE is broken
- fix query link_suspect_medicine_to_med_no_partner - has false positives
- Highest pseudo is used to check “bad PHIN” for incompletes - better solution?
- this should be done in CCMDB instead, see Requested_CCMDB_changes_for_the_next_version#Important_change_request
- "Tina will work to implement this new “HASH” system."
- collapse autopsy...
- make query to set time part of tmp dateVar to nothing
- why are there blank BirthMYs?
- what happens to BirthMY when Pagasa updates Birth?
Preventing inappropriate edits by data processor
other spot that might contain requirements...
TMSX MedTMS to Centralized go-live