Handbook
Track updates
SA HB 138-2013
[Current]E-health architecture principles
Describes key e-health architecture principles that can be used to guide the development of interoperable e-health systems; a companion document to SA HB 137-2013, E-health Interoperability Framework, but can also be used as a standalone document.
Published: 17/06/2013
Pages: 15
Table of contents
Cited references
Content history
Table of contents
Header
About this publication
Preface
1 Scope and general
1.1 Scope
1.2 Intended audience
1.3 Referenced documents
1.4 Abbreviations
2 E-health architecture principles
2.1 Context
2.2 EHAP 1: Improve the safety and quality of healthcare
2.2.1 Statement
2.2.2 Rationale
2.2.3 Implications
2.3 EHAP 2: Improve the efficiency of healthcare services
2.3.1 Statement
2.3.2 Rationale
2.3.3 Implications
2.4 EHAP 3: Ensure e-health solutions support interoperability
2.4.1 Statement
2.4.2 Rationale
2.4.3 Implications
2.5 EHAP 4: Ensure solutions are fit for purpose
2.5.1 Statement
2.5.2 Rationale
2.5.3 Implications
2.6 EHAP 5: Support service-oriented approaches
2.6.1 Statement
2.6.2 Rationale
2.6.3 Implications
2.7 EHAP 6: Comply with legislative and policy requirements
2.7.1 Statement
2.7.2 Rationale
2.7.3 Implications
2.8 EHAP 7: Re-use e-health components
2.8.1 Statement
2.8.2 Rationale
2.8.3 Implications
2.9 EHAP 8: Adopt pragmatic approaches
2.9.1 Statement
2.9.2 Rationale
2.9.3 Implications
2.10 EHAP 9: Engage with all relevant stakeholders
2.10.1 Statement
2.10.2 Rationale
2.10.3 Implications
2.11 EHAP 10: Maintain security
2.11.1 Statement
2.11.2 Rationale
2.11.3 Implications
2.12 EHAP 11: Assess whole-of-life costs
2.12.1 Statement
2.12.2 Rationale
2.12.3 Implications
2.13 EHAP 12: Use common terminologies and data definitions
2.13.1 Statement
2.13.2 Rationale
2.13.3 Implications
2.14 EHAP 13: Manage information quality
2.14.1 Statement
2.14.2 Rationale
2.14.3 Implications
2.15 EHAP 14: Manage information assets
2.15.1 Statement
2.15.2 Rationale
2.15.3 Implications
2.16 EHAP 15: Ensure information consistency in distributed environments
2.16.1 Statement
2.16.2 Rationale
2.16.3 Implications
2.17 EHAP 16: Express policy compliance as business rules
2.17.1 Statement
2.17.2 Rationale
2.17.3 Implications
2.18 EHAP 17: Support loose coupling
2.18.1 Statement
2.18.2 Rationale
2.18.3 Implications
2.19 EHAP 18: Express policy in technology-independent terms
2.19.1 Statement
2.19.2 Rationale
2.19.3 Implications
2.20 EHAP 19: Use standards-based approaches
2.20.1 Statement
2.20.2 Rationale
2.20.3 Implications
2.21 EHAP 20: Ensure supportability, sustainability and continuity
2.21.1 Statement
2.21.2 Rationale
2.21.3 Implications
2.22 EHAP 21: Manage change
2.22.1 Statement
2.22.2 Rationale
2.22.3 Implications
2.23 EHAP 22: Manage technical diversity
2.23.1 Statement
2.23.2 Rationale
2.23.3 Implications
Appendix A
Cited references in this standard
Content history
One-time Purchase
Access via web browser on any device
One-time purchase
Single publication
Offline access via PDF^
$83.52 AUD
Inclusive of GSTFormat *
Web Reader
Licenses *
1 user
Total$83.52 AUD
IMPORTANT