|
|
| (53 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| The '''CCMDB.mdb''' stands for '''Critical Care Medicine Database'''. This is an '''Access''' database that the [[PDA]]s synchronize into. It screens the data for internal consistency and ranges, and then exports it in a format that can be imported into [[TMSX]] or [[MedTMS]]. | | The '''CCMDB.accdb''' is a Microsoft Access database, with the name being the acronym for '''Critical Care Medicine Database'''. CCMDB.accdb screens the data for internal consistency and ranges, and then exports it for further processing during [[Sending Patients | sending]]. |
|
| |
|
| Each [[PDA]] has a combo of two [[:Category: Access databases | Access databases]] associated to it:
| | == Updating of CCMDB.accdb Program == |
| ::'''ccmdb.mdb''' file which is identical for all until synced into
| | Rolling out new versions of [[CCMDB.accdb]] is done by Tina or Lisa using [[:Category: Batch Files | a batch file]] called [[updt_all.bat]]. See the update [[Log]] for information about changes, and see [[Requested CCMDB changes for the next version | Requested Changes]] for changes planned for the future. |
| ::[[settings.mdb]] which contains location specific information such as the path to the [[Regional Server]], and the hospital and ward names.
| |
| * Any data in the ccmdb.mdb is considered transient, the file can be replaced with an empty new version at any time
| |
| * Rolling out new versions of ccmdb.mdb is done by Tina or Trish using [[:Category: Batch Files | a batch file]] called [[updt_all.bat]]. A ccmdb.mdb file that is currently open WILL NOT be overwritten.
| |
|
| |
|
| *Additionally, this program folder contains a \Master directory where the master version of the ccmdb.mdb is stored. Any changes required to the program can be made on the master file, and then rolled out by copying the master\[[updt_all.bat]] [[:Category: Batch Files | batch file]] to a local drive (batch code can’t cope with running from an unnamed drive) and running it.
| | == Data in the CCMDB.accdb == |
| | | Data in CCMDB.accdb is stored in |
| == Changes in the laptop version of CCMDB.mdb == | | * c:\ccmdb_data\CCMDB data.mdb |
| We are getting ready to have everyone use the new version of the CCMDB that will work for the laptops. On the front, the changes are relatively minor. Some of the ones that have caused confusion are explained below. If you find any problems with this version, please see and participate in [[Editing Laptop Testing (section)]].
| | * see: [[CCMDB data.mdb]] |
| | | See also [[Laptop Setup]] |
| === Form Sizes ===
| |
| The forms are all larger now. This might mean they don't fit onto your screen. If that is the case, [[change your screen resolution]].
| |
|
| |
|
| | == Form Sizes == |
| | The form sizes on the laptops are continuously being tweaked to accommodate, especially, any of the laptops we use. |
| The form size was increased to accommodate the screens on the laptops which are small but have a high native resolution. | | The form size was increased to accommodate the screens on the laptops which are small but have a high native resolution. |
|
| |
|
| ===X out of Program=== | | == Password == |
| *We find that if you are in the program and you have enlarged the view box, and then you "X" out, it closes out the program, not just take you back to the start up page of "edit patients" etc. But if you are in the view box and you are in smaller screen and "X" out, it doesn't close the program it goes to the start up screen "edit patients". Which is what we want.Are we doing something wrong? [[User:WGobert|gogogirl]] 14:33, 3 June 2009 (CDT)
| | Located: \\AD.WRHA.MB.CA\WRHA\HSC\SHARED\WRHA\WRHA_CCMED\Passwords_mainoffice\Passwords_MainOffice_use.xlsx |
| ** There should be '''two''' Xs at the top right corner. The top one closes the entire application, the bottom one only that screen. If you use the door button instead in the patient view form then there should be no confusion. I don't think this has changed between the regular app and this one, has it? [[User:Ttenbergen|Ttenbergen]] 13:25, 9 June 2009 (CDT)
| |
| | |
| === Yellows that don't go away when the value is fixed ===
| |
| Sometimes the fields for values that appear to be correct are still highlighted in yellow.
| |
| | |
| If this happens, try putting a checkmark into the complete box corresponding to that tab. This will re-run the checks.
| |
| | |
| Also, if the error box at the bottom seems to have out-of-date info in it, click the "Reset Err" button.
| |
| | |
| This problem happens because some changes in data will affect multiple boxes (e.g. survive and discharge-to) and running all checks after every change would slow down the program further.
| |
| | |
| ===Lab, Pharm checks===
| |
| If the settings are set to "ICU" then Lab and Pharm used to have a checkbox in the ccmdb.mdb that had to be checked if there were no labs or pharmacy. This was changed so that Lab and Pharm that are legitimately empty need to have "no drugs" or "no labs" entered (much like "no comorbids") before they can be checked off.
| |
| | |
| If the settings are set to "medicine" you will not need to check off the "lab" or "pharm" checkboxes in order to set the "final check" box to send the patient.
| |
| | |
| === TISS box gone ===
| |
| There is no longer a TISS box at the top of the patient viewer. People told me there were not using it and that it was just extra work.
| |
| | |
| === Object With Variable Error ===
| |
| Occasionally the following error comes up
| |
| Microsoft Office Access
| |
| Object variable of With block variable not set - Patient <number>
| |
| OK
| |
| This error occurs when the program has previously run into a different problem and is still "confused". If this happens, go back to the main screen (i.e. exit out of the patient viewer) and click the "reset" button.
| |
| | |
| == Program Development and Changes ==
| |
| See the [[:Category:Development Documentation | Development Documentation Category]]
| |
| | |
| | |
| == Before Synching ==
| |
| Some of you seem to do extensive checks before synching and letting CCMDB.mdb do checks for you. I am curious - why? I thought we made the ccmdb to automate and facilitate these checks. Any thoughts? [[User:Ttenbergen|Ttenbergen]] 22:25, 4 May 2009 (CDT) {{discussion}}
| |
| | |
| == Synching ==
| |
| See [[Syncing the PDA]]
| |
| | |
| == Sending Patients ==
| |
| See [[Sending Patients]]
| |
| | |
| ==Deleting data on PDA after sending from access==
| |
| What is the process everyone should follow '''before''' deleting sent patients from the PDA? Some people check with Pagasa, some check on the regional server that data has actually been posted. Is it a common occurrence for data not to have been posted? [[User:Ttenbergen|Ttenbergen]] 22:32, 4 May 2009 (CDT) {{discussion}}
| |
| *go to regional server Output folder.
| |
| Check Vic folder
| |
| go to recent batch #.CSV
| |
| check files, scroll to ensure all files present.
| |
| say no to save if you change anything.
| |
| Delete completed profiles off PDA.
| |
| [[User:WGobert|gogogirl]] 16:19, 18 March 2009 (CDT)
| |
|
| |
|
| *After closing access I click on output, then your unit open up the info and check. eg the number of completes, admits, comorbs, etc. I then delete my completes on my PDA--[[User:PStein|PStein]] 08:36, 18 March 2009 (CDT)
| | The password for the [[CCMDB.accdb]] is known as "the tasty password". If you don't know it, and need to know it, talk to [[p:Trish Ostryzniuk |Trish]] or any data collector. All data collectors need to be thoughtful as to who they give this password out to. |
|
| |
|
| *After sending you check your output by opening twister and clicking on output, then find your site and click on the batch number csv you just sent. Your sent files should appear, scroll across and make sure the areas that have to have information in them ie. admit date and time etc. are filled in. If everything looks OK close out and you can deiete your completed files. Lois -- [[User:LBilesky|LBilesky]] 14:47, 17 March 2009 (CDT)
| | The [[CCMDB.accdb]] is using the same password everywhere. This used to be required to make sure the PDAs work. It is now required because collectors cover at different locations and using different passwords would get people to write them down. Since laptops are encrypted, and accessed using the user's network password, this should not be a problem. |
|
| |
|
| | == Related articles == |
| | {{Related Articles}} |
|
| |
|
| [[Category:IT Instructions]] | | [[Category: IT Instructions]] |
| [[Category: Data Repository]] | | [[Category: Data Repository]] |
| [[Category: Questions_IT]] | | [[Category: CCMDB.accdb | *]] |
| | [[Category: Password]] |
The CCMDB.accdb is a Microsoft Access database, with the name being the acronym for Critical Care Medicine Database. CCMDB.accdb screens the data for internal consistency and ranges, and then exports it for further processing during sending.
Updating of CCMDB.accdb Program
Rolling out new versions of CCMDB.accdb is done by Tina or Lisa using a batch file called updt_all.bat. See the update Log for information about changes, and see Requested Changes for changes planned for the future.
Data in the CCMDB.accdb
Data in CCMDB.accdb is stored in
See also Laptop Setup
Form Sizes
The form sizes on the laptops are continuously being tweaked to accommodate, especially, any of the laptops we use.
The form size was increased to accommodate the screens on the laptops which are small but have a high native resolution.
Password
Located: \\AD.WRHA.MB.CA\WRHA\HSC\SHARED\WRHA\WRHA_CCMED\Passwords_mainoffice\Passwords_MainOffice_use.xlsx
The password for the CCMDB.accdb is known as "the tasty password". If you don't know it, and need to know it, talk to Trish or any data collector. All data collectors need to be thoughtful as to who they give this password out to.
The CCMDB.accdb is using the same password everywhere. This used to be required to make sure the PDAs work. It is now required because collectors cover at different locations and using different passwords would get people to write them down. Since laptops are encrypted, and accessed using the user's network password, this should not be a problem.
Related articles