Difference between revisions of "System Requirements"
From Hiasobi - FHIR
| Line 2: | Line 2: | ||
These specifications are for all of the following active versions of Oridashi-Hiasobi adapter | These specifications are for all of the following active versions of Oridashi-Hiasobi adapter | ||
| − | |||
* DSTU2 2.3.65, 2.3.66 | * DSTU2 2.3.65, 2.3.66 | ||
* STU3 3.0.3.10 | * STU3 3.0.3.10 | ||
| − | Practice Software Versions | + | Supported Practice Software Versions |
* Medical Director: 3.16 onward | * Medical Director: 3.16 onward | ||
* Best Practice: 1.8.4.642 onward | * Best Practice: 1.8.4.642 onward | ||
Revision as of 08:48, 20 March 2018
These are the nominal system requirements for the core Oridashi-Hiasobi component operation.
These specifications are for all of the following active versions of Oridashi-Hiasobi adapter
- DSTU2 2.3.65, 2.3.66
- STU3 3.0.3.10
Supported Practice Software Versions
- Medical Director: 3.16 onward
- Best Practice: 1.8.4.642 onward
| Back-End/Server | Desktop/Workstation | |
|---|---|---|
| CPU | Intel Quad Core or better (equivalent) | Intel Core 2 Duo or better (equivalent) |
| RAM | Hardware: 4GB or better Usage: Typical < 50Mb | Hardware: 2GB or Better Typical < 50Mb |
| Hard Disk | Application: < 20Mb Data: Typical < 250 Mb* (Scheduling, Synchronising) | Application: < 20Mb Data: N/A |
| OS | Windows 7 SP 3, 8.1,10 Windows Server 2003, 2008, 2012, 2016 | Windows 7 SP 3, 8.1,10 Windows Server 2003, 2008, 2012, 2016 |
* The Back-End/Server installation may include external data synchronisation tracking for schedule and health record data which requires local storage of data. Data usage will vary based on the number of patient records being synchronised. No health record information is stored in this data, only change tracking data used in synchronisation is recorded.
