Difference between revisions of "AquilaCRS"

From EHS Help
Jump to: navigation, search
m
Line 6: Line 6:
 
[[Aquila Software Status]]
 
[[Aquila Software Status]]
  
==Core Help Topics==
+
=== Getting Started ===
 
+
 
*[[Login to AquilaCRS]]
 
*[[Login to AquilaCRS]]
 
**[[Finding the version number of your software]]
 
**[[Finding the version number of your software]]
Line 24: Line 23:
 
**[[Validation Error List]]
 
**[[Validation Error List]]
  
== IBID Records ==
+
=== IBID Records ===
 
+
 
*[[IBID -- Burn Injury Data]]
 
*[[IBID -- Burn Injury Data]]
 
**[[IBID Contact Details]]
 
**[[IBID Contact Details]]
Line 49: Line 47:
 
**[[Care Journal]]
 
**[[Care Journal]]
  
== Dependency Records ==
+
=== Dependency Records ===
 
+
 
*[[Dependency Records - IBID]]
 
*[[Dependency Records - IBID]]
 
**[[Dependency Header]]
 
**[[Dependency Header]]
***[[Linking Depenendency with IBID]]
+
***[[Linking Dependency with IBID]]
 
**[[Daily Dependency]]
 
**[[Daily Dependency]]
 
**[[Intensive Care]]
 
**[[Intensive Care]]
Line 63: Line 60:
 
**[[Dependency Outpatient Activity]]
 
**[[Dependency Outpatient Activity]]
  
 +
=== Advanced Topics ===
  
==Technical Topics==
+
=== System Options ===
 +
* [[User Options]]
  
 +
=== Technical Topics ===
 
*[[Aquila Component Overview]]
 
*[[Aquila Component Overview]]
 
*[[IT & Governance Issues]]
 
*[[IT & Governance Issues]]

Revision as of 10:03, 8 March 2013

AquilaCRS icon.png

This is the AquilaCRS product home page


Software Status

Aquila Software Status

Getting Started

IBID Records

Dependency Records

Advanced Topics

System Options

Technical Topics


Overview

Aquila Care Records System is an innovative care records system currently incorporating the International Burn Injury Database (iBID). For information on how to obtain AquilaCRS please contact us.

For the latest information on product development, please see the AquilaCRS Whats New page.

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.