Advanced Search
Search Results
29 total results found
Open Clinical History
Public-facing Open Clinical History documentation.
About Open Clinical History
Overview, purpose, scope, safety, limitations and roadmap for Open Clinical History.
User Guide
Practical guidance for using Open Clinical History.
Installation & Administration
Installation, configuration, administration and troubleshooting.
Installation Guide
Installation and deployment guide for Open Clinical History.
Administrator Guide
Administration and maintenance of Open Clinical History.
Troubleshooting
Diagnosis and resolution of common Open Clinical History problems.
Technical Documentation
Architecture, development and database documentation.
System Architecture
Technical architecture and processing design.
Developer Guide
Developer documentation for extending and maintaining the system.
Database Reference
Reference documentation for the Open Clinical History database.
Standards & Clinical Model
Clinical terminology, data modelling and interoperability.
SNOMED CT
How Open Clinical History uses SNOMED CT and SNOMED CT-AU.
Clinical Safety & Limitations
Open Clinical History is a working proof of concept designed to organise fragmented clinical information into a structured longitudinal history. It is not intended to replace the original medical record, clinical judgement, diagnosis, treatment decisions or di...
How Open Clinical History Works
Open Clinical History converts fragmented clinical documents into a structured longitudinal history through a staged ingestion, extraction, classification and presentation process. The system is designed so that the original source material remains important t...
What is Open Clinical History?
Open Clinical History is a working proof-of-concept platform for turning fragmented, unstructured health information into a coherent longitudinal clinical history. Health information is often spread across scanned letters, discharge summaries, pathology report...
Why Open Clinical History Exists
Open Clinical History began with a simple problem: a patient's medical history may exist, but that does not mean the person treating them can easily see or understand it. A complex health history can span many years, hospitals, specialists, imaging providers, ...
Configuration
admin_config.php provides the central runtime configuration interface for Open Clinical History. Application settings are stored in the app_config database table and accessed through lib/app_config.php. These settings are separate from deployment-level confi...