Search Results

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...

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...

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...

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, ...

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...

Open Clinical History uses a local SNOMED CT RF2 Snapshot release to provide clinical terminology, terminology search, anatomical hierarchy information and clinical concept-to-body-layer mappings. The SNOMED distribution is large and the initial import can tak...

API documentation: Updated for the public patient UUID response behaviour verified on 27 August 2026. Machine integration: The API finds or creates the patient synchronously and returns the stable public patient_uuid in the initial response. Clinical extracti...

Open Clinical History provides a browser-based workflow for manually importing an existing patient history from a plain-text document. The manual import page is: /history_import.php It is designed for importing raw, unstructured clinical history without requir...

The SNOMED Re-index / Learning Queue manages clinical terms that Open Clinical History could not safely resolve during patient-history import. The page is: /process_queue.php During patient import, Open Clinical History deliberately avoids guessing when it can...

The Gemini Usage dashboard provides operational visibility into the Large Language Model usage generated by Open Clinical History. The page is: /gemini_usage.php It displays: current LLM configuration state today's request budget today's token budget historica...

This guide describes how to deploy a new Open Clinical History installation. Open Clinical History includes a temporary first-run setup assistant: setup_delete_after_setup.php The setup assistant is deliberately self-contained so that it can run before config...

Open Clinical History presents a patient's medical history as a longitudinal timeline combined with an anatomical visualisation. The aim is to make a large clinical history easier to scan while preserving access to: the chronological sequence the original sour...

Open Clinical History uses SNOMED CT as its primary clinical terminology foundation. SNOMED CT provides a standard way to represent clinical concepts such as: disorders findings symptoms procedures anatomical structures clinical situations observable entities ...