|
|
| (55 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 |
| | * c:\ccmdb_data\CCMDB data.mdb |
| | * see: [[CCMDB data.mdb]] |
| | 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. |
|
| |
|
| == Program Development and Changes == | | == Password == |
| See the [[:Category:Development Documentation | Development Documentation Category]]
| | 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 [[p:Trish Ostryzniuk |Trish]] or any data collector. All data collectors need to be thoughtful as to who they give this password out to. |
|
| |
|
| == Before Synching ==
| | 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. |
| 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 == | | == Related articles == |
| See [[Syncing the PDA]]
| | {{Related Articles}} |
|
| |
|
| == Sending Patients ==
| | [[Category: IT Instructions]] |
| 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)
| |
| | |
| *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)
| |
| | |
| == Discussion ==
| |
| * data collectors must participate and fill this information in.[[User:TOstryzniuk|TOstryzniuk]] 22:31, 29 October 2008 (CDT)
| |
| | |
| **'''ATTENTION''' to all Data collectors: please contribute to the above information in regards to the steps using ACCESS. This forum is a collaborative and was requested by data collectors thus we require your participation on the WIKI here. We need to have documentation of what steps that collector follow.[[User:TOstryzniuk|TOstryzniuk]] 23:31, 26 February 2009 (CST)
| |
| **Confused, why gather this information when we are expecting lap-tops soon and the process will change?--[[User:JHutton|JHutton]] 09:53, 16 March 2009 (CDT)
| |
| ***Thank you for your contribution. All sites being able to use a lap-top is some time away. At this time we will only use laptops at one site for beta testing. Never-the-less, the lap top will employ the use of '''MS ACCESS''' for collection and entry, therefore the above steps are will still apply. --[[User:TOstryzniuk|TOstryzniuk]] 13:26, 16 March 2009 (CDT)
| |
| **** Articles describing most of these steps already existed. Please make sure you do a search before starting an article so you don't duplicate work that has already been done. That said, I am glad to see so many of you providing input! [[User:Ttenbergen|Ttenbergen]] 22:32, 4 May 2009 (CDT)
| |
| | |
| [[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