These are common questions we have been asked about palCentre. If you have additional questions not answered here, please contact Alanna Connolly on (02) 4221 5640 or Sam Burns on (02) 4298 1141 or via email at contact us at at pcoc@uow.edu.au or pacop-data@uow.edu.au.
| Expand | ||
|---|---|---|
| ||
palCentre was designed as a way for services/homes to collect and use the PCOC and PACOP information. It also allows services to submit data to PCOC and PACOP for analysis and reporting, and promotes consistent terminology, processes and protocols among services/homes participating in PCOC and PACOP. palCentre consists of two components: a client application (the ‘front end’) and a database. The database is where the data is stored and managed, while the client application displays the information on a user-friendly interface to allow entry, editing and use of the information. This structure allows the database to be stored in a central location for one or many computers to communicate with it.Both the database and client application have to be installed. There are 2 database options:
|
| Expand | ||
|---|---|---|
| ||
Installation of palCentre is intended to be simple and safe. The built in database configuration wizard can create and configure the SQL database and logins for you with a bare minimum of customisable data entry. The wizard allows you to specify your own SQL database name, SQL logins and passwords and an encryption key specific to your service/home. This ensures that the configuration of the database at your site will be able to comply with your own naming standards and password security policies. The configuration wizard takes less than 10 minutes run. Once the database configuration wizard has been run once, the client configuration wizard can be run to connect a client machine to the palCentre database. Alternatively, the configuration wizards create a configuration file which can be deployed to client machines, eliminating the need for running the client configuration wizard. |
...
| Expand | ||
|---|---|---|
| ||
PCOC or PACOP will send your service a preconfigured pre-configured SQL Compact database. This file (typically called pcoc.sdf) needs to be stored on a network drive that is accessible by all client computers. The client configuration wizard can be run to connect a client machine to the palCentre database. Alternatively, the configuration wizards create a configuration file which can be deployed to client machines, eliminating the need for running the client configuration wizard. |
...
| Expand | ||
|---|---|---|
| ||
palCentre uses the .NET Extended Framework v4.6. Past testing indicates that most Windows XP and 7 machines do not have this framework This is pre-installed .For reporting, epiCentre uses the Crystal Reports for Visual Studio 2010 runtime. Crystal Reports requires that the Visual C++ 2005 SP1 32-bit Runtime and the ATL Security Update for Visual C++ 2005 have been installedon Windows 10, but will need to be installed manually on earlier versions. If the database option chosen is SQL compact then Microsoft SQL Server Compact 4.0 is also installed as a prerequisite. If preferred, prerequisites should can be able to be deployed automatically as there are no configuration steps required by them. Some of the prerequisites may already be installed on the client machine and if so, the installer will inform you of this and you can move on to the next step. Depending on which prerequisites are required, and the speed of the client machine this procedure should take between 5 and 15 minutes per client machine. Note that epiCentre palCentre is a 32 bit application, as are all pre-requisites. This decision was made to allow support for older Windows XP machines. epiCentre palCentre and its dependencies have been specifically tested on Windows XP (32 and 64 bit), Windows 7 (32 and 64 bit), Windows 8 (64 bit), and Windows 10 (64 bit). |
...
| Expand | ||
|---|---|---|
| ||
|
...