Difference between revisions of "AquilaCRS"
From EHS Help
m |
(Removed all How To Links) |
||
| Line 6: | Line 6: | ||
For the latest information on product development, please see the [[AquilaCRS What's New]] page. | For the latest information on product development, please see the [[AquilaCRS What's New]] page. | ||
| + | ==Help System== | ||
| + | [http://extranet.mdsas.nhs.uk/mdsas/NBID/iBID%20Help/Welcome%20to%20iBID.aspx IBID System Documentation] | ||
| + | |||
| + | ==Administration== | ||
| + | *[[Installing AquilaCRS]] | ||
| + | *[[AquilaCRS Settings]] | ||
| + | *[[Aquila Server Settings]] | ||
| + | ** [[Database connection string]] | ||
| + | |||
| + | ==Technology Overview== | ||
| + | [[AquilaCRS]] is built on the principles of [[multi-tier]] architecture and as such is fast, resilient and scalable. [[AquilaCRS]] can be implemented on a WAN (N3 or Internet), LAN (i.e. trust or practice-wide) or even as a traditional two-tier or standalone solution. | ||
| + | |||
| + | <!-- | ||
==How To== | ==How To== | ||
*[[Login to AquilaCRS]] | *[[Login to AquilaCRS]] | ||
| Line 21: | Line 34: | ||
**[[Care Journal]] | **[[Care Journal]] | ||
*[[Enter Burn Dependency Data]] | *[[Enter Burn Dependency Data]] | ||
| − | + | --> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Category:User Help]] | [[Category:User Help]] | ||
[[Category:AquilaCRS]] | [[Category:AquilaCRS]] | ||
[[Category:IBID]] | [[Category:IBID]] | ||
Revision as of 11:21, 20 March 2012
This is the AquilaCRS product home page
Aquila Care Records System is an innovative care records system currently incorporating the International Burn Injury Database (iBID). To obtain AquilaCRS please contact us.
For the latest information on product development, please see the AquilaCRS What's New page.
Help System
Administration
Technology Overview
AquilaCRS is built on the principles of multi-tier architecture and as such is fast, resilient and scalable. AquilaCRS can be implemented on a WAN (N3 or Internet), LAN (i.e. trust or practice-wide) or even as a traditional two-tier or standalone solution.
